|
· Föderation EN So 05.01.2025 00:19:19 @dgoldsmith I think this is an ActivityPub issue and not a Mastodon one, but I will write an issue and see how it goes. |
|
Föderation EN So 05.01.2025 00:21:10 @drahardja @dgoldsmith Oh, I hate this so much, yes!! |
|
Föderation EN So 05.01.2025 00:22:12 @drahardja Mastodon works on changes to ActivityPub to support user-requested features. Right now they're working on an ActivityPub proposal to support reply controls. |
|
Föderation EN So 05.01.2025 10:01:16 @drahardja it's not an ActivityPub issue. In the ActivityStreams vocabulary a inReplyTo property for an object can contain the entire list for the replies in the chain. My service uses that to allow it to do easy reply threading. Mastodon however breaks when encounters a list in the property. I think the working group on threaded conversations in the fediverse has reached the same conclusion as I did, when sending a reply, you should include the links to all its parents and grandparents as their inReplyTo. |
|
Föderation EN So 05.01.2025 10:19:42 @mariusor @dgoldsmith Hmm, I don’t see an array as an allowable value type for inReplyTo, and I’m wary of storing a large number of references to replied posts rather than a linked list, but it would certainly be more robust to broken intermediate posts. |
|
Föderation EN So 05.01.2025 10:33:27 @drahardja in that documentation the properties which can receive a single value are marked as "Functional: true" (you can check the ID property for an example). The inReplyTo is not functional: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-inreplyto |
|
Föderation · So 05.01.2025 13:32:00 @mariusor@metalhead.club @drahardja@sfba.social @dgoldsmith@mastodon.social the threaded discussions working group has settled on using resolvable contexts to get around the deficiencies of inReplyTo travertine achieve topic backfill. See FEP 7888 |
