Nostr notes by greenart7c3

You need to ask fountain to fix their app

2026-10-12T11:52:20Z

In reply to nevent1q…33yw
_________________________

You need to ask fountain to fix their app

#nevent1q…kexu

2026-10-12T11:13:15Z

quoting nevent1q…kexu
## Amber 6.6.8

- Fix a crash on some devices when opening Amber from another app or after rejecting a request, caused by the system failing to read the referring app

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.8)

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-v6.6.8.txt` and `manifest-v6.6.8.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.8.txt.sig manifest-v6.6.8.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 "
```

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-v6.6.8.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

I joined the group you sent earlier, I think citrine doesn't ...

2026-10-10T19:01:40Z

In reply to nevent1q…lt3j
_________________________

I joined the group you sent earlier, I think citrine doesn't support concord if that's what you are trying to do.

I see you also built some signer stuff, I was building some ...

2026-10-09T18:42:28Z

In reply to nevent1q…mzep
_________________________

I see you also built some signer stuff, I was building some adapted nip 5f for amber desktop to be more like the nip 55. https://github.com/greenart7c3/Amber/blob/claude/desktop-mac-linux-support-rihkah/desktop/LOCAL_SIGNER.md

I'll see if I can add the dbus signer later

Just tested again and it connected normally using the built in ...

2026-10-06T12:22:40Z

In reply to nevent1q…547e
_________________________

Just tested again and it connected normally using the built in tor and orbot

#nevent1q…atse

2026-10-05T13:37:35Z

quoting nevent1q…atse
## Amber 6.6.7

- Fix relays staying disconnected until the app was force closed: relays marked dead after a stretch of bad connectivity now get another chance after a 15 minute cooldown, and failed connection attempts are no longer counted twice
- Reset relay connections when a VPN comes up or goes down, or when the device regains internet access, the same way switching between Wi-Fi and mobile data does; network changes now drop stale sockets and clear the reconnect backoff so relays come back immediately
- Detect web requests from browsers other than Chrome (such as DuckDuckGo), which previously failed with "Unknown signer type"
- Fix a crash when a permission was saved for an application that had just been deleted or reset

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.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-v6.6.7.txt` and `manifest-v6.6.7.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.7.txt.sig manifest-v6.6.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 "
```

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-v6.6.7.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

Yes

2026-10-04T11:43:37Z

In reply to nevent1q…g9wx
_________________________

Yes

I think it's named android developer verifier

2026-10-04T10:43:07Z

In reply to nevent1q…juwu
_________________________

I think it's named android developer verifier

The android developer verification thing started in a few ...

2026-10-04T10:11:48Z

The android developer verification thing started in a few countries, as you can guess it doesn't protect your children from pedos or anyone from scammers.
It's easily bypassed by disabling a system app.
For now the only thing it does is put app developers at risk.

@nprofile…7nrg nostr1 certificate expired

2026-10-02T14:13:57Z

cloud fodder (nprofile…7nrg) nostr1 certificate expired

#nevent1q…7csx

2026-10-02T09:03:21Z

quoting nevent1q…7csx
## Morganite 0.0.6

- Fix crash on startup when port 24242 is already used by another app: the error is now shown as a dialog and a notification on a new "Server errors" channel instead of killing the process
- New translations for Spanish, Brazilian Portuguese and Chinese

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.morganite), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Morganite/releases/tag/v0.0.6)

### 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 for 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-v0.0.6.txt` and `manifest-v0.0.6.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v0.0.6.txt.sig manifest-v0.0.6.txt
```

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-v0.0.6.txt
```

Also there's another thing very bad in this space besides ...

2026-10-01T09:49:54Z

In reply to nevent1q…tprx
_________________________

Also there's another thing very bad in this space besides breaking user space
Most people in the developer world should unlearn a few things vcs/fintechs etc taught them.
A lot of user facing errors gets ignored for months/years
The companies I worked for always taught me that I should stop everything I'm doing when a user reports a error, but what I see in this space is people making errors low priority and fixing them only after months/years
As a example flutter has a lot of issues and they never fix them because someone set a low priority to it

