@jmc is that mostly because the place you receive the callback is not the place where you have the state and context to use it?
There's always the solution using another layer of abstraction; basically all those ways of receiving events are pushed into a message queue locally, that you pull events from. The rest is mostly just details of transport and who is responsible for queue state. The pain comes when your client isn't an entire platform with queues and capable of hosting hooks.
=> More informations about this toot | View the thread | More toots from uep@octodon.social
=> View jmc@unix.house profile
text/geminiThis content has been proxied by September (ba2dc).