Dark Arc

It’s a lot more than a random text editor.

It’s a text editor from (at least some of) the people that made Atom at GitHub (with the explicit premise of learning from Atom/building a faster, better, Atom).

The business plan is to sell collaboration features (e.g., remote pair programming).

It’s far more common for Democrat run municipalities to create municipal cable and for Republicans to outlaw (or propose outlawing) municipal cable state wide.

It’s not even politicizing it’s a literal Republican talking point that the government should stay out of things and let free market competition sort these things out.

The problem with that of course is that they’d rather take money from some regional monopolies than actually create a free market system with reasonable restrictions on it.

I haven’t given Discord a dime from the start because I knew this was going to happen.

The entire premise of Discord’s free service was to gobble up the market from TeamSpeak, Ventrillo, and Mumble and capture the ecosystem using a ton of venture capital. In any sane world it would be an illegal mode of operation to provide “free service” based on venture capital like that.

TeamSpeak did manage to react but their reaction has been slow (I think they’re a much smaller team and still a private company). Their new client is fairly feature complete but still not out of beta (AFAIK).

Mumble is an open source project and is still ticking as a result as well (though obviously it’s received much less love since Discord stole the spotlight).

Google is introducing planned obsolesence in Fitbit

Have they? In what way?

They’ve done good work for Android and Pixel, promising 7 years of updates for the latest Pixels. Samsung has also gotten much better about this with their recent phones. That’s going to put a huge dent in the e-waste as Android phones have surely been heavy contributors (certainly much higher than fitbit).

TVs get bricked with firmware upgrades.

What TVs? Vizio, Hisense, the Chinese junk budget brands?

Very sympathetic to your e-waste concerns; I think the source of the problem is actually getting better not worse though. In general, the mobile tech sector is “growing up” and supporting products longer.

It’s called Voyager now

I don’t know enough about Lemmy’s JWT design, but some JWT designs don’t store the JWT in a database at all, so the only correct response is to regenerate the secret and kill all the sessions by them failing the validity checks.

No, you said you can’t generate valid tokens within the database. I just told you this is the secret, not the tokens (that is present in the database).

This is the secret, not the tokens.

Hm… They could’ve edited the config or just exit(1) if the credential is the default, but very fair.

Oof, okay well that’s not how I would’ve done it. The JWT secret in the database itself could be a vulnerability (e.g., someone that gains read only access to the database could then use that as a wedge to create any JWT they wanted). I’m not sure if that’s actually worth bringing up or not (it’s a bit of an odd case).

JWT secret keys are not in the DB (speaking typically, maybe for Lemmy they are, but that would be very surprising), that’s typically an environment variable or configuration file sort of thing.

In any case, this isn’t the part that’s broken, it doesn’t need fixed.