Instead of redirecting to twiiit.com, it'd be much better (imo) if you'd to edit the script in a way to allow for insertion of multiple instances.
eg: instead of the script straight up redirecting to twiiit, it would choose randomly from a list of instances that you've given it.
The reasoning behind this is simply because according to twiiit, only 2 instances are up as of writing this, when in reality 4 are actually up according to https://github.com/zedeus/nitter/wiki/Instances. Even then, twiiit seems to prioritise the lucabased instance instead of this other instance thats up, which may result with lucabased instance receiving the most server load instead of it being spread out across instances.
Changing the link to farside.link/nitter would thereotically be better as farside listed 3 instances being up instead of twiiit's 2, but it's still missing one working instance from their list.
Instead of redirecting to twiiit.com, it'd be much better (imo) if you'd to edit the script in a way to allow for insertion of multiple instances.
eg:
instead of the script straight up redirecting to twiiit, it would choose randomly from a list of instances that you've given it.
The reasoning behind this is simply because according to twiiit, only 2 instances are up as of writing this, when in reality 4 are actually up according to https://github.com/zedeus/nitter/wiki/Instances. Even then, twiiit seems to prioritise the lucabased instance instead of this other instance thats up, which may result with lucabased instance receiving the most server load instead of it being spread out across instances.
Changing the link to farside.link/nitter would thereotically be better as farside listed 3 instances being up instead of twiiit's 2, but it's still missing one working instance from their list.