Notices by erincandescent (erincandescent@akko.erincandescent.net)
-
erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 06-Nov-2024 08:09:28 JST 
erincandescent
@silverpill @scott @julian @evan @mikedev @jenniferplusplus @trwnh @trwnh the context property is in the objects, not the activities -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Saturday, 19-Oct-2024 01:29:02 JST
erincandescent
He's learning about other ActivityPub implementations #plushtodon -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 16-Oct-2024 00:06:27 JST
erincandescent
@mntmn which is ironic, because a lot of stuff is made here, and yet making new stuff can be very hard! -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 25-Sep-2024 01:23:05 JST
erincandescent
Between FediForum and now the Social Web Foundation I'm very tired of seeing these intensely corporate initiatives in this space where the majority of projects are entirely volunteer (or grant supported) efforts -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 18-Sep-2024 01:13:37 JST
erincandescent
@trwnh @julian @silverpill I think the question here is "does a thread actually have any distinct properties of its own?"
Maybe a title, but that can also be inherited from either the first or most recent post. Many threaded discussion systems don't have thread objects at all, of course (email is perhaps the canonical example)
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.
And I think that's better, especially because having significant semantics on collections starts getting confusing when e.g. you have collection pages flying around
Really I think most types which can be represented directly as a collection (e.g. image galleries) are best represented as an object that possess a collection, though not everyone might agree -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 18-Sep-2024 01:13:36 JST
erincandescent
@trwnh @julian @silverpill (the other option is instead of redirection do <link> tags, and then you can link to both if you wish; imagine including <link rel="as:context" href="...">)
-
erincandescent (erincandescent@akko.erincandescent.net)'s status on Saturday, 14-Sep-2024 02:46:22 JST
erincandescent
@helge most implementations inline the replies collection, so it shouldn't be required to go and fetch it explicitly most of the time, except that most implementations also only include self replies in the inline collection -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Saturday, 14-Sep-2024 02:46:21 JST
erincandescent
@helge If the replies collection’s items were always inlined (or were always inlined when low enough in number, at least), it would be N fetches for N posts which is not too unreasonable.
The Threadiverse people (Discourse, NodeBB, Lemmy?, MBin?) are also coalescing around the idea of a context collection which contains every post in the entire (logical) thread
-
erincandescent (erincandescent@akko.erincandescent.net)'s status on Saturday, 14-Sep-2024 02:46:20 JST
erincandescent
@helge Akkoma and Pleroma already internally maintain the same idea of a context so I have plans to implement an MR which reifies it at a fetchable URL.
-
erincandescent (erincandescent@akko.erincandescent.net)'s status on Friday, 08-Mar-2024 01:32:09 JST
erincandescent
@evan @Edent @Gargron yeah - pretend the body does not exist until the signature is verified. Then verify that the key authorises the actor specified in the body to do what they are doing -
erincandescent (erincandescent@akko.erincandescent.net)'s status on Monday, 12-Feb-2024 18:41:10 JST
erincandescent
Hello, is this thing on?
All ０７６萌ＳＮＳ content and data are available under the