Minutes from 3 October 2024 WG Meeting

Evan Prodromou

@julian @darius I started a new FEP to define a vocabulary specifically for threads.

FEP 76ea: Conversation Threads

fep - Fediverse Enhancement Proposals

Codeberg.org (codeberg.org)

Erin 💽✨

@evan @julian @darius How does the “thread” property differ from the “context” property which basically every implementer is already using and has been doing so for 6+ years?

Darius Kazemi

@erincandescent @julian @evan can you give an example of the "context" property in use?

julian

@[email protected] @[email protected] keep in mind we're talking about as:context and not @context

Erin 💽✨

@darius @julian @evan

curl -H "Accept: application/ld+json" https://akko.erincandescent.net/objects/6d40d43e-9929-4bf9-9a9b-725ef3a682cd | jq

{
  ...
  "context": "https://community.nodebb.org/topic/18328",
  "id": "https://akko.erincandescent.net/objects/6d40d43e-9929-4bf9-9a9b-725ef3a682cd",
  "inReplyTo": "https://cosocial.ca/users/evan/statuses/113250578296473665",

infinite love ⴳ

@julian @darius @erincandescent self-referential: https://browser.pub/https://mastodon.social/@[email protected]/113250586247164172

Erin 💽✨

@trwnh (same braincell!)

infinite love ⴳ

@erincandescent side note it is cool that browser.pub handles redirects seamlessly

Erin 💽✨

@trwnh yeah i couldn’t remember the flag to pass to curl

Erin 💽✨

@trwnh side note: this subthread is a totally perfect illustation of why being able to “fork” the thread would be useful.

infinite love ⴳ

@erincandescent right! it's not about replies at all, you can reply to something in a different thread, so it's wrong to define a "thread" as equivalent to a "reply tree"

julian

@[email protected] after we deal with conversational contexts we should probably define forking threads. I've been thinking on that a bit recently.

infinite love ⴳ

@julian @erincandescent likewise. my initial thought was using Move to signal something like "these 6 posts were moved to another thread by a moderator"

julian

@[email protected] @[email protected] Right, it gets a little confusing when implementors inherit context from the objects they're replying to (or maybe the root node?), but that's exactly what 7888 tries to codify/demystify.

But Akkoma's use of context seems to be in line with 7888 (in that it's pointing back to the resolvable context provided by NodeBB).

Emelia 👸🏻

@trwnh @julian @erincandescent I guess there you'd need to look at Move and make sure the target/actor/objects weren't Actors but where other objects?

Darius Kazemi

@erincandescent @trwnh so by my reckoning, Mastodon and Misskey don't use context, akkoma does... ugh, I need to add more sources to my observatory

Erin 💽✨

@darius @evan @julian side note: Akkoma also emits a “conversation” property containing the same URL, which is JSON-LD mapped tohttp://ostatus.org#conversation. This is because Mastodon will pass-through the conversation property to replies, but doesn’t know about context. When Mastodon generates a Conversation tag (e.g. when its absent from the parent post), it stuffs a tag URI like tag:cosocial.ca,2024-10-04:objectId=26829720:objectType=Conversation into it. This is visible in evan’s earlier post

side side note: “conversation” is misdeclared as a “@value” and not “@id” property in Mastodon’s context. Oh well.

Erin 💽✨

@julian @trwnh When Akkoma originates a thread the context it populates it with doesn’t resolve.

However, fixing that is on my plate.

Erin 💽✨

@darius @trwnh and I believe Lemmy & co do? But I honestly haven’t followed them

infinite love ⴳ

@julian @erincandescent if you want your post to be in the same context as the thing you're replying to, then it's inherited from the thing you're replying to.

7888 also describes what could happen if you decide to set your own context, or set *no* context. in fact, this is how you would self-fork a topic.