1.Nitter
Our Nitter instance is up and running again (on life support) however, to prevent bots and crawlers from fucking it up, we had to add a browser verification step (similar to CloudFlare) and impose some heavy ratelimits. This also means that JavaScript is needed to use the instance.
These measures are here to stay unless Twitter magically changes their mind about how their api works, however, that seems highly unlikely under the current↵ administration↵.
The instance is not fully set-up and tested yet so in the following 2-3 weeks, expect random outages or errors.
2. Teddit
Teddit is dead :/
The repo says it and the instance showed it. It's unfortunate but there's not much that can be done about it. Currently RedLib is still running and being maintained so at least one frontend is still up... for now.
>>Forward>>
Some time ago I stumbled upon Beatbump↵ and Hyperpipe↵ - alternative frontends for YouTube Music and found them quite useful.
I did try fully self-hosting them (including the api) but didn't put much effort and time into it since it's not urgent to have an alternative for YTM but when I have more time I'll definetly look into it a little more unless Manifest V3↵ and this clusterfuck thing↵ mess up my experience in which case I will very much look into it.
Changelog/TLDR
- Nitter instance url will be added back to the homepage once testing stage completes.
- Browser verification and rate limiting was implemented and is being tested with Nitter.
- Teddit url has been removed.
- Looking forward into YTM frontends to host.