distributed-transcode VS nitter

Back when I still cared about saving disk space, I made a cluster of NVidia Jetson Nanos running in a docker swarm configuration [1], but honestly even when you have six computers working at once, H264 on a single computer is still often faster.

On the Jetson Nanos I was lucky to get maybe 1fps in ffmpeg using VP9. Multiply that by six boards and that's about 6fps in total; ffmpeg running x264 in software mode was getting around 11fps on a single board, not even counting using the onboard encoder chip, meaning that I was getting better performance from one board using x264 than all six using VP9.

Now obviously this is a single anecdote on specific hardware, so I'm not saying that this applies to every single case, but it's a big reason why I personally have not used VP9 for anything substantial yet.

[1] https://gitlab.com/tombert/distributed-transcode

I have a fairly large blu-ray collection (~300 movies, ~15 complete TV series). I rip them and serve them with Jellyfin, which works, but due to codec annoyances, I need to transcode them to run on web browsers, and the SBC I'm running Jellyfin + ZFS on is not really fast enough to transcode in real time.

Since I have a ton of little SBCs sitting around my house, I decided to write a clojure app the queues up and transcodes my movies to H264. It uses Docker Swarm to handle distribution of nodes, RabbitMQ to queue up the movies, and core.async to handle local queuing within the application, and uses the Java NIO filesystem stuff to handle any kind of atomicity.

It's hardly the "first" or the "best" at what it does, but the advantage of writing your own is of course that you can tailor it exactly to your setup, and of course it was fun to write.

https://gitlab.com/tombert/distributed-transcode

Don't use Youtube without going through a proxy like Invidious [1] or Newpipe

Don't use {site} Search without going through a proxy like SearxNG [2]

Don't use TwiXXer without going through a proxy like Nitter - this has gotten more difficult lately but it still works as long as you feed the daemon some registered accounts. Video does not work at the moment but that seems to be fixable.

Don't use Reddit without going through a proxy like libreddit [4]

Start noticing the pattern? Maybe it is time to start producing promotional posters:

The only thing to come between you and ADS could be a proxy / ADS. I'ts just not worth the risk

ADS / New rules for a sane net / Sane net protects you, your partner and your community

A proxy here and a filter there, ADS nowhere

The more you tighten your grip, ${site}, the more viewers will slip through your fingers

[1] https://github.com/iv-org/invidious

[2] https://github.com/searxng/searxng

[3] https://github.com/zedeus/nitter

[4] https://github.com/libreddit/libreddit

https://nitter.esmailelbob.xyz/liuzhuang1234/status/17601959...

(bit of trial and error from https://github.com/zedeus/nitter/wiki/Instances)

I assume this is why Nitter got slammed and is on the verge of breaking.

https://github.com/zedeus/nitter/issues/1154

The creator of the project left this comment an hour ago:

https://github.com/zedeus/nitter/issues/1155#issuecomment-19...

(HN removed the deep link to the specific comment from the title)

Most of the time you can just replace twitter.com with nitter.net or nitter.it but when these instances are down or blocked you can use other instances listed here: https://github.com/zedeus/nitter/wiki/Instances

But as the other commenter said Libredirect is the way to go: https://libredirect.github.io/

Use a Youtube proxy like Invidious [1], problem solved and you get to subscribe to channels without telling the Beast about your interests. Add Sponsorblock (which supports Invidious) to get rid of any in-stream advertising which remains and you'll be transported back to those hallowed times of yore when men were men, women were women and advertising was something you found in newspapers. Youtube will try to make this harder just like Xitter is trying to make it harder to use proxies like Nitter [2].

[1] https://github.com/iv-org/invidious

[2] https://github.com/zedeus/nitter

njal.la restored nitter.net, and replied with their reasons: https://github.com/zedeus/nitter/issues/1150#issuecomment-18...

tbh I can totally understand why they acted this way.