I have extended the IPv6 access via AS208694 to redlib.tiekoetter.com and nitter.tiekoetter.com
VIP
A group for people who are very important sponsors of Tiekoetter.com
Private
Posts
-
AS208694 -
nitter.tiekoetter.comJust checked it. It was actually Twitter that was down and not the Nitter instances. It is still a bit flaky but so is Twitter itself right now.
-
nitter.tiekoetter.comIt looks like Nitter got nuked.
https://status.d420.de/
My instance only has cached results available. I will have to take a look later today. -
Feedback collection regarding IPv6 access via AS208694Hello,
please post your feedback / issues / comments regarding IPv6 access via AS208694 (www.as.tiekoetter.net)I would appreciate your input to evaluate the functionality of AS208694 for future adjustments.
-
AS208694I have implemented IPv6 access via AS208694 for searx.tiekoetter.com, invidious.tiekoetter.com, wikiless.tiekoetter.com and this Forum.
AS208694 is operated by me and serves as another layer of control. Currently only IPv6 is possible as IPv4 is far too expensive for an individual to get. The IPv6 access is terminated at the same server, it is just routed differently. It works in conjunction with the current IPv6. I may expand this to the other services in the future.
More information about AS208694 can be found here: www.as.tiekoetter.net
-
Feedback & Missing FeaturesFor the missing features please refer to the GitHub repository of the developer of Nitter: https://github.com/zedeus/nitter
The "following users" suggestion is on the roadmap (account system) I don't know how far this feature is in development. You can open an issue there regarding the NSFW options.
Thanks for the feedback! I hope my hosted services continue to be useful to you and others!
-
nitter.tiekoetter.comThe Nitter instance is now fully restored again.
-
wikiless.tiekoetter.comAfter a bit more testing and one full day of evaluation Wikiless is now restored.
The aggressive caching didn't really help. I added Anubis on top of Wikiless and after a few minutes it completely removed the rate limit on the back-end.
Meaning JavaScript is now required for Wikiless but the barrage of bot requests gets filtered out. In my opinion a fair trade off.Shoutout to Anubis. This software is incredible at stopping bots/scrapers https://github.com/TecharoHQ/anubis
-
wikiless.tiekoetter.comI have implemented very long caching rules. This should mitigate the hammering of the wikipedia.org servers. From my usage when encountering an "INVALID_HTML" page (429 from upstream) refreshing a few times will get the page eventually. These cached pages are considered fresh for 6 hours and stale for up to 1 day, afterwards they are discarded if no other user requests the page in the meantime.
This is not optimal but a good enough intermediate solution.
-
wikiless.tiekoetter.comI guess Wikipedia has finally decided to block my Server.
The back-end reports 429 from the wikipedia.org servers.
Currently Wikiless doesn't support proxy servers. I would have to fork Wikiless and implement it myself for it use my proxy back-end. I may have to look into this in the future.