One regret I have about ActivityPub is that navigating reverse chronological collections is really error-prone.
-
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?
-
julian@activitypub.space ha condiviso questa discussione su
-
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".
-
Sistema ha condiviso questa discussione su
-
@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.
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi