hhmx.de

julian

julian (@julian@community.nodebb.org)

Föderation · Di 17.09.2024 17:40:06

@erincandescent@akko.erincandescent.net said:



So I lean towards the idea that you should just redirect to the first thread in the post, and place the context (which when becomes just a collection of in-thread posts; an implementation detail) at another URL where it mostly becomes invisible to users.



That's why I'm still on the fence about this whole thing. In principle, a thread object can and does exist in software, but in practice there is lots of prior art that says otherwise.


That said, email might be a threaded chain of messages, but most email clients I know have standardized around representing them as a discrete topic, if only in the UI.


@trwnh@mastodon.social @evan@cosocial.ca @silverpill@mitra.social


infinite love â´³

infinite love ⴳ (@trwnh@mastodon.social)

Föderation EN Di 17.09.2024 17:45:00

@julian @erincandescent @evan @silverpill Let me put it this way: the latter half of FEP-7888 can be summarized as "reifying context as an object, and specifically a Collection". If you *just* want the grouping, then it could be an arbitrary opaque IRI. But what you gain by reifying the context as an object is specifically the ability to give it metadata properties. Particularly things like `attributedTo` or `audience`. Maybe even `followers` or `outbox`. An opaque IRI cannot do this.

Erin 💽✨

Erin 💽✨ (@erincandescent@akko.erincandescent.net)

Föderation EN Di 17.09.2024 17:48:16

@trwnh @julian @evan @silverpill I never did the URI should be opaque; what I implied was that perhaps it should be an implementation detail URI as opposed to a directly visible one.

Some of this is that I wonder how decoupled such a thread truly is *semantically* from it's root post

Evan Prodromou

Evan Prodromou (@evan@cosocial.ca)

Föderation EN Di 17.09.2024 17:50:44

@trwnh @julian @erincandescent @silverpill you can also get the whole thing! That's the big benefit of having a `Collection` -- you can retrieve it.

silverpill

silverpill (@silverpill@mitra.social)

Föderation · Di 17.09.2024 18:01:46

@julian I reported this to you because one user asked me "why I can't discover this NodeBB thread from my instance?". I think this is going to happen quite often across the Fediverse.
Maybe in the future we will figure out how to deal with these collections, but right now this leads to a bad user experience

@trwnh @evan @erincandescent @evan

infinite love â´³

infinite love ⴳ (@trwnh@mastodon.social)

Föderation EN Di 17.09.2024 18:10:11

@silverpill @evan@cosocial.ca @erincandescent @julian @evan@community.nodebb.org I'd prefer impls update to support showing threads/collections, rather than NodeBB being held back. UX will get better as other impls update.

At the very least, browser.pub can do it! :P

Erin 💽✨

Erin 💽✨ (@erincandescent@akko.erincandescent.net)

Föderation EN Di 17.09.2024 18:18:04

@trwnh @silverpill @evan @julian @evan so, truthfully, I'm ambivalent to whether a thread object exists. But if it does, I feel like it should probably be reified distinctly from the thread collection primarily because I don't think treating collections as objects is a good idea. Maybe I'm wrong, but that's my strongly held opinion!

And yeah, then we can give threads a following collection and let people follow them as they wish.

Erin 💽✨

Erin 💽✨ (@erincandescent@akko.erincandescent.net)

Föderation EN Di 17.09.2024 18:32:39

@trwnh @evan @evan @julian @silverpill and to be clear my ambivalence about whether there should be a thread object comes primarily because I don't think this is a point on which we will ever get universal agreement

It's an area where I feel the only real route is the "why not both?" compromise that doesn't really make anyone happy

Evan Prodromou

Evan Prodromou (@evan@cosocial.ca)

Föderation EN Di 17.09.2024 18:35:48

@erincandescent @julian @evan@community.nodebb.org @trwnh @silverpill Standards are about making arbitrary decisions in the pursuit of uniformity.