Yes I did some internal overhaul of invidious-companion video fetching and retry behavior. I also increased the compute power of the companion edge server. I will still look if this is possible to merge.
Posts
-
[Invidious] Merge the embedded YouTube link for the error page? -
Account avatars force you to crop the uploaded image to ~45%That sounds like an issue with NodeBB; please report that here: https://github.com/NodeBB/NodeBB/issues/
-
[Invidious] Merge the embedded YouTube link for the error page?I will look if it is still compatible.
-
proxyVideos?Yes this is intentionally locked server-side because it consumes a lot of bandwidth and is very inefficient per volume for the server cpu.
-
wikiless.tiekoetter.comWikiless is now fully developed by me. https://github.com/tiekoetter/Wikiless
-
invidious.tiekoetter.comInvidious video fetching has been optimized. Playback should be smoother now.
-
nitter.tiekoetter.comThe nitter instance now has access to multiple accounts making it more reliable.
-
AS208694A Looking Glass for AS208694 is now available.
You can check it out here: https://www.lg.as.tiekoetter.net
-
invidious.tiekoetter.comInvidious works again!
-
invidious.tiekoetter.comMy Invidious instance is currently dead since Google/YouTube blocked all my proxy IPs and I can't get a valid token anymore. There is a possibility I can use my own AS for IPs soon but that is not 100% sure yet.
-
The search feature of your nitter instanceHey 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.
-
Whoogle Instance?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!
-
Regarding Invidious and it's brand goals.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.
-
Nitter Instance StatusYeah the status page is just checking if the index responds with 200 or at all. I could check specific paths but I cache most of it.
The reason why it behaves like this is because my instances gets hammered with 5 times the usual traffic for almost the last 72 hours.
Looks like legitimate traffic.I would have to add more twitter accounts as the current number always sits limited at 95-98% which gives you the "rate limited" error message. If you refresh a few times you may get through to a valid session.
I will have to monitor this for the next few days. Adding more twitter accounts is very tedious.
Thanks for voicing your concerns!
-
Forum Software: NodeBB DiscourseYou can change this on under your profile -> settings. There you can change each different notification type from "notification only" to "notification & email". I have this set to notification only so it doesn't spam inboxes by default.
Hope this helps and thanks for your feedback!
-
Forum Software: NodeBB DiscourseThat is a good question and I was looking at Discourse initially but couldn't get it to work how I would have wanted. It also throws countless errors and seems more hacked together than a thought through software. The docker image was not really working, this may also be an error on my part but they officially don't support docker as an install method which I thought was a red flag.
I came across NodeBB in my research for a modern forum software. Looked promising. They provided a clean docker install method. I also noticed that Netgate (the company behind pfSense) uses NodeBB for their forums.
It also looked easy to maintain, which turned out true, so I settled on it.
-
Thanks for using Anubis instead of cloudflare!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.
-
AS208694I have extended the IPv6 access via AS208694 to redlib.tiekoetter.com and nitter.tiekoetter.com
-
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.