I'm not sure if you're joking or not, but the behavior of journald is fairly dynamic and can be configured to an obnoxious degree, including compression and sealing.
By default, the size limit is 4GB:
SystemMaxUse= and RuntimeMaxUse= control how much disk space the journal may use up at most. SystemKeepFree= and RuntimeKeepFree= control how much disk space systemd-journald shall leave free for other uses. systemd-journald will respect both limits and use the smaller of the two values.
The first pair defaults to 10% and the second to 15% of the size of the respective file system, but each value is capped to 4G.
That's a BSOD for DRM failures I think, not a generic BSOD like on Windows.
Assuming you mean texting style acronyms, yeah, we have them in German and I'd assume in other languages too.
Alongside the stuff borrowed from English 1:1, there's stuff like bb for "Bis bald" (See you soon) or hdl for "hab dich lieb" (Love you)
I'd assume other languages do the same out of efficiency or laziness.
What? I thought Nvidia didn't want to mainline the open driver??
Edit: Grrrr, clickbait. This is not about their open driver but as far as I understood about exposing a more minimal driver for vGPU usage, in light of development of Nova, a Rust based nouveau successor.
Are we really going to start this pointless discussion again? They are two licenses with different use cases and different considerations. GPL has a lot more mental overhead to using it, MIT is hands off, both of these aren't inherently invalid.
Also Tanenbaum in your own link mentions that Intel probably would have just written their own microkernel if need be.
What about the uh.... hate speech toggle....
I'm not sure if they backpedaled on that but come on.
Yeah, it's a technically difficult problem to deal with because you're probably often sharing an IP address or a block of IPs with bad actors. You can't really share details about it without giving them a hand.
I guess cynically said, you could probably go through their VPN service to fix it, I've seen that from time to time.
Essentially, their entire schtick is being a middleman. By sitting between the server you want to visit, they can do helpful things like DDOS protection, being a CDN (basically store website assets closer to you), managing HTTPS for you and providing access to your website over IPv6 even if your server doesn't have it.
By nature of that though, their position is quite sensitive since it has become a service that a good chunk of the Internet goes through. That causes concerns about centralization and pisses in a lot of people's cereals politically.
It's the same thing with different presentation, I highly doubt Valve is not aware of it, quite the opposite.
It's something that requires a lot of technical prowess to fix (especially to not disappoint the community now). I don't blame Valve employees with not wanting to work with it, especially with TF2 code probably counting as legacy nowadays.
In all fairness, Linux got 64 bit and Vulkan so maybe there's still some people interested but their damage control for bot chat spam (read, disabling chat for free to play) got flamed so that's not confidence inspiring.
You need to wander through links a bit to find it but https://ofourdan.blogspot.com/2023/10/xwayland-rootful-part1.html talks about the rootful and the recent changes.
I have a eating disorder so most vegetables make me retch, so I kind of don't have a choice.
Also companies do way more emissions than I ever will, yet I'm asked to stop.
Actual context is that iirc the bot posts wikihow titles with a random wikihow image, sometimes leading to hijinks
Blame the Mastodon team, if you're not running a fork, you have to go into the source and adjust the character limit manually.
Nobody has to do it like this, Mastodon supports longer posts since other servers and clients support more, it's seemingly just a choice from upstream.
Essentially functionally stripped sudo, smaller in size than sudo. See also Pottering's thoughts about the ecosystem
Holy shit the comments on this one are vile. If you don't like the article, don't read it and go on with your day.
The footer of the blog shows a Nix file structure, skimming their blog they wrote a bunch of articles and guides for Nix, checking their repo they have a bunch of Nix work, they're not exactly a nobody (if you couldn't judge from the people saying they'll miss them on the Nix forum post)
This entire article is an extension of https://save-nix-together.org which is the actual thing that sparked the the gasoline covered Nix community, this will probably seem more coherent with that background.
