Yeah, anyone can claim whatever they want. Making other people respect your claim is the hard part.

Source: https://beige.party/@intransitivelie/117057396732763183

Why is everything screenshots these days :(

We actually do. Libraries are traditionally named something like libfoo1.2.3.so. Then there are symlinks from libfoo1.so and libfoo1.2.so. This way you can depend on libfoo1.2.so and it works fine even if the user has libfoo 1.2.6.

Now there are lots of problems here.

1. It would require distros to ship multiple versions. This is a lot of maintenance work so it typically only done for very core libraries.
2. It requires applications to accurately express their dependencies.
3. It doesn’t work very well for version ranges beyond patches (I need at least version 1.2, but version 1.3 is also fine).
4. It requires the library maintain binary compatibility which is difficult to do in C and C++.

So yes, shared libraries and careful management is more elegant and efficient. But like so many things worse is better so “It works on your machine? We’re shipping your machine”.

My first thought: If it isn’t always running it honestly not a major concern how much memory the weather app uses.

My second thought: 1.2GB WTF? Ok, that is way over the top. The executive in charge should be fired.

My third thought: 250MB? That is still a little unnecessary, even if it probably does fall under the “doesn’t matter” threshold.

My fourth thought: gnome-weather uses 180MB, not great, not bad.

I really don’t care what you use but I highly recommend picking something extensible or fully featured. No need to cut yourself off of valuable tools.

(Also I use Neovim BTW)

If you only take the bottom (lowest) 1% of all frame rate measurements (and average them)

I don’t think that is the methodology. I think it is taking the 99th percentile frame time. So basically if took the time it took to generate every single frame this is the time that 99% of frames were faster than and 1% were slower than.

If this number goes down it means that the worst frames are less bad. This is a pretty important part of the experience as even if you have good average frame time (and decent FPS) having a few slow frames really makes the game feel choppy and can make precise inputs difficult.

Honestly AI has been used for moderation for decades. The newer models will be quite effective. It could be very useful for limiting lower effort spam. Sure dedicated spammers will figure it out and get by it but as the models get better that will get harder.

Of course like every use of probabilistic technology like AI it should still go to human review. We shouldn’t be shadowbanning people because computer said no. But holding suspicious posts in a review queue for the moderators seems quite reasonable (much like they already do with their current systems).

Honestly this sounds more like an investor update showing how innovative we are using modern technology and how it is going to really improve the platform and stonks will go up up up than any meaningful change to their current moderation systems.

In theory it is safe. When a Nix package is built it isn’t “installed”. Unless root is running/installing random packages out of the Nix store there is no problem. As long as the user’s aren’t added to the trusted-users option they shouldn’t be able to cause any problems for other users.

However like any multi-user system you are sharing a Linux kernel. A kernel is a very complex piece of software with a huge attack surface. Privileged escalation vulnerabilities are commonly found. (This also applies to the nix-daemon, but it is a bit smaller attack surface but vulnerabilities are still occasionally found.) So you shouldn’t assume strong security isolation. I would say that a setup like this is acceptable for mostly-trusted people like coworkers or friends that are not expected to actively exploit vulnerabilities but definitely wouldn’t let random unknown users use the system.

So if you want strong isolation use a VM or separate hardware, but then you won’t be able to share the builds and packages defeating the point in this case.

Every team has a QA environment. The fancy ones have a separate production environment.

In most distros shutdown is a symlink to systemctl.

Apple is a lot better than Windows but slowly getting worse. They keep pushing their own services more and more aggressively while the quality of their software drops over time. Not to mention that iOS is so locked down that they don’t have to worry about things like pushing Edge because they just don’t allow any other browsers.

Oh, right. The OP is wrong it appears and I didn’t think much 😆

2026-06-27 to be unambiguous. (About two hours in the future from time of posting)

Edit: Actually 2026-07-27, OP has the wrong date.

declaring multiple variables is less error-prone than in C. In C, the following declares x to be a pointer, but (surprisingly at first!) y to be a normal integer:

int* x, y;

Whereas the equivalent in Go does what you’d expect, declaring both to be pointers:

var x, y *int

I don’t think this is a related at all. C could have easily decided that the definition makes both x and y pointers. They just decided not to so that you can declare more variables on one line by being able to do int x, *y, **z, .... It is more flexible.

Similarly that Go line could have been parsed like var x, (y*) int if they wanted to. They just made a different choice.

I’ve definitely ran into the situation where I fucked something up half-way though installing a new distro, then had to wipe it to go back to an old distro so that I could access the internet and find out what I did wrong so that I could start from scratch.

I hate doing debugging on my phone, but man sometimes is it better than the alternative.

Because not everyone has or wants credit cards. Children can’t get credit cards. Code cards are also useful for gifts.

I think you are right that even less people will buy them than physical games, but I don’t think they will be irrelevant.

Trump doesn’t appear to care much about the law.

I understand that this is frustrating but it is arguably the right option. If the correct owner can recover the account without TOTP then the TOTP isn’t really protecting the account.

Of course there are various ways to authenticate and it can make sense to have authentication to be (username + password + OTP) OR (email verification) but for a lot of people that email verification is a weaker link. It is more secure to only allow the former.

What I wish is that more sites would document their account recovery procedure. Often times they ask for a phone number for verification or notifications and that silently becomes a backdoor into the account. Even better would be if users can select what authentication combos are supported on a per-account basis (there are a few companies with “lockdown” settings that are a simplified version of this).

Of course it then becomes important to make it clear to the user “if you ever loose you X your account is forever lost”. It shouldn’t be surprise.

This advice feels like “Have you moved to the surface of the sun? Make sure to drink lots of water.” It’s not wrong, but also not particularly helpful. The only solution is to stop buying these things. Ideally take them back and get a refund if it isn’t too late.

We have all evaluated the options. Most of us decided that sewing was in fact too extreme.