Just be sure to pause for garbage collection occasionally.

I’m pointing at the architecture, not the specific implementation. Build something like Spanner, not something like a blockchain.

1a. I must have misunderstood the problem report.
1b. No wait, holy shit, how did this ever work!?

2a. The director reminded us, at the last all-hands, that we should escalate to senior members of the team if we don’t know how to check our work.
2b. … yeah, they’re at Burning Man.

3a. Remember, they knew I didn’t have a CS degree when they hired me. Dammit Jim, I’m a chemist, not a compiler engineer.

4a. It could be worse. I could be back in academia.

5a. There are more cute people in academia.

6a. HOW THE FUCK DID THE THREE-HOUR COMMIT QUEUE NOT CATCH THIS BUG BEFORE IT WAS PUSHED ON FRIDAY AFTERNOON?
6b. (looks up author of broken commit) Oh, we need to send more whiskey to that team on Friday mornings. That’d shut them up.

7a. … yeah no, imma run the regression tests another time against an unchanged repo
7b. … resync and run them again
7c. … fuck, this is fucking voodoo but imma do it anyway WHY DID IT BREAK NOW

8a. Wow, fixing that took, um, four actual bytes of delta?
8b. Everyone should slow the fuck down and see if they can fix all their bugs in four actual fucking characters of change to the actual fucking source code.
8c. What the fuck do I know. Megan committed 924 LOC last week that fixed lfile caching, and caught the btqmixer bug.

9a. Sleeeeeeeep.

This surprises me since Cloudflare has AAAA records listed for lemmy.world. Do you know your way around tcpdump? If so, it might be interesting to see what’s happening with traffic to those addresses. My desktop doesn’t have v6 right now (sigh) or I’d be testing that myself …

That’s its goal, not mine!

A game has a set of goals, and you can quit it without dying.

If there’s no set of goals, it’s not a game, it’s a toy.

If you can’t quit it without dying, it’s not a game, it’s real life.

(Does real life have a set of goals? Depends who you ask.)

Have you ever been a developer of a project that has a lot of public comment on it?

On the other hand: Many comments from people unfamiliar with the code base and the project organizers’ plans are unlikely to be useful to the people actually doing the work. Discussions that are low-signal/high-noise are likely to be simply ignored by the people actually working on the code.

Sure, for Lemmy instances who are Cloudflare customers. But I don’t think it can be integrated with the Lemmy code by default.

On the other hand, if the people who want those images can satisfy their urges using AI fakes, that could mean less spreading of images of actual abuse. It might even mean less abuse happening.

However, because they’re terrible people, I have to suspect that’s not the case.

Even without the issue of new AI-generated images, those hash-based scanning tools aren’t available to hobbyist projects like the typical Lemmy instance. If they were given to hobbyist projects, it would be really easy for an abuser to just tweak their image collection until it didn’t set off the filter.

Doc, if you can’t count to 1023 on your fingers, you might be doing CS wrong!

Spanner.

C[], the language of buffer overruns.

If you think you’ve found the one honest snake-oil salesman, you’re almost certainly wrong. That’s part of reality.

Theoretically? Sure. But in reality, blockchain pushers are fanatics, scammers, or both, so no real organization should trust them.

They don’t have to. If you don’t have database replicas that are actively trying to subvert the system, inject bogus transactions, etc. then you don’t have the set of failure domains for which blockchains are in theory useful for.

If you’re running backups for a single organization, you just need replicated data storage on servers owned and operated by that organization. If you’re running backups for a set of users who all trust your organization (e.g. if you’re Dropbox or the like), you also don’t need blockchain.

If a single organization owns all the servers, there’s not even in theory a reason to prefer blockchain over a plain replicated database. And in practice anyone who’s pushing blockchain is either an ideologue or a scammer; either way they don’t have the user’s best interests at heart.

What you want in that situation is called a “replicated database”, not a “distributed ledger” and certainly not a “blockchain”.

A blurry chunk of screenshot that someone bled on, that’s what.