Websocket streaming (compat w/ GoToSocial)

[codl]

Mastodon effectively has two streaming APIs, the server-sent events endpoints at /api/v1/streaming/THING, and the websocket stream at wss://INSTANCE/api/v1/streaming. Mastodon.py only uses the SSE endpoints. However GoToSocial only implements the websocket stream, not SSE, so it's impossible to stream events with mastopy on a GTS server.

Also apparently the websocket stream can multiplex many event streams and that might be useful, idk, that's not what I'm personally interested in.

I fully get if this is out of scope, given that it involves probably pulling a new dependency to add support for a whole other protocol to improve not mastodon support in a project called mastodon.py.

[halcy]

Nah it‘s 100% in scope. I‘ve been meaning to add this for a long time now, but never had the energy. The websocket streaming api is clearly the preferred and possibly better one. Anyone reading this, feel free to take a crack at an implementation, or maybe I will (if you do, please comment something to the tune of „i will give it a try“ here)

…

On Sat, Nov 22, 2025, at 10:46 AM, codl wrote: Mastodon effectively has two streaming APIs, the server-sent events endpoints at `/api/v1/streaming/THING`, and the websocket stream at `wss://INSTANCE/api/v1/streaming`. Mastodon.py only uses the SSE endpoints. However GoToSocial only implements the websocket stream, not SSE, so it's impossible to stream events with mastopy on a GTS server. Also apparently the websocket stream can multiplex many event streams and that might be useful, idk, that's not what I'm personally interested in. I fully get if this is out of scope, given that it involves probably pulling a new dependency to add support for a whole other protocol to improve *not mastodon* support in a project called *mastodon.py*. — Reply to this email directly, view it on GitHub <#432> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAOR4LTZ622C7NM3XN7OOT36APF3BFHORZGSZ3HMVZKMY3SMVQXIZNMON2WE2TFMN2F65DZOBS2KSLTON2WLJTUN5YGSY3TSKBKI5DZOBS2U4TFOBXXG2LUN5ZHTJLWMFWHKZNIG42DMMJYHAYDDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDGNRVGQZDMNJXGA32UYLUORZGSYTVORSXHFECUV3GC3DVMWSHI4TVMWSG4YLNMW5XI2DSMVQWIX3QMFZHI2LDNFYGC3TUL5QWG5DJOZUXI6MCUV3GC3DVMWSWS43TOVS2I3TBNVS2W5DIOJSWCZC7OR4XAZMCUV3GC3DVMWTDGMJVGEZTTJDOMFWWLKDBMN2G64S7NFSIFJLWMFWHKZNEORZHKZNENZQW2ZNOO5QXIY3IL5QWG5DJOZUXI6I>. You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.