leftyspook

The sensible regulation would be aiming at socially harmful features of tech, not forcing people to provide proof of identity to a third party in order to continue harming themselves with the same exact features.

Imagine if such an approach was taken to, for example, food safety? Instead of closing down a restaurant that has poor hygiene, you'd be instead horce the restaurant to hire a private security contractor to check people's IDs to verify that they are old enough to consent to getting a foodborne illness. That's an absurd approach.

All software runs on somebody's hardware. Ultimately even an utterly benign program like `cowsay` could be backdoored to upload your ssh keys somewhere.

The meat brain is the only one that can be held accountable.

Do you think the attention and engagement is because people think this is some sort of an "ai misalignment" thing? No. AI misalignment is total hogwash either way. The thing we worry about is that people who are misaligned with the civilised society have unfettered access to decent text and image generators to automate their harassment campaigns, social media farming, political discourse astroturfing, etc.

I think when Fish shell announced the Rust rewrite, they especially highlit that, in the form of "being more attractive to contributors" as one of the reasons.

> I'm not 100% clear on what you mean here

The core of their complaint is that if you use `jj edit` it's not obvious how to get a diff of what you did. The answer, of course, is that you can use `jj evolog -p`.

Ah, I see Tom the Genius has moved on from using Subversion for his enterprise JSON DSL

I think a part of the point is to question the need for things like that. Do your users actually need all of these bells and whistles?

Nothing changed, you need to know that host:port first, and that's where the problems with the official serverlist being flooded with fake entries become apparent.

That really is not a solution.

Third party servers used to host plenty of non-standard gamemodes that Valve does not provide. Retakes, mentioned in the blogpost, is one of those modes.

Could it be that it gets no credit for things it got right because it got barely anything right?

I think you make a pretty bad case for how embedding a Scheme interpreter is going to help with the pain points of async. Listing "stack traces full of tokio code" and then seemingly proposing to solve that by adding more glue to pollute the stack traces is especially weird.

I'm not saying they are related, just saying that the committee committeing is going to take half a decade at least for both.