The project was using a way to bypass requiring a backing account to proxy the requests, but the API update broke that
The instances that chose (and choose) to go the extra mile by creating and maintaining proxy account(s) are the ones still working
If the instance gets too popular the twitter goons quickly figure out what the proxy account is and ban it, though. So it's a constant game of cat and mouse.