It deletes the draft after you post
i allowed it, now ill harass nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 about why it didnt stick the deny drafts 😎
The remember my choice is not working when you deny?
I think it was already there or was added when they changed it to use bunker uri
If you have your own domain or your nip 5 provider has support for this you can enable it
Here's what I use:
https://github.com/greenart7c3/greenart7c3.com/blob/main/.well-known%2Fnostr.json
If I remember correctly you just need the nip 46 Json inside the nostr.json
If you have your own domain or your nip 5 provider has support for this you can enable it
Here's what I use:
https://github.com/greenart7c3/greenart7c3.com/blob/main/.well-known%2Fnostr.json
nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 is this on citrine's roadmap? Or already done?
I haven't tested anything yet using Bluetooth but I'll try eventually.
Sending the events after getting internet connection too
nostr:naddr1qq2yx6t5wf5kuefdxqkn2tfj95mryeeevdmsyg9c8ehc985m8c8nlzxuxlpf987ex99jhaarh3payhn2yqa88snhtqpsgqqqw4rsjfehe6
nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 why does obtainium show 'conflict:amber' for the new amber? did sigs or app name change or ?
I changed the signature in version 2
Same for citrine
There's a hardware from lnbits but I forgot who is building it
https://github.com/nostr-protocol/nips/pull/1341
I updated amber to the new way, the only call I didn't change yet is the return value from get_public_key
Criei uma issue no repositório do nostr:npub142gywvjkq0dv6nupggyn2euhx4nduwc7yz5f24ah9rpmunr2s39se3xrj0 para existir a opção de seguir pessoas de forma privada: https://github.com/vitorpamplona/amethyst/issues/1121
O kotlingeekdev já está trabalhando em melhorar suporte a listas no amethyst
Other issue is kind 1 as replies. This brings a lot of unnecessary data usage specially for clients that use different screens for replies
And another issue is clients are asking the same data all the time.
If I scroll 20 posts and go back to the beginning and start scrolling again most clients are going to ask the same data again
1 - there's a pull request to change that but the nip repo is slow
2 - This could also be changed. I think result would be better for all kinds
3 - Private zaps use a different method of encrypting the data
Unless you know exactly what relay you should connect to fetch this event in amethyst you cant do nothing.
I usually open the event in noStrudel and there it shows an option with a relay list to try to fetch the event if the event is not found
You can also use some library that does all the work for you like https://github.com/fiatjaf/window.nostr.js and https://github.com/nostrband/nostr-login
you can do both, there's a nostrconnect uri that a client can generate and there's a bunker uri that the signer generate.
In amber to generate the bunker string you go to permissions, press the plus button and then press the new app button
It was a bug in amber not splitting the strong correctly.
Amber supports nip 46
I fixed it but it would be much better experience for your application if you used nip 46 instead of nip 55
What are you trying to implement? Nip 46?
Do you have something I can debug?
More stable Amber support for NIP-46 nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 and a desktop signer to do the same.
I have plans to make it multiplatform but haven't started working on it yet
My son setup the alarm for 3 am
Did you change anything in settings or just retored a backup file?
Do you see the error if you go to the logs screen after the crash? It would help me if you can get the error
Tried to create a Google developer account
Sms verification didn't work for 3 days
No credit card is working.
For apple I had to create the account in a apple device, but everything else worked.
Know issue if you are using amber. This will be fixed next release