Every time I explain joinstr to a new developer or user, I realize the documentation isn't helpful. I hope this e-magazine makes it easier to understand.
Basic tool to download a text file with all the ids for NIP 4 events in which entered pubkey was sender. You can try deleting these events either one by one or in batches using other tools.
Bring Your Own Algo: https://uncensoredtech.substack.com/p/bring-your-own-algo
My favorite tools in nostrudel 'tools and other' stuff section:
DM Graph and DM Timeline
Exploiting SGX: https://xcancel.com/_markel___/status/1828112469010596347
1. First thing you can do as capital provider is to stop misleading. Its not necessary that only CEOs will get arrested. Tornado Cash smart contract still works and being used.
2. Nostr is a bunch of clients and relays. Clients can censor, in fact there are NIPs for it: NIP-56, NIP-51. Relays can censor some events and a few relays share this info using NIP 11.
A nostr developer and relay operator can be asked to "moderate" and they do control things.
3. Even ecash is being promoted as censorship resistant although its not. Mints can enforce KYC for mint, melt, swap etc. at some point and censor some users based on different things.
Joinstr R&D Group (simplex). Wont be active on telegram anymore.
I think this is possible on nostr as well if you share a key with all the followers and encrypt each post. Is there a better way to achieve this?
BIP 8.5: Flag day activation based on nLockTime signaling
https://delvingbitcoin.org/t/bip-8-5-flag-day-activation-based-on-nlocktime-signaling/1078
Best bitcoiners believe in freedom and let others use whatever they want for social networking.
You can fork protocols the same way you fork any open source software. I will share the link and NIP1 equivalent when I do it.
This is nostr in a nutshell. I am not sure if its the best way to create a censorship-resistant social network. A fork of nostr that focuses on privacy, security and multi-party bitcoin protocols could work better for all use cases.
BIP and 1 implementation by the end of this month.
Fractional reserve is possible with all custodial solutions, including ecash. Anyone who says otherwise is trying to scam you.
Send me some testnet coins to this address: bc1p7w5xk76j3cufczuruayl0h4kv8e02q4xan3e5qxxl8yvafp2tnrqppxjge
Even I am using it for testing something.
Mint ecash from thin air on each refresh: https://thismoneydoesnotexist.github.io
NIP 9 and NIP 40 allows clients to request deletion of events. Relays delete them most of the times. Not looking for security but to avoid manual deletion of events after shitposting. A user could enable expiry, shitpost for a few hours and forget it.