If you had the chance to create your perfect newsletter around Bitcoin, privacy, and self-sovereignty:
1) What would you be sure to include?
2) What would you definitely avoid?
3) What would you do differently than other newsletters?
If you had the chance to create your perfect newsletter around Bitcoin, privacy, and self-sovereignty:
1) What would you be sure to include?
2) What would you definitely avoid?
3) What would you do differently than other newsletters?
1000 sat zaps to the best answers β‘
Find examples of bad opsec leading to getting rekt
How to setup PCβs to not have internet surveillance, and how to manage Bitcoin without having KYC relationships!
Obviously, what is the difference between a non custodian wallet, a costodian wallet and what we mean by "Not your keys, Not your bitcoin"
1) Easy to follow guides for improving oneβs privacy
2) Avoid ads; zap funded
3) Live chat / Nostr Nests similar to Citadel Dispatch
Staircase concept to privacy especially for plebs.
π€― how much foundational security/privacy I didnβt have even prior to getting specific to π this π π£.
I would try to find real life examples and stories that highlight the importance of privacy. Too many people think that privacy is only important if you have something to hide. But usually the importance of privacy doesn't make itself apparent until it is too late. The more people value privacy in their everyday lives, the bigger of a push for privacy there will be in the products and services that are available to society.
- Best practices for UTXO labeling and management
- Puzzles to solve via OXT (see @LaurentMT on Twitter)
- Updates around privacy related BIPs
Honestly there is too much that would need to be included to make a simple list but I'll try.
1) Basic networking principles, VPNs, TOR, Dns resolvers, BTC, XMR, browser protections (like fingerprinting, auto cookie deletion, false profile randomizers, etc), self sovereignty through self hosting, what OS' to use and avoid (ie Windows vs Linux vs Unraid), sandboxing information with VMs or Unraid and so much more
2) Absolutely nothing. If I want to avoid it I would include how to avoid it.
3) No idea as I do not read newsletters usually.
I think I would just include actual advances/updates/products in these fields. I don't need to hear what's coming down the line, I just want to know what I can actually do today to improve my situation.
Love it, actionable content is so much more useful!
#plebchain π take as advice and not boosting.
You never know how other frens π« will value π«΅ ππ or memes π.
I was just scrolling and almost didnβt respond. Took 5sec to π and this π§‘π is the result.
Value for value
π§‘π€π

#[1]
Avoid the newsletter format and just keep posting quality content here on Nostr
#[0]
1) limits of privacy steps as it relates to threat models
ie: limit of a privacy phone as it relates to a government level adversary
2) avoid the esoteric/philosophical takes about Bitcoin. Thereβs already plenty of that
3) outline one practical step people can take at the end of the newsletter so the reader can put the post into action
I would always include a section for listing business that take BTC as payment, not advertising but just helping create a circular economy, and very varied stuff like where to buy eggs with btc, fruit, clothes, etc. And I would avoid making it exclusively american, and showing bitcoin economies worldwide instead so more people can join their own circular economies
1) Extreme privacy advice/practices, horror stories of the rekt,
2) white hat, osint, that which can be used for ill
3) find recurring contributors people trust, excerpts from Naiomi Blockwell, etc
Latest data breaches
Sorry, Rushed, signal dropping.
Include latest prominent data breaches, anyone sitting on fence to up their privacy may be persuaded.
1. Latest security advisories and news (a la Dark Reading but for bitcoin stuff), privacy and security tips and case studies of when a threat model fails.
2. The pump and dump defi stuff.
3. I'm not sure. I have yet to subscribe on a bitcoin newsletter.
Need to include how to move it around with OpSec in mind.
Getting it privately.
Moving it without having to be extremely technical but still being private.
Thanks for everything you do! I watch and learn from you all the time.