We seriously need to talk about deletion not being real in the fedi.
General Discussion
3
Posts
3
Posters
17
Views
-
We seriously need to talk about deletion not being real in the fedi.
Some instances never erase your toots when you delete them.
-
We seriously need to talk about deletion not being real in the fedi.
Some instances never erase your toots when you delete them.
@maikel The two uncomfortable truths of the internet, since the '90s:
- You can never reliably publish something.
- You can never reliably delete something once it's published.
-
We seriously need to talk about deletion not being real in the fedi.
Some instances never erase your toots when you delete them.
maikel@vmst.io what is there to talk about? ActivityPub is a decentralized and distributed protocol. Deletion is best effort and while the ideal use case would be instant deletion of your own content, everywhere, on demand, it's just not feasible.
I sympathize, I really do, I just don't have any answers.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@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.
-
Another thing is whether "pages" in your collection are real objects -- buckets that fill up with items as time goes on -- or just fixed-length offsets from the most recent item. I think having real pages is much better for caching and synchronization.
