greenart7c3

nostr:nevent1qqsz38vlquncl0xyadsp8ulh424vymnfdzpsnwv6uddjd4wrkvvmx3qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8wuwg7as64rmfrh9ssyl0zx4wq7tvf4y467jvdnd6gvdmc6zuhcgpsgqqqqqqsj5cs7w

Please share more less known projects nostr:nevent1qqsqhkewxc8tmmxs98hd4ygy9k7wsyw7rpq5znaeq4s50826ukjl6vgpzamhxue69uhkummnw3ezuerfv94k7epwvdhk6tczyp4kxm6mskj2uyju5nc9qc5qwagje3d87n7w0qqgfdfqjapel475jqcyqqqqqqgjaycxf

Jumble is the fastest project I ever built Git clone Npm ci Npm run build Took less than 1 minute Awesome job nostr:nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7q2uwaehxw309ac8ymmc0yhxummnw3ez6un9d3shjtnpwpcz7ct9xvcxycfjxvmnycm9vsmxxvfexccxgdpevvcryd3kvejxgvm9xqmkxetpx5exyvtzvcenwwrxv33rvwp5v9jk2d3nxcekgetrxsmqqltm2c

nostr:nevent1qqsqj0gvy7xe357dytnzvmy0gccxwkx7888dxjkv7wa878kny332cmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8wuwg7as64rmfrh9ssyl0zx4wq7tvf4y467jvdnd6gvdmc6zuhcgpsgqqqqqqs9cjmap

The reasons for my node getting corrupted all the time was the energy dropping every week for some milliseconds and sometimes it was getting to 300v instead of 220

## Amber 4.0.3-pre1 - Fix close application logic for bunkers - Add a Export/Import accounts method by nostr: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 nostr: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 <greenart7c3@proton.me>" ``` That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes: ``` bash cat manifest-v4.0.3-pre1.txt ``` One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.