#atmention — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #atmention, aggregated by home.social.
-
@[email protected] we’ve tracked the bug down to one or more problems stemming from having a link in a post to an https: URL that fails to resolve or times out, in the context of an @-mention.
Bridgy Fed is attempting to fetch it and times out. When a #fediverse instance fetches the AS2 version of a post, and Bridgy Fed attempts to fetch that post’s links to construct the AS2 for the post, Bridgy Fed times out, which then likely times out the original AS2 request, so #Mastodon instances never get the requested AS2 post.
There are multiple possible problems:
* content authoring errors (including bad links, links going bad)
* Bridgy Fed attempting to retrieve every link in a post in order to construct the AS2 for a post, possibly with too long timeouts, so the overall AS2 construction takes too long
* Mastodon timing out when requesting the AS2 for a post, then giving up and never trying again (e.g. even when it receives an UPDATE for the post)
More discussion here:
* https://chat.indieweb.org/dev/2024-09-04#t1725421768496000
More details here:
* https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883
#BridgyFed #atMention #ActivityStreams2 -
@[email protected] 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 @[email protected] 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: “@[email protected]'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 @[email protected] 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 @[email protected]? 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 -
@[email protected] 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 @[email protected] 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: “@[email protected]'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 @[email protected] 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 @[email protected]? 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 -
@[email protected] 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 @[email protected] 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: “@[email protected]'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 @[email protected] 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 @[email protected]? 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 -
@[email protected] 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 @[email protected] 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: “@[email protected]'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 @[email protected] 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 @[email protected]? 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 -
@[email protected] 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 @[email protected] 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: “@[email protected]'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 @[email protected] 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 @[email protected]? 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