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.

I also used to read a lot as a kid then stopped for a long while. I have gotten back into it by reading before bed. I try to get to bed at least 30min early on most days—sometimes much earlier if I am having a lazy day or otherwise feeling like I don’t want to stay up—then I get a bunch of reading before bed. As a bonus reading makes me sleepy so I always nod right off when I put the book down (or sometimes have to put the book down because I am falling asleep and can’t keep my eyes open) I’ve managed to finish a good number of books already this year.

But I think the moral of the story is just find some time that works for you, reserve a bit of time in your day and try to make a bit of a habit out of it.

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.

This is my vote. I don’t know why the tax rate stops at 50%. Making your second million is easier than your first million, you should take home less of it. IMHO it should approach 100% as you make more and more. And the more money that you have the less valuable it is to you so we can put it to better uses for the society.

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.

To drive this point home, even if there are smaller alternatives voting for them is actively harmful in first-past-the-post elections because you are effectively giving an advantage to the party that you are least aligned with. (Look up the the “spoiler effect”.)

So in most countries the logical voting strategy is to vote for whichever of the two most popular parties you favour, even if the reason is just that they are marginally better than the alternative.

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.

Not just the first hit in general but this also sounds likely to be a bait-and-switch. They will roll with that free 1TiB as long as they can for marketing and market capture. They have a few profit streams (ads, whales on bigger plans) to help cover those marketing costs. But most likely they will not be profitable and eventually will reduce/remove the free plan and try to upgrade as many users as possible to the paid plan (reducing costs and increasing revenue in one go).

Yeah, carbon capture doesn’t math. I think the saying is that an ounce of prevention is worth a pound of cure.

The only reason why it is promoted is because the fossil fuel cartels push it as it moves the blame and focus from them to someone else’s problem. Then a bunch of garbage “carbon credit” companies start up and make a lot of noise while doing basically nothing. All the while they can keep pushing for fossil fuel projects because “it’s fine, carbon capture will solve it”.

Generally speaking it will be fine. SSH will also refuse keys with open permissions so you would notice if it was wide-open to other users of the device.

But you know if you are running random code or AI harnesses as that user it can be at risk. Or if you copy around the key all over the place it is more likely to leak. But generally speaking you are secure by default, just don’t do something dumb with the key and you’ll have no problems.

It sounds pretty reasonable. As long as you keep SSH patched and keep the key safe it should be quite locked down. Do double-check that password login isn’t allowed (or that all users have a very strong password).

One non-security note is be careful with rsync backup. Generally rsync isn’t considered a backup as any mistakes made in the source will be propagated to the “backup” on next sync. Although there are ways to use rsync to take good backups (like copying to a new directory for each backup).