No mention of vaccines
You agree with the idea?
Try Organic Maps 👌
It's time to start my GrapheneOS journey. Any tips/recommendations for starting?
My plan:
1) Use the owner profile only for administrative purposes.
2) Whenever possible, use nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 and Obtanium.
3) Avoid unnecessary apps.
4) Don't be too restrictive; it's a midterm project.
So good to see more and more users care about their privacy. Do not forget though: The tracking and spying is on multiple layers.
The nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43q4gnztg shipped browser (Vanadium) does not protect against HTML Canvas Fingerprinting per default.
Check your traces here:
It's time to start my GrapheneOS journey. Any tips/recommendations for starting?
My plan:
1) Use the owner profile only for administrative purposes.
2) Whenever possible, use nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 and Obtanium.
3) Avoid unnecessary apps.
4) Don't be too restrictive; it's a midterm project.
Congrats and welcome to the fam!
I am using the main profile for applications that do not compromise my privacy, e.g. do not need Google Play Services. For everything else: Sandboxed profile with GP services, disabled cross-profile-notifications.
Also consider de-googling yourself. I have moved everything away. Feels much more natural to not use Gmail or Gmaps.
There are alternatives for everything.
Never been more glad for nostr:nprofile1qydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gqyp59v0qjxury4x3jn7a6gcuh299maysnupweqpffx88rz5wfwcrlq7neddl 's secure sandbox than when running Claude Code.
Running AI generated code on anything else than a sandboxed environment is craizy..
Ok so the best way to solve this is using a dedicated account of your wallet and deducting from child extended public keys. In this way only a subset of your public keys will be exposed.
nostr:nprofile1qqs9zs7rw003k4y2wltea360yuj46y5md9d4yt0mt06rfx96fdgpm7gpzamhxue69uhkummnw3ezuct60fsk6mewdejhgtcpzamhxue69uhkummnw3ezuan4d3cx2mfwvdhk6tc5plgka As far as I understand it, the payment request includes the xpub at path 47. So the privacy will be slightly improved by not sharing all (?) paths of the xpub I guess?
The broker example was bad. A better examplr would be a Mining Farm Provider, where you need to configure your Payout Adresses. No KYC.
Yea, but I think they have implemented BIP 47 version 1 (or 2) until now. Seems like version 3 RFC is final but yet not implemented.
Do you know any implementation of BIP47 Version 3?
True, but let's say you want to make use of this in a non-kyc context..
Is there a more privacy friendly way to achieve changing public keys then sharing your xpub?
Example:
I am buying Bitcoin from a broker and instead of changing my BTC address everytime, I would like to have it automatically pick a new one each time. I have seen some brokers accept xpub, but this means they know ALL of my pub keys which is a privacy problem imo.
Ideal would be something like a partial xpub, where I can decide how many pub keys are being shared.
#asknostr #xpubprivacy
Super useful. Could also be built in nostr flavor.
