But there's nowhere in entire JSON for any alt-text. The plan is to add alt-text as a 'name' in there.
In-line images do prove a point for the OP, though. A Lemmy comment with one will be sent out as <img src="<a href="https://lemmy.world/pictrs/image/9d483052-29b6-4d34-baaf-3ee092be9718.png" rel="nofollow ugc" target="_blank">https://lemmy.world/pictrs/image/9d483052-29b6-4d34-baaf-3ee092be9718.png</a>" alt="bear vs man in woods meme" /> in the 'content' field, but Mastodon expects all images to be attachments, so it just completely ignores it. (compare https://lemmy.zip/comment/10342640 with https://mastodon.social/@Honytawk@lemmy.zip/112438348076482957).
That's arguably the expected behaviour - for a discussion, 'link' effectively takes you to the comments, for an article (or a link to a image), it takes you there instead.
You could use 'guid' instead - that always links to the post on Lemmy, and it usually contains a useful thing on other sites' RSS feeds.
There was a great windows app called 'dvdshrink' that let you rip commercial DVDs onto blank DVDs (shrinking them if necessary). It got taken down with a Cease & Desist, but the MPAA or whoever didn't worry about who took the domain. For a long time, the site was just filled with ads instead - now it's a bit more sophisticated: no real link to download the software, but lots of genuine-seeming donation requests.
The fake site is at the first search result for that software (edit: it's probably best not to link directly to it)
That sounds like a tricky combination. Wherever you go, they'll be a good chunk of users who are unaware of / indifferent to how well the app they're using interacts with other Fediverse platforms. Mastodon has the userbase, and - as you say - is the place where the serious discussion of accessibility takes place.
As for Lemmy - it doesn't yet support alt-text, but when it does, I believe that the plan is to follow Mastodon's format (i.e. a 'name' field in the 'attachment' array)
Oh, right. Sorry. I've gone back and checked the post I was thinking of when I made that comment, and - yeah - it turns out I was misremembering / didn't properly investigate the first time.
Yeah - I think anything the UI is doing, it's getting the info from the API, so the poster would've had to use the 'cross-post' feature. There are some apps (e.g. Voyager) that try to wrangle cross-posts by title or URL, but title-matching can give false postives, and URL-matching usually assumes that one link hasn't picked up some cruft, and it can't do much for uploaded images if the poster didn't cross-post (because it'll be 2 different files with different URLs)
No idea whether you'll get this or not. You should do, even it's only as an Inbox message (sent if there's no subscribers to this community on lemm.ee, because it'll reject this if that's the case).
My first reply made it to lemmy.ml (see https://lemmy.ml/post/15165488), so that suggests the federation issue was on Lemmy's end, not PieFed's. (I'll see if this reply makes it to .ml, to confirm).
Edit: actually, just checked lemme.ee, and this reply is there, so 'Ner', and indeed, 'Ner'.
Oh. If you're viewing this post from a Lemmy instance, there's a comment tree missing because Lemmy didn't sign its request for the Mastodon user's details. Hopefully, this'll come in 0.19.4