Tiekoetter.com Forum

Just 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.

That worked flawlessly. Got the email. Such a nice software from a user perspective.

Invidious works again!

After 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

A Looking Glass for AS208694 is now available. You can check it out here: https://www.lg.as.tiekoetter.net

thank you, good to know

Sorry for the late reply. Invidious is a front-end / proxy for YouTube. You can check the source code from the Invidious project at https://github.com/iv-org/invidious If you have any specific questions regarding my instance of invidious feel free to ask.

For 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!

Yeah that was the intention; to keep everything self-hosted. Although cloudflare is great for some tasks one would have to take their word that they are not reading user data when they act as the TLS termination.

What you are describing is the current problem with the bing and yahoo engine. They don't give quality results for an unknown reason for some percentage of results. The reason why bing is the default on my instance is because it gives near limitless results as it doesn't rate limit. Before I had google enabled as default but it broke in early october (refer to this GitHub issue if you want to read up on it: https://github.com/searxng/searxng/issues/5286) Either way since duckduckgo and brave also increased their bot detection the only "quality" general search engine left is presearch. You can switch the engines when you go to preferences -> engines. There you can enable/disable engines however you want. Hope this helps and thanks for your feedback!

Hey thanks for the feedback! No the search feature is not intentionally limited. I have encountered it myself a few times. As far as I have seen it depends on the time of day due to how many people are using it. Why it is limited way more than the actual content and media I don't know. I probably have to add a few more twitter accounts to my instance to avoid this. This will take a bit of time because these accounts have to wait a but before they can be used for the instance.