Yes. I think we just need a cultural norm where indie instances proudly proclaim their indie credentials and the associated risks, while large reliable servers share how they are backed up and managed, as well.

Oh! Thanks!

No. Put the Genie back in the bottle. We need air traffic control for this shit. Or we just have to shut down all the PHP and NodeJs servers. (This is sarcasm…mostly.)

Allowing private corporations to have the ability to block what is seen on the internet seems to us to be a dangerous and infinitely deep problem.

Is a great quote, and gets to the heart of the issue.

But the French authorities are idiots. So there’s no win to be had, here.

Maybe deep packet inspection to drop any traffic that happens to be in the French langauge.

There are more important reasons geoIP blocking will not work. We already prevailed in a similar legal case in Germany in 2021-2023 in which we learned an important lesson: we tried to use geoIP blocking as a “hack” in a similar circumstance at the start of the legal proceedings, allowing us to continue services in Germany until the case concluded. The plaintiff (Sony Music Entertainment GmbH) then used a VPN to access the blocked content from Germany in circumvention of the geoIP blocking. The court agreed with Sony in their assertions of noncompliance, and we were fined for contempt of court.

A very “fuck you” to Sony, once again, as well.

We could start a buy/sell/swap space using existing Lemmy technology, if we left the messy details for users to figure out for themselves.

Messy details add up quick, though. Payments, currencies, mailing addresses, reputation, conflict resolution, returns, scammers and spam.

But “Craigs List” solved very little of that on day one, and went on to be pretty successful.

So it’s possible. happening now, I’ve just learned. Neat!. https://lemmy.sdf.org/c/buyselltrade

(Edit: Added link to the real thing. Thanks!) (Edit 2: I swallowed the onion whole. Mostly jokes, there, I think. I’m gonna leave the link anyway.)

It’s fine. I read all about it in the classic novel “Never Build the Torment Nexus”.

Come to think of it, I wonder if finishing the novel would help me learn how to build the Torment Nexus…? Oh, well. I’ll be too busy to finish the novel, since I need to spend all my time building the Torment Nexus.

We’ve done it. Humanity has achieved peak possible asshole design during the perfect alignment of the planets.

We can now create the Torment Nexus.

Never half-ass a transporter meld of two officers. Always kill the transporter abomination, to recover one full-ass vulcan officer.

If Neelix also survives, you can claim you did that on purpose, too.

I just want my warp core back, man!

Same here.

Rescue Dukat, obviously.* One careless mistake should not erase his ceaseless dedication to the citizens of the quadrant.

I heard it was mostly instigated by some Ensign she never promoted…

Oh shit! No dip!?

I always thought it would be…them. Exaclty them.

I plan to operate on expired certificates for two to four years, forcing all three of my users to click past a terrible warning.

Then I will automate my six day certificate rotation with Ansible (officially), but maybe actually with a stupid bash script in CRON (unofficially).

The real value is in the agility needed to update certs every six days.

Six days is still too long to leave a compromised key in play, but anyone who can rotate their keys every six days can probably also rotate their keys quite quickly if there’s a comprise.

+55653

Says everything I need to know about the change.

You put your hands on your hips!

A dozen, a hundred…? It’s impossible to resist.