Ryan Barrett

Oh man. I switched the image URLs from the Jetpack CDN to my site directly (snarfed.org), and that fixed it. Ugh, so that CDN is blocking Mastodon, or it's otherwise...

Also, the two other bad example posts were probably unrelated, I suspect Mastodon expected their `attachment`s were images and choked on them?

Confirmed. I removed the attachment from one of them, and the broken image went away. https://indieweb.social/@[email protected]/109934332056357887

Oh and re https://github.com/snarfed/bridgy-fed/issues/439#issuecomment-1469040563, looks like indieweb.social is hosted on https://masto.host/, not Reclaim.

Looks like we started adding `attachment` for Mastodon, initially discovered in https://github.com/snarfed/bridgy-fed/issues/33#issuecomment-440965618. Evidently they still use it: https://github.com/mastodon/mastodon/blob/65669d3c5719e72000bf26849d0ee1eaec1f9d1b/app/lib/activitypub/activity/create.rb#L255-L282

One hacky fix here would be to auto detect WP Jetpack CDN URLs and rewrite them to the original URL. ~Unfortunate to need to do that only because Reclaim is...

https://mastodon.art/ has the same problem, and they're also on masto.host.

Hrm, so does https://mastodon.social/ , and they're not on masto.host. Haven't yet found anything relevant in https://github.com/mastodon/mastodon/issues

Found an interesting workaround here: leave the `img` pointing to the CDN image, move the `u-photo` to an `` wrapping it that points to the local (ie not CDN) image...

Data points to help determine priority: - https://nostr.io/#profile-chart says there are 365k users (profiles) right now - https://stats.nostr.band/ says there are 1.13M users (profiles) right now, 13k ["high" (ie non-zero)...