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.

@sn @Mastodon we had a lot of problems with AI crawlers and don't want to use sth like Cloudflare. Once we get a handle on that problem, we will reenable it
@hausmeister @Mastodon thx for the reply! In the meantime I'll check there's any other, ethical way of getting local public timelines so I get some options