I know that people like to dump on Cloudflare, but it's incredibly easy to enable a built-in CSAM scanner with CloudFlare.
On that note, I'd like to see built-in moderation tools using something like PDQ and TMK+PDQF and a shared hashtable of CSAM and other material that may be outlawed or desirable to filter out in different regions (e.g. terrorist content, Nazi content in Germany, etc.)
As much as I dislike Oracle, they've been pretty good stewards of the Java open source project, and haven't had any issues with anyone else rebadging the JDK, whether it be Zulu, BellSoft, Amazon, Microsoft, SAP, IBM, etc.
If anything, I'd like to see them put their money where their mouth is and hire Linux devs to continue Oracle Linux in an open manner.
Probably going to spin up an open identi.ca instance. It federates well with both lemmy and mastodon and does more. After that I'll probably whip up a script to automatically follow new accounts and communities to get it all federated into my instance.
XHTML 1.1 is much more elegant than HTML 2
Take a look at the prices at Costco. $40 for 25lb seems like a rip-off.
We get the jasmine rice there and it's showing as under $19 for 25lb. Just about 18 mos ago it was something like $23 for 50lb.
The calrose there is pretty good too if you like short grain.
The ability to insert flow charts on the go with the draw.io integration built in is amazing for technical documentation.
Joplin is nice, but I've grown to love Logseq for my notes.
In that vein, Dendron in VS Code or VSCodium is equally amazing.
Can you post them? Name and shame.
I use Pulsar every day at work. It's a great system. Highly recommended.
One thing, if you're using the Helm chart from the project, the default settings for Zookeeper/Bookkeeper/the broker are a little conservative and you'll need to bump up the memory a bit.
Also, although the Helm chart doesn't support it by default, you can override the command line to support S3 for tiered storage.
Same here. Jeroba would randomly crash. Connect hasn't yet.
It looks like it scans and flags on the outbound (user download of the image), so as long as it sits in front of your instance, it should work just fine.
You're still responsible for removing the material, complying with any preservation requirements, and any other legal obligations, and notifying CloudFlare that it's been removed.
It would be ideal if it could block on upload, so the material never makes it to your instance, but that would likely be something else like integration with PhotoDNA or something similar.