greenart7c3

PGP

44F0AAEB77F373747E3D5444885822EED3A26A6D

Developing

@npub1am3ermkr250dywukzqnaug64cred3x5jht6f3kdhfp3h0rgtjlpqecxrv7

@npub1hqlxlq57nvlq70ugmsmu9y5lmyc5k2lh5w7y85j7dgsr5u7zwavq5agspw

@npub1q2f8m7jwdkvfpz72ce0chsnx2qqhgahkrj7fpudk9wnq6ze5pvjsrvvueg

https://greenart7c3.com

Public Key

npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5

Profile Code

nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsnd7fgf

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5

Show more details

Last Notes

2026-05-08 23:00:11 CEST

- reply

Really? I always tough it had

2026-05-08 16:46:09 CEST

- reply

Haven't tried arti yet

2026-05-08 16:45:09 CEST

- reply

kmp-tor

2026-05-08 16:31:50 CEST

#nevent1q…afum

2026-05-08 15:52:59 CEST

#nevent1q…ntn8

2026-05-06 21:04:18 CEST

- reply

Finally
Meanwhile nostr devs be like:
No, I need my zaps instantly I can't wait. No one will use this

2026-05-06 16:29:33 CEST

- reply

Archiving the group maybe? Never tried

2026-05-05 14:46:23 CEST

- reply

Yes regular clients should implement it, I'll try to add it to amethyst.
I think it was @nprofile…nuzy who made aerith

2026-05-05 14:19:31 CEST

- reply

I think only aerith
https://github.com/hardran3/Aerith

2026-05-02 14:06:24 CEST

- reply

By default amethyst uses tor for unknown relays (inbox/outbox relays from other people), try changing the privacy settings to basic

2026-05-01 00:42:12 CEST

- reply

Sure, I can use my wife's ipad

2026-04-30 23:13:34 CEST

@nprofile…ae9u
https://github.com/greenart7c3/Nip46Lab
I started building the nip 46 tester, claude 1 shot this.
Will have a better look at it tomorrow or Monday
Just run the html locally and test it with any bunker

2026-04-29 14:03:29 CEST

#nevent1q…n6rw

2026-04-25 19:05:53 CEST

- reply

In the permissions from the connect request you are sending get_pubic_key instead of get_public_key

2026-04-24 11:58:56 CEST

- reply

Aegis on iOS, don't know what apps support it
There's also primal but I haven't tested how it works on ios

2026-04-22 18:17:52 CEST

Relay performance on android - Pixel 6a
~200k events added to the relay before the test
Strfry 1.1.0 on android terminal:
Published: 1000
Duration: 1.99s
Rate: 501.63 events/s
Executing 100 queries...
Executed: 100
Duration: 25.61s
Rate: 3.90 queries/s
Events returned: 7800
Topaz:
Published: 1000
Duration: 2.75s
Rate: 363.42 events/s
Executing 100 queries...
Executed: 100
Duration: 20.81s
Rate: 4.80 queries/s
Events returned: 7800
Citrine:
Published: 1000
Duration: 4.49s
Rate: 222.80 events/s
Executing 100 queries...
Executed: 100
Duration: 13.80s
Rate: 7.25 queries/s
Events returned: 10000

2026-04-21 15:46:00 CEST

- reply

No, it's only relays that accept bunker requests. Paid relays will not work, all others should work if they don't block ephemeral events.
When you try to add a relay you will see a message if something is wrong or the relay don't accept bunker requests
The profile relays can be the relays you use in other clients.

2026-04-20 13:28:37 CEST

- reply

It looks like lnvps is not following the nip 46 spec, it should ask for the user pubkey after connect but it's not doing it
https://github.com/nostr-protocol/nips/blob/0a25dd524389d642ec153d9009a16fb183eb23ce/46.md?plain=1#L34

2026-04-19 21:25:39 CEST

- reply

You can disable the HDR brightness in display settings if thats your issue

2026-04-17 20:14:26 CEST

- reply

Next release fixes this issue

2026-04-17 00:15:53 CEST

- reply

I checked the option that I don't have any encryption and hoped for the best. 5 years and they never asked anything yet

2026-04-16 10:53:41 CEST

- reply

Thanks for the logs, will look into it

2026-04-16 09:55:06 CEST

- reply

Thank you

2026-04-15 18:05:07 CEST

- reply

You are probably using a old zapstore version, try updating it from the official website
https://zapstore.dev

2026-04-15 16:28:24 CEST

- reply

