Thing is that searx.be has been remarkably good for my use case since a long time. With other instances YMMV.
lemmyreader
The mentioned server side changes (e.g. A server move you mentioned but could also be server settings, provider settings, etc).
I guess that is the case. According to https://searx.space/ the searx.be server is in Austria but might use some proxy to talk to Google and similar to avoid quick blocking. The maintainer of searx.be also maintains yewtu.be and that one uses proxies (The proxy names can be seen when blocking auto play of videos in Tor browser).
Also getting results in Russian here since a few days. Usually it is either Swedish or Dutch. Never German.
👏 Fireworks! 🎆
Most if not all Piped video instances seem unusable right now : https://lemmy.ml/post/19084660/12956916
Indeed. I tried on mobile with LibreTube and with Mull and both fail. And also fails now in Tor browser. The list is getting shorter.
Now I've tried almost all of them in the Piped instances list (Several domain name for sale and server not found errors) and only the smnz.de one works for me. :( I am wondering whether a freshly installed self-hosted private Piped video instance will work fine.
Works for me still (Using Tor browser. I'm Europe located).
The instances list is not up to date :
- List of instances : https://github.com/TeamPiped/Piped/wiki/Instances But after trying maybe more than 10 of them I found one which manages to play a video :
https://piped.smnz.de/watch?v=bBhDWTZDH9c
There's probably more working instances.
Plan B : I guess running your own Piped instance and not sharing it with a lot of people could be worth considering.
Personally I'm sticking to https://wiki.archlinux.org/title/Yt-dlp#Faster_downloads for the video downloading I do.
Was about to post the great blog post from my bookmarks, but another commenter beat me to it (t y !). Here's comments on that blog post on Lobsters and HN :
Yes and no. Code development for Nitter has officially stopped afaik, but there are still some instances not completely dead.
- https://status.d420.de/ Nitter Instance Uptime & Health
Ouch, that's a nasty bug imho. Thanks to this wiki entry I've looked up the file librewolf.cfg in /var/lib/flatpak/ and changed :
pref("network.trr.mode", 2);
into
pref("network.trr.mode", 5);
and that seems to fix it for now (till a newer LibreWolf maybe overrides that file).