Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.
-
@[email protected] said in Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.:
And of course as mentioned we use them for conversations so that everybody sees the same view of the discussion. It's a very under-utilised organisational mechanism and that seems odd. They're quite useful.
Ah yes, that was what I was referring to, a collection for a conversation. It certainly does seem under-utilised but I wasn't entirely sure whether that was true or not.
Are you aware of any other implementors that expose a collection for a collection of a topic's content?
-
"Are you aware of any other implementors that expose a collection for a collection of a topic's content?"
Not currently. -
@julian @mikedev
Fedbox does, and they use the Replies collection for it.marius (@[email protected])
@[email protected] in #FedBOX I use a list of IDs when sending an object as a reply. The list contains all ancestors of said object all the way to the initial grand parent. It makes it easier to generate trees out of the replies, but it's also maybe a misappropriation of the reply concept. :D @[email protected]
Metalhead.club (metalhead.club)
Letterbook will. I'm flexible as to how, but my current plan is to duplicate the OP's replies collection into the context.
cc @mariusor
-
I'm not sure if this is what @julian asks about, but this would be an example of what I meant in the post mentioned by @jenniferplusplus:
https://federated.id/objects/2e6cf5a8-ffa8-4fca-b4cd-8e0c9a584a75/replies
You can see the list of replies fully (the public ones at least), and some of them have inReplyTo attributes that reference multiple objects. This is done to have a way to reconstitute the reply tree structure.
-
That's fine for what you're doing, but we don't have a reply 'tree'. We have a conversation which is an object owned by its creator. They add and remove activities from it. If it wasn't added to the conversation collection, it's not part of the official conversation and supporting applications will ignore it. In this way we co-exist with microblogs, but we can do lots of things that they can't. Like hold a coherent conversation with a defined audience, and support circles/aspects and private groups, and have comment controls. And we can relay things without third party permission artifacts. And we aren't wasting time talking to people that never see us and don't even know we're in the conversation. it's actually a pretty clever construct.
-
@mikedev I wasn't following the larger discussion thread, I don't really know what you guys are talking about. I only meant my reply as a clarification to the quote Jennifer++ posted.
-
No worries. This is a microblog conversation, which means it's not a single conversation but a bunch of different people broadcasting to different audiences and everybody sees a different conversation tree. So it's easy to lose track of who's talking to whom and about what and that's pretty much exactly what I've been addressing.
-
@[email protected] Thanks for sharing this use-case, it's very helpful and quite novel, I might add!
An
inReplyToarray addresses the problem of backfill/ghost-replies with a bottom-up approach, vs a context collection which would be a top-down approach... though depending on what direction your tree grows, perhaps it's the other way around
A context collection would also provides the entire tree, which depending on size may or may not be preferred. Tradeoffs...
I think perhaps there is space for both, although I will admit that if my code encountered an Array in
inReplyToit might just terminate because it expects a single uri.
re: the original ask, specifically I was asking whether any other implementors specify
contextin anas:Note, resolvable to a Collection. -
@[email protected] said:
Letterbook will. I'm flexible as to how, but my current plan is to duplicate the OP's replies collection into the context.
Good to know, I'll add your potential implementation into the table I'm creating... at present I'd want to know the current or potential usages of
context. Hopefully there won't be too many disparate and incompatible implementations to reckon with... -
mariusreplied to julian on last edited by [email protected]
> ...if my code encountered an Array in inReplyTo it might just terminate because it expects a single uri
@julian sadly that's the case for most fediverse software at the moment.
-
Tully, transient subjectreplied to julian on last edited byThis post is deleted!
-
Tully, transient subjectreplied to julian on last edited byThis post is deleted!