By default it checks for updates every day, you can disable that in settings
By default it tries to get your profile from some default relays, you can change the relays or remove all of them for disabling this
Bunker requests (usually used for web apps) have some default relays, you can change it in the settings
Bunker requests in the last few updates generates a new key for each app.
The offline version can't connect to the internet, not even localhost since it also needs network permission
In all cases clients know who you are and most nostr requests can leak information about who you are and what are you doing
For bunker requests I recommend using a local relay like citrine for a faster experience but not all clients accepts connections to local relays

2026-04-15 15:18:15 CEST

#nevent1q…pkgy

2026-04-10 21:14:27 CEST

- reply

https://github.com/nostr-protocol/nips/blob/master/55.md#L125-L135
https://github.com/nostr-protocol/nips/blob/master/46.md#L112

2026-04-10 21:11:42 CEST

- reply

There's only a optional parameter clients can send when connecting

2026-04-08 13:17:24 CEST

#nevent1q…lsqp

2026-04-08 10:04:59 CEST

- reply

Clear the storage in zapstore settings

2026-04-06 22:15:59 CEST

- reply

Thank you

2026-04-06 22:12:00 CEST

- reply

Writing This event was published by jumble.imwald.eu in every alt tag also doesn't help, clients usually write a short description like alt = "Short text note" for kind 1

2026-04-06 20:40:58 CEST

- reply

alt tags should be a short summary of the event kind, currently it's "This event was published by https://jumble.imwald.eu/"
https://github.com/nostr-protocol/nips/blob/master/31.md

2026-04-02 10:01:00 CEST

- reply

Can you add a option to format numbers in the current locale?

2026-04-02 09:51:03 CEST

- reply

Yes

2026-04-01 23:34:13 CEST

- reply

I upload it again to zapstore, check if the version is correct now

2026-04-01 23:20:40 CEST

- reply

Try clearing the local storage in zapstore
https://cdn.nostrcheck.me/3a5a4378f7ed592519306181cc4ad3c577cba4ef19b954f2d1e33633f6cafb66.webp

2026-04-01 22:19:56 CEST

- reply

It probably gets flagged as malware because they support monero

2026-04-01 21:32:08 CEST

#nevent1q…sn09

2026-04-01 21:31:02 CEST

- reply

There's two more android relays but I don't remember the name now

2026-04-01 20:27:05 CEST

- reply

Its painful, even with a local relay or using nip 55

2026-04-01 20:24:54 CEST

- reply

I think it's this issue here, hes already looking into it
#nevent1q…qqaf

2026-04-01 20:14:16 CEST

- reply

Coracle

2026-04-01 19:57:31 CEST

- reply

New method*

2026-04-01 19:57:13 CEST

- reply

What client are you trying?
There's a new spec in nip 46 for switch relays it's probably that

2026-04-01 16:06:48 CEST

- reply

https://apks.relay.tools/apks/

2026-04-01 10:47:15 CEST

- reply

I see now, it's another repo

2026-04-01 10:42:03 CEST

- reply

When it doesn't have a user at the top it's the one signed by zapstore I think

2026-03-31 15:04:19 CEST

- reply

Not yet, I haven't separated by kind yet

2026-03-31 11:15:11 CEST

- reply

If you take amethyst as example you can block clear text and events to disable dms and allow tags to make the app work with you blocklist, relays, bookmarks etc

2026-03-31 11:12:01 CEST

- reply

If you want to allow the client to decrypt everything or only clear text, tags or events

2026-03-29 19:56:23 CEST

- reply

What client is this happening? Check if putting citrine in the default relay in settings makes it work

2026-03-27 22:43:40 CET

- reply

I think it was using a old version of amber with the newer amethyst or the old version of amethyst with the newer version of amber

2026-03-27 22:41:15 CET

- reply

Maybe an old version, I think it happened before and was fixed

2026-03-27 22:36:58 CET

- reply

Its on 1.06.0

2026-03-27 22:10:25 CET

#nevent1q…uwwp

2026-03-27 20:24:49 CET

- reply

Nice, when you manage to go to the play store you need to remember to remove the install APK permission or they will reject it

2026-03-27 11:52:29 CET

#nevent1q…yzhk

2026-03-26 16:48:29 CET

- reply

Maybe I could change the auth stuff in amber to use some sort of white list.
The notification is probably something that could be asked just once

2026-03-26 16:24:31 CET

- reply

Most apps just forget that any request can be rejected and they just keep asking again.
Could also be some bug in amber or some kind of infinite loop in the client
What app are you seeing this?

2026-03-26 11:19:44 CET

- reply

You didn't need to enable developer settings before, just give permission to install apps for the file manager or the browser

