@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.
@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?
@dlx@ethanlipnik BTW the recommended for you to follow of the explore part of Mastodon.social is not bad at all. I’m going there regularly to pick new follow.
@dlx Maybe @Gargron know something? Why do some users don't see the explore tab on .social? And when manually going on the explore URL no content is shown there.
@Gargron@atomicpoet@gruber BTW. Ice cubes support for other kind of server is coming… I guess. But also I have « For Mastodon » in the app name on the App Store so ?♂️
@Gargron@Ronnie it can but it means you have to pull a looooot of pages of notifications and you could hit the rate limit faster. I’ll explore the idea.
It’s actually technically a nightmare. I’ll have to test Mona to see how accurate it is but on my 500 notifications per hours account it could either crash the API or not be accurate at all. I wonder if @Gargron have that in the roadmap.
🍎 SwiftUI engineer🤖 AI Stuff👨💻 Staff iOS engineer @medium🇫🇷 Entrepreneur, iOS/macOS & more🫡 Previously @glose 📖 @google 🔍 & various other🧊 Maker of @IceCubesApp, an open source Mastodon client in SwiftUI: https://github.com/Dimillian/IceCubesApp #IceCubesApp Download it on the App Store: https://apps.apple.com/us/app/ice-cubes-for-mastodon/id6444915884Also on Threads: https://www.threads.net/@dimillian