This is some steak saving advice
View quoted note →
m4d4m
npub1m4d4...c2n3
-(/*<>*/)-
// whatever //
Still @Amber is the best and only usable solution known to me (for Android) keeping nsec usable (outside of passwd manager) yet quite safe.
And also not that hard to use for an average user.
The ongoing problem is clients not respecting the user’s choice.
For example, YakiHonne doesn’t respect the push‑notification decline and cannot let me leave the app if I do not confirm it.
Sometimes there are many requests for one event.
0xChat asked me for many confirmations for a single message iirc; I have no idea what I’m signing for, so blindly confirming them all.
View quoted note →
Still haven't figured out how to choose a 'good relay' and what it is even.
In Amethyst, at least, there is nice description what each type of relay is good for.
Except for @Citrine (many thanks @greenart7c3 ), that is by design a good relay.
View quoted note →
@M¡lan this may be interesting for you
View article →
This guide still holds great.
Surprised how not many users (even the technically knowledgeable base of nostr) taking advantage of having npub personalized a bit.
Possibly because it's not just a common knowledge.
Or maybe, as NOSTR clients tend to shorten the npub, it's mainly hidden a lot.
Would be great if npub1 part is ommited entirely as it doesn't carrying any meaningful info from my perspective.
(This tool allowing the few last characters to be the part of the pattern, so this solves the problem a bit.)
View article →
There is this https://delete.nostr.com/.
Works perfectly; the notes are deleted.
But the likes, boost, zaps, and alike are still present in the network.
Is there a way to broadcast the kind 5 for them as well?
#asknostr
Installed @0xchat.
Someone with whom I would like to connect also uses this client.
We both have relay.0xchat.com as DM Inbox
Yet I'm getting only this:
and followed by this:
When the QR code generated in the next step, 'Invite Friends,' is shared with the other party and scanned, the attempt times out.
What we are doing wrong?
and followed by this:
When the QR code generated in the next step, 'Invite Friends,' is shared with the other party and scanned, the attempt times out.
What we are doing wrong?Installed the tlp because I wanted a battery management but later found out it didn't support my HW.
Sadly the tlp uninstall(?) in the process the power-profiles-daemon.
At least in my case I had to install it clean to have the power menu back again. Simply systemctl enable the service nowhere to be found.
C'mon, why.
Interesting, if I understand this correctly:
1) the trade-off is basically about how much time to allocate. Balancing the potential leak damage (timespan) versus nsec access frequency (how often to create epoch keys).
2) this basically gives me (or the nostr client) a temporary key to protect instead of using the nsec for each event.
Have other solutions been proposed? If so, why weren't they implemented?
(
View quoted note →

Untraceable Digital Dissident
Cold Root Identity for Nostr: How Epoch Keys Fix the Hot Key Problem
Nostr identities break when a single hot key leaks. This guide shows how cold root keys, deterministic derivation, and rotating epoch subkeys creat...
Have private bookmarks (in Amethyst) and would like to transfer them all into another account (under a new nsec) because they are a nice collection I don’t want to lose easy access to.
Switching the account is a hassle.
Is there an automated way to do this?
Presumably not; I didn’t find an easy way.
So is there some CLI tool I could use?
#asknostr
Every time I have to do something IT‑related for family and friends, it’s a truly grounding experience.
You can see, remind yourself, the countless reasons why everything feel so smooth (UI), integrated (SSO), closed (AAA), and direct (curated feed), almost hiccup free (NFC payments).
Defaults are powerful and hard to uproot later on.
View quoted note →
#asknostr
PoW, user just spend short time on Nostr.
Well I know the settings can be adjusted (on some clients and usually on/off for WiFi/cellular).
But what is the solution?
Media proxy, enforcing the size of media/file per note/blossom event while client attempt to make a use of media/file?
Not only relay wasting bandwidth but also user suffer - it's really so far still data heavy and not usable on many places around the world.
So far seems to me that only can filter content eventually through some relays that will do the job (DVM for data saving?) for me if client will sense the device is on mobile data.
Or caching feed offline on WiFi and letting me mainly read it with info that it's not in-time atm of seeing notes.
Where I can read more about actual state of this within the Nostr space?
PoW, user just spend short time on Nostr.
Well I know the settings can be adjusted (on some clients and usually on/off for WiFi/cellular).
But what is the solution?
Media proxy, enforcing the size of media/file per note/blossom event while client attempt to make a use of media/file?
Not only relay wasting bandwidth but also user suffer - it's really so far still data heavy and not usable on many places around the world.
So far seems to me that only can filter content eventually through some relays that will do the job (DVM for data saving?) for me if client will sense the device is on mobile data.
Or caching feed offline on WiFi and letting me mainly read it with info that it's not in-time atm of seeing notes.
Where I can read more about actual state of this within the Nostr space?