I don’t know. It’s a common practice though just look it up
ISPs turn off connectivity out of fear from lawsuits. Cox is contesting this, saying it’s too much of a burden (which it is) for both them and customers to turn off internet.
Its also fucking dangerous to do that in this day and age.
“Stain” doesn’t need to apply to the human visible spectrum of light
It’ll be easier to just fork QB at this point. Even features like “this torrent already exists in your list, would you like to merge trackers” are completely nonexistent in Transmission.
This is exactly the answer I was wanting. Thank you.
That also does not answer my question. I must’ve said it wrong.
I was wondering “if I run a single command with sudo, and the timeout to when I would have to enter my password again for another sudo is aay 5 minutes, and I run another command without sudo within those five minutes inside that same shell, would that command be able to maliciously elevate itself using sudo?”
That doesnt at all answer my concern but I’ll interpret the answer as no it doesn’t do that.
Its because investors will sue for not disclosing conditions when something goes wrong.
Because they dont need to
Okay. So you must invoke sudo fr on the exact same shell? It cant be taken from a subsequent script?
Can’t programs steal sudo access if the timeout isn’t 0?
I don’t know what the issue is. I genuinely think it’s because Transmission is entirely single threaded. Memory is fine, running at 50% utilized.
And it’s like 3-4 hundred ish.
just spread the torrents among multiple torrent client instances
No. Just… no.
Mullvad of course but they turned off port forwarding :(
NP. I’m gonna get way faster upload with qB, so yay. I used to do like a TB a day but Transmission has been sluggish lately. I’ve been limited to maybe a quarter.
Per day***
The headline makes it seem like it’s per lifetime or something.
Medical emergencies and devices are more important than protecting shittily-protected systems.