Seems like masto.kukei.eu will soon be dead with Mastodon 4.5.0 that adds auth behind public timelines API.
I see many instances already having this enabled so I guess I won't get toots without scraping and for this I have no motivation.
Seems like masto.kukei.eu will soon be dead with Mastodon 4.5.0 that adds auth behind public timelines API.
I see many instances already having this enabled so I guess I won't get toots without scraping and for this I have no motivation.
@Mastodon and @hausmeister out of curiosity, what is the motivation to put public timeline API behind auth on your instance?
For the context: I'm using it to get local, public timelines for masto.kukei.eu that indexes public and opt-in-search posts in a central place.
Seems like it's doomed to fail if everyone enables auth.