You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
General Discussion
1
Posts
1
Posters
0
Views
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
You know, it’s entirely possible to use ATProto without touching anything owned by Bluesky proper
Pretending that Bluesky is the whole of ATProto is like pretending the whole of the Fediverse is Mastodon
Stop using your ignorance as vindication in your choice of home platform, it’s not ATProto vs ActivityPub
It’s the Social Web vs centralized social media
-
@evan@cosocial.ca in reverse chron every page changes when a new item is pushed to the stack.
Even in chronological sets if you need to account for deletions you've basically given up already because there's no immutability guarantee! This is why caching headers exist, no?
-
@macgirvin like, only the most recent page should be volatile. Except for deletions, older pages should not change.
-
@julian you monster
-
@macgirvin oh, but: I disagree about configurable page sizes. I think pages should have stable contents, have last-modified dates, and be easily cacheable. It makes traversal and synchronization much better.
-
@evan@cosocial.ca remind me to change pagination size to 1 on April 1st
-
@macgirvin the 12-item page size is a real kick in the teeth.
-
Anyway, here's my thought: I think the advantages of embedded objects are offset by the problems with caching. I think we should make collection pages real, stable objects, with fixed contents and real modification dates. Return only references, not embedded objects. Do filtering, though. And make pages big -- 100 items or more.
