Hi..I am a developer of zapddit. We are not using the same event to store the subscriptions today.
nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv is working on this at the moment.
Positively sometime this week you can use all 3 softwares using the same subscriptions.
Looking forward to it, thanks!
Why are community subscriptions on zapddit different from subs on nostr.kiwi and satellite.earth? They are not sharing the same lists...
Nostr is still early, weird and esoteric, but it is a real opportunity to escape the centralizing forces that they claim are inescapable. But you as a user make your own community here so if you don't like what you find that's on you, and certainly not a reflection of the protocol itself.
He makes a compelling argument.
#HasTanel ever played Never Have I Ever?
Looks like you’re already familiar? 🤔
nostr:npub1p93204359p3f2httnwktq69a0662p25gcpfv0ec9pfykc82u4y2sufcpwu People are fundamentally flawed. There's nothing stopping people from going to smaller instances, but they want bigger numbers and to be "where everyone else is."
People naturally flock toward centralization, and they naturally want a king despite acting like they want a vote. The average person just wants to be told what to do (while maybe making some vague, halfhearted protest against it). No platform or protocol can fix that.
You’re receiving my notes bridged from a protocol that already fixes this. I didn’t even intend to reach mastodon users, lol.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 bridging nostr communities with lemmy/kbin would be pretty awesome 👀
ActivityPub is fundamentally flawed as a protocol for the people. It’s built for institutions, not for people. 
Eventually they are going to have to support broader cryptographic functionality. The current situation is untenable and third party keychains can’t fill the gap without introducing additional attack surface. The only alternative is hardware keys but that gets annoying if it’s just for social stuff like nostr or PGP.
I often wonder why apps don’t have some standard method of requesting permission to sign messages with designated keys from the device’s keychain, without accessing the private key directly. Is that not something the keychain API can do? Feels incredibly primitive juggling private keys in different apps and relying on devs to be trustworthy and responsible and not screw you over in some supply chain attack.
Apple sent them a C&D
Would def appreciate this as an option nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
kaloudis just announced nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 no longer requires you run a separate lightning node 🫡
- embedded node on your phone
- no channel management necessary
- self custody as expected
- users will be prompted at first start if they want to connect to an existing remote node or create a new wallet
ok... neat
