DEFUND THE STATE. CHOOSE #BITCOIN nostr:note12lpc5prgh0kp7qv5rjta6p63hzwlclkj3yj28wc7mjnf2qjlpjrsavzkre
Technically any client can that allows npub login. Just log in as your target npub, then go to the posts & replies tab.
What's the hardware advantage of a cold wallet, like nostr:nprofile1qqs9500z3l7sn46sdnls5fnjm0d3lqmrq7707qshes2y7j8pnm4rllcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtclyt6rh or any other device that looks like it's related to #Bitcoin and might draw undesired attention e.g. at airports or crossing international borders vs a self made simple USB wallet based on tailOS, as described in the article below?
And if there is any hardware advantage why not engineer the cold wallet with the most simple look of a standard USB stick or hard disk to avoid unnecessary attention?
Maybe Low-key is the secret key!
The purpose of a #Bitcoin signing device (hardware wallet) is to protect your secret material (seed, private keys) while in use. That is, during signing.
When your seed is at rest, there’s no need for it to reside on silicon. It’s just information. That information can be written on paper, memorized, stored elsewhere, etc.
Which way to store the information comes down to the purpose of travel. If it’s a permanent exodus, you might use multiple techniques to move seed material along with pre-signed transactions so you have plausible deniability and the ability to bail.
If you’re just traveling temporarily, then you probably don’t need to bring a hardware wallet with you. Leave your Bitcoin at home.
I still follow Twitter/X links posted in Telegram, just to read that specific content, but that’s about it.
#asknostr Which #nostr clients support automatic removal of tracking URL parameters? nostr:note1ehqf73gdlw5625szaek9524yzfj2gjlx5g4ae4y6jwsys884vfhshnqt6c
Once you give a client your nsec, technically, the client can sign whatever notes it wants. So if you’re serious about stopping replaceable notes, you’d want to individually inspect and approve each event JSON before signing. For example, you could use an extension (like nostore, the Safari plugin) with a web client.
In general you don’t need to worry about it. Clients that are for regular messaging will make regular kind=1 events for text, kind=7 events for reactions, kind=0 events to update your profile, kind=3 events for your follow list, kind=4 for DMs etc. You can browse a list of known kind number meanings here: https://github.com/nostr-protocol/nips?tab=readme-ov-file#event-kinds
In addition, clients tend to ignore events of kinds they don’t recognize. When your client subscribes to events from a relay, it sends a REQ message, which can include filters. It’s common to filter the events returned to just known, necessary event kinds. This reduces network traffic and bandwidth usage.
Some are. It depends on the kind number.
Each event (note) has a kind number. Kind=1 notes are regular text like this message to you. Kind=7 is a reaction. Kind=5 is a deletion, and so on.
Every event has a unique ID, and so they can’t be replaced by ID alone. Replaceable events have kind numbers in specific ranges. Based on the author’s npub, kind number, and tags (parameters) some events can be replaced by later events.
So for example, if you write a long-form article and want to be able to update it, you could publish it as a parameterized, replaceable event so that later if you want to make edits, relays will accept your replacement event.
You gotta go on Universe at different times and scroll for a while. Different times because different people live in different time zones.
#asknostr nostr:note10fc4373up5vgaecy6gqnwl35ksvx8z9rrclp3u46q3c6hs0x7znszr5e7q
Haven’t tried it. But I do hold my breath when driving sleepy to stay awake. Best strat I’ve found.