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.

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.

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.

Not so sure that's true though. If you look at a 4chan threads in some boards, you can recognize the individual anonymous' from the ID next to them.

I suspect it's using either a cookie, or the IP address to track a user and while not storing that info, generating an ID hash from perhaps a unique ID for the thread + their details.

No reason you couldn't federate using the same. But, even without that, each post and comment has a post ID and replies would be tracked that way. Just, you'd need to remember which replies were your own.

The home instance could store for a thread some info about posts/comments from an IP or cookie too and highlight them. But that info wouldn't be federated.

I actually don't think it'd be a problem, really. But, is this something missing from our lives? I'm not so sure.

It should be protected against. But, you know if a business changes to dynamic pricing and their next quarterly numbers shows that the vast majority of people didn't swallow it, and revenue is hugely down, they would undo it in a second.

The fact is, though. They know enough people WILL let them them get away with it. From their point of view, why would they turn down free money?

I mean, while they can block most things, to give people a usable experience they're going to allow http and https traffic through, and they can't really proxy https because of the TLS layer.

So for universal chance of success, running openvpn tcp over port 443 is the most likely to get past this level of bad. I guess they could block suspicious traffic in the session before TLS is established (in order to block certain domains). OpenVPN does support traversing a proxy, but it might only work if you specify it. If their network sets a proxy via DHCP, maybe you could see that and work around it.

I did have fun working around an ex gf's university network many years ago to get a VPN running over it. They were very, very serious about blocking non-standard services. A similar "through" the proxy method was the last resort they didn't seem to bother trying to stop.

I don't think users should reward the behaviour. If they actually lost money because of these decisions, they would stop making those decisions.

But, we both know enough people will bend over and take it.

But, in terms of cost it can be a good move. It's just for us, it makes at best, no difference.