<unnamed>

Public Key

npub1am3ermkr250dywukzqnaug64cred3x5jht6f3kdhfp3h0rgtjlpqecxrv7

Profile Code

nprofile1qqswacu3amp428kj8wtpqf77yd2upukcn2ft4aycmxm5scmh359e0sspp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs7amnwvaz7tmwdaehgu3wd4hk6s3l5rp

Publishing to

nos.lol

relay.damus.io

nostr.mom

Last Notes

2026-01-16 09:48:40 UTC

## Amber 4.1.0-pre1
- New ui for login, events and permissions screen
- Refactor relay counters to use the updated method from quartz library
- Fix relay connection not closing when trying to add a unsupported relay
Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.0-pre1)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.1.0-pre1.txt` and `manifest-v4.1.0-pre1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.1.0-pre1.txt.sig manifest-v4.1.0-pre1.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.1.0-pre1.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2026-01-07 12:03:11 UTC

## Amber 4.0.7
- Fix some crashes
- Separate relay and service notifications
- Save screen state in the login screen
Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.7)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.7.txt` and `manifest-v4.0.7.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.7.txt.sig manifest-v4.0.7.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.7.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-11-28 22:58:11 UTC

- reply

jumble.social

2025-11-28 21:41:05 UTC

- reply

Added it

2025-11-28 20:17:23 UTC

- reply

Sure, I'll add it later

2025-09-19 15:46:39 UTC

## Amber 4.0.2
- Change Dockerfile to build from the local repo
- Show all accounts in the backup screen
- Show the backup dialog if any account needs backup
- Enable gradle configuration cache
- Fix migration from old version
- Fix 404 link in README by @npub1lczxedq435kkzvuhf04kpxh67alqs4sa4glv24xfy6nw5tvwnwxqhwwxyr
Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.2)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.2.txt` and `manifest-v4.0.2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.2.txt.sig manifest-v4.0.2.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.2.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-09-10 11:11:36 UTC

## Amber 4.0.1
- Fix reproducibility and added instruction in the README
- Fix the validation of the current logged in user when sending a event from another user
- When using intents send a reject response
- Fix the edit permissions screen not updating correctly the fields when rejecting/accepting a permission
- Update to gradle 9
Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.1)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.1.txt` and `manifest-v4.0.1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.1.txt.sig manifest-v4.0.1.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.1.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-09-01 14:34:26 UTC

- reply

Thanks

2025-08-29 14:26:31 UTC

## Amber 4.0.0
- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature
Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0.txt` and `manifest-v4.0.0.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0.txt.sig manifest-v4.0.0.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.0.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-08-27 12:45:39 UTC

## Amber 4.0.0-pre2
- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature
Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre2)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0-pre2.txt` and `manifest-v4.0.0-pre2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0-pre2.txt.sig manifest-v4.0.0-pre2.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.0-pre2.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-08-22 10:36:36 UTC

## Amber 4.0.0-pre1
- Refactor everything to use the new quartz update
Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre1)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0-pre1.txt` and `manifest-v4.0.0-pre1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v4.0.0-pre1.txt.sig manifest-v4.0.0-pre1.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v4.0.0-pre1.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-08-11 11:00:38 UTC

## Amber 3.4.5
- Added a button in notifications and AppBar to restart connection to relays
- When connecting to relay try sending the subscription again
- If there’s a error sending a message to the relay try restarting it and sending again
- Check for encryption type again (not every app has support for nip44 yet)
- Revert QrCode reader support for multi-window (it was not reading inverted QrCodes)
- Generate a new event when there’s an error instead of trying to send the same event to avoid receiving duplicated messages from relays
- Send a error notification if it was not possible to send the event to the relays
- Close the app first and then try to send the event to the relays
Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v3.4.5)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v3.4.5.txt` and `manifest-v3.4.5.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.5.txt.sig manifest-v3.4.5.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v3.4.5.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-07-11 11:47:35 UTC

## Amber 3.4.2
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities screen
- Always encrypt bunker responses with nip 44
- Target android 16
- Add some error handling to check for network permissions
- Remove gson dependency
- Add more default relays
Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v3.4.2)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v3.4.2.txt` and `manifest-v3.4.2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.2.txt.sig manifest-v3.4.2.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v3.4.2.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-06-25 20:06:59 UTC

## Amber 3.4.2-pre2
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
- Separated Bunker and Intent logic
- Fixed bunker relay validation when adding a new relay
- Option to reuse an existing connection
- New activities screen
Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v3.4.2-pre2)
If you like my work consider making a [donation](https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v3.4.2-pre2.txt` and `manifest-v3.4.2-pre2.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.2-pre2.txt.sig manifest-v3.4.2-pre2.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v3.4.2-pre2.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2025-06-11 19:27:28 UTC

## Amber 3.4.2-pre1
- Added loading indicator when running migrations
- Fix ncryptsec export
- Add a icon when using a proxy and check if the proxy is working
- Add more event translations
- Add a screen to send feedback on nostr
- Start separating Bunker and native implementations
- Fix service start error in slow devices when the user moves the app to the background faster than the app can start
- Fix scrollbar position
- Fix requests not disappearing when accepting/rejecting
- Fix QR code scanner when using multiwindow mode
- Use datasource to fetch profile data
- Remove check for paid and auth in relays
- Remove listening for new connections option
- Make secret mandatory for bunker requests
- Update notification less often
- Updated dependencies
Download it with [zap.store]( https://zapstore.dev/download), [Obtainium]( https://github.com/ImranR98/Obtainium), [f-droid]( https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page]( https://github.com/greenart7c3/Amber/releases/tag/v3.4.2-pre1)
If you like my work consider making a [donation]( https://greenart7c3.com)
## Verifying the release
In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```
Once you have his PGP key you can verify the release (assuming `manifest-v3.4.2-pre1.txt` and `manifest-v3.4.2-pre1.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v3.4.2-pre1.txt.sig manifest-v3.4.2-pre1.txt
```
You should see the following if the verification was successful:
``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
``` bash
cat manifest-v3.4.2-pre1.txt
```
One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

2024-04-14 18:16:50 UTC

- reply

Not yet for web clients

2024-03-13 13:48:35 UTC

## Amber - v0.8.2
* Fix activity not clearing when using web clients

2024-01-08 20:36:21 UTC

## Amber - v0.7.2
- Update quartz to v.83.5
- Added decrypt content to the show details button
- Created links to source code, donation page and OpenSats
Download:
https://github.com/greenart7c3/Amber/releases/tag/v0.7.2

2023-12-06 10:03:57 UTC

## Amber - 0.6.6
- Fix encryption/decryption in web apps
Download:
https://github.com/greenart7c3/Amber/releases/tag/v0.6.6

2023-12-01 14:34:49 UTC

## Amber - 0.6.5
- Support for signing multiple events at once
- Support for sending default permissions to be allowed by the user when loginin
https://image.nostr.build/beb0311cf9b4a5d2f39b5a8f8a3bfe3ed9da8b86e07d6a70e9308d81d368130e.png
https://image.nostr.build/18ab69385278ddddd87e82f7ec41e353a2490f66333f9e0c35bda0644bfc9f8e.png