mastodon api griping 

i've mostly said this before, but it's so annoying how the mastodon timeline api's refuse to give you the tools to ensure a non-gappy timeline...

the websocket/sse streams just spit toots at you, with no context of ordering and if you missed anything, the pagination api uses link headers but only contain information about the chunk you just received, so you're totally blind on what ranges are continuous unless you make sure to request overlaps and merge based on that...

mastodon api griping 

@f0x This sounds like I am in for a fun ride... (I am currently as I am waiting for a PR to be finished to start my rust pixelfed server writing a small pixelfed client in GTK... So I have to use this api ^^)

Follow

re: mastodon api griping 

@MTRNord it's not great... Matrix' long polling is a lot nicer in this regard because you're always dealing with clearly delineated chunks, with next/previous batch id's

(and even that can be complex to deal with, from a UI perspective etc)

Sign in to participate in the conversation
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.