Jesus fuck thank you, it’s so hard seeing a bunch of doomer shit in threads like this

Kinda curious what kind of posts you were making that got you this sort of treatment: maybe running up against some hyper specific filters?

If you looked at the original github link, you’ll see that it has libadwaita (and naturally, gtk4) as a dependency.

This isn’t fragmenting anything, and adwaita already has good documentation. This is just another binding for another language, not a whole new implementation.

Blind brand loyalty to something you don’t enjoy is a waste of your precious time on earth

If you’re having issues with the core matrix integration, please file a bug! You never know who else might be having the same issue.

If you need to include a file from an external folder in your notifications, you will have to list the source folder as allowed.

https://www.home-assistant.io/integrations/matrix/

This applies to you.

You’re thinking of BD-R: BD-RE can be rewritten/erased hundreds of times

https://en.m.wikipedia.org/wiki/Blu-ray_Disc_recordable

I’d honestly prefer raw parroting in most cases, even if it’s “obviously” wrong. I don’t want people selectively interpreting the facts as have been conveyed to them, unless they’re prepared to do a proper peer review.

Though btw, I also think it’s fascinating the difference if you look up Pyhäsalmi Mine gravitricity "2 MW" vs Pyhäsalmi Mine gravitricity "2MW"

You’ll get different articles entirely

I googled Pyhäsalmi Mine gravitricity "2 MW" and EVERY article covering this has also cited 2 MW.

Now, under Occam’s Razor, what’s more likely:

1. Absolutely none of the article writers have any clue what the difference between a MW and a MWh is because none of them remember any physics
2. Some of them could suspect that it’s wrong, but an authoritative source of the claim wrote/said 2 MW capacity when they meant “2 MW peak generation” or “2 MWh storage” (I’d presume Gravitricity, but I’m struggling to find such a source, myself)
3. One writer miswrote/misquoted as per 2, and everyone is mindlessly recycling that original article’s contents with no attribution or care.

I don’t know which one it is. But I’d generally lean against 1.

As a Bay area native, I’ve never encountered worse drivers than the entire state of Maryland.

An API token is more secure than a password by virtue of it not needing to be typed in by a human. Phishing, writing down passwords, and the fact that API tokens can have restricted scopes all make them more secure.

Expiration on its own doesn’t make it more secure, but it can if it’s in the context of loading the token onto a system that you might lose track of/not have access to in the future.

Individual API tokens can also be revoked without revoking all of them, unlike a password where changing it means you have to re-login everywhere.

And that’s just the tip of the iceberg. Lmk if you have questions, though.

DAE enshittification bad!!1!

go fmt has been a thing for almost 11 years

So others have already talked about how great Star Trek is. I agree with them, but I think that literally everyone has missed the point of your question:

https://startrek.website

It’s its own lemmy instance. It was spawned from the migration away from reddit, and it’s stayed alive since. So combine an active former-reddit community with lemmy and a good reason to all rally around, and finally the final ingredient of federation, and the Star Trek related rooms will always be on every server, and they’ll always be populated.

Absolutely fucking me_irl

That’s only for a single service, not really what OP seems to be asking for

Fuck’s sake, people. Gitlab already didn’t allow search unless you were logged in.
This ain’t enshittification.

Depending on whether this code is in a hotpath (and considering how “elementary” it is, I figure that’s a possibility), this could very well be a significant speed improvement.

Though I’d say that only excuses it if it’s truly an elementary function (and not one line as part of a larger function), as otherwise it’s unreadable garbage. But on its own it:

• has a clear purpose
• (presumably) isn’t reimplementing functionality
• is easily tested
• can be modified with no side effects (besides breaking your calendar, but that’s beside the point)

Right? Like, I felt like I was missing the punchline here.