r00ty

Ah, so the kind of crypto bro, that instead of a fistbump, does a diffie-hellman key exchange instead?

Because, starlink and their investors probably want users in Brazil to be able to pay them for using the service. And, you know without the government's support that would likely become a problem.

Here's what I think. Both opinions are correct.

Rust is sufficiently different that you cannot expect C developers to learn rust to the level they have mastered C in order to be working at the kernel level. It's not going to happen.

I don't really know too much about rust. Maybe one day I'll actually mess around with it. But the one time I looked at a rust git repo I couldn't even find where the code to do a thing was. It's just different enough to be problematic that way.

So I think probably, the best way IS to go the way linus did. Just go ahead and write a very basic working kernel in rust. If the project is popular it will gain momentum.

Trying to slowly adapt parts of the kernel to rust and then complain when long term C developers don't want to learn a new language in order to help isn't going to make many friends on that team.

I would agree, but there's been at least two updates in the last six months that restarted my machine before I even got to see the pending restart warning. I use it every day and shutdown if I won't be. So the restart happened less than 24 hours after any warning if there even was a warning.

That has the potential to lose things I'm working on. Windows pathetic attempt to bring things back falls woefully short of functional.

Flash up alerts to say there's critical updates, but the action to actually restart should be a human interaction.

I was a teenager, it was a dual carriageway with no pedestrians.

Not that it's any of your fucking business you fucking plank.

Nah my local expensive hipster craft beer place usually has 6 on tap. One will usually be a UK style ipa, 2-3 others will be a mix of USA/oceana style pale ales. One local brewery and one non pale ale (blonde, Porter, stout etc)

But you really can't tell until you try them.

Because, that's what the police told me it was.

I was caught, many years ago. 78.94 in a 50. I was driving a 1988 ford fiesta 1.1 (hint you don't even get an engine that small in the USA, I think 1.6 is the smallest in a fiesta). So in a proper car? That's got to be easy.

That's got to be extremely rare. Not much you can do in that case. But they will hit many problems with that approach.

That's weird. I'm getting to the age where I wouldn't see the point in 4k, I'd need to have my head on top of the screen to see it. But refresh rate can be felt in fluid scrolling etc and definitely even if only on the unconcious level, improves awareness in games too.

Lithium batteries have a very high energy density. When that's released all at once with a short circuit or very high current draw resulting in thermal runaway, that's when these fires start. The great news is, they're self fuelling fires too!

But, most reputable manufacturers, create charging/protection circuits that protect the batteries against such situations. Making them far less likely (but still possible) to happen.

The problem you're going to get is when there's disreputable companies, operating in countries with less stringent safety laws that are operating the production, processing and shipping entirely outside of the sight of countries with safety rules. Well, then you get a product with a fake FCC/CE sticker on it, that is very dangerous indeed.

I will not buy electronics from those sites for this very reason. Batteries, chargers and power supplies are usually very shoddy from these companies.

It's not to say don't buy stuff made by country X. Because there's plenty of stuff I have bought made in, these countries but sold by companies that DO make sure there's some testing done, and they're not fake stickering everything. But, we all know the companies I'm talking about I think. Also, ebay (because private sellers buy in bulk from these places and then resell them) is something to be careful of too.

When you post in a thread you get an ID for that thread. When you post in a different thread you get a different id.

That's what I said. You don't need any ID to federate the messages. If you reply to a comment the nesting is based on the comment/post ID and not the usernames.

You couldn't track a users posts after the fact, and I think that's kinda the point.