Can you send me the crash log? What device and os are you using?

2026-09-29T12:13:36Z

In reply to nevent1q…xerx
_________________________

Can you send me the crash log?
What device and os are you using?

#nevent1q…5seh

2026-09-28T11:27:20Z

quoting nevent1q…5seh
# Changelog

## Amber 6.6.6

- Fix the nostrconnect parser corrupting connect-param values that contain `=` (such as base64-padded secrets): the connect response returned mangled values instead of the original secret, so NDK-based clients failed their secret check
- Fix white text and icons on light-amber surfaces in dark theme (Edit Relays floating action button, add-relay icon buttons, selected filter chips on the feedback screen)
- Fix the Tor/proxy status icon in the top app bar being nearly invisible in light theme — status icons now use theme-aware colors in both themes, and the relay reconnect icon matches the adjacent relay count
- Feedback issues are now published to the relays advertised on Amber's repository announcement instead of a hardcoded relay, falling back to the previous behavior when the announcement can't be fetched; longer timeouts on Tor so slow relays still confirm the publish

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.6)

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-v6.6.6.txt` and `manifest-v6.6.6.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.6.txt.sig manifest-v6.6.6.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 "
```

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-v6.6.6.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

#nevent1q…sjty

2026-09-18T10:27:24Z

quoting nevent1q…sjty
## Citrine 3.2.0

- Fixed silent crashes (OOM) with the relay aggregator enabled: REQ queries now stream results in batches instead of materializing the full match set in memory
- Bounded relay aggregator memory: capped outbound relays at 200 and bounded caches
- Added an option to hide the graph in the show events page
- Out-of-memory errors are now logged to the in-app log screen so they can be diagnosed
- Updated dependencies (including Quartz 1.15.2)
- Updated translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.citrine), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v3.2.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-v3.2.0.txt` and `manifest-v3.2.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v3.2.0.txt.sig manifest-v3.2.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 "
```

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.2.0.txt
```

One can use the `shasum -a 256 ` 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.

Does it happen when using some client or when not doing anything ...

2026-09-16T15:05:45Z

In reply to nevent1q…xm06
_________________________

Does it happen when using some client or when not doing anything it also happens?

It's probably running out of memory, what is your device?

2026-09-16T15:02:13Z

In reply to nevent1q…h50v
_________________________

It's probably running out of memory, what is your device?

When you open citrine it should show the crash report, try dming ...

2026-09-15T21:04:26Z

In reply to nevent1q…27zk
_________________________

When you open citrine it should show the crash report, try dming it to me so I can look into it

🤣🤣🤣 You should also check the Izzy on droid faq on ai

2026-09-15T21:02:23Z

In reply to nevent1q…4jsp
_________________________

🤣🤣🤣

You should also check the Izzy on droid faq on ai

#nevent1q…ny8w

2026-09-11T09:36:50Z

quoting nevent1q…ny8w
## Citrine 3.1.1

- Fixed an NIP-42 auth bypass where kind-22242 AUTH events were added to the connection without signature verification
- Scoped REQ subscription ids per connection so a duplicate id from one socket can no longer clobber another's subscription
- NIP-45: COUNT filters now aggregate into a single count response without EOSE and no longer register live subscriptions
- Fixed NIP-42 access control denying authenticated users filtering kinds-less {"#p":[]}
- Replaceable events now tie-break on the lowest id at equal created_at (NIP-01)
- ids and authors filters are now exact 64-hex matches (NIP-01)
- Standardized OK message prefixes for duplicate, deleted, and blocked events (NIP-01/09)
- NIP-11: relay info document is now built quote-safe and advertises Access-Control-Allow-Headers; dropped deprecated NIP-04
- NIP-86: added unbanpubkey and unallowpubkey; allowpubkey no longer unbans as a side effect

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.citrine), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v3.1.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-v3.1.1.txt` and `manifest-v3.1.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v3.1.1.txt.sig manifest-v3.1.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 "
```

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.1.1.txt
```

One can use the `shasum -a 256 ` 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.

#nevent1q…e4sp

2026-09-09T22:36:09Z

quoting nevent1q…e4sp
# Changelog

## Amber 6.6.3

- Fix the "start service on boot" setting not being respected after an app update
- Fix a crash on the offline flavor caused by a `SecurityException` from WorkManager network tracking left over from an upgrade
- Fix the Russian translation of the "Amber is a free and open source project" string
- Fix a release build failure caused by an AGP 9.4.0 regression

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.3)

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-v6.6.3.txt` and `manifest-v6.6.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.3.txt.sig manifest-v6.6.3.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 "
```

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-v6.6.3.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

