deleted / deleted is on Nostr

"c60e1b2c66bb678a2e605a813f79b43069e38e7c6b58316173ab69c2cc6b372287d7085d25226dfb401d69aa182d6f220df637c3e854a4e5b8b803f000dd0f36"

Last Notes

2024-05-17 10:25:18 CEST

- reply

Keepass2Android's apks have been available on their Github page for almost three years. I pull them automatically using Obtainium, but you can also direct download.
https://github.com/philippc/keepass2android

2024-05-09 04:35:05 CEST

How do I open a #bounty for a feature request? #asknostr

2024-04-29 08:26:06 CEST

Looking for a recommendation: epub reader with highlighting & notes support
#asknostr #epub

2024-04-05 12:05:17 CEST

The Lord is cultivating my patience. How is your day going? https://image.nostr.build/cf80253495ebe7838a6dfe83ba20815bf3861297bfb7d208339f2cdadc5841f3.jpg

2024-03-22 04:14:54 CET

- reply

Do you have a link?

2024-03-21 12:51:40 CET

- reply

When copying note IDs from Amethyst, I have to clear the "nostr:" prefix for nostr.band. Also, the nostr.band "view relays" function does not appear to work. #nostrband

2024-03-21 12:38:45 CET

I see this a lot. Where can I go to search for the note id and figure out what relay I'm missing? #Amethyst #asknostr
https://image.nostr.build/83d982847cad61dbd62f1a5844e2b2b655a18842ef50a9c642ad66e6aa5ad6e7.jpg

2024-03-13 04:47:50 CET

- reply

Same issue in 0.84.3

2024-03-11 18:48:27 CET

- reply

This is awesome

2024-03-06 03:17:17 CET

- reply

I open the app every single day for this vary reason

2024-03-06 03:05:08 CET

- reply

Reason always says "Channel closed because user manually force-closed the channel" - which has NEVER been true. In the last incident, I was trying to zap a zap goal with splits for #Amethyst devs.

2024-03-05 19:09:46 CET

- reply

Same here. I've now lost 3 channels to #Mutiny random closes.

2024-03-05 19:01:30 CET

- reply

Well, just tried to zap you all from #Mutiny, and my channel force closed - again. Lightning sucks. Sorry guys. Keep up the good work!

2024-02-15 08:55:14 CET

- reply

Even if you implement nip49, I still think you need to include nsec export. Vitor says nip49 is not meant to replace nsec, and nsec should still be stored in a separate place. If you permit a user to generate new keys, then you need to permit nsec export. Otherwise, users might be left with a lock in situation to your bunker - especially now when client support for all these new nips is incomplete and buggy.

2024-02-15 05:44:01 CET

- reply

That would be awesome. And maybe add a confirmation/warning dialogue for the uninitiated.

2023-11-17 19:09:50 CET

- reply

Can you give more detail? I've used this method without issue

2023-11-17 03:02:36 CET

- reply

Proton has an onion site