2026-03-25 23:02:26 CET

- reply

I think the mutex change is not needed

2026-03-25 22:52:55 CET

- reply

https://github.com/barrydeen/wisp/pull/324

2026-03-25 21:32:04 CET

- reply

The auth loop is still happening, not sure why yet

2026-03-25 21:08:51 CET

- reply

I'll run some tests and let you know in a few minutes if it worked

2026-03-25 17:43:05 CET

- reply

There's also a reconnect issue when rejecting a request without rejecting it forever.
When doing it in the login screen it keeps reconnecting to auth.nostr1 and thats why it enters in a auth loop.
Maybe change to something like only disconnects from relays after N seconds that the app went to background.

2026-03-25 13:24:11 CET

- reply

The issue is inside the SignerIntentBridge, the mutex should be inside the remote signer or you should try the content resolver again inside the requestSign function

2026-03-24 16:10:11 CET

- reply

There's two tabs in the connect screen now, but I also don't like it and will change it

2026-03-24 15:24:05 CET

- reply

Sure, I'll try to reproduce this later. I think it will be hard to reproduce

2026-03-24 00:14:37 CET

Latest version of amethyst you can disable, reorder and remove counts from the reactions row
https://cdn.nostrcheck.me/e1dbd13fc40240962666a40f206eda98c20245352fca36de0d5940dbe69516f6.webp

2026-03-22 00:12:25 CET

- reply

You downloaded the offline version then, you need to download the free version, after that you need to enable the network permission again if I remember correctly

2026-03-21 23:57:20 CET

- reply

You probably selected to always open primal by default, you need to open primal application info page and clear the open by default option.
This is an Android setting not a primal one

2026-03-21 09:59:11 CET

- reply

Yea, one of the best ideas Vitor had was the crash reports
Fixed so many issues that I could never reproduce

2026-03-20 22:34:52 CET

- reply

Still the same, but from my tests it's not firing the document visibility change anymore

2026-03-20 20:30:49 CET

- reply

Oh, changing amber to a bottom sheet broke pubpay. Will see if I can do something about this

2026-03-19 18:54:04 CET

lol you will have to wait 24 hours to sideload apps
https://android-developers.googleblog.com/2026/03/android-developer-verification.html

2026-03-18 18:01:14 CET

- reply

Fixed the crash on version 5.0.1
Also changed the crash report screen to show the report and let you edit it

2026-03-18 17:59:31 CET

- reply

Fixed the crash on version 5.0.1

2026-03-18 17:58:40 CET

#nevent1q…h4uj

2026-03-18 16:43:18 CET

- reply

Will look into it, thank you

2026-03-18 16:09:34 CET

- reply

After the crash open amber again and send the crash report please, what client is making amber crash?

2026-03-18 14:00:17 CET

#nevent1q…2tqz

2026-03-17 21:03:09 CET

- reply

https://github.com/nostr-protocol/nips/pull/1907
I think this is what @nprofile…2lxp is using

2026-03-14 18:35:23 CET

- reply

Amber already have the remember on rejections

2026-03-14 16:37:30 CET

- reply

As próprias carteiras poderiam rodar como serviço opcional igual tem na Zeus ou então sincronizar de tem em tempo. Acho que a cake tem uma opção assim pra silent payments, não sei se também fizeram pra spark

2026-03-14 16:29:02 CET

👀
#nevent1q…3c9u

2026-03-14 15:28:38 CET

- reply

I tried again a few days ago adding to amethyst but it breaks every other functionality.
When Google was adding it to compose in the beta you could just add a function to any text field but they are now forcing to use the basic text field which requires changing everything

2026-03-14 10:52:40 CET

- reply

Tested it this morning, looks like wisp is not respecting the rejected event when using content resolvers.
cc @nprofile…fzvp

2026-03-13 23:00:01 CET

- reply

Thanks, I'll look into it on Monday

2026-03-13 12:48:05 CET

- reply

If the client you are using send them it can be saved as long as you don't have the relay to only accept events from some people

2026-03-12 16:33:04 CET

- reply

Already in there in the latest version, if you setup it to auto approve before you need to change it in amber. Didn't want to break the experience for anyone

2026-03-11 19:14:35 CET

#nevent1q…9fwp

2026-03-11 16:50:07 CET

- reply

I didn't

2026-03-11 15:26:16 CET

#nevent1q…u48p

2026-03-11 14:26:36 CET

- reply

When I tried with amber they wanted me to change my company name because duns added some spaces in the name

2026-03-10 15:11:16 CET

- reply