I think @nprofile…g58a also built something if I'm not ...

2026-09-06T19:52:30Z

In reply to nevent1q…4es3
_________________________

I think Alex Gleason (nprofile…g58a) also built something if I'm not mistaken

Also nak from fiatjaf

2026-09-06T19:51:31Z

In reply to nevent1q…6e7q
_________________________

Also nak from fiatjaf

Nostr event nevent1qqsdalckthgzkz30ujg0azhzk8muw2jd2fmgj25v4yga3u3cwt93ekqzyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93jxkj0mf

2026-09-06T19:50:47Z

In reply to nevent1q…ad7l
_________________________

https://github.com/Letdown2491/signet

https://github.com/dsbaars/bunker46

#nevent1q…94ww

2026-09-04T11:44:49Z

quoting nevent1q…94ww
# Changelog

## Amber 6.6.1

- Fix parsing of incoming permission lists when a permission has no `kind` field in its JSON, so the whole list no longer fails to load
- Fix rejected signer requests not returning the request id in the result, leaving calling apps unable to match the rejection to their request
- Update the default signer relays to `auth.nostr1.com`, `bucket.coracle.social`, `nrs.primal.net` and `relay.nip46.com`, and add `indexer.coracle.social` to the default indexer relays (#518)
- Add missing translations for Marmot protocol event kinds

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.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-v6.6.1.txt` and `manifest-v6.6.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.1.txt.sig manifest-v6.6.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 "
```

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-v6.6.1.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

#nevent1q…xvcf

2026-08-31T11:26:36Z

quoting nevent1q…xvcf
## Amber 6.6.0

- New: pre-approve individual permissions when connecting an app under the "Manually approve each permission" policy — an "Add permission" button lets you pick from the full permission catalog (searchable, including custom sign-event kinds) so those requests are approved automatically while everything else still asks
- New: when a NIP-46 connect request arrives while the kill switch is enabled, Amber now asks whether to disable it so the request can be answered, and the kill switch gained a toggle in the Settings network section
- Toggling the "Enable biometrics" setting now requires biometric authentication first, so the setting cannot be deactivated without authorization and broken sensors are caught before activation
- Toggling "require unlocked device" now shows a progress indicator with a do-not-close warning while every stored secret is re-encrypted, instead of silently freezing
- Fix the account picker not scrolling and its title not being visible
- Fix a crash in profile feed subscriptions when an account is removed while its events are being processed
- Trim the image and trust-score caches when the system reports memory pressure, so the 32 MB bitmap cache no longer stays fully resident while the app is in the background
- Performance: cache decrypted application lists so periodic relay refreshes stop re-decrypting every application row through the Keystore (the dominant native memory user on populated accounts), and warm up timezone data off the main thread to remove a ~170 ms disk read during the Applications screen's first composition
- Update Kotlin to 2.4.10, Gradle to 9.7.1, Quartz to 1.14.0 and the rest of the dependency stack

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.6.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-v6.6.0.txt` and `manifest-v6.6.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.0.txt.sig manifest-v6.6.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 "
```

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-v6.6.0.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

Searching for terminal should in setting should show it Otherwise ...

2026-08-26T20:08:04Z

In reply to nevent1q…egmf
_________________________

Searching for terminal should in setting should show it
Otherwise it's in the debugging session a menu called Linux development environment

If you have a pixel phone you can enable developer setting and ...

2026-08-26T09:37:38Z

In reply to nevent1q…te06
_________________________

If you have a pixel phone you can enable developer setting and enable the terminal app. Not sure other manufacturers have it

Yes, I try to run them once a month or when a new model arrives.

2026-08-20T20:54:07Z

In reply to nevent1q…26yp
_________________________

Yes, I try to run them once a month or when a new model arrives.

#nevent1q…6ce8

2026-08-18T13:43:45Z

quoting nevent1q…6ce8
# Changelog

## Amber 6.5.2

- Fix the Applications screen taking several seconds to load on populated accounts: the list no longer decrypts the encrypted `secret`/`localKey` columns it doesn't render, and the Keystore key handle is cached instead of re-fetched for every decryption
- Warm the account cache at app start so the switch-accounts button lists all accounts again instead of only the current one
- Fix a crash when scrolling the activity history screens caused by the same row appearing in two loaded pages at once
- Debounce relay status-counter notification updates so the status notification no longer freezes on stale text during bursts of relay traffic

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.5.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-v6.5.2.txt` and `manifest-v6.5.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.5.2.txt.sig manifest-v6.5.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 "
```

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-v6.5.2.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

Thanks, will look into it and also add a way to copy the logs

2026-08-18T09:28:06Z

In reply to nevent1q…rssh
_________________________

Thanks, will look into it and also add a way to copy the logs

#nevent1q…yxsk

2026-08-14T13:25:56Z

quoting nevent1q…yxsk
## Morganite 0.0.4

- Verify blob hashes during download in a single pass before caching
- Track cache size incrementally to avoid directory rescans on every blob save
- Increase buffer sizes and move blocking network calls to I/O threads for better performance
- Reuse Tika instances for faster MIME-type detection
- Persist logs to a local Room database instead of logcat
- Expose logs as StateFlow for the log viewer
- Remove permission result logging in MainActivity
- Update deployment target selection state in IDE configuration

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.morganite), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Morganite/releases/tag/v0.0.4)

### 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-v0.0.4.txt` and `manifest-v0.0.4.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v0.0.4.txt.sig manifest-v0.0.4.txt
```

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-v0.0.4.txt
```

#nevent1q…d939

2026-08-14T12:52:41Z

quoting nevent1q…d939
## Citrine 3.1.0

- Added NIP-29 relay-based groups support
- Added NIP-86 relay management API and settings screen
- Added a tool to rebroadcast stored events to selected relays
- Offer to purge stored events when banning a pubkey locally
- Added configurable REJECTED_KINDS to block non-publishable artifact kinds
- Added import-from-lists picker to access control settings
- Added nsite (NIP-5A) support to Web Clients
- Modernized the browse nsites list: website icons, search bar, sort by last update, and install progress
- Added a setting to choose relays for fetching nsites, with dedicated defaults (nsite.run, nos.lol, nostr.land)
- Show nsite description and restyle nsite lists as cards with an author header
- Performance improvements on the WebSocket and REQ query hot paths
- Removed permessage-deflate extension from the WebSocket server
- Fixed Tor not starting/stopping when the expose-via-Tor setting changes
- Always stop Tor when the relay service is destroyed
- Show the home screen without waiting for the service to bind
- Subscribe to all kinds when the aggregator kinds list is empty
- Move the aggregator kinds reset button below the text field
- Persist logs to a local database and gate logcat to debug builds
- Updated Gradle, Kotlin, and project dependencies
- Updated translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.citrine), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v3.1.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-v3.1.0.txt` and `manifest-v3.1.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v3.1.0.txt.sig manifest-v3.1.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 "
```

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.1.0.txt
```

One can use the `shasum -a 256 ` 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.

#nevent1q…x79u

2026-08-14T11:55:31Z

quoting nevent1q…x79u
# Changelog

## Amber 6.5.0

- Fix relay-auth whitelist authorizing any requester (GHSA-vx4h-56qj-wcp7)
- Fix NIP-46 freshness and replay protection (GHSA-h9fv-9247-3582)
- Envelope-encrypt NIP-46 connection secrets at rest (GHSA-5fjp-ghh8-wch8)
- Add opt-in unlocked-device requirement for Keystore key (GHSA-8844)
- Authorize before decrypt in SignerProviderQuery (GHSA-8844)
- Redact key material from logs and crash reports (GHSA-8844)
- Set FLAG_SECURE on sensitive QR surfaces (GHSA-8844)
- Warn on insecure ws:// connections to non-onion relays (GHSA-8844)
- Parse unknown permission remember types as NEVER to fail closed (GHSA-8844)
- Lazy-load account keys on cache miss and properly zeroize them on logout (GHSA-8844)
- Update translations for new string resources
- Fix CI test failures and linter violations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.5.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-v6.5.0.txt` and `manifest-v6.5.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.5.0.txt.sig manifest-v6.5.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 "
```

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-v6.5.0.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

They are running this for so long, the person who is running it ...

2026-08-13T09:38:12Z

In reply to nevent1q…n2eh
_________________________

They are running this for so long, the person who is running it must really think it helps

#nevent1q…qu03

2026-08-07T10:41:51Z

quoting nevent1q…qu03
## Amber 6.4.0

- Redesign the multi-request approval screen with explicit Approve/Deny toggles per request and per group, replacing the select-and-confirm flow, with proper error responses for denied bunker requests
- Add support for 113 more event kinds with localized labels across all shipped locales, including the Concord kinds, NIP-51 git repository bookmarks and NIP-53 room presence
- Add light/dark Compose previews for the multi-event approval screens
- Ignore platform finalizer-watchdog TimeoutExceptions in crash reports
- Fix a NegativeArraySizeException crash in relay subscriptions by guarding shared maps for concurrent access
- Translate the new approval strings (approve, confirm, remember my choice for) in all supported locales
- Update translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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/v6.4.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-v6.4.0.txt` and `manifest-v6.4.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.4.0.txt.sig manifest-v6.4.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 "
```

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-v6.4.0.txt
```

One can use the `shasum -a 256 ` 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.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

Yeah that was the issue, I'll try again with a sub but looks ...

2026-08-07T09:59:48Z

In reply to nevent1q…5a39
_________________________

Yeah that was the issue, I'll try again with a sub but looks like the sub is not working for Kimi on opencode

Maybe i'm doing something wrong but using kimi or glm seems a ...

2026-08-07T09:17:45Z

Maybe i'm doing something wrong but using kimi or glm seems a lot more expensive than claude or codex.
with claude or codex with 20$ - 100$ I can code the whole month almost never hitting a limit but with glm and kimi with was 20$ in 3 days

Lol what are those people smoking When using the login with ...

2026-07-30T14:00:53Z

In reply to nevent1q…e5sw
_________________________

Lol what are those people smoking
When using the login with Google they don't have to type their password or multi factor auth again

I think someone did build something like nip 55 for desktop but ...

2026-07-24T18:16:15Z

In reply to nevent1q…ytqw
_________________________

I think someone did build something like nip 55 for desktop but I'm not finding it now
I have a desktop branch I was testing amber but currently it's just using nip 46

The app image doesn't even open when using arch linux

2026-07-24T15:33:44Z

In reply to nevent1q…ff50
_________________________

The app image doesn't even open when using arch linux

I think there's no fips library for android yet.

2026-07-22T15:05:58Z

In reply to nevent1q…ntzn
_________________________

I think there's no fips library for android yet.

It's just because I was using the claude web interface and ...

2026-07-22T13:01:20Z

In reply to nevent1q…6h5z
_________________________

It's just because I was using the claude web interface and didn't configure it to use ngit

Not related to ngit but related to gitworkshop.dev Don't know ...

2026-07-22T12:29:22Z

In reply to nevent1q…s6r0
_________________________

Not related to ngit but related to gitworkshop.dev

Don't know if it's possible but it would be nice to be able to search for the contents of the repo files in the web ui.
Sometimes I want to search the code of a repository but I don't know in which file it is

Yes but you need to enable access to local network in the VPN ...

2026-07-20T21:00:39Z

In reply to nevent1q…ekcd
_________________________

Yes but you need to enable access to local network in the VPN settings and disable blocking connection without VPN in the phone settings

https://github.com/localsend/localsend I use this

2026-07-20T20:25:19Z

In reply to nevent1q…va2a
_________________________

https://github.com/localsend/localsend

I use this

After clearing the storage in the settings it worked

2026-07-18T11:40:25Z

In reply to nevent1q…fqps
_________________________

After clearing the storage in the settings it worked

@nprofile…gsu4 when I try to install an app and it can't ...

2026-07-18T10:21:11Z

Zapstore (nprofile…gsu4) when I try to install an app and it can't find the dev profile the app gets stuck at this screen

This was trying to install the new app from kohei (nprofile…353r)

It looks like it's your barcode scanner dependency that ...

2026-07-13T21:56:01Z

In reply to nevent1q…zag0
_________________________

It looks like it's your barcode scanner dependency that contains some kind of tracker

https://www.plebsvszombies.cc/

2026-07-05T16:22:40Z

In reply to nevent1q…xlnd
_________________________

https://www.plebsvszombies.cc/

You probably have some special character somewhere in your nsec, ...

2026-07-05T11:45:27Z

In reply to nevent1q…kt5m
_________________________

You probably have some special character somewhere in your nsec, whatever you used to save/copy the nsec added a hidden character

My experience with other applications was usually just updating ...

2026-07-03T09:20:13Z

In reply to nevent1q…3wwz
_________________________

My experience with other applications was usually just updating the ndkVersion inside build.gradle
Usually doing this in your app solves the issue but sometimes you need to do it inside the library you use also

You can change the citrine port if you want

2026-07-02T11:46:46Z

In reply to nevent1q…q8c2
_________________________

You can change the citrine port if you want

You have relay.nostr.band in your lists, it could be it causing ...

2026-06-26T18:08:06Z

In reply to nevent1q…xa43
_________________________

You have relay.nostr.band in your lists, it could be it causing issues because this relay is gone.
You could also try other clients

Drawer menu -> wallet

2026-06-24T09:18:33Z

In reply to nevent1q…2hxg
_________________________

Drawer menu -> wallet

I think the design uses a different limit than code and uses more ...

2026-06-23T09:27:00Z

In reply to nevent1q…hg70
_________________________

I think the design uses a different limit than code and uses more tokens, at least it was this way when they introduced it.
Are you on max subscription?

#nevent1q…gpxn

2026-06-19T11:17:29Z

quoting nevent1q…gpxn
## Citrine 3.0.1

- Fixed a crash when unregistering an unregistered Pokey receiver

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.citrine), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.citrine) or download it directly in the [releases page
](https://github.com/greenart7c3/Citrine/releases/tag/v3.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-v3.0.1.txt` and `manifest-v3.0.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v3.0.1.txt.sig manifest-v3.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 "
```

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.0.1.txt
```

One can use the `shasum -a 256 ` 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.

Damus blocks tor connection. Theres a few relays with .onion in ...

2024-04-16T22:58:22Z

In reply to nevent1q…m7h7
_________________________

Damus blocks tor connection.
Theres a few relays with .onion in this GitHub repo
https://github.com/0xtrr/onion-service-nostr-relays

https://relayable.org/ also has a .onion