@thisismissem@hachyderm.io re: “issue might be with what you're federating out maybe”, possibly except that regardless of what I’m federating out, the point in my reply to @flaki@flaki.social is that #Mastodon is still getting it half-right, which is a bug in Mastodon regardless of what I’m federating out.
Either Mastodon should be treating my hashtags precisely as hashtags, (re)linking them to the local tagSpace *and* ignoring them for link previews, or it should be treating them “purely” as links, and not changing their default/published hyperlink and considering them for a link-preview.
Re: “help to have the activities json representation” — my understanding is that should be automatically discoverable from my post permalink, so all that should be needed for a bug report is my post permalink. Perhaps @snarfed.org can clarify since I’m using https://fed.brid.gy/ to provide that representation.
Either way, is there a validator for the “activities json representation” that we can use to test a particular post permalink, have it auto-discover an activities json representation, and report back what it finds and the validity thereof?
For example, since my posts use the h-entry standard, I am able to validate my post permalinks using the IndieWebifyMe h-entry validator:
https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Ftantek.com%2F2024%2F132%2Ft1%2F
Which finds and validates that I have marked up my hashtags/categories correctly.
Re: “@flaki@flaki.social's Mention there got federated as a Link instead of as a Mention (since replying to this post didn't automatically include flaki's handle)” — this too sounds like a (different) Mastodon bug, since I believe @flaki@flaki.social was notified of my reply and mention of their handle. Perhaps Mastodon is getting it half-right: notifying but not canoeing¹?
Did you receive a notification in your Mastodon instance/client of this reply and its mention of your @thisismissem@hachyderm.io? Or only one but not the other?
#federate #federating #federated #hashTag #hashTags #atMention #atAtMention
Post glossary:
h-entry
https://microformats.org/wiki/h-entry
IndieWebifyMe
https://indiewebify.me/
References:
¹ https://indieweb.org/canoe
@flaki@flaki.social no cross-posting at all, that post, and this reply are federated directly from my personal domain. If you look at the top of my post in your Mastodon client / reader you can see that it’s from @tantek.com — no need for a username when you use your own domain.
Regarding “why the expanded link preview is to one of the (first) hashtags and not to one of the links in the post”, that’s likely a #Mastodon link preview bug with how it treats hashtags.
If you view your reply in your Mastodon (client), you can see that the first hashtag in my post #webDevelopers is correctly (re)linked to your Mastodon’s tagspace: https://flaki.social/tags/webDevelopers, so Mastodon is at least getting that part right, recognizing it as a hashtag, and linking it correctly for your view.
However, Mastodon is still for some reason using the default link for that hashtag on my site (where I am using https://indieweb.social as the tagspace¹) as the link for the link preview.
Since you use Mastodon, perhaps you could file an issue on Mastodon to fix that bug? Something like:
If Mastodon recognizes a hashtag and converts it to link to a local tagspace, it MUST NOT use that hashtag’s prior/default hyperlink as the link for the link preview shown on a post.
Thanks!
#hashTag #linkPreview #federation #fediverse #federated #tagSpace
References:
¹ https://tantek.com/2023/100/t1/auto-linked-hashtags-federated