diff --git a/docs/changelogs/0.0.1.md b/docs/changelogs/0.0.1.md new file mode 100644 index 00000000..aa77a867 --- /dev/null +++ b/docs/changelogs/0.0.1.md @@ -0,0 +1,3 @@ +# Amber 0.0.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.0.2.md b/docs/changelogs/0.0.2.md new file mode 100644 index 00000000..4d3b8fbc --- /dev/null +++ b/docs/changelogs/0.0.2.md @@ -0,0 +1,6 @@ +# Amber - 0.0.2 + +- Removed internet connections +- Sign button will only copy the signature and not the whole event +- Update readm with planned features +- Updated readme with how to implement support for Amber in your web application diff --git a/docs/changelogs/0.0.3.md b/docs/changelogs/0.0.3.md new file mode 100644 index 00000000..469cef26 --- /dev/null +++ b/docs/changelogs/0.0.3.md @@ -0,0 +1,7 @@ +# Amber - 0.0.3 + +- New UI +- Fill pubkey and id if pubkey not present in the event +- Support for login with hex key + +![Captura de tela 2023-08-04 151102](https://github.com/greenart7c3/Amber/assets/115044884/bd73afd0-a28a-4b2a-8781-7ad277f1609c) diff --git a/docs/changelogs/0.0.4.md b/docs/changelogs/0.0.4.md new file mode 100644 index 00000000..5d8933d6 --- /dev/null +++ b/docs/changelogs/0.0.4.md @@ -0,0 +1,3 @@ +# Amber - 0.0.4 + +- Fix for id and pubkey not showing diff --git a/docs/changelogs/0.0.5.md b/docs/changelogs/0.0.5.md new file mode 100644 index 00000000..3c5c0481 --- /dev/null +++ b/docs/changelogs/0.0.5.md @@ -0,0 +1,6 @@ +# Amber - 0.0.5 + +- Fix error deserializing json when there's no id or pubkey +- Created a button to copy the raw json of the event + +![image](https://github.com/greenart7c3/Amber/assets/115044884/4bd9e7e2-3f4e-457c-961e-d29d4c84e946) diff --git a/docs/changelogs/0.0.6.md b/docs/changelogs/0.0.6.md new file mode 100644 index 00000000..6637829b --- /dev/null +++ b/docs/changelogs/0.0.6.md @@ -0,0 +1,5 @@ +# Amber - 0.0.6 + +- Ugly icon +- Preparations to decrypt/encrypt dm's +- Only scroll the raw json diff --git a/docs/changelogs/0.0.7.md b/docs/changelogs/0.0.7.md new file mode 100644 index 00000000..0a3482e8 --- /dev/null +++ b/docs/changelogs/0.0.7.md @@ -0,0 +1,5 @@ +# Amber - 0.0.7 + +- Support for get_public_key +- UI for encrypt/decrypt nip04 +- Updated dependencies diff --git a/docs/changelogs/0.0.8.md b/docs/changelogs/0.0.8.md new file mode 100644 index 00000000..f7c50ff2 --- /dev/null +++ b/docs/changelogs/0.0.8.md @@ -0,0 +1,3 @@ +# Amber 0.0.8 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.0.9.md b/docs/changelogs/0.0.9.md new file mode 100644 index 00000000..af05bdd5 --- /dev/null +++ b/docs/changelogs/0.0.9.md @@ -0,0 +1,3 @@ +# Amber 0.0.9 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.1.0.md b/docs/changelogs/0.1.0.md new file mode 100644 index 00000000..a223de45 --- /dev/null +++ b/docs/changelogs/0.1.0.md @@ -0,0 +1,4 @@ +# Amber - 0.1.0 + +- When you have remember my choice checked you can use content resolver to sign events in background +- Created a button to reset all permissions diff --git a/docs/changelogs/0.1.1.md b/docs/changelogs/0.1.1.md new file mode 100644 index 00000000..882c20c1 --- /dev/null +++ b/docs/changelogs/0.1.1.md @@ -0,0 +1,3 @@ +# Amber 0.1.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.1.2.md b/docs/changelogs/0.1.2.md new file mode 100644 index 00000000..ad0740ae --- /dev/null +++ b/docs/changelogs/0.1.2.md @@ -0,0 +1,3 @@ +# Amber 0.1.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.1.3.md b/docs/changelogs/0.1.3.md new file mode 100644 index 00000000..185a05ab --- /dev/null +++ b/docs/changelogs/0.1.3.md @@ -0,0 +1,3 @@ +# Amber 0.1.3 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.1.4.md b/docs/changelogs/0.1.4.md new file mode 100644 index 00000000..0f3a28aa --- /dev/null +++ b/docs/changelogs/0.1.4.md @@ -0,0 +1,4 @@ +# Amber - 0.1.4 + +- Code cleanup +- Fix crash with zaps with no "e" tag diff --git a/docs/changelogs/0.2.0.md b/docs/changelogs/0.2.0.md new file mode 100644 index 00000000..3a7dd572 --- /dev/null +++ b/docs/changelogs/0.2.0.md @@ -0,0 +1,11 @@ +# Amber - 0.2.0 + +- Upgrade to material 3 dependencies +- Created settings and permissions screen +- Added arm64-v8a and armeabi-v7a builds + +![f52df91be87335d7d3ad1b5a951e9718b88e21760b7a28571200cd218c41c394](https://image.nostr.build/f52df91be87335d7d3ad1b5a951e9718b88e21760b7a28571200cd218c41c394.png) + +![d1dd32e59a9761e158dfbcb6b2089f022e2084ae3d422cfc314a22d1ff0f845b](https://image.nostr.build/d1dd32e59a9761e158dfbcb6b2089f022e2084ae3d422cfc314a22d1ff0f845b.png) + +![8db6e214d2a9030e370e1a42afc4df5cf54e81265df1de4e5ba9db6d4565b53f](https://image.nostr.build/8db6e214d2a9030e370e1a42afc4df5cf54e81265df1de4e5ba9db6d4565b53f.png) diff --git a/docs/changelogs/0.3.0.md b/docs/changelogs/0.3.0.md new file mode 100644 index 00000000..ac6f9fd6 --- /dev/null +++ b/docs/changelogs/0.3.0.md @@ -0,0 +1,3 @@ +# Amber - 0.3.0 + +- Support for multiple accounts diff --git a/docs/changelogs/0.3.1.md b/docs/changelogs/0.3.1.md new file mode 100644 index 00000000..27c03378 --- /dev/null +++ b/docs/changelogs/0.3.1.md @@ -0,0 +1,5 @@ +# Amber - 0.3.1 + +- Added an option to name your accounts + +![Screenshot_20230927_160102](https://github.com/greenart7c3/Amber/assets/115044884/c7e7f299-32f9-4ff1-844e-273964bb8bc4) diff --git a/docs/changelogs/0.3.2.md b/docs/changelogs/0.3.2.md new file mode 100644 index 00000000..c2b2e3c4 --- /dev/null +++ b/docs/changelogs/0.3.2.md @@ -0,0 +1,3 @@ +# Amber 0.3.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.0.md b/docs/changelogs/0.4.0.md new file mode 100644 index 00000000..9e6774bc --- /dev/null +++ b/docs/changelogs/0.4.0.md @@ -0,0 +1,5 @@ +# Amber - 0.4.0 + +- Change the current account by pressing the Top AppBar +- Add Show/Hide details button on all signer types +- Updated readme with an example on how to send the intent from a web client diff --git a/docs/changelogs/0.4.1.md b/docs/changelogs/0.4.1.md new file mode 100644 index 00000000..ca6d8a1f --- /dev/null +++ b/docs/changelogs/0.4.1.md @@ -0,0 +1,3 @@ +# Amber 0.4.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.2.md b/docs/changelogs/0.4.2.md new file mode 100644 index 00000000..22a7f529 --- /dev/null +++ b/docs/changelogs/0.4.2.md @@ -0,0 +1,3 @@ +# Amber 0.4.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.3.md b/docs/changelogs/0.4.3.md new file mode 100644 index 00000000..007aa04c --- /dev/null +++ b/docs/changelogs/0.4.3.md @@ -0,0 +1,3 @@ +# Amber 0.4.3 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.4.md b/docs/changelogs/0.4.4.md new file mode 100644 index 00000000..85026e57 --- /dev/null +++ b/docs/changelogs/0.4.4.md @@ -0,0 +1,3 @@ +# Amber 0.4.4 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.5.md b/docs/changelogs/0.4.5.md new file mode 100644 index 00000000..ab1b3b4e --- /dev/null +++ b/docs/changelogs/0.4.5.md @@ -0,0 +1,3 @@ +# Amber 0.4.5 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.6.md b/docs/changelogs/0.4.6.md new file mode 100644 index 00000000..00524292 --- /dev/null +++ b/docs/changelogs/0.4.6.md @@ -0,0 +1,3 @@ +# Amber 0.4.6 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.4.7.md b/docs/changelogs/0.4.7.md new file mode 100644 index 00000000..7648e933 --- /dev/null +++ b/docs/changelogs/0.4.7.md @@ -0,0 +1,3 @@ +# Amber 0.4.7 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.5.0.md b/docs/changelogs/0.5.0.md new file mode 100644 index 00000000..8f851b44 --- /dev/null +++ b/docs/changelogs/0.5.0.md @@ -0,0 +1,7 @@ +# Amber - 0.5.0 + +- Created history screen +- Show the relay url when it's an auth event +- Show app version in the settings screen +- Fix bottom sheet overlapping nav buttons +- Change content provider name in debug diff --git a/docs/changelogs/0.5.1.md b/docs/changelogs/0.5.1.md new file mode 100644 index 00000000..0429e091 --- /dev/null +++ b/docs/changelogs/0.5.1.md @@ -0,0 +1,3 @@ +# Amber 0.5.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.5.2.md b/docs/changelogs/0.5.2.md new file mode 100644 index 00000000..1107fc5e --- /dev/null +++ b/docs/changelogs/0.5.2.md @@ -0,0 +1,4 @@ +# Amber - 0.5.2 + +- Updated dependencies +- also check return type when not using callback url diff --git a/docs/changelogs/0.5.3.md b/docs/changelogs/0.5.3.md new file mode 100644 index 00000000..e67621df --- /dev/null +++ b/docs/changelogs/0.5.3.md @@ -0,0 +1,5 @@ +# Amber - 0.5.3 + +- Updated dependencies +- Show event kind in history tab +- Fix generate new key button hidden on some devices diff --git a/docs/changelogs/0.6.0.md b/docs/changelogs/0.6.0.md new file mode 100644 index 00000000..afeacb7e --- /dev/null +++ b/docs/changelogs/0.6.0.md @@ -0,0 +1,3 @@ +# Amber 0.6.0 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.6.1.md b/docs/changelogs/0.6.1.md new file mode 100644 index 00000000..dfea66a4 --- /dev/null +++ b/docs/changelogs/0.6.1.md @@ -0,0 +1,3 @@ +# Amber 0.6.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.6.3.md b/docs/changelogs/0.6.3.md new file mode 100644 index 00000000..56dcd8aa --- /dev/null +++ b/docs/changelogs/0.6.3.md @@ -0,0 +1,3 @@ +# Amber 0.6.3 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.6.4.md b/docs/changelogs/0.6.4.md new file mode 100644 index 00000000..935f4e2e --- /dev/null +++ b/docs/changelogs/0.6.4.md @@ -0,0 +1,3 @@ +# Amber 0.6.4 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.6.5.md b/docs/changelogs/0.6.5.md new file mode 100644 index 00000000..7d032dc0 --- /dev/null +++ b/docs/changelogs/0.6.5.md @@ -0,0 +1,8 @@ +# 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/beb0311cf9b4a5d2f39b5a8f8a3bfe3ed9da8b86e07d6a70e9308d81d368130e.png) + +![https://image.nostr.build/18ab69385278ddddd87e82f7ec41e353a2490f66333f9e0c35bda0644bfc9f8e.png](https://image.nostr.build/18ab69385278ddddd87e82f7ec41e353a2490f66333f9e0c35bda0644bfc9f8e.png) diff --git a/docs/changelogs/0.6.6.md b/docs/changelogs/0.6.6.md new file mode 100644 index 00000000..db1ad4e7 --- /dev/null +++ b/docs/changelogs/0.6.6.md @@ -0,0 +1,3 @@ +# Amber - 0.6.6 + +- Fix encryption/decryption in web apps diff --git a/docs/changelogs/0.7.0.md b/docs/changelogs/0.7.0.md new file mode 100644 index 00000000..43639b0f --- /dev/null +++ b/docs/changelogs/0.7.0.md @@ -0,0 +1,3 @@ +# Amber 0.7.0 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.7.1.md b/docs/changelogs/0.7.1.md new file mode 100644 index 00000000..18ec81fc --- /dev/null +++ b/docs/changelogs/0.7.1.md @@ -0,0 +1,5 @@ +# Amber 0.7.1 + +Amber - v0.7.1 + +- Moves to NIP-44v2 diff --git a/docs/changelogs/0.7.2.md b/docs/changelogs/0.7.2.md new file mode 100644 index 00000000..da6dcbe0 --- /dev/null +++ b/docs/changelogs/0.7.2.md @@ -0,0 +1,7 @@ +# Amber 0.7.2 + +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 diff --git a/docs/changelogs/0.7.3.md b/docs/changelogs/0.7.3.md new file mode 100644 index 00000000..51676384 --- /dev/null +++ b/docs/changelogs/0.7.3.md @@ -0,0 +1,3 @@ +# Amber 0.7.3 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.7.4.md b/docs/changelogs/0.7.4.md new file mode 100644 index 00000000..9a729ff9 --- /dev/null +++ b/docs/changelogs/0.7.4.md @@ -0,0 +1,12 @@ +# Amber - v0.7.4 + +- Remember my choice now works when you reject the event + +Applications will need to update to the new spec. +You can check how to implement it in this pull request in Amethyst and in the Amber readme file: + +https://github.com/vitorpamplona/amethyst/pull/744 + +https://github.com/greenart7c3/Amber + +Basically you need to send a new parameter in the contentResolver.query and check if Amber returned the column "rejected" diff --git a/docs/changelogs/0.7.5.md b/docs/changelogs/0.7.5.md new file mode 100644 index 00000000..e1ccbba7 --- /dev/null +++ b/docs/changelogs/0.7.5.md @@ -0,0 +1,4 @@ +# Amber - v0.7.5 + +- Updated dependencies +- Fix edit permission screen showing permissions from every app diff --git a/docs/changelogs/0.7.6.md b/docs/changelogs/0.7.6.md new file mode 100644 index 00000000..cfa1fd01 --- /dev/null +++ b/docs/changelogs/0.7.6.md @@ -0,0 +1,3 @@ +# Amber 0.7.6 + +No release notes were provided for this version. diff --git a/docs/changelogs/0.8.0.md b/docs/changelogs/0.8.0.md new file mode 100644 index 00000000..8247a4e1 --- /dev/null +++ b/docs/changelogs/0.8.0.md @@ -0,0 +1,4 @@ +# Amber - v0.8.0 + +- Support for nip 49 (ncryptsec) +- Option to show you private keys as Qr Code diff --git a/docs/changelogs/0.8.1.md b/docs/changelogs/0.8.1.md new file mode 100644 index 00000000..77fd52e1 --- /dev/null +++ b/docs/changelogs/0.8.1.md @@ -0,0 +1,4 @@ +# Amber - v0.8.1 + +- Update dependencies +- Fix activity not clearing when using web clients diff --git a/docs/changelogs/0.8.2.md b/docs/changelogs/0.8.2.md new file mode 100644 index 00000000..73a6295d --- /dev/null +++ b/docs/changelogs/0.8.2.md @@ -0,0 +1,3 @@ +# Amber - v0.8.2 + +* Fix activity not clearing when using web clients diff --git a/docs/changelogs/1.0.0-pre.md b/docs/changelogs/1.0.0-pre.md new file mode 100644 index 00000000..01a1c552 --- /dev/null +++ b/docs/changelogs/1.0.0-pre.md @@ -0,0 +1,12 @@ +# Amber - 1.0.0 - Beta 1 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre10.md b/docs/changelogs/1.0.0-pre10.md new file mode 100644 index 00000000..cdaa1478 --- /dev/null +++ b/docs/changelogs/1.0.0-pre10.md @@ -0,0 +1,16 @@ +# Amber - 1.0.0 - Beta 10 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents +- Fix decryption for web apps using intents + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre11.md b/docs/changelogs/1.0.0-pre11.md new file mode 100644 index 00000000..93a476cb --- /dev/null +++ b/docs/changelogs/1.0.0-pre11.md @@ -0,0 +1,17 @@ +# Amber - 1.0.0 - Beta 11 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents +- Fix decryption for web apps using intents +- Added activity history screen + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre12.md b/docs/changelogs/1.0.0-pre12.md new file mode 100644 index 00000000..28f1e4d0 --- /dev/null +++ b/docs/changelogs/1.0.0-pre12.md @@ -0,0 +1,17 @@ +# Amber - 1.0.0 - Beta 12 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents +- Fix decryption for web apps using intents +- Added activity history screen + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre2.md b/docs/changelogs/1.0.0-pre2.md new file mode 100644 index 00000000..20b3e7f0 --- /dev/null +++ b/docs/changelogs/1.0.0-pre2.md @@ -0,0 +1,14 @@ +# Amber - 1.0.0 - Beta 2 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Fixes Account name editing + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre3.md b/docs/changelogs/1.0.0-pre3.md new file mode 100644 index 00000000..a9e127b0 --- /dev/null +++ b/docs/changelogs/1.0.0-pre3.md @@ -0,0 +1,3 @@ +# Amber 1.0.0-pre3 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.0.0-pre4.md b/docs/changelogs/1.0.0-pre4.md new file mode 100644 index 00000000..7bfc6eff --- /dev/null +++ b/docs/changelogs/1.0.0-pre4.md @@ -0,0 +1,3 @@ +# Amber 1.0.0-pre4 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.0.0-pre5.md b/docs/changelogs/1.0.0-pre5.md new file mode 100644 index 00000000..3255a84e --- /dev/null +++ b/docs/changelogs/1.0.0-pre5.md @@ -0,0 +1,15 @@ +# Amber - 1.0.0 - Beta 5 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Fixes Account name editing +- Add settings to connect to relay directly + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre6.md b/docs/changelogs/1.0.0-pre6.md new file mode 100644 index 00000000..b5d45495 --- /dev/null +++ b/docs/changelogs/1.0.0-pre6.md @@ -0,0 +1,14 @@ +# Amber - 1.0.0 - Beta 6 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre7.md b/docs/changelogs/1.0.0-pre7.md new file mode 100644 index 00000000..bfb19631 --- /dev/null +++ b/docs/changelogs/1.0.0-pre7.md @@ -0,0 +1,15 @@ +# Amber - 1.0.0 - Beta 7 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0-pre9.md b/docs/changelogs/1.0.0-pre9.md new file mode 100644 index 00000000..fa3c83c9 --- /dev/null +++ b/docs/changelogs/1.0.0-pre9.md @@ -0,0 +1,16 @@ +# Amber - 1.0.0 - Beta 9 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents +- Fix decryption for web apps using intents + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.0.md b/docs/changelogs/1.0.0.md new file mode 100644 index 00000000..b50c8c27 --- /dev/null +++ b/docs/changelogs/1.0.0.md @@ -0,0 +1,17 @@ +# Amber - 1.0.0 + +- Amber now supports nip 46 +- There's 3 versions of the application to download now: + - Play - This uses the google services push notifications + - Free - This uses ntfy push notifications + - Offline - This does not support nip 46 +- Support for Orbot proxy +- Add settings to connect to relay directly +- Fix crash when using web applications with nostrsigner: intents +- Fix decryption for web apps using intents +- Added activity history screen + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.0-pre) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.1.md b/docs/changelogs/1.0.1.md new file mode 100644 index 00000000..f42ab2cf --- /dev/null +++ b/docs/changelogs/1.0.1.md @@ -0,0 +1,10 @@ +# Amber - 1.0.1 + +- Fix private zaps +- French translation - @npub106efcyntxc5qwl3w8krrhyt626m59ya2nk9f40px5s968u5xdwhsjsr8fz +- Swahili translation - @npub1q6ps7m94jfdastx2tx76sj8sq4nxdhlsgmzns2tr4xt6ydx6grzspm0kxr + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.1) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.2.md b/docs/changelogs/1.0.2.md new file mode 100644 index 00000000..dd9540a5 --- /dev/null +++ b/docs/changelogs/1.0.2.md @@ -0,0 +1,13 @@ +# Amber - 1.0.2 + +- Implemented sign_message +- Fix notification text +- Don't send the error field when there's no error +- Fix get_public_key when using bunker +- Support for seed words in the login screen +- Show relay error messages to the user + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.2) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.3.md b/docs/changelogs/1.0.3.md new file mode 100644 index 00000000..3eb5973a --- /dev/null +++ b/docs/changelogs/1.0.3.md @@ -0,0 +1,12 @@ +# Amber - 1.0.3 + +- Fix missing permission when asking for multiple permissions +- update dependencies +- german translations by @npub19a6x8frkkn2660fw0flz74a7qg8c2jxk5v9p2rsh7tv5e6ftsq3sav63vp +- chinese translations by @npub1gd8e0xfkylc7v8c5a6hkpj4gelwwcy99jt90lqjseqjj2t253s2s6ch58h +- french translations by @npub106efcyntxc5qwl3w8krrhyt626m59ya2nk9f40px5s968u5xdwhsjsr8fz + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.3) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.4.md b/docs/changelogs/1.0.4.md new file mode 100644 index 00000000..d253eeee --- /dev/null +++ b/docs/changelogs/1.0.4.md @@ -0,0 +1,9 @@ +# Amber 1.0.4 + +- Fix relay button showing for native applications +- Improve the layout of the edit permissions screen + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.4) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.5.md b/docs/changelogs/1.0.5.md new file mode 100644 index 00000000..179dc883 --- /dev/null +++ b/docs/changelogs/1.0.5.md @@ -0,0 +1,11 @@ +# Amber 1.0.5 + +- Add a timeout when accepting/rejecting events from nip 46 +- Add a retry logic when using nip 46 +- Fix a bug that added a new app when rejecting a connect request +- Only update the connection status of an application after the relay response + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.5) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.6.md b/docs/changelogs/1.0.6.md new file mode 100644 index 00000000..fbe77abb --- /dev/null +++ b/docs/changelogs/1.0.6.md @@ -0,0 +1,8 @@ +# Amber 1.0.6 + +- Relay connection improvements + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.6) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.7-pre2.md b/docs/changelogs/1.0.7-pre2.md new file mode 100644 index 00000000..9dac7226 --- /dev/null +++ b/docs/changelogs/1.0.7-pre2.md @@ -0,0 +1,9 @@ +# Amber 1.0.7 - Beta 2 + +- Log screen (Setting -> Logs) +- Improved error handling and relay connection + +Download it with [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page +](https://github.com/greenart7c3/Amber/releases/tag/v1.0.7-pre2) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.7.md b/docs/changelogs/1.0.7.md new file mode 100644 index 00000000..82688563 --- /dev/null +++ b/docs/changelogs/1.0.7.md @@ -0,0 +1,9 @@ +# Amber 1.0.7 + +- Log screen (Setting -> Logs) +- Improved error handling and relay connection +- Fix permissions screen when a permission contains a large text + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.0.7) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.8.md b/docs/changelogs/1.0.8.md new file mode 100644 index 00000000..058323b8 --- /dev/null +++ b/docs/changelogs/1.0.8.md @@ -0,0 +1,12 @@ +# Amber 1.0.8 + +- Fix login with qrcode silent failing +- Fix messages appearing when it's not supposed to +- Fix connection with relay when app is in background +- Fix remember my choice not working when receiving multiple events +- Added a option to change the default relay +- Add a relay icon in the app bar to show connected relays and logs + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.0.8) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.0.9.md b/docs/changelogs/1.0.9.md new file mode 100644 index 00000000..6c464cec --- /dev/null +++ b/docs/changelogs/1.0.9.md @@ -0,0 +1,8 @@ +# Amber 1.0.9 + +- Added setting to choose the notification distributor when using the free edition +- Added more logs to the notifications + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.0.9) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.1.0-pre1.md b/docs/changelogs/1.1.0-pre1.md new file mode 100644 index 00000000..32a5eff3 --- /dev/null +++ b/docs/changelogs/1.1.0-pre1.md @@ -0,0 +1,13 @@ +# Amber 1.1.0 - Beta 1 + +- Fix app opening when not supposed to when using some native apps +- Always run a service so the app is not stopped by the os +- Show a message if there's no unified push distributor installed +- Fix translations when there's a notification +- Upgrade to kotlin 2 +- Try to restart the app when the app is updated +- Fix dns issues when in deep sleep + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.1.-0-pre1) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.1.0.md b/docs/changelogs/1.1.0.md new file mode 100644 index 00000000..5ab6510e --- /dev/null +++ b/docs/changelogs/1.1.0.md @@ -0,0 +1,13 @@ +# Amber 1.1.0 + +- Fix app opening when not supposed to when using some native apps +- Always run a service so the app is not stopped by the os +- Show a message if there's no unified push distributor installed +- Fix translations when there's a notification +- Upgrade to kotlin 2 +- Try to restart the app when the app is updated +- Fix dns issues when in deep sleep + +Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.1.-0-pre1) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.1.1.md b/docs/changelogs/1.1.1.md new file mode 100644 index 00000000..39cafd2b --- /dev/null +++ b/docs/changelogs/1.1.1.md @@ -0,0 +1,11 @@ +# Amber 1.1.1 + +- Support for sending and receiving bunker requests with nip44 +- Fix remember my choice not working for reject when not using content resolvers +- Improvements to edit relay screen +- Option to listen to new connections without creating new application +- Option to setup biometrics/pin + +Download it with [zap.store](https://zap.store/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/v1.1.1) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.1.2.md b/docs/changelogs/1.1.2.md new file mode 100644 index 00000000..8885a99e --- /dev/null +++ b/docs/changelogs/1.1.2.md @@ -0,0 +1,3 @@ +# Amber 1.1.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.2.0.md b/docs/changelogs/1.2.0.md new file mode 100644 index 00000000..bbbb2e80 --- /dev/null +++ b/docs/changelogs/1.2.0.md @@ -0,0 +1,10 @@ +# Amber 1.2.0 + +- Support for sending nips as permissions instead of kinds +- Better descriptions for nip 29 event kinds +- Don't let secret be used twice +- Improved sending events with nip 46 + +Download it with [zap.store](https://zap.store/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/v1.2.0) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.0-pre1.md b/docs/changelogs/1.3.0-pre1.md new file mode 100644 index 00000000..c69773ac --- /dev/null +++ b/docs/changelogs/1.3.0-pre1.md @@ -0,0 +1,8 @@ +# Amber 1.3.0 - Beta 1 + +- Login/Signup redesign +- Support for seed words + +Download it with [zap.store](https://zap.store/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/v1.2.0) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.0-pre2.md b/docs/changelogs/1.3.0-pre2.md new file mode 100644 index 00000000..7537f477 --- /dev/null +++ b/docs/changelogs/1.3.0-pre2.md @@ -0,0 +1,3 @@ +# Amber 1.3.0-pre2 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.3.0-pre3.md b/docs/changelogs/1.3.0-pre3.md new file mode 100644 index 00000000..785d8864 --- /dev/null +++ b/docs/changelogs/1.3.0-pre3.md @@ -0,0 +1,3 @@ +# Amber 1.3.0-pre3 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.3.0-pre4.md b/docs/changelogs/1.3.0-pre4.md new file mode 100644 index 00000000..2bf9bb3d --- /dev/null +++ b/docs/changelogs/1.3.0-pre4.md @@ -0,0 +1,10 @@ +# Amber 1.3.0 - Beta 4 + +- Login/Signup redesign +- Support for seed words +- Sign policy settings +- Show permissions without having to click the notification if the application is open + +Download it with [zap.store](https://zap.store/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/v1.2.0) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.0.md b/docs/changelogs/1.3.0.md new file mode 100644 index 00000000..85646b87 --- /dev/null +++ b/docs/changelogs/1.3.0.md @@ -0,0 +1,10 @@ +# Amber 1.3.0 + +- Login/Signup redesign +- Support for seed words +- Sign policy settings +- Show permissions without having to click the notification if the application is open + +Download it with [zap.store](https://zap.store/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/v1.3.0) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.1.md b/docs/changelogs/1.3.1.md new file mode 100644 index 00000000..c5be3634 --- /dev/null +++ b/docs/changelogs/1.3.1.md @@ -0,0 +1,12 @@ +# Amber 1.3.1 + +- Fix reject button not working +- Group multiple events +- Only show message of no distributors installed when not using direct connection to relays +- Update dependencies + +https://image.nostr.build/c699ba5496804fe3465190ca492c59a9968dec0225b6c30823f950525fcfdce5.png + +Download it with [zap.store](https://zap.store/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/v1.3.1) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.2.md b/docs/changelogs/1.3.2.md new file mode 100644 index 00000000..de03aaf4 --- /dev/null +++ b/docs/changelogs/1.3.2.md @@ -0,0 +1,3 @@ +# Amber 1.3.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/1.3.3.md b/docs/changelogs/1.3.3.md new file mode 100644 index 00000000..b659da60 --- /dev/null +++ b/docs/changelogs/1.3.3.md @@ -0,0 +1,10 @@ +# Amber 1.3.3 + +- Fix a crash when signing events in background +- Updated dependencies +- Fixes in the push notification when using ntfy +- Changed remember my choice position when receiving multiple events + +Download it with [zap.store](https://zap.store/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/v1.3.3) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.4.md b/docs/changelogs/1.3.4.md new file mode 100644 index 00000000..623e14c2 --- /dev/null +++ b/docs/changelogs/1.3.4.md @@ -0,0 +1,10 @@ +# Amber 1.3.4 + +- Fix nostrconnect uri parser +- Change foreground service type +- Support for permissions when using nostrconnect uri +- UI changes when receiving multiple events + +Download it with [zap.store](https://zap.store/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/v1.3.4) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.5.md b/docs/changelogs/1.3.5.md new file mode 100644 index 00000000..1473c5fe --- /dev/null +++ b/docs/changelogs/1.3.5.md @@ -0,0 +1,7 @@ +# Amber 1.3.5 + +- Fix some connection issues + +Download it with [zap.store](https://zap.store/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/v1.3.5) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.6.md b/docs/changelogs/1.3.6.md new file mode 100644 index 00000000..1f78e848 --- /dev/null +++ b/docs/changelogs/1.3.6.md @@ -0,0 +1,9 @@ +# Amber 1.3.6 + +- More connection fixes +- Don't register to the push server when using direct connection +- if theres no relay use the default relays + +Download it with [zap.store](https://zap.store/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/v1.3.6) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/1.3.7.md b/docs/changelogs/1.3.7.md new file mode 100644 index 00000000..546efc3b --- /dev/null +++ b/docs/changelogs/1.3.7.md @@ -0,0 +1,9 @@ +# Amber 1.3.7 + +- Fix connection to the push notification server when using gCompat UP distributor +- Added more event descriptions +- Updated dependencies + +Download it with [zap.store](https://zap.store/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/v1.3.7) + +If you like my work consider making a [donation](https://greenart7c3.com) diff --git a/docs/changelogs/2.0.0.md b/docs/changelogs/2.0.0.md new file mode 100644 index 00000000..2d00fc5e --- /dev/null +++ b/docs/changelogs/2.0.0.md @@ -0,0 +1,39 @@ +# Amber 2.0.0 + +- New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version +- When you not configured a notification type Amber will ask you to configure and default to direct connection to relays +- Check if is a valid relay before adding it when changing the default relays or adding a relay to a application + +Download it with [zap.store](https://zap.store/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/v2.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-v2.0.0.txt` and `manifest-v2.0.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.0.txt.sig manifest-v2.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 " +``` + +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-v2.0.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. diff --git a/docs/changelogs/2.0.1.md b/docs/changelogs/2.0.1.md new file mode 100644 index 00000000..a4c119d2 --- /dev/null +++ b/docs/changelogs/2.0.1.md @@ -0,0 +1,39 @@ +# Amber 2.0.1 + +- New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version +- When you not configured a notification type Amber will ask you to configure and default to direct connection to relays +- Check if is a valid relay before adding it when changing the default relays or adding a relay to a application + +Download it with [zap.store](https://zap.store/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/v2.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-v2.0.1.txt` and `manifest-v2.0.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.1.txt.sig manifest-v2.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-v2.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. diff --git a/docs/changelogs/2.0.2.md b/docs/changelogs/2.0.2.md new file mode 100644 index 00000000..c750f6f3 --- /dev/null +++ b/docs/changelogs/2.0.2.md @@ -0,0 +1,38 @@ +# Amber 2.0.2 + +- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version +- Redesign the multi event screen + +Download it with [zap.store](https://zap.store/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/v2.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-v2.0.2.txt` and `manifest-v2.0.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.2.txt.sig manifest-v2.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 " +``` + +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-v2.0.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. diff --git a/docs/changelogs/2.0.3.md b/docs/changelogs/2.0.3.md new file mode 100644 index 00000000..be9e4750 --- /dev/null +++ b/docs/changelogs/2.0.3.md @@ -0,0 +1,38 @@ +# Amber 2.0.3 + +- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version +- Fix crash when signing multiple events + +Download it with [zap.store](https://zap.store/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/v2.0.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-v2.0.3.txt` and `manifest-v2.0.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.3.txt.sig manifest-v2.0.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-v2.0.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. diff --git a/docs/changelogs/2.0.4.md b/docs/changelogs/2.0.4.md new file mode 100644 index 00000000..b8795897 --- /dev/null +++ b/docs/changelogs/2.0.4.md @@ -0,0 +1,40 @@ +# Amber 2.0.4 + +- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version +- Update dependencies +- When using a native app always show the package id +- When reading a QrCode in the login screen make it lowercase + +Download it with [zap.store](https://zap.store/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/v2.0.4) + +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-v2.0.4.txt` and `manifest-v2.0.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.4.txt.sig manifest-v2.0.4.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-v2.0.4.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. diff --git a/docs/changelogs/2.0.5.md b/docs/changelogs/2.0.5.md new file mode 100644 index 00000000..dc5507b7 --- /dev/null +++ b/docs/changelogs/2.0.5.md @@ -0,0 +1,38 @@ +# Amber 2.0.5 + +- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version +- Fix nip 04 decryption for web applications + +Download it with [zap.store](https://zap.store/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/v2.0.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-v2.0.5.txt` and `manifest-v2.0.5.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.5.txt.sig manifest-v2.0.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 " +``` + +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-v2.0.5.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. diff --git a/docs/changelogs/2.0.6.md b/docs/changelogs/2.0.6.md new file mode 100644 index 00000000..06dec2d0 --- /dev/null +++ b/docs/changelogs/2.0.6.md @@ -0,0 +1,42 @@ +# Amber 2.0.6 + +- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version +- Fix remember my choice when rejecting the event +- Update dependencies +- Fix crash when not sending id in the content provider +- Fix seed words not being saved correctly +- Fix empty permission when using bunker + +Download it with [zap.store](https://zap.store/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/v2.0.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-v2.0.6.txt` and `manifest-v2.0.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.6.txt.sig manifest-v2.0.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-v2.0.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. diff --git a/docs/changelogs/2.0.7.md b/docs/changelogs/2.0.7.md new file mode 100644 index 00000000..610ffeea --- /dev/null +++ b/docs/changelogs/2.0.7.md @@ -0,0 +1,37 @@ +# Amber 2.0.7 + +- Fix -null in nip 4 encryption + +Download it with [zap.store](https://zap.store/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/v2.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-v2.0.7.txt` and `manifest-v2.0.7.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.7.txt.sig manifest-v2.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 " +``` + +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-v2.0.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. diff --git a/docs/changelogs/2.0.8.md b/docs/changelogs/2.0.8.md new file mode 100644 index 00000000..5a5e4a8f --- /dev/null +++ b/docs/changelogs/2.0.8.md @@ -0,0 +1,37 @@ +# Amber 2.0.8 + +- Fix signing private zaps + +Download it with [zap.store](https://zap.store/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/v2.0.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-v2.0.8.txt` and `manifest-v2.0.8.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v2.0.8.txt.sig manifest-v2.0.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-v2.0.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. diff --git a/docs/changelogs/3.0.0-pre1.md b/docs/changelogs/3.0.0-pre1.md new file mode 100644 index 00000000..2c470236 --- /dev/null +++ b/docs/changelogs/3.0.0-pre1.md @@ -0,0 +1,44 @@ +# Amber 3.0.0 - Beta 1 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key + +Download it with [zap.store](https://zap.store/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.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-v3.0.0-pre1.txt` and `manifest-v3.0.0-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre1.txt.sig manifest-v3.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 " +``` + +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.0-pre1.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. diff --git a/docs/changelogs/3.0.0-pre2.md b/docs/changelogs/3.0.0-pre2.md new file mode 100644 index 00000000..e4d45bb3 --- /dev/null +++ b/docs/changelogs/3.0.0-pre2.md @@ -0,0 +1,45 @@ +# Amber 3.0.0 - Beta 2 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 + +Download it with [zap.store](https://zap.store/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.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-v3.0.0-pre2.txt` and `manifest-v3.0.0-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0.txt-pre2.sig manifest-v3.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 " +``` + +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.0-pre2.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. diff --git a/docs/changelogs/3.0.0-pre3.md b/docs/changelogs/3.0.0-pre3.md new file mode 100644 index 00000000..00d541a9 --- /dev/null +++ b/docs/changelogs/3.0.0-pre3.md @@ -0,0 +1,48 @@ +# Amber 3.0.0 - Beta 3 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected + +Download it with [zap.store](https://zap.store/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.0.0-pre3) + +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.0-pre3.txt` and `manifest-v3.0.0-pre3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0.txt-pre2.sig manifest-v3.0.0-pre3.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.0-pre3.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. diff --git a/docs/changelogs/3.0.0-pre4.md b/docs/changelogs/3.0.0-pre4.md new file mode 100644 index 00000000..63fd022d --- /dev/null +++ b/docs/changelogs/3.0.0-pre4.md @@ -0,0 +1,49 @@ +# Amber 3.0.0 - Beta 4 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size + +Download it with [zap.store](https://zap.store/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.0.0-pre4) + +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.0-pre4.txt` and `manifest-v3.0.0-pre4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0.txt-pre2.sig manifest-v3.0.0-pre4.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.0-pre4.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. diff --git a/docs/changelogs/3.0.0-pre5.md b/docs/changelogs/3.0.0-pre5.md new file mode 100644 index 00000000..17432b37 --- /dev/null +++ b/docs/changelogs/3.0.0-pre5.md @@ -0,0 +1,55 @@ +# Amber 3.0.0 - Beta 5 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key + +Download it with [zap.store](https://zap.store/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.0.0-pre5) + +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.0-pre5.txt` and `manifest-v3.0.0-pre5.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre5.txt.sig manifest-v3.0.0-pre5.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.0-pre5.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. diff --git a/docs/changelogs/3.0.0-pre6.md b/docs/changelogs/3.0.0-pre6.md new file mode 100644 index 00000000..3d02c7e0 --- /dev/null +++ b/docs/changelogs/3.0.0-pre6.md @@ -0,0 +1,55 @@ +# Amber 3.0.0 - Beta 6 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key + +Download it with [zap.store](https://zap.store/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.0.0-pre6) + +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.0-pre6.txt` and `manifest-v3.0.0-pre6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre6.txt.sig manifest-v3.0.0-pre6.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.0-pre6.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. diff --git a/docs/changelogs/3.0.0-pre7.md b/docs/changelogs/3.0.0-pre7.md new file mode 100644 index 00000000..b49a2d95 --- /dev/null +++ b/docs/changelogs/3.0.0-pre7.md @@ -0,0 +1,57 @@ +# Amber 3.0.0 - Beta 7 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key +- Fix relay not connecting after adding a new bunker +- Fix logout not working sometimes + +Download it with [zap.store](https://zap.store/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.0.0-pre7) + +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.0-pre7.txt` and `manifest-v3.0.0-pre7.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre7.txt.sig manifest-v3.0.0-pre7.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.0-pre7.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. diff --git a/docs/changelogs/3.0.0-pre8.md b/docs/changelogs/3.0.0-pre8.md new file mode 100644 index 00000000..75f5dd54 --- /dev/null +++ b/docs/changelogs/3.0.0-pre8.md @@ -0,0 +1,57 @@ +# Amber 3.0.0 - Beta 8 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key +- Fix relay not connecting after adding a new bunker +- Fix logout not working sometimes + +Download it with [zap.store](https://zap.store/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.0.0-pre8) + +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.0-pre8.txt` and `manifest-v3.0.0-pre8.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre8.txt.sig manifest-v3.0.0-pre8.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.0-pre8.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. diff --git a/docs/changelogs/3.0.0-pre9.md b/docs/changelogs/3.0.0-pre9.md new file mode 100644 index 00000000..3ab28dda --- /dev/null +++ b/docs/changelogs/3.0.0-pre9.md @@ -0,0 +1,58 @@ +# Amber 3.0.0 - Beta 9 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key +- Fix relay not connecting after adding a new bunker +- Fix logout not working sometimes +- Fix login screen showing when trying to login to some applications + +Download it with [zap.store](https://zap.store/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.0.0-pre9) + +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.0-pre9.txt` and `manifest-v3.0.0-pre9.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0-pre9.txt.sig manifest-v3.0.0-pre9.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.0-pre9.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. diff --git a/docs/changelogs/3.0.0.md b/docs/changelogs/3.0.0.md new file mode 100644 index 00000000..f21c832e --- /dev/null +++ b/docs/changelogs/3.0.0.md @@ -0,0 +1,58 @@ +# Amber 3.0.0 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key +- Fix relay not connecting after adding a new bunker +- Fix logout not working sometimes +- Fix login screen showing when trying to login to some applications + +Download it with [zap.store](https://zap.store/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.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-v3.0.0.txt` and `manifest-v3.0.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.0.txt.sig manifest-v3.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 " +``` + +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.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. diff --git a/docs/changelogs/3.0.1.md b/docs/changelogs/3.0.1.md new file mode 100644 index 00000000..e2232597 --- /dev/null +++ b/docs/changelogs/3.0.1.md @@ -0,0 +1,59 @@ +# Amber 3.0.1 + +- New design (still a work in progress) +- Removed the push notification server +- Open the permissions page with the correct account +- Fix crash when signing in with ncryptsec +- Fix icon size on notifications +- Fix relay connection when changing the default relays +- Option to setup a custom pin for the app +- Button to copy your public key +- Fix layout on Android < 15 +- Fix multi event screen +- Fetch profile data +- Show relay message when event is rejected +- Fix profile icon size +- Don’t close app when using nostrconnect arcade +- Better check for valid relays +- Fix padding and scrolling +- Support for secret when using nostrconnect +- Fix empty relay notice +- Fix get_public_key not replying with hex key +- Fix relay not connecting after adding a new bunker +- Fix logout not working sometimes +- Fix login screen showing when trying to login to some applications +- Fix duplicated applications when connecting a new app + +Download it with [zap.store](https://zap.store/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.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. diff --git a/docs/changelogs/3.0.2.md b/docs/changelogs/3.0.2.md new file mode 100644 index 00000000..e876ee65 --- /dev/null +++ b/docs/changelogs/3.0.2.md @@ -0,0 +1,38 @@ +# Amber 3.0.2 + +- Improved onboarding +- Don’t show floating button when using the offline version + +Download it with [zap.store](https://zap.store/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.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-v3.0.2.txt` and `manifest-v3.0.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.2.txt.sig manifest-v3.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 " +``` + +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.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. diff --git a/docs/changelogs/3.0.3.md b/docs/changelogs/3.0.3.md new file mode 100644 index 00000000..dd2466f5 --- /dev/null +++ b/docs/changelogs/3.0.3.md @@ -0,0 +1,41 @@ +# Amber 3.0.3 + +- Fix racing condition when using bunkers +- Better pin entry screen +- Add a close application config in the ui +- Separate the service notification in a group +- Always return a hex key for the get_public_key method + +Download it with [zap.store](https://zap.store/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.0.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-v3.0.3.txt` and `manifest-v3.0.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.3.txt.sig manifest-v3.0.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-v3.0.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. diff --git a/docs/changelogs/3.0.4.md b/docs/changelogs/3.0.4.md new file mode 100644 index 00000000..a898df77 --- /dev/null +++ b/docs/changelogs/3.0.4.md @@ -0,0 +1,39 @@ +# Amber 3.0.4 + +- Revert sending hex key in the get_public_key method +- Fix connect request for bunkers +- Add appName parameter to web apps + +Download it with [zap.store](https://zap.store/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.0.4) + +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.4.txt` and `manifest-v3.0.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.4.txt.sig manifest-v3.0.4.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.4.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. diff --git a/docs/changelogs/3.0.5.md b/docs/changelogs/3.0.5.md new file mode 100644 index 00000000..8c3a04d1 --- /dev/null +++ b/docs/changelogs/3.0.5.md @@ -0,0 +1,39 @@ +# Amber 3.0.5 + +- Add appName parameter for web apps using nip 55 +- Try to fix bunker requests showing up again after accepting/rejecting them +- Fix loading screen + +Download it with [zap.store](https://zap.store/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.0.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.0.5.txt` and `manifest-v3.0.5.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.5.txt.sig manifest-v3.0.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 " +``` + +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.5.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. diff --git a/docs/changelogs/3.0.6.md b/docs/changelogs/3.0.6.md new file mode 100644 index 00000000..ef5a64c8 --- /dev/null +++ b/docs/changelogs/3.0.6.md @@ -0,0 +1,37 @@ +# Amber 3.0.6 + +- Fix a crash when using some web apps + +Download it with [zap.store](https://zap.store/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.0.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-v3.0.6.txt` and `manifest-v3.0.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.6.txt.sig manifest-v3.0.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-v3.0.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. diff --git a/docs/changelogs/3.0.7.md b/docs/changelogs/3.0.7.md new file mode 100644 index 00000000..7fa8cabb --- /dev/null +++ b/docs/changelogs/3.0.7.md @@ -0,0 +1,38 @@ +# Amber 3.0.7 + +- Fix a crash when using some web apps +- Fix connected apps not marked as connected + +Download it with [zap.store](https://zap.store/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.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-v3.0.7.txt` and `manifest-v3.0.7.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.0.7.txt.sig manifest-v3.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 " +``` + +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.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. diff --git a/docs/changelogs/3.1.0.md b/docs/changelogs/3.1.0.md new file mode 100644 index 00000000..48110578 --- /dev/null +++ b/docs/changelogs/3.1.0.md @@ -0,0 +1,43 @@ +# Amber 3.1.0 + +- Fix bunker requests showing up again after accepting +- Move bunker and nostrconnect to its own files +- Fix a infinite loop when receiving bunker requests +- Show relays after the app is connected +- Recover service when app crashes +- Update quartz dependency +- Fix ui contrast when using dark theme + +Download it with [zap.store](https://zap.store/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.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. diff --git a/docs/changelogs/3.1.1.md b/docs/changelogs/3.1.1.md new file mode 100644 index 00000000..b9b59956 --- /dev/null +++ b/docs/changelogs/3.1.1.md @@ -0,0 +1,3 @@ +# Amber 3.1.1 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.2.md b/docs/changelogs/3.1.2.md new file mode 100644 index 00000000..2a4686b1 --- /dev/null +++ b/docs/changelogs/3.1.2.md @@ -0,0 +1,3 @@ +# Amber 3.1.2 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.3.md b/docs/changelogs/3.1.3.md new file mode 100644 index 00000000..b504ec13 --- /dev/null +++ b/docs/changelogs/3.1.3.md @@ -0,0 +1,3 @@ +# Amber 3.1.3 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.4.md b/docs/changelogs/3.1.4.md new file mode 100644 index 00000000..e81f4c1d --- /dev/null +++ b/docs/changelogs/3.1.4.md @@ -0,0 +1,3 @@ +# Amber 3.1.4 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.5.md b/docs/changelogs/3.1.5.md new file mode 100644 index 00000000..07044a8c --- /dev/null +++ b/docs/changelogs/3.1.5.md @@ -0,0 +1,3 @@ +# Amber 3.1.5 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.6.md b/docs/changelogs/3.1.6.md new file mode 100644 index 00000000..f1950dd0 --- /dev/null +++ b/docs/changelogs/3.1.6.md @@ -0,0 +1,3 @@ +# Amber 3.1.6 + +No release notes were provided for this version. diff --git a/docs/changelogs/3.1.7.md b/docs/changelogs/3.1.7.md new file mode 100644 index 00000000..587f63c5 --- /dev/null +++ b/docs/changelogs/3.1.7.md @@ -0,0 +1,39 @@ +# Amber 3.1.7 + +- Delete old history +- Add more logs when receiving bunker requests +- Check if it’s a valid method + +Download it with [zap.store](https://zap.store/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.1.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-v3.1.7.txt` and `manifest-v3.1.7.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.1.7.txt.sig manifest-v3.1.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-v3.1.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. diff --git a/docs/changelogs/3.1.8.md b/docs/changelogs/3.1.8.md new file mode 100644 index 00000000..802a179c --- /dev/null +++ b/docs/changelogs/3.1.8.md @@ -0,0 +1,39 @@ +# Amber 3.1.8 + +- Button to clear cached data in settings +- Fix multiple bunker requests not clearing when accepting or rejecting +- Show relays status in the notification + +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.1.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-v3.1.8.txt` and `manifest-v3.1.8.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.1.8.txt.sig manifest-v3.1.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-v3.1.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. diff --git a/docs/changelogs/3.1.9.md b/docs/changelogs/3.1.9.md new file mode 100644 index 00000000..36d99e6c --- /dev/null +++ b/docs/changelogs/3.1.9.md @@ -0,0 +1,38 @@ +# Amber 3.1.9 + +- Add missing logs for relay errors +- Change listen for new connections button text and icons + +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.1.9) + +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.9.txt` and `manifest-v3.1.9.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.1.9.txt.sig manifest-v3.1.9.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.9.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. diff --git a/docs/changelogs/3.2.0.md b/docs/changelogs/3.2.0.md new file mode 100644 index 00000000..59513107 --- /dev/null +++ b/docs/changelogs/3.2.0.md @@ -0,0 +1,41 @@ +# Amber 3.2.0 + +- Fix relay connection when starting the service +- Added profile picture in the incoming requests screen when using a large screen device +- Added more event kinds translations +- Added a log with the bunker request response +- Use the relay from the request to send the response when no app is found + +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.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. diff --git a/docs/changelogs/3.2.1.md b/docs/changelogs/3.2.1.md new file mode 100644 index 00000000..af97635f --- /dev/null +++ b/docs/changelogs/3.2.1.md @@ -0,0 +1,39 @@ +# Amber 3.2.1 + +- Add some details when signing a contact list +- Refactor check for logged in account +- After granting notification permissions show the notification + +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.2.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.2.1.txt` and `manifest-v3.2.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.1.txt.sig manifest-v3.2.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.2.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. diff --git a/docs/changelogs/3.2.2.md b/docs/changelogs/3.2.2.md new file mode 100644 index 00000000..6ce44b87 --- /dev/null +++ b/docs/changelogs/3.2.2.md @@ -0,0 +1,39 @@ +# Amber 3.2.2 + +- Allow to always reject permissions on the multi event screen +- Allow copying the bunker uri after connected +- Don't try to url decode requests by native apps + +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.2.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.2.2.txt` and `manifest-v3.2.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.2.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.2.3.md b/docs/changelogs/3.2.3.md new file mode 100644 index 00000000..c89709fc --- /dev/null +++ b/docs/changelogs/3.2.3.md @@ -0,0 +1,41 @@ +# Amber 3.2.3 + +- Add translation string for sign_message method +- Add a log when encryption/decryption fails +- Fix some lints +- Fix tor connection when enabling tor and trying to add a new relay +- Fix a crash when checking if the current logged in account is the same as the event + +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.2.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-v3.2.3.txt` and `manifest-v3.2.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.3.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.2.4.md b/docs/changelogs/3.2.4.md new file mode 100644 index 00000000..50ee43e0 --- /dev/null +++ b/docs/changelogs/3.2.4.md @@ -0,0 +1,37 @@ +# Amber 3.2.4 + +- Fix incoming request screen not appearing automatically when using the offline version of the app + +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.2.4) + +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.4.txt` and `manifest-v3.2.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.4.txt.sig manifest-v3.2.4.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.4.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. diff --git a/docs/changelogs/3.2.5.md b/docs/changelogs/3.2.5.md new file mode 100644 index 00000000..6989ed84 --- /dev/null +++ b/docs/changelogs/3.2.5.md @@ -0,0 +1,37 @@ +# Amber 3.2.5 + +- Added scroll bars + +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.2.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.2.5.txt` and `manifest-v3.2.5.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.5.txt.sig manifest-v3.2.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 " +``` + +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.5.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. diff --git a/docs/changelogs/3.2.6.md b/docs/changelogs/3.2.6.md new file mode 100644 index 00000000..ea3e6455 --- /dev/null +++ b/docs/changelogs/3.2.6.md @@ -0,0 +1,38 @@ +# Amber 3.2.6 + +- Use a fixed font scaling +- Update 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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.2.7.md b/docs/changelogs/3.2.7.md new file mode 100644 index 00000000..0549ecef --- /dev/null +++ b/docs/changelogs/3.2.7.md @@ -0,0 +1,58 @@ +# Amber 3.2.7 + +- refactor NostrSigner.getInstance() into NostrSigner.instance +- refactor: removed appDatase from parameters +- fix logged account switch when using bunkers +- Use bunker response from quartz +- Remove bunker request from the content pending intent +- Open amber when pressing the connected relays notification +- Fix connected relays notification +- Include zapstore in the new bunker and initial message +- Only show a backup message after sign up +- Add search to the activity screen +- Delete old logs and activities automatically +- Show option to never close the app when using bunker url +- Fix application activity logs not saving correctly +- Move relay listeners to it’s own files +- Cast to lowercase and trim data when logging in +- Separate general prefs and account prefs keys +- Fix tor connection when using a local relay +- Add loading indicator when trying to fetch profile picture +- Use Hex.decode from quartz instead of acinq +- Retry sending events when it fails +- Better message when orbot/tor is not working +- Only show orbot/tor in the login/signup once + +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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.2.8.md b/docs/changelogs/3.2.8.md new file mode 100644 index 00000000..fb0eae11 --- /dev/null +++ b/docs/changelogs/3.2.8.md @@ -0,0 +1,59 @@ +# Amber 3.2.8 + +- refactor NostrSigner.getInstance() into NostrSigner.instance +- refactor: removed appDatase from parameters +- fix logged account switch when using bunkers +- Use bunker response from quartz +- Remove bunker request from the content pending intent +- Open amber when pressing the connected relays notification +- Fix connected relays notification +- Include zapstore in the new bunker and initial message +- Only show a backup message after sign up +- Add search to the activity screen +- Delete old logs and activities automatically +- Show option to never close the app when using bunker url +- Fix application activity logs not saving correctly +- Move relay listeners to it’s own files +- Cast to lowercase and trim data when logging in +- Separate general prefs and account prefs keys +- Fix tor connection when using a local relay +- Add loading indicator when trying to fetch profile picture +- Use Hex.decode from quartz instead of acinq +- Retry sending events when it fails +- Better message when orbot/tor is not working +- Only show orbot/tor in the login/signup once +- Fix connection check when sending an event + +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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.2.9.md b/docs/changelogs/3.2.9.md new file mode 100644 index 00000000..5e79407c --- /dev/null +++ b/docs/changelogs/3.2.9.md @@ -0,0 +1,38 @@ +# Amber 3.2.9 + +- Show the error message when failed to convert private key +- Only show the seed words if the user has a valid seed word in the backup 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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.3.0.md b/docs/changelogs/3.3.0.md new file mode 100644 index 00000000..782188c5 --- /dev/null +++ b/docs/changelogs/3.3.0.md @@ -0,0 +1,37 @@ +# Amber 3.3.0 + +- Remove any special characters when pasting the nsec + +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.2.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-v3.2.6.txt` and `manifest-v3.2.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.2.6.txt.sig manifest-v3.2.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-v3.2.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. diff --git a/docs/changelogs/3.4.0.md b/docs/changelogs/3.4.0.md new file mode 100644 index 00000000..bb255228 --- /dev/null +++ b/docs/changelogs/3.4.0.md @@ -0,0 +1,45 @@ +# Amber 3.4.0 + +- Move from deprecated Autofill api +- Move from deprecated ClipboardManager api +- Move from encrypted shared preferences to DataStore and normal shared preferences +- Add more event translations +- Fix a crash when starting service +- Bigger qrcodes, increase brightness when showing the qrcode +- Added a option to accept/reject a permission temporarily +- Better connection handling when switching networks +- Fix reject for bunker requests always showing the request again + +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.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.4.0.txt` and `manifest-v3.4.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.0.txt.sig manifest-v3.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-v3.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. diff --git a/docs/changelogs/3.4.1.md b/docs/changelogs/3.4.1.md new file mode 100644 index 00000000..67fd2f93 --- /dev/null +++ b/docs/changelogs/3.4.1.md @@ -0,0 +1,46 @@ +# Amber 3.4.1 + +- Move from deprecated Autofill api +- Move from deprecated ClipboardManager api +- Move from encrypted shared preferences to DataStore and normal shared preferences +- Add more event translations +- Fix a crash when starting service +- Bigger qrcodes, increase brightness when showing the qrcode +- Added a option to accept/reject a permission temporarily +- Better connection handling when switching networks +- Fix reject for bunker requests always showing the request again +- Fix things not loading after migration to DataStore + +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.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.4.1.txt` and `manifest-v3.4.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.1.txt.sig manifest-v3.4.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.4.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. diff --git a/docs/changelogs/3.4.2-pre1.md b/docs/changelogs/3.4.2-pre1.md new file mode 100644 index 00000000..7d62fec4 --- /dev/null +++ b/docs/changelogs/3.4.2-pre1.md @@ -0,0 +1,52 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/3.4.2-pre2.md b/docs/changelogs/3.4.2-pre2.md new file mode 100644 index 00000000..9cc44c74 --- /dev/null +++ b/docs/changelogs/3.4.2-pre2.md @@ -0,0 +1,56 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/3.4.2-pre3.md b/docs/changelogs/3.4.2-pre3.md new file mode 100644 index 00000000..a02643ef --- /dev/null +++ b/docs/changelogs/3.4.2-pre3.md @@ -0,0 +1,57 @@ +# Amber 3.4.2-pre3 + +- 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 + +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-pre3) + +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-pre3.txt` and `manifest-v3.4.2-pre3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.2-pre3.txt.sig manifest-v3.4.2-pre3.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.4.2-pre3.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. diff --git a/docs/changelogs/3.4.2-pre4.md b/docs/changelogs/3.4.2-pre4.md new file mode 100644 index 00000000..e2bd4ffc --- /dev/null +++ b/docs/changelogs/3.4.2-pre4.md @@ -0,0 +1,61 @@ +# Amber 3.4.2-pre4 + +- 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 +- Fix Bunker events not working in multi event 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-pre4) + +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-pre4.txt` and `manifest-v3.4.2-pre4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.2-pre4.txt.sig manifest-v3.4.2-pre4.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.4.2-pre4.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. diff --git a/docs/changelogs/3.4.2.md b/docs/changelogs/3.4.2.md new file mode 100644 index 00000000..fc33e8ce --- /dev/null +++ b/docs/changelogs/3.4.2.md @@ -0,0 +1,61 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/3.4.3.md b/docs/changelogs/3.4.3.md new file mode 100644 index 00000000..8da64473 --- /dev/null +++ b/docs/changelogs/3.4.3.md @@ -0,0 +1,40 @@ +# Amber 3.4.3 + +- Fix crash when sending multiple intents +- Move profile fetch to its own file +- Change the clear logs task to a workManager +- Start the clear logs only after 5 minutes + +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.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-v3.4.3.txt` and `manifest-v3.4.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.3.txt.sig manifest-v3.4.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-v3.4.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. diff --git a/docs/changelogs/3.4.4.md b/docs/changelogs/3.4.4.md new file mode 100644 index 00000000..f07e8283 --- /dev/null +++ b/docs/changelogs/3.4.4.md @@ -0,0 +1,37 @@ +# Amber 3.4.4 + +- Fix get_public_key not working for some native apps + +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.4) + +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.4.txt` and `manifest-v3.4.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.4.txt.sig manifest-v3.4.4.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.4.4.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. diff --git a/docs/changelogs/3.4.5-pre1.md b/docs/changelogs/3.4.5-pre1.md new file mode 100644 index 00000000..6d53dc95 --- /dev/null +++ b/docs/changelogs/3.4.5-pre1.md @@ -0,0 +1,44 @@ +# Amber 3.4.5-pre1 + +- 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-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.5-pre1.txt` and `manifest-v3.4.5-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.5-pre1.txt.sig manifest-v3.4.5-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 " +``` + +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-pre1.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. diff --git a/docs/changelogs/3.4.5.md b/docs/changelogs/3.4.5.md new file mode 100644 index 00000000..9d72fa12 --- /dev/null +++ b/docs/changelogs/3.4.5.md @@ -0,0 +1,44 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/3.4.6.md b/docs/changelogs/3.4.6.md new file mode 100644 index 00000000..a382f8ee --- /dev/null +++ b/docs/changelogs/3.4.6.md @@ -0,0 +1,37 @@ +# Amber 3.4.6 + +- Fixed kind not being saved when rejecting an event from a native app forever + +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.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-v3.4.6.txt` and `manifest-v3.4.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v3.4.6.txt.sig manifest-v3.4.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-v3.4.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. diff --git a/docs/changelogs/4.0.0-pre1.md b/docs/changelogs/4.0.0-pre1.md new file mode 100644 index 00000000..8f703b87 --- /dev/null +++ b/docs/changelogs/4.0.0-pre1.md @@ -0,0 +1,37 @@ +# Amber 4.0.0-pre1 + +- Refactor everything to use the new quartz update + +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-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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.0.0-pre2.md b/docs/changelogs/4.0.0-pre2.md new file mode 100644 index 00000000..a998d201 --- /dev/null +++ b/docs/changelogs/4.0.0-pre2.md @@ -0,0 +1,39 @@ +# Amber 4.0.0-pre2 + +- 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-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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.0.0.md b/docs/changelogs/4.0.0.md new file mode 100644 index 00000000..a8f0431f --- /dev/null +++ b/docs/changelogs/4.0.0.md @@ -0,0 +1,39 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.0.1-pre1.md b/docs/changelogs/4.0.1-pre1.md new file mode 100644 index 00000000..6b6087fb --- /dev/null +++ b/docs/changelogs/4.0.1-pre1.md @@ -0,0 +1,37 @@ +# Amber 4.0.1-pre1 + +- Fix reproducibility + +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-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.1-pre1.txt` and `manifest-v4.0.1-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.1-pre1.txt.sig manifest-v4.0.1-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 " +``` + +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-pre1.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. diff --git a/docs/changelogs/4.0.1.md b/docs/changelogs/4.0.1.md new file mode 100644 index 00000000..b8340904 --- /dev/null +++ b/docs/changelogs/4.0.1.md @@ -0,0 +1,41 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.0.2-pre1.md b/docs/changelogs/4.0.2-pre1.md new file mode 100644 index 00000000..3fd80828 --- /dev/null +++ b/docs/changelogs/4.0.2-pre1.md @@ -0,0 +1,41 @@ +# Amber 4.0.2-pre1 + +- 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 + +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-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.2-pre1.txt` and `manifest-v4.0.2-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.2-pre1.txt.sig manifest-v4.0.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 " +``` + +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-pre1.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. diff --git a/docs/changelogs/4.0.2.md b/docs/changelogs/4.0.2.md new file mode 100644 index 00000000..5e532d2b --- /dev/null +++ b/docs/changelogs/4.0.2.md @@ -0,0 +1,42 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.0.3-pre1.md b/docs/changelogs/4.0.3-pre1.md new file mode 100644 index 00000000..5c94bb9f --- /dev/null +++ b/docs/changelogs/4.0.3-pre1.md @@ -0,0 +1,50 @@ +# Amber 4.0.3-pre1 + +- Fix close application logic for bunkers +- Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw +- Separate relay reqs per account +- Update relay reqs when adding an account +- New encryption/decryption ui +- Support for ping requests when using bunker +- Fix encryption type by @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 +- Separate logs and history tables in it's own databases +- Add crash reporting +- Try to get the saved account in the get public key of the content provider +- Use quartz from maven +- Save logs when there's a error using content provider +- Add a text to the relays page floating button +- Show the relays used by apps + +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.3-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.3-pre1.txt` and `manifest-v4.0.3-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.3-pre1.txt.sig manifest-v4.0.3-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 " +``` + +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.3-pre1.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. diff --git a/docs/changelogs/4.0.3-pre2.md b/docs/changelogs/4.0.3-pre2.md new file mode 100644 index 00000000..aaba43f9 --- /dev/null +++ b/docs/changelogs/4.0.3-pre2.md @@ -0,0 +1,55 @@ +# Amber 4.0.3-pre2 + +- Fix close application logic for bunkers +- Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw +- Separate relay reqs per account +- Update relay reqs when adding an account +- New encryption/decryption ui +- Support for ping requests when using bunker +- Fix encryption type by @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 +- Separate logs and history tables in it's own databases +- Add crash reporting +- Try to get the saved account in the get public key of the content provider +- Use quartz from maven +- Save logs when there's a error using content provider +- Add a text to the relays page floating button +- Show the relays used by apps +- Fix export account +- Clear account cache on logout +- Only load private keys on demand +- Remove nip11 fetch when adding a new relay since we don't verify anything anymore +- Update relay requests when deleting an app + +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.3-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.3-pre2.txt` and `manifest-v4.0.3-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.3-pre2.txt.sig manifest-v4.0.3-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 " +``` + +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.3-pre2.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. diff --git a/docs/changelogs/4.0.3.md b/docs/changelogs/4.0.3.md new file mode 100644 index 00000000..95a54039 --- /dev/null +++ b/docs/changelogs/4.0.3.md @@ -0,0 +1,50 @@ +# Amber 4.0.3 + +- Fix close application logic for bunkers +- Add a Export/Import accounts method by @npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw +- Separate relay reqs per account +- Update relay reqs when adding an account +- New encryption/decryption ui +- Support for ping requests when using bunker +- Fix encryption type by @npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 +- Separate logs and history tables in it's own databases +- Add crash reporting +- Try to get the saved account in the get public key of the content provider +- Use quartz from maven +- Save logs when there's a error using content provider +- Add a text to the relays page floating button +- Show the relays used by apps + +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.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-v4.0.3.txt` and `manifest-v4.0.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.3.txt.sig manifest-v4.0.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-v4.0.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. diff --git a/docs/changelogs/4.0.4.md b/docs/changelogs/4.0.4.md new file mode 100644 index 00000000..a1b5afff --- /dev/null +++ b/docs/changelogs/4.0.4.md @@ -0,0 +1,39 @@ +# Amber 4.0.4 + +- Fix NullPointerException +- Improve activity screen performance +- Add some event kinds translations + +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.4) + +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.4.txt` and `manifest-v4.0.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.4.txt.sig manifest-v4.0.4.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-v4.0.4.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. diff --git a/docs/changelogs/4.0.5.md b/docs/changelogs/4.0.5.md new file mode 100644 index 00000000..50eb3948 --- /dev/null +++ b/docs/changelogs/4.0.5.md @@ -0,0 +1,41 @@ +# Amber 4.0.5 + +- Implemented pagination in the application, logs and activities screen +- Fix database size calculation inside the settings screen +- Optimize `getSavedRelays` to query unique relay lists directly +- Remove application name pre-loading in `IncomingRequestScreen` +- Use direct `DELETE` queries for clearing old logs and history instead of iterative deletion + +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.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-v4.0.5.txt` and `manifest-v4.0.5.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.5.txt.sig manifest-v4.0.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 " +``` + +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.5.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. diff --git a/docs/changelogs/4.0.6-pre1.md b/docs/changelogs/4.0.6-pre1.md new file mode 100644 index 00000000..cdfe5b9f --- /dev/null +++ b/docs/changelogs/4.0.6-pre1.md @@ -0,0 +1,41 @@ +# Amber 4.0.6-pre1 + +- Remove `get_public_key` from content provider +- Handle parsing errors when trying to decrypt content to show the content for the user +- Fix a crash on edit app the permission screen +- Add a cache to the signer to improve performance +- Use finishAndRemoveTask instead of finish + +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.6-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.6-pre1.txt` and `manifest-v4.0.6-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.6-pre1.txt.sig manifest-v4.0.6-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 " +``` + +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.6-pre1.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. diff --git a/docs/changelogs/4.0.6-pre2.md b/docs/changelogs/4.0.6-pre2.md new file mode 100644 index 00000000..98d5b82e --- /dev/null +++ b/docs/changelogs/4.0.6-pre2.md @@ -0,0 +1,42 @@ +# Amber 4.0.6-pre2 + +- Remove `get_public_key` from content provider +- Handle parsing errors when trying to decrypt content to show the content for the user +- Fix a crash on edit app the permission screen +- Add a cache to the signer to improve performance +- Use finishAndRemoveTask instead of finish +- Fix screen recomposition + +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.6-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.6-pre2.txt` and `manifest-v4.0.6-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.6-pre2.txt.sig manifest-v4.0.6-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 " +``` + +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.6-pre2.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. diff --git a/docs/changelogs/4.0.6.md b/docs/changelogs/4.0.6.md new file mode 100644 index 00000000..908f1b42 --- /dev/null +++ b/docs/changelogs/4.0.6.md @@ -0,0 +1,44 @@ +# Amber 4.0.6 + +- Remove `get_public_key` from content provider +- Handle parsing errors when trying to decrypt content to show the content for the user +- Fix a crash on edit app the permission screen +- Add a cache to the signer to improve performance +- Use finishAndRemoveTask instead of finish +- Fix screen recomposition +- Fix crash when reading a invalid nostrconnect URI +- Retry sending connect event on failure when adding a 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.0.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-v4.0.6.txt` and `manifest-v4.0.6.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.0.6.txt.sig manifest-v4.0.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-v4.0.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. diff --git a/docs/changelogs/4.0.7.md b/docs/changelogs/4.0.7.md new file mode 100644 index 00000000..c6a6ace3 --- /dev/null +++ b/docs/changelogs/4.0.7.md @@ -0,0 +1,39 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.1.0-pre1.md b/docs/changelogs/4.1.0-pre1.md new file mode 100644 index 00000000..af2f779e --- /dev/null +++ b/docs/changelogs/4.1.0-pre1.md @@ -0,0 +1,39 @@ +# 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 " +``` + +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 ` 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. diff --git a/docs/changelogs/4.1.0-pre2.md b/docs/changelogs/4.1.0-pre2.md new file mode 100644 index 00000000..cd2d31d9 --- /dev/null +++ b/docs/changelogs/4.1.0-pre2.md @@ -0,0 +1,41 @@ +# Amber 4.1.0-pre2 + +- 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 +- Expose datastore errors +- Fix connection not being deleted when it fails when using bunker + +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-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.1.0-pre2.txt` and `manifest-v4.1.0-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.0-pre2.txt.sig manifest-v4.1.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 " +``` + +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-pre2.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. diff --git a/docs/changelogs/4.1.0-pre3.md b/docs/changelogs/4.1.0-pre3.md new file mode 100644 index 00000000..eeda7bc1 --- /dev/null +++ b/docs/changelogs/4.1.0-pre3.md @@ -0,0 +1,46 @@ +# Amber 4.1.0-pre3 + +- 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 +- Expose datastore errors +- Fix connection not being deleted when it fails when using bunker +- Add a loading indicator when login in +- Let the app crash when it fails to read the intent +- Use application wide scope for the datastore +- Remove migration code from old encrypted shared preferences +- Throw a error if could not find the private keys inside the keystore + +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-pre3) + +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-pre3.txt` and `manifest-v4.1.0-pre3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.0-pre3.txt.sig manifest-v4.1.0-pre3.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-v4.1.0-pre3.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. diff --git a/docs/changelogs/4.1.0.md b/docs/changelogs/4.1.0.md new file mode 100644 index 00000000..54caaeac --- /dev/null +++ b/docs/changelogs/4.1.0.md @@ -0,0 +1,47 @@ +# Amber 4.1.0 + +- 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 +- Expose datastore errors +- Fix connection not being deleted when it fails when using bunker +- Add a loading indicator when login in +- Let the app crash when it fails to read the intent +- Use application wide scope for the datastore +- Remove migration code from old encrypted shared preferences +- Throw a error if could not find the private keys inside the keystore +- Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore) + +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) + +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.txt` and `manifest-v4.1.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.0.txt.sig manifest-v4.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-v4.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. diff --git a/docs/changelogs/4.1.1.md b/docs/changelogs/4.1.1.md new file mode 100644 index 00000000..8d361065 --- /dev/null +++ b/docs/changelogs/4.1.1.md @@ -0,0 +1,50 @@ +# Amber 4.1.1 + +- 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 +- Expose datastore errors +- Fix connection not being deleted when it fails when using bunker +- Add a loading indicator when login in +- Let the app crash when it fails to read the intent +- Use application wide scope for the datastore +- Remove migration code from old encrypted shared preferences +- Throw a error if could not find the private keys inside the keystore +- Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore) +- Relay trusted score by @npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu +- Verify if account exists before trying to load the keys +- Support for `switch_relays` method + +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.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.1.1.txt` and `manifest-v4.1.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.1.txt.sig manifest-v4.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-v4.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. diff --git a/docs/changelogs/4.1.2-pre1.md b/docs/changelogs/4.1.2-pre1.md new file mode 100644 index 00000000..dca77138 --- /dev/null +++ b/docs/changelogs/4.1.2-pre1.md @@ -0,0 +1,43 @@ +# Amber 4.1.2-pre1 + +- Fix some missing Relay trusted score in some screens +- Move some components to it's own file +- Use full uuid for bunker secrets +- Remove some unused dependencies +- Migrate from LiveData to Flow in the account Model +- Upgrade to gradle plugin 9 +- Fix json parsing error for encrypt/decrypt requests when they are not nostr events + +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.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-v4.1.2-pre1.txt` and `manifest-v4.1.2-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.2-pre1.txt.sig manifest-v4.1.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 " +``` + +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.2-pre1.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. diff --git a/docs/changelogs/4.1.2.md b/docs/changelogs/4.1.2.md new file mode 100644 index 00000000..1c0a315f --- /dev/null +++ b/docs/changelogs/4.1.2.md @@ -0,0 +1,44 @@ +# Amber 4.1.2 + +- Fix some missing Relay trusted score in some screens +- Move some components to it's own file +- Use full uuid for bunker secrets +- Remove some unused dependencies +- Migrate from LiveData to Flow in the account Model +- Upgrade to gradle plugin 9 +- Fix json parsing error for encrypt/decrypt requests when they are not nostr events +- Fix a crash when receiving a auth event without relay tags + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.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.1.2.txt` and `manifest-v4.1.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.2.txt.sig manifest-v4.1.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-v4.1.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. diff --git a/docs/changelogs/4.1.3-pre1.md b/docs/changelogs/4.1.3-pre1.md new file mode 100644 index 00000000..7d2885d1 --- /dev/null +++ b/docs/changelogs/4.1.3-pre1.md @@ -0,0 +1,48 @@ +# Amber 4.1.3-pre1 + +- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me +- Better relay notification text +- Fix relay icon when more than 10 relays +- Hide icon and relay notification if not using apps that connect to relays +- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec +- Do not use strongBox when it's a mediatek device, it's breaking all the time +- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press +- Remove relay.nsec.app from defaults (it's not working properly sometimes) +- Close profile subscriptions once receiving EOSE from relays +- Fix icon size and themed icon +- Show the account that is signing the event +- Show a button to report unknown event kinds + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.3-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.3-pre1.txt` and `manifest-v4.1.3-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.3-pre1.txt.sig manifest-v4.1.3-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 " +``` + +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.3-pre1.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. diff --git a/docs/changelogs/4.1.3-pre2.md b/docs/changelogs/4.1.3-pre2.md new file mode 100644 index 00000000..7daa9675 --- /dev/null +++ b/docs/changelogs/4.1.3-pre2.md @@ -0,0 +1,53 @@ +# Amber 4.1.3-pre2 + +- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me +- Better relay notification text +- Fix relay icon when more than 10 relays +- Hide icon and relay notification if not using apps that connect to relays +- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec +- Do not use strongBox when it's a mediatek device, it's breaking all the time +- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press +- Remove relay.nsec.app from defaults (it's not working properly sometimes) +- Close profile subscriptions once receiving EOSE from relays +- Fix icon size and themed icon +- Show the account that is signing the event +- Show a button to report unknown event kinds +- Better relay connection management +- Refactor start service +- Use bottom sheet for requests instead of showing the full application +- Display the "Sign as" widget in the multi event screen +- Decrease the timeout of sending response to relays + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.3-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.1.3-pre2.txt` and `manifest-v4.1.3-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.3-pre2.txt.sig manifest-v4.1.3-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 " +``` + +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.3-pre2.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. diff --git a/docs/changelogs/4.1.3-pre3.md b/docs/changelogs/4.1.3-pre3.md new file mode 100644 index 00000000..6d0a40b2 --- /dev/null +++ b/docs/changelogs/4.1.3-pre3.md @@ -0,0 +1,56 @@ +# Amber 4.1.3-pre3 + +- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me +- Better relay notification text +- Fix relay icon when more than 10 relays +- Hide icon and relay notification if not using apps that connect to relays +- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec +- Do not use strongBox when it's a mediatek device, it's breaking all the time +- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press +- Remove relay.nsec.app from defaults (it's not working properly sometimes) +- Close profile subscriptions once receiving EOSE from relays +- Fix icon size and themed icon +- Show the account that is signing the event +- Show a button to report unknown event kinds +- Better relay connection management +- Refactor start service +- Use bottom sheet for requests instead of showing the full application +- Display the "Sign as" widget in the multi event screen +- Decrease the timeout of sending response to relays +- Show rquest content in the activities screen +- Client auth permissions by relay +- Fix a crash when loading profile image + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.3-pre3) + +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.3-pre3.txt` and `manifest-v4.1.3-pre3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.3-pre3.txt.sig manifest-v4.1.3-pre3.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-v4.1.3-pre3.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. diff --git a/docs/changelogs/4.1.3-pre4.md b/docs/changelogs/4.1.3-pre4.md new file mode 100644 index 00000000..8e77be56 --- /dev/null +++ b/docs/changelogs/4.1.3-pre4.md @@ -0,0 +1,57 @@ +# Amber 4.1.3-pre4 + +- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me +- Better relay notification text +- Fix relay icon when more than 10 relays +- Hide icon and relay notification if not using apps that connect to relays +- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec +- Do not use strongBox when it's a mediatek device, it's breaking all the time +- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press +- Remove relay.nsec.app from defaults (it's not working properly sometimes) +- Close profile subscriptions once receiving EOSE from relays +- Fix icon size and themed icon +- Show the account that is signing the event +- Show a button to report unknown event kinds +- Better relay connection management +- Refactor start service +- Use bottom sheet for requests instead of showing the full application +- Display the "Sign as" widget in the multi event screen +- Decrease the timeout of sending response to relays +- Show rquest content in the activities screen +- Client auth permissions by relay +- Fix a crash when loading profile image +- Do not group events when receiving multiple events + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.3-pre4) + +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.3-pre4.txt` and `manifest-v4.1.3-pre4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.3-pre4.txt.sig manifest-v4.1.3-pre4.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-v4.1.3-pre4.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. diff --git a/docs/changelogs/4.1.3.md b/docs/changelogs/4.1.3.md new file mode 100644 index 00000000..24790375 --- /dev/null +++ b/docs/changelogs/4.1.3.md @@ -0,0 +1,57 @@ +# Amber 4.1.3 + +- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me +- Better relay notification text +- Fix relay icon when more than 10 relays +- Hide icon and relay notification if not using apps that connect to relays +- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec +- Do not use strongBox when it's a mediatek device, it's breaking all the time +- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press +- Remove relay.nsec.app from defaults (it's not working properly sometimes) +- Close profile subscriptions once receiving EOSE from relays +- Fix icon size and themed icon +- Show the account that is signing the event +- Show a button to report unknown event kinds +- Better relay connection management +- Refactor start service +- Use bottom sheet for requests instead of showing the full application +- Display the "Sign as" widget in the multi event screen +- Decrease the timeout of sending response to relays +- Show request content in the activities screen +- Client auth permissions by relay +- Fix a crash when loading profile image +- Do not group events when receiving multiple events + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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.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-v4.1.3.txt` and `manifest-v4.1.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v4.1.3.txt.sig manifest-v4.1.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-v4.1.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. diff --git a/docs/changelogs/5.0.0.md b/docs/changelogs/5.0.0.md new file mode 100644 index 00000000..bc5aaa59 --- /dev/null +++ b/docs/changelogs/5.0.0.md @@ -0,0 +1,42 @@ +# Amber 5.0.0 + +- Always remove internet permissions from offline build to avoid dependencies adding them +- Add a CI check for the internet permissions in the offline build +- Option for built in tor +- Search the content in the activities screen +- Granular encryption/decryption based on data type +- Migrate PIN storage from SharedPreferences to encrypted DataStore + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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/v5.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-v5.0.0.txt` and `manifest-v5.0.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v5.0.0.txt.sig manifest-v5.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 " +``` + +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-v5.0.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. diff --git a/docs/changelogs/5.0.1.md b/docs/changelogs/5.0.1.md new file mode 100644 index 00000000..600f20e8 --- /dev/null +++ b/docs/changelogs/5.0.1.md @@ -0,0 +1,44 @@ +# Amber 5.0.1 + +- Always remove internet permissions from offline build to avoid dependencies adding them +- Add a CI check for the internet permissions in the offline build +- Option for built in tor +- Search the content in the activities screen +- Granular encryption/decryption based on data type +- Migrate PIN storage from SharedPreferences to encrypted DataStore +- Fix crash on offline build +- Show the crash report content before sending + +Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [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/v5.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-v5.0.1.txt` and `manifest-v5.0.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v5.0.1.txt.sig manifest-v5.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-v5.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. diff --git a/docs/changelogs/5.0.2.md b/docs/changelogs/5.0.2.md new file mode 100644 index 00000000..ea6e8e48 --- /dev/null +++ b/docs/changelogs/5.0.2.md @@ -0,0 +1,44 @@ +# Amber 5.0.2 + +- Do not start service, tor or notifications when using the offline version +- Do not re-add bunker requests when failed to send response +- Better performance when receiving multiple requests +- Add a 30 second timeout for profile subscriptions +- Remove the tabs from the connect screen +- Fix rejection not respecting the scoped encrypt/decrypt +- Show alt tags when there's no translation for a event kind +- use a boolean for the intent rejection + +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/v5.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-v5.0.2.txt` and `manifest-v5.0.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v5.0.2.txt.sig manifest-v5.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 " +``` + +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-v5.0.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. diff --git a/docs/changelogs/5.0.3.md b/docs/changelogs/5.0.3.md new file mode 100644 index 00000000..74d991f9 --- /dev/null +++ b/docs/changelogs/5.0.3.md @@ -0,0 +1,45 @@ +# Amber 5.0.3 + +- Do not start service, tor or notifications when using the offline version +- Do not re-add bunker requests when failed to send response +- Better performance when receiving multiple requests +- Add a 30 second timeout for profile subscriptions +- Remove the tabs from the connect screen +- Fix rejection not respecting the scoped encrypt/decrypt +- Show alt tags when there's no translation for a event kind +- use a boolean for the intent rejection +- Fix the accept/reject button not showing when scanning a nostrconnect qrcode + +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/v5.0.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-v5.0.3.txt` and `manifest-v5.0.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v5.0.3.txt.sig manifest-v5.0.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-v5.0.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. diff --git a/docs/changelogs/5.0.4.md b/docs/changelogs/5.0.4.md new file mode 100644 index 00000000..7875783d --- /dev/null +++ b/docs/changelogs/5.0.4.md @@ -0,0 +1,45 @@ +# Amber 5.0.4 + +- Do not start service, tor or notifications when using the offline version +- Do not re-add bunker requests when failed to send response +- Better performance when receiving multiple requests +- Add a 30 second timeout for profile subscriptions +- Remove the tabs from the connect screen +- Fix rejection not respecting the scoped encrypt/decrypt +- Show alt tags when there's no translation for a event kind +- use a boolean for the intent rejection +- Fix the accept/reject button not showing when scanning a nostrconnect qrcode + +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/v5.0.4) + +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-v5.0.4.txt` and `manifest-v5.0.4.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v5.0.4.txt.sig manifest-v5.0.4.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-v5.0.4.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. diff --git a/docs/changelogs/6.0.0-pre1.md b/docs/changelogs/6.0.0-pre1.md new file mode 100644 index 00000000..7d14f26a --- /dev/null +++ b/docs/changelogs/6.0.0-pre1.md @@ -0,0 +1,42 @@ +# Amber 6.0.0-pre1 + +- Add per-connection signing keys for NIP-46 bunker protocol +- Add NIP-42 relay auth whitelist settings +- Add mnemonic recovery phrase login screen +- Fix a crash when receiving duplicated events +- Optimize performance in content resolvers, intents and activity screen +- Optimized logs and activities to reduce the size of the database + +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.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-v6.0.0-pre1.txt` and `manifest-v6.0.0-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.0.0-pre1.txt.sig manifest-v6.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 " +``` + +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.0.0-pre1.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. diff --git a/docs/changelogs/6.0.0.md b/docs/changelogs/6.0.0.md new file mode 100644 index 00000000..2df68502 --- /dev/null +++ b/docs/changelogs/6.0.0.md @@ -0,0 +1,47 @@ +# Amber 6.0.0 + +- Add per-connection signing keys for NIP-46 bunker protocol +- Add NIP-42 relay auth whitelist settings +- Add mnemonic recovery phrase login support +- Fix a crash when receiving duplicated events +- Optimize performance in content resolvers, intents and activity screen +- Optimized logs and activities to reduce the size of the database +- Fix a crash when pasting from clipboard +- Make relays notifications minimized by default +- Fix a database migration error +- Warn the user when their device has a broken KeyStore +- Add a self updater + +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.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-v6.0.0.txt` and `manifest-v6.0.0.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.0.0.txt.sig manifest-v6.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 " +``` + +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.0.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. diff --git a/docs/changelogs/6.0.1.md b/docs/changelogs/6.0.1.md new file mode 100644 index 00000000..f216033d --- /dev/null +++ b/docs/changelogs/6.0.1.md @@ -0,0 +1,43 @@ +# Amber 6.0.1 + +- Fix missing event validation when checking for app updates and profile events +- Fix racing condition when receiving intents +- Fix subscriptions never closing when removing an app +- Remove richtext dependency +- Update Quartz library to 1.08.0 +- Add two new backup options, webdav and share to google drive +- Implement exponential backoff for relay reconnections + +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.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-v6.0.1.txt` and `manifest-v6.0.1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.0.1.txt.sig manifest-v6.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-v6.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. diff --git a/docs/changelogs/6.0.2.md b/docs/changelogs/6.0.2.md new file mode 100644 index 00000000..75417f53 --- /dev/null +++ b/docs/changelogs/6.0.2.md @@ -0,0 +1,41 @@ +# Amber 6.0.2 + +- Fix racing condition when receiving intents +- Upgrade gradle and agp +- Add account index option when using seed words +- Fix relay reconnection on startup if the relay is offline +- Add missing periodic worker for app updates + +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.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-v6.0.2.txt` and `manifest-v6.0.2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.0.2.txt.sig manifest-v6.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 " +``` + +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.0.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. diff --git a/docs/changelogs/6.0.3.md b/docs/changelogs/6.0.3.md new file mode 100644 index 00000000..aac97f9e --- /dev/null +++ b/docs/changelogs/6.0.3.md @@ -0,0 +1,42 @@ +# Amber 6.0.3 + +- Fix racing condition when receiving intents +- Upgrade gradle and agp +- Add account index option when using seed words +- Fix relay reconnection on startup if the relay is offline +- Add missing periodic worker for app updates +- Check for empty request ids when receiving intents + +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.0.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.0.3.txt` and `manifest-v6.0.3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.0.3.txt.sig manifest-v6.0.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.0.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. diff --git a/docs/changelogs/6.1.0-pre1.md b/docs/changelogs/6.1.0-pre1.md new file mode 100644 index 00000000..8973eeac --- /dev/null +++ b/docs/changelogs/6.1.0-pre1.md @@ -0,0 +1,49 @@ +# Amber 6.1.0-pre1 + +- Better layout when connecting a new app +- Fix some reported crashes +- Fix signer dialog not closing after accepting a bunker request +- Show name and npub when showing your account +- Add a select/deselect all option in the permissions screen when connecting a new app +- Show a invalid request screen when receiving a invalid request +- Preview missing translation report before sending it +- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) +- Some optimizations when accepting/rejecting intent requests +- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications +- Added a option to disable the service start on boot +- Only start the profile subscription for the current account +- Always return hex key when logging in to an app to comply with nip 55 + +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.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-v6.1.0-pre1.txt` and `manifest-v6.1.0-pre1.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.1.0-pre1.txt.sig manifest-v6.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 " +``` + +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.1.0-pre1.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. diff --git a/docs/changelogs/6.1.0-pre2.md b/docs/changelogs/6.1.0-pre2.md new file mode 100644 index 00000000..fc9a8087 --- /dev/null +++ b/docs/changelogs/6.1.0-pre2.md @@ -0,0 +1,55 @@ +# Amber 6.1.0-pre2 + +- Better layout when connecting a new app +- Fix some reported crashes +- Fix signer dialog not closing after accepting a bunker request +- Show name and npub when showing your account +- Add a select/deselect all option in the permissions screen when connecting a new app +- Show a invalid request screen when receiving a invalid request +- Preview missing translation report before sending it +- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) +- Some optimizations when accepting/rejecting intent requests +- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications +- Added a option to disable the service start on boot +- Only start the profile subscription for the current account +- Always return hex key when logging in to an app to comply with nip 55 +- Added a close button in the empty requests screen +- Added loading state to the report screens +- Support for beta releases for the auto updater +- Add a reset button for bunkers +- Fix a connection issue when connecting to a new bunker by @npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p +- Fix app starting on boot when not enabled + +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.1.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-v6.1.0-pre2.txt` and `manifest-v6.1.0-pre2.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.1.0-pre2.txt.sig manifest-v6.1.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 " +``` + +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.1.0-pre2.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. diff --git a/docs/changelogs/6.1.0-pre3.md b/docs/changelogs/6.1.0-pre3.md new file mode 100644 index 00000000..b5632a6a --- /dev/null +++ b/docs/changelogs/6.1.0-pre3.md @@ -0,0 +1,59 @@ +# Amber 6.1.0-pre3 + +- Better layout when connecting a new app +- Fix some reported crashes +- Fix signer dialog not closing after accepting a bunker request +- Show name and npub when showing your account +- Add a select/deselect all option in the permissions screen when connecting a new app +- Show a invalid request screen when receiving a invalid request +- Preview missing translation report before sending it +- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) +- Some optimizations when accepting/rejecting intent requests +- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications +- Added a option to disable the service start on boot +- Only start the profile subscription for the current account +- Always return hex key when logging in to an app to comply with nip 55 +- Added a close button in the empty requests screen +- Added loading state to the report screens +- Support for beta releases for the auto updater +- Add a reset button for bunkers +- Fix a connection issue when connecting to a new bunker by @npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p +- Fix app starting on boot when not enabled +- Support for sign psbt method +- Fix relay auth whitelist when the relay contains port number +- Change selectable options to be a bottom sheet +- Added more options to the automatically sign this for + +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.1.0-pre3) + +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.1.0-pre3.txt` and `manifest-v6.1.0-pre3.txt.sig` are in the current directory) with: + +``` bash +gpg --verify manifest-v6.1.0-pre3.txt.sig manifest-v6.1.0-pre3.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.1.0-pre3.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. diff --git a/docs/changelogs/README.md b/docs/changelogs/README.md index b84e1469..28a91d06 100644 --- a/docs/changelogs/README.md +++ b/docs/changelogs/README.md @@ -1,6 +1,6 @@ # Changelogs -Release notes for Amber, one file per version. The most recent release is listed first. +Release notes for Amber, one file per version (pre-releases included). The most recent release is listed first. | Version | Changelog | |---------|-----------| @@ -9,5 +9,190 @@ Release notes for Amber, one file per version. The most recent release is listed | 6.2.1 | [6.2.1.md](6.2.1.md) | | 6.2.0 | [6.2.0.md](6.2.0.md) | | 6.1.0 | [6.1.0.md](6.1.0.md) | +| 6.1.0-pre3 | [6.1.0-pre3.md](6.1.0-pre3.md) | +| 6.1.0-pre2 | [6.1.0-pre2.md](6.1.0-pre2.md) | +| 6.1.0-pre1 | [6.1.0-pre1.md](6.1.0-pre1.md) | +| 6.0.3 | [6.0.3.md](6.0.3.md) | +| 6.0.2 | [6.0.2.md](6.0.2.md) | +| 6.0.1 | [6.0.1.md](6.0.1.md) | +| 6.0.0 | [6.0.0.md](6.0.0.md) | +| 6.0.0-pre1 | [6.0.0-pre1.md](6.0.0-pre1.md) | +| 5.0.4 | [5.0.4.md](5.0.4.md) | +| 5.0.3 | [5.0.3.md](5.0.3.md) | +| 5.0.2 | [5.0.2.md](5.0.2.md) | +| 5.0.1 | [5.0.1.md](5.0.1.md) | +| 5.0.0 | [5.0.0.md](5.0.0.md) | +| 4.1.3 | [4.1.3.md](4.1.3.md) | +| 4.1.3-pre4 | [4.1.3-pre4.md](4.1.3-pre4.md) | +| 4.1.3-pre3 | [4.1.3-pre3.md](4.1.3-pre3.md) | +| 4.1.3-pre2 | [4.1.3-pre2.md](4.1.3-pre2.md) | +| 4.1.3-pre1 | [4.1.3-pre1.md](4.1.3-pre1.md) | +| 4.1.2 | [4.1.2.md](4.1.2.md) | +| 4.1.2-pre1 | [4.1.2-pre1.md](4.1.2-pre1.md) | +| 4.1.1 | [4.1.1.md](4.1.1.md) | +| 4.1.0 | [4.1.0.md](4.1.0.md) | +| 4.1.0-pre3 | [4.1.0-pre3.md](4.1.0-pre3.md) | +| 4.1.0-pre2 | [4.1.0-pre2.md](4.1.0-pre2.md) | +| 4.1.0-pre1 | [4.1.0-pre1.md](4.1.0-pre1.md) | +| 4.0.7 | [4.0.7.md](4.0.7.md) | +| 4.0.6 | [4.0.6.md](4.0.6.md) | +| 4.0.6-pre2 | [4.0.6-pre2.md](4.0.6-pre2.md) | +| 4.0.6-pre1 | [4.0.6-pre1.md](4.0.6-pre1.md) | +| 4.0.5 | [4.0.5.md](4.0.5.md) | +| 4.0.4 | [4.0.4.md](4.0.4.md) | +| 4.0.3 | [4.0.3.md](4.0.3.md) | +| 4.0.3-pre2 | [4.0.3-pre2.md](4.0.3-pre2.md) | +| 4.0.3-pre1 | [4.0.3-pre1.md](4.0.3-pre1.md) | +| 4.0.2 | [4.0.2.md](4.0.2.md) | +| 4.0.2-pre1 | [4.0.2-pre1.md](4.0.2-pre1.md) | +| 4.0.1 | [4.0.1.md](4.0.1.md) | +| 4.0.1-pre1 | [4.0.1-pre1.md](4.0.1-pre1.md) | +| 4.0.0 | [4.0.0.md](4.0.0.md) | +| 4.0.0-pre2 | [4.0.0-pre2.md](4.0.0-pre2.md) | +| 4.0.0-pre1 | [4.0.0-pre1.md](4.0.0-pre1.md) | +| 3.4.6 | [3.4.6.md](3.4.6.md) | +| 3.4.5 | [3.4.5.md](3.4.5.md) | +| 3.4.5-pre1 | [3.4.5-pre1.md](3.4.5-pre1.md) | +| 3.4.4 | [3.4.4.md](3.4.4.md) | +| 3.4.3 | [3.4.3.md](3.4.3.md) | +| 3.4.2 | [3.4.2.md](3.4.2.md) | +| 3.4.2-pre4 | [3.4.2-pre4.md](3.4.2-pre4.md) | +| 3.4.2-pre3 | [3.4.2-pre3.md](3.4.2-pre3.md) | +| 3.4.2-pre2 | [3.4.2-pre2.md](3.4.2-pre2.md) | +| 3.4.2-pre1 | [3.4.2-pre1.md](3.4.2-pre1.md) | +| 3.4.1 | [3.4.1.md](3.4.1.md) | +| 3.4.0 | [3.4.0.md](3.4.0.md) | +| 3.3.0 | [3.3.0.md](3.3.0.md) | +| 3.2.9 | [3.2.9.md](3.2.9.md) | +| 3.2.8 | [3.2.8.md](3.2.8.md) | +| 3.2.7 | [3.2.7.md](3.2.7.md) | +| 3.2.6 | [3.2.6.md](3.2.6.md) | +| 3.2.5 | [3.2.5.md](3.2.5.md) | +| 3.2.4 | [3.2.4.md](3.2.4.md) | +| 3.2.3 | [3.2.3.md](3.2.3.md) | +| 3.2.2 | [3.2.2.md](3.2.2.md) | +| 3.2.1 | [3.2.1.md](3.2.1.md) | +| 3.2.0 | [3.2.0.md](3.2.0.md) | +| 3.1.9 | [3.1.9.md](3.1.9.md) | +| 3.1.8 | [3.1.8.md](3.1.8.md) | +| 3.1.7 | [3.1.7.md](3.1.7.md) | +| 3.1.6 | [3.1.6.md](3.1.6.md) | +| 3.1.5 | [3.1.5.md](3.1.5.md) | +| 3.1.4 | [3.1.4.md](3.1.4.md) | +| 3.1.3 | [3.1.3.md](3.1.3.md) | +| 3.1.2 | [3.1.2.md](3.1.2.md) | +| 3.1.1 | [3.1.1.md](3.1.1.md) | +| 3.1.0 | [3.1.0.md](3.1.0.md) | +| 3.0.7 | [3.0.7.md](3.0.7.md) | +| 3.0.6 | [3.0.6.md](3.0.6.md) | +| 3.0.5 | [3.0.5.md](3.0.5.md) | +| 3.0.4 | [3.0.4.md](3.0.4.md) | +| 3.0.3 | [3.0.3.md](3.0.3.md) | +| 3.0.2 | [3.0.2.md](3.0.2.md) | +| 3.0.1 | [3.0.1.md](3.0.1.md) | +| 3.0.0 | [3.0.0.md](3.0.0.md) | +| 3.0.0-pre9 | [3.0.0-pre9.md](3.0.0-pre9.md) | +| 3.0.0-pre8 | [3.0.0-pre8.md](3.0.0-pre8.md) | +| 3.0.0-pre7 | [3.0.0-pre7.md](3.0.0-pre7.md) | +| 3.0.0-pre6 | [3.0.0-pre6.md](3.0.0-pre6.md) | +| 3.0.0-pre5 | [3.0.0-pre5.md](3.0.0-pre5.md) | +| 3.0.0-pre4 | [3.0.0-pre4.md](3.0.0-pre4.md) | +| 3.0.0-pre3 | [3.0.0-pre3.md](3.0.0-pre3.md) | +| 3.0.0-pre2 | [3.0.0-pre2.md](3.0.0-pre2.md) | +| 3.0.0-pre1 | [3.0.0-pre1.md](3.0.0-pre1.md) | +| 2.0.8 | [2.0.8.md](2.0.8.md) | +| 2.0.7 | [2.0.7.md](2.0.7.md) | +| 2.0.6 | [2.0.6.md](2.0.6.md) | +| 2.0.5 | [2.0.5.md](2.0.5.md) | +| 2.0.4 | [2.0.4.md](2.0.4.md) | +| 2.0.3 | [2.0.3.md](2.0.3.md) | +| 2.0.2 | [2.0.2.md](2.0.2.md) | +| 2.0.1 | [2.0.1.md](2.0.1.md) | +| 2.0.0 | [2.0.0.md](2.0.0.md) | +| 1.3.7 | [1.3.7.md](1.3.7.md) | +| 1.3.6 | [1.3.6.md](1.3.6.md) | +| 1.3.5 | [1.3.5.md](1.3.5.md) | +| 1.3.4 | [1.3.4.md](1.3.4.md) | +| 1.3.3 | [1.3.3.md](1.3.3.md) | +| 1.3.2 | [1.3.2.md](1.3.2.md) | +| 1.3.1 | [1.3.1.md](1.3.1.md) | +| 1.3.0 | [1.3.0.md](1.3.0.md) | +| 1.3.0-pre4 | [1.3.0-pre4.md](1.3.0-pre4.md) | +| 1.3.0-pre3 | [1.3.0-pre3.md](1.3.0-pre3.md) | +| 1.3.0-pre2 | [1.3.0-pre2.md](1.3.0-pre2.md) | +| 1.3.0-pre1 | [1.3.0-pre1.md](1.3.0-pre1.md) | +| 1.2.0 | [1.2.0.md](1.2.0.md) | +| 1.1.2 | [1.1.2.md](1.1.2.md) | +| 1.1.1 | [1.1.1.md](1.1.1.md) | +| 1.1.0 | [1.1.0.md](1.1.0.md) | +| 1.1.0-pre1 | [1.1.0-pre1.md](1.1.0-pre1.md) | +| 1.0.9 | [1.0.9.md](1.0.9.md) | +| 1.0.8 | [1.0.8.md](1.0.8.md) | +| 1.0.7 | [1.0.7.md](1.0.7.md) | +| 1.0.7-pre2 | [1.0.7-pre2.md](1.0.7-pre2.md) | +| 1.0.6 | [1.0.6.md](1.0.6.md) | +| 1.0.5 | [1.0.5.md](1.0.5.md) | +| 1.0.4 | [1.0.4.md](1.0.4.md) | +| 1.0.3 | [1.0.3.md](1.0.3.md) | +| 1.0.2 | [1.0.2.md](1.0.2.md) | +| 1.0.1 | [1.0.1.md](1.0.1.md) | +| 1.0.0 | [1.0.0.md](1.0.0.md) | +| 1.0.0-pre12 | [1.0.0-pre12.md](1.0.0-pre12.md) | +| 1.0.0-pre11 | [1.0.0-pre11.md](1.0.0-pre11.md) | +| 1.0.0-pre10 | [1.0.0-pre10.md](1.0.0-pre10.md) | +| 1.0.0-pre9 | [1.0.0-pre9.md](1.0.0-pre9.md) | +| 1.0.0-pre7 | [1.0.0-pre7.md](1.0.0-pre7.md) | +| 1.0.0-pre6 | [1.0.0-pre6.md](1.0.0-pre6.md) | +| 1.0.0-pre5 | [1.0.0-pre5.md](1.0.0-pre5.md) | +| 1.0.0-pre4 | [1.0.0-pre4.md](1.0.0-pre4.md) | +| 1.0.0-pre3 | [1.0.0-pre3.md](1.0.0-pre3.md) | +| 1.0.0-pre2 | [1.0.0-pre2.md](1.0.0-pre2.md) | +| 1.0.0-pre | [1.0.0-pre.md](1.0.0-pre.md) | +| 0.8.2 | [0.8.2.md](0.8.2.md) | +| 0.8.1 | [0.8.1.md](0.8.1.md) | +| 0.8.0 | [0.8.0.md](0.8.0.md) | +| 0.7.6 | [0.7.6.md](0.7.6.md) | +| 0.7.5 | [0.7.5.md](0.7.5.md) | +| 0.7.4 | [0.7.4.md](0.7.4.md) | +| 0.7.3 | [0.7.3.md](0.7.3.md) | +| 0.7.2 | [0.7.2.md](0.7.2.md) | +| 0.7.1 | [0.7.1.md](0.7.1.md) | +| 0.7.0 | [0.7.0.md](0.7.0.md) | +| 0.6.6 | [0.6.6.md](0.6.6.md) | +| 0.6.5 | [0.6.5.md](0.6.5.md) | +| 0.6.4 | [0.6.4.md](0.6.4.md) | +| 0.6.3 | [0.6.3.md](0.6.3.md) | +| 0.6.1 | [0.6.1.md](0.6.1.md) | +| 0.6.0 | [0.6.0.md](0.6.0.md) | +| 0.5.3 | [0.5.3.md](0.5.3.md) | +| 0.5.2 | [0.5.2.md](0.5.2.md) | +| 0.5.1 | [0.5.1.md](0.5.1.md) | +| 0.5.0 | [0.5.0.md](0.5.0.md) | +| 0.4.7 | [0.4.7.md](0.4.7.md) | +| 0.4.6 | [0.4.6.md](0.4.6.md) | +| 0.4.5 | [0.4.5.md](0.4.5.md) | +| 0.4.4 | [0.4.4.md](0.4.4.md) | +| 0.4.3 | [0.4.3.md](0.4.3.md) | +| 0.4.2 | [0.4.2.md](0.4.2.md) | +| 0.4.1 | [0.4.1.md](0.4.1.md) | +| 0.4.0 | [0.4.0.md](0.4.0.md) | +| 0.3.2 | [0.3.2.md](0.3.2.md) | +| 0.3.1 | [0.3.1.md](0.3.1.md) | +| 0.3.0 | [0.3.0.md](0.3.0.md) | +| 0.2.0 | [0.2.0.md](0.2.0.md) | +| 0.1.4 | [0.1.4.md](0.1.4.md) | +| 0.1.3 | [0.1.3.md](0.1.3.md) | +| 0.1.2 | [0.1.2.md](0.1.2.md) | +| 0.1.1 | [0.1.1.md](0.1.1.md) | +| 0.1.0 | [0.1.0.md](0.1.0.md) | +| 0.0.9 | [0.0.9.md](0.0.9.md) | +| 0.0.8 | [0.0.8.md](0.0.8.md) | +| 0.0.7 | [0.0.7.md](0.0.7.md) | +| 0.0.6 | [0.0.6.md](0.0.6.md) | +| 0.0.5 | [0.0.5.md](0.0.5.md) | +| 0.0.4 | [0.0.4.md](0.0.4.md) | +| 0.0.3 | [0.0.3.md](0.0.3.md) | +| 0.0.2 | [0.0.2.md](0.0.2.md) | +| 0.0.1 | [0.0.1.md](0.0.1.md) | -Release notes for older versions are available on the [GitHub releases page](https://github.com/greenart7c3/Amber/releases). +Binaries and signed manifests for every release are available on the [GitHub releases page](https://github.com/greenart7c3/Amber/releases).