@Stricter specifications for pagination of Collections and OrderedCollections - ActivityPub / Client to Server - SocialHub
https://socialhub.activitypub.rocks/t/stricter-specifications-for-pagination-of-collections-and-orderedcollections/2633/4
i am thinking about pagination for https://seppo.app a lot. My current take on it is
1. page content SHOULD be immutable (except for deletions),
2. there are no edits of post, but modified re-posts plus a delete in case,
3. due to deletions page size is mutable(!), there may be degenerated empty ones,
4. numbering is reverse for stable, static page contents (as long as there are no deletes),
5. the current (most recent) page has no number
6. the current (most recent) page is always full, the 2nd (thus the most recent bearing a number) has volatile size, all others are stable.
Most I do it at https://mro.name/microblog for years now.
P.S.: works for dynamic pages, too.
#Paged #Atom #Feed #ActivityPub #ShaarliGo #Seppo
¹ mro.name/ardd3c3
https://socialhub.activitypub.rocks/t/stricter-specifications-for-pagination-of-collections-and-orderedcollections/2633/4
i am thinking about pagination for https://seppo.app a lot. My current take on it is
1. page content SHOULD be immutable (except for deletions),
2. there are no edits of post, but modified re-posts plus a delete in case,
3. due to deletions page size is mutable(!), there may be degenerated empty ones,
4. numbering is reverse for stable, static page contents (as long as there are no deletes),
5. the current (most recent) page has no number
6. the current (most recent) page is always full, the 2nd (thus the most recent bearing a number) has volatile size, all others are stable.
Most I do it at https://mro.name/microblog for years now.
P.S.: works for dynamic pages, too.
#Paged #Atom #Feed #ActivityPub #ShaarliGo #Seppo
¹ mro.name/ardd3c3
Stricter specifications for pagination of Collections and OrderedCollections
Overview ActivityPub primarily depends on direct delivery of activities, but many implementations expose old post history via the outbox. In theory, you could fetch the outbox to discover old posts that weren’t delivered to you but should still be visible to you (e.g. Public posts that persist in the outbox). However, there is one big problem: pagination. Specifically, pagination is an issue because you will have to fetch multiple pages, and you don’t know exactly when to stop, or how to disco...