Conversation

Notices

1. Embed this notice
   Thomas Ricouard (dimillian@mastodon.social)'s status on Friday, 03-Feb-2023 22:09:17 JST Thomas Ricouard

   • Eugen Rochko

   @Gargron Did mastodon.social streaming API got killed?

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Friday, 03-Feb-2023 22:09:17 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP

     @dimillian No, we moved it to a subdomain. Can you not connect?

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Friday, 03-Feb-2023 22:10:27 JST Thomas Ricouard

     in reply to

     • Eugen Rochko

     @Gargron nop. Health check resolve to 404. And ws endpoint tell me that my tokens don’t have proper rights.

   • Embed this notice
     Andrea Grandi 🦕 (andreagrandi@mastodon.social)'s status on Friday, 03-Feb-2023 22:34:50 JST Andrea Grandi 🦕

     in reply to

     • Eugen Rochko

     @Gargron @dimillian not sure if related, but the web version of Mastodon also is not refreshing/updating with new posts anymore. I have to reload the browser page. Even the house icon remains black.

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 03:08:58 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @renchap @Gargron also noticed I need to upgrade to v2/instance, using v1 right now and there is no information about the streaming url. Definitely not a quick fix on my side. But I feel like the redirect is working but the tokens are not given the proper right on the new domain?

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Saturday, 04-Feb-2023 03:08:58 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP
     • Renaud Chaput

     @dimillian @renchap It's there in v1 too, urls.streaming_api

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 03:08:59 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron I am looking at moving the endpoint back to the original URL, will update you on this.

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 03:09:01 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @renchap @Gargron Hmm so my client does not read configuration.urls.streaming, it just have the hardcoded streaming endpoint from the doc. I can look to add that but it means it's breaking every live app.

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 03:09:02 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron
     There is a redirect in place for the old URL to the new one (on a subdomain). And the new URL is correctly exposed via `/api/v2/instance` (in `configuration.urls.streaming`). Is you client having trouble updating it to the new one?

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 03:20:18 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @Gargron @renchap Nice I'll use this then for now.

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 03:46:12 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput
     • icecubesapp

     @Gargron @renchap I did a fix to handle them correctly in @icecubesapp

     https://github.com/Dimillian/IceCubesApp/commit/4de46610e007cae40a5717bf1a2ed11fe3d92035

     But will be in the store only in a couple of days.

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 05:28:04 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @renchap @Gargron on iOS same error as before: Error: Access token does not cover required scopes

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Saturday, 04-Feb-2023 05:28:04 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP
     • Renaud Chaput

     @dimillian @renchap I'm curious why this error occurs. How do you attach the access token to the request? What scopes does the token have, and what channels are you trying to subscribe to?

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 05:28:05 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron Can you retry? I switched to a 308 redirect, which should tell the client to send the payload again, if any (not supported everywhere)

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 05:28:06 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @renchap @Gargron And on iOS I don't get a 404, the socket seems to connect, but at every message I get this error: Error: Access token does not cover required scopes

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 05:28:07 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput
     • icecubesapp

     @renchap @Gargron Just to be sure, even root path is doing that. And this is what @icecubesapp is using, send I send different messages to connect to various stream depending of the context.

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 05:28:07 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron What is the best way for me to reproduce this? Everything I tried gave me a 301…

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 05:28:08 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron Yes, this is what https://github.com/mastodon/mastodon/issues/23383 is about. It looks like reverting to the original URL will take more time than planned, I will add redirects for those paths.

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 05:28:09 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @renchap @Gargron This do a 404 for example

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Saturday, 04-Feb-2023 05:28:10 JST Renaud Chaput

     in reply to

     • Eugen Rochko

     @dimillian @Gargron tokens should not be scoped by domain, the servers behind are the same, only the URL changed. I am not sure of whats happening here ?

   • Embed this notice
     Thomas Ricouard (dimillian@mastodon.social)'s status on Saturday, 04-Feb-2023 05:32:17 JST Thomas Ricouard

     in reply to

     • Eugen Rochko
     • Renaud Chaput

     @Gargron @renchap The scopes are the same as the one I'm using when an user authenticate with the app as I'm using the same tokens, so the scope are "read write follow push". And I'm sending them in the "Authorization" header, same as for other requests. Sending messages to connect to the user & direct stream. Now my guess is that don't transfert over a redirect? Working fine if I connect directly to the new URL. And was working before the redirect for production app.

   • Embed this notice
     Lalufu (lalufu@mastodon.social)'s status on Saturday, 04-Mar-2023 02:04:28 JST Lalufu

     in reply to

     • Eugen Rochko

     @Gargron @dimillian
     It seems this got broken again around 2 days ago? https://mastodon.social/api/v1/streaming redirects, but subpaths like https://mastodon.social/api/v1/streaming/user do not.