One regret I have about ActivityPub is that navigating reverse chronological collections is really error-prone.
Technical Discussion
5
Posts
3
Posters
15
Views
-
One regret I have about ActivityPub is that navigating reverse chronological collections is really error-prone. "first", "last", "next" and "prev" mean the opposite of what you think they mean, so it's easy to get mixed up and navigate things the wrong way.
It's too late to change now, but I could see adding some synonyms for these properties, like "newest", "oldest", "older" and "newer", to make it easier to do the navigation code.
-
One regret I have about ActivityPub is that navigating reverse chronological collections is really error-prone. "first", "last", "next" and "prev" mean the opposite of what you think they mean, so it's easy to get mixed up and navigate things the wrong way.
It's too late to change now, but I could see adding some synonyms for these properties, like "newest", "oldest", "older" and "newer", to make it easier to do the navigation code.
@evan could this be fixed by a future version? Or given that the set is not overlapping I guess they could be provided concurrently for compatibility?
-
undefined julian@activitypub.space shared this topic on
-
One regret I have about ActivityPub is that navigating reverse chronological collections is really error-prone. "first", "last", "next" and "prev" mean the opposite of what you think they mean, so it's easy to get mixed up and navigate things the wrong way.
It's too late to change now, but I could see adding some synonyms for these properties, like "newest", "oldest", "older" and "newer", to make it easier to do the navigation code.
evan@cosocial.ca what about
after? Using paginated collections is easy, but could be problematic if the set changes while you are navigating.Using
afteris a little more complicated but much more reliable in terms of getting exactly the next set of items. -
@julian Pages should be real containers, not slices of the collection like "last 25 items".
-
System shared this topic on
-
@evan could this be fixed by a future version? Or given that the set is not overlapping I guess they could be provided concurrently for compatibility?
@flancian It's an egregiously backwards-incompatible change, so probably no.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@douwe@waag.social The protocol itself hasn't changed radically in the last 18 months. If you want to understand ActivityPub and ATProto's similarities and differences, you can't find a better analysis than Christine's. She is one of my co-authors on ActivityPub, and she really dug deep into both protocols.
-
@evan that is indeed a while ago. As far as I understood ATproto has made significant improvements for federation since...
-
@douwe This article by @danabra.mov is pretty helpful: https://overreacted.io/open-social/
-
@douwe@waag.social Christine Lemmer-Webber did a great analysis a while ago:
https://dustycloud.org/blog/how-decentralized-is-bluesky/
It's a great place to start.
-
Trying to better understand ATproto and Activitypub similarities and differences.
People here with recent reading/listening/watch tips?
#fediverse #eurosky #bluesky #activitypub #ATProto #Mastodon
-
definitely not a fan of this. tbh, there should just not be a global feed that new accounts see, because they see a lot of stuff they don't understand or know the community norms for, and that leads to bad engagement.
-
There is the Web Share API, and the future Web Share Targets API, but I think we could also align Web Share with FedCM and be able to say "I want to share to this type of application"
-
@reiver i think the disjunction between Object and Link was actually unnecessary. https://github.com/w3c/activitystreams/issues/666
i also think there's too much emphasis on types when there really shouldn't be -- it's the *properties* that you end up using almost all of the time. pretty much the only types that actually matter are the Activity types (because you can't infer those).
