The problem is probably unrelated to the firmware, and caused by some other upgrade.
After experiencing the issue, you should be able to switch to a different tty with ctrl-alt-f6 (or any other f key), log in, and check journalctl -b for an error message. Edit: Use the End key or shift-G to scroll to the end of the journal.
The leecher will keep trying to connect until it reaches its configured limit. So for a torrent with 10 seeders, you will certainly be connected to.
You can win over faster seeders by configuring your client to use TCP instead of UDP (µTP), and your operating system to an aggressive TCP congestion control algorithm like BBR.
If you do this you’ll saturate your upload and win over every other peer using µTP or cubic/reno TCP, even if the peer is very far away.
downloading whole 8 seasons when I want to watch series is kinda off
You can untick every episode except the first few when you download.
You can also download a torrent sequentially and play it while it’s downlading but it’s fiddly.
How are you decoding the H.264 MVC video?
I’ve got a hang-over pet policy from when I was a baby leftist to abolish rents on land, but with a twist: Any exchange of money for the use of a property is a sale. It’s absolutely financial neo
bullshit but I can’t take it off my mind.
The idea being that if, over time, you pay the landlord for maintenance + the value of the house, you get the title for the house, and this is the law and you can go to court, prove that you’ve paid for rent over however many years, and get the title of the house.
If you leave before that there’d be some system where the “rent” payments are split equally and you get the value back from whoever is currently living there, because you’re selling your share to them. Since the payments are split equally minority “shareholders” leave first. If nobody lives there but you’re paying taxes and maintenance, you still paying for the house so you accrue shares of the house.
I think it might be palatable for neolibs, destroy the value of homes for rent-seeking, but preserve it for construction, which is what libs always complain about when you talk about abolishing rent.
Be the change you wish to see in the world.
https://library.bz/main/upload/ anonymous username genesis password upload
You can’t go wrong with rutracker.
https://rutracker.org/forum/viewtopic.php?t=6391420
You can either get the torrent or download the official image form the website and apply the perl patch at the end of the post.
There are two low level tricks that make a huge difference for seeding, even if you can’t open ports. These are generic Linux tweaks, you may have to adapt them for QNAP depending on how customized it is. Ask me if you need help. As far as I can tell you need to ssh to the “admin” acount, so open a command line and type ssh admin@your-nas.
To make both tweaks permanent you need to edit /etc/sysctl.conf. you can try editing them with nano. If you don’t have nano you’ll have to try with vi, but vi is not intuitive at all to use.
nano /etc/sysctl.conf
The first tweak makes you a lot more effective to peers that are on unstable connections and on wi-fi. Google uses it for most of their infrastructure, originally on YouTube. You can read their article for more info on how it works.
Add this line to /etc/sysctl.conf, close nano with ctrl-X, and reboot:
net.ipv4.tcp_congestion_control = bbr
The second tweak decides how fast you can upload to people far away from you. If you calculate 2 * this value / your latency to them, you get the max speed you can upload to them. For simplicity I set it to be the same as my upload speed: let’s say you have 10 MB/s upload, that’s 10000000 bytes / second:
Add this line to /etc/sysctl.conf, close nano with ctrl-X, and reboot:
net.core.wmem_max = 10000000
This way even someone in Australia with 500 ms of latency can download at 10 MB/s from you, (2 * 10000000 bytes / 0.500s = 10 MB/s)
After rebooting you can check if the setting stuck with the command sysctl net.ipv4.tcp_congestion_control and sysctl net.core.wmem_max respectively.
For any of this to make a difference you should disable µTP in your torrent client, or make it prefer TCP over µTP.
To me it makes an enormous difference, from barely any upload at all to 100 GB per day. And I’m sure it’s nice for whoever is downloading on the other side to get what they’re looking for super fast.
It is possible by opening the network tab in the browser developer tools. blocking the “disable-devtools.js” script, refreshing, hitting play, saving the “resolve-token” as m3u8, feeding it to ffmpeg, figuring out how to fool the “track-progress” throttling…
It’s however much easier to just download the same film from rutracker. This is the 8 GB rip: magnet:?xt=urn:btih:9E4A961592C535DBEF9C8C66181CE7A6A002969A&tr=http%3A%2F%2Fbt4.t-ru.org%2Fann%3Fmagnet and there’s also a 40 GB full bluray available for best quality.