There is no way to control user devices and the software they run for any of our open protocols, so there's simply no way for server providers to scan E2EE content transmitted via their services. Let them cripple WhatsApp and Signal. Why do you care so much?

I'm watching kind 4 direct messages from popular relays in a live stream, and it feels almost as dirty as watching the Venmo firehose, albeit with encrypted content at least.

Enjoying noStrudel a lot! Looks basic at first, but is actually much more capable than most clients. And yet, it feels lightweight and fun.

Hooray! Just before the end of CEST Sunday, I have completed our strfry LDAP policy, which only permits known users to write to our #nostr relay!

Gitea

Add strfry policies and members-only LDAP policy

This will look up nostr pubkeys in the LDAP directory to allow or deny publishing notes to the local relay. Works out of the box with the Docker C...

(Beware that you will need to register the nostrKey attribute in your server's schema to make it searchable. You can find an LDIF file for that in the akkounts repo as well.)

Every time someone inquires about my "career":

I wish octopi weren't so damn delicious, because I frequently have to contend with the predicament of both admiring their intelligence and wanting to eat them.

Fun fact: I'm getting notified via #xmpp when you zap me on #nostr, because we're mixing up and connecting various decentralized protocols in our (open-source) accounts back-end. (And for secondary accounts I usually set it to notify via email.) Also, I log into my Kosmos account using my Nostr key via @Alby. Many more integrations to come! Currently setting up our members-only relay, so we can do things like auto-sync notes and media to a user's #remoteStorage and such.

I just fixed a small bug in our Zap (NIP-57) implementation, which broke the creation of receipts in production. Zap me 1 sat so I can test it more extensively!