Minutes from 3 October 2024 WG Meeting
-
Erin 💽✨ 🔜 38C3replied to infinite love ⴳ on last edited by
@trwnh (same braincell!)
-
infinite love ⴳreplied to Erin 💽✨ 🔜 38C3 on last edited by
@erincandescent side note it is cool that browser.pub handles redirects seamlessly
-
Erin 💽✨ 🔜 38C3replied to infinite love ⴳ on last edited by
@trwnh yeah i couldn’t remember the flag to pass to curl
-
Erin 💽✨ 🔜 38C3replied to Erin 💽✨ 🔜 38C3 on last edited by
@trwnh side note: this subthread is a totally perfect illustation of why being able to “fork” the thread would be useful.
-
infinite love ⴳreplied to Erin 💽✨ 🔜 38C3 on last edited by
@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"
-
@[email protected] after we deal with conversational contexts we should probably define forking threads. I've been thinking on that a bit recently.
-
@julian @erincandescent likewise. my initial thought was using Move to signal something like "these 6 posts were moved to another thread by a moderator"
-
@[email protected] @[email protected] Right, it gets a little confusing when implementors inherit
contextfrom 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
contextseems to be in line with 7888 (in that it's pointing back to the resolvable context provided by NodeBB). -
@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?
-
@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 💽✨ 🔜 38C3replied to Erin 💽✨ 🔜 38C3 on last edited by
@darius @evan @julian side note: Akkoma also emits a “conversation” property containing the same URL, which is JSON-LD mapped to
http://ostatus.org#conversation. This is because Mastodon will pass-through theconversationproperty to replies, but doesn’t know aboutcontext. When Mastodon generates a Conversation tag (e.g. when its absent from the parent post), it stuffs a tag URI liketag:cosocial.ca,2024-10-04:objectId=26829720:objectType=Conversationinto it. This is visible in evan’s earlier postside side note: “conversation” is misdeclared as a “@value” and not “@id” property in Mastodon’s context. Oh well.
-
-
@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.
-
Erin 💽✨ 🔜 38C3replied to Erin 💽✨ 🔜 38C3 on last edited by
-
@thisismissem @julian @erincandescent yeah, honestly the existing use of Move for migrations is really unfortunate because you're saying "i moved myself from myself to another person" which makes no sense. it should have been defined some other way (Migrate activity? intransitive, takes `actor` and `target` but no `object`). Move makes more sense to manipulate collections (and that's the example provided in AS2-Vocab)
-
@trwnh @julian @erincandescent agreed, another FEP?
-
infinite love ⴳreplied to Erin 💽✨ 🔜 38C3 on last edited by
@erincandescent @darius Lemmy uses `audience` instead, referring to the Lemmy community, which is a Group actor, and you're expected to look through the `outbox` and reconstruct replies on your own. the only hint you have is that the root of a reply tree is represented by an Announce Create Page.
good luck
-
Erin 💽✨ 🔜 38C3replied to infinite love ⴳ on last edited by
-
@[email protected] @[email protected]
Arguably, when Lemmy uses
audiencethey mean one level of abstraction higher than we do (the community). Like Mastodon, Lemmy doesn't actively support the concept of a context... I think.
