Yeah, it’s old, but it took effect this month for existing customers, hence why I noticed.

Thanks for the suggestion. Any issues with the transfer speeds?

What hardware strain are you concerned about? Seeding is just a read, which is pretty gentle on hardware, especially if it’s an SSD.

The bigger concern IMO is saturating your bandwidth, making other things perform poorly, but then you can just cap bandwidth.

The lazy approach is the best approach IMO. Seed everything, and if the ratio gets high, drop it. That way you get rid of useless popular torrents and keep the less popular ones. If everyone does that, things will work better.

That’s a big part of why I stick with my ISP. My download speeds aren’t super competitive for the price, but my upload is half my download, which is nice.

Yeah, I always went for 2:1. It doesn’t really cost me anything, so why not?

They’ll just settle if the case isn’t going their way.

Same. We have two grocery stores nearby, both with loyalty programs. One requires using the program to get discounts, while the other doesn’t (you just miss out on points). Guess which I shop at…

If I need to go to the other one (Kroger family), I’ll use my parents’ number so they get the points. I go maybe once/year if there’s a particularly good deal.

Yeah, that’s a nope from me. I’m trying to eliminate as many apps from my life as I can.

Wait, is everyone using the same account or something? Why don’t they just use whatever email account they already use?

Proton just sends and accepts regular, unencrypted email, which is totally fine for something like a casual game. Whether you use Proton or something else is irrelevant, all that matters is that your end works.

I’m in a red state with GOP reps. I really don’t think any of those will go anywhere.

And not sure what going on strike would accomplish. My company isn’t based in the US, my boss isn’t American (and likes Trump), and 2/3 of my team are outside of the US anyway. I like my company and my boss, and going on strike would just get me fired for no reason. Why would I do that? My company didn’t donate to him or anything, so how would pissing my boss off accomplish anything?

The only effective measures I have would put my family at risk, and those have a remote chance of working. Why would I do that? It’s illogical, especially when the chances of Trump actually becoming a dictator are slim to none.

I’m not going to screw up my life just for some internet cred. I’ll do what I did in the last three elections: vote against him and urge those around me to do the same. Not that it matters, because the Republican will always win my state and district, but it’s something.

The most effective use of my time is to largely ignore him. Anything else is illogical IMO.

That does literally nothing though. Buying a share of a company is like buying a used product, none of that money goes to the company. The only benefit to a company is the share price rising, and your contribution to that is effectively zero, and it only matters if the company issues or buys back shares, which is somewhat rare.

It’s the same reason that buying “green” shares does nothing.

Invest based on what’s most likely to give you a good return, even if you don’t agree with their products. And then buy products based on your convictions. If you want to feel like you’re “sticking it to the man,” use the profits to buy from their competitors.

No we don’t. Trump deserves to be kicked to the curb, but Americans are absolutely fine, if a bit short sighted.

A country is not its leadership, it’s the people. And it’s incredibly hard for the people to replace their leadership outside of election season, and even then, there’s a lot of pressure to make poor choices on your ballot.

We don’t really make anything though, aside from software I guess.

That’s a bit of an extreme take. Surely you can see some differences between them…

Let’s do it again! Let’s make sure nobody can break his record for impeachments.

Does Proton bridge work? I know nothing about that game.

It’s not like Linux compiles down to one binary or anything, most of it is linked together over a pre-determined API. Anything that can satisfy that API (and ABI) can drop in. There are some “magic” bindings, but they still conform to that API.

Read the rest of Greg KH’s thread, here’s the last half of that paragraph:

Adding another language really shouldn’t be a problem, we’ve handled much worse things in the past and we shouldn’t give up now on wanting to ensure that our project succeeds for the next 20+ years. We’ve got to keep pushing forward when confronted with new good ideas, and embrace the people offering to join us in actually doing the work to help make sure that we all succeed together.

And earlier:

Rust also gives us the ability to define our in-kernel apis in ways that make them almost impossible to get wrong when using them. We have way too many difficult/tricky apis that require way too much maintainer review just to “ensure that you got this right” that is a combination of both how our apis have evolved over the years (how many different ways can you use a ‘struct cdev’ in a safe way?) and how C doesn’t allow us to express apis in a way that makes them easier/safer to use. Forcing us maintainers of these apis to rethink them is a GOOD thing, as it is causing us to clean them up for EVERYONE, C users included already, making Linux better overall.

Those are solid arguments. As long as the APIs are well designed and documented, a mixed codebase is fine, and you get most of the benefits of Rust where it’s used.

True. We should have both better tooling and better languages. Someone posted this thread with Greg KH, which has this gem:

The majority of bugs (quantity, not quality/severity) we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory (not that rust can catch all of these by far), error path cleanups, forgetting to check error values, and use-after-free mistakes. That’s why I’m wanting to see Rust get into the kernel, these types of issues just go away, allowing developers and maintainers more time to focus on the REAL bugs that happen (i.e. logic issues, race conditions, etc.)

I’m all for moving our C codebase toward making these types of problems impossible to hit, the work that Kees and Gustavo and others are doing here is wonderful and totally needed, we have 30 million lines of C code that isn’t going anywhere any year soon. That’s a worthy effort and is not going to stop and should not stop no matter what.

But for new code / drivers, writing them in rust where these types of bugs just can’t happen (or happen much much less) is a win for all of us, why wouldn’t we do this?

In short, let’s do both.

For the lazy, I liked these parts:

Rust isn’t a “silver bullet” that will solve all of our problems, but it sure will help in a huge number of places, so for new stuff going forward, why wouldn’t we want that?

…

Yes, I understand our overworked maintainer problem (being one of these people myself), but here we have people actually doing the work!

The whole thing is great.

Exactly. The kinds of things Rust yells at you for, you should consider changing in C as well.