nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 have you checked the uploading procedures that sign a NIP-98 payload?
Will check again to see if there's something wrong
Is there any plans for a native app?
Edward nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9 gave us all a stern warning, and despite the standing ovation, I don’t think most people understood or cared.
Snowden agrees that Bitcoin is the best tool we have to fight the surveillance state, but "Bitcoin has a privacy problem".
The reason we see talks of ETFs and acceptance from the SEC is BECAUSE Bitcoin is not private.
Snowden says it’s not enough for a few to know best privacy practices. Those who have good OPSEC should use that skill to provide privacy to the masses.
Privacy must be the default.
Notice he doesn’t say we should switch to Monero. Monero is a shitcoin. He says the technology to make decentralized, private payments with Bitcoin exists RIGHT NOW, and the minority of us who truly care about freedom need to pay attention to the discourse and stop asking for permission.
In other words, we have to stop accepting "Bitcoin shouldn’t do that because it might cause legal issues".
Separate money from the fucking state https://v.nostr.build/yw85.mov
## 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
If you visit this profile on Amethyst, does it automatically block the user for you?
nostr:npub147mp7se7latwmvpjreea0cgc5j75aqsylpu866pwxk2yjykcxc7sz203fa
Go to the security filters page and uncheck filter spam from strangers.
Can you share what device and os you are using?
Your messages are encrypting twice don't know why yet
Maybe remove zaps from the profile page.
I saw some people complaining that some devs receive more zaps than other and having this info in the profiles can lead to attacks, so showing how much a person is receiving should be discouraged
Spring browser v.0.3.0 adds NsecBunker support.
Finally nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft can try it without worrying about his precious keys 😉
With Spring, you can use NsecBunker with any Nostr app, even when it's not supported by the app itself. Just add your nsecBunker token to Spring and "Login with extension" will be bridged to nsecBunker from apps opened inside Spring.
Full change log:
New:
- NsecBunker support
- Signed event history
- Pinned app settings on long-tap, delete pin button
- Clicks on lightning: links pays from current wallet
- Select/copy of LN invoice shows 'Pay invoice' action in context menu
- Add 'Open in system browser' action
- Add content feed settings
- Add browser tab GC to constrain resources occupied by active tabs
- Show npub and key type on profile screen
- Add 'View replies' action via replies.nostrapps.org
Fixed:
- Bootstrap logic that caused duplication of pinned apps
- Slow swiper for homepage content feeds
- Back button inside tab returns to last active page
- Hanging relay connection by checking conns on resume
Get it on Play Store: https://play.google.com/store/apps/details?id=com.nostr.universe
APK: https://github.com/nostrband/nostr-universe/releases/download/v0.3.0/spring-nostr-browser-v0.3.0.apk
Don't forget to check the 'Pre-releases' box in Obtainium.
Let us know what you think!
I see only the encrypted text from your account
...still happening...am I doing something wrong? Problem with #amethyst, #amber, or this user?
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

I need more information. Is this happening in all dms? Are you using the remember my choice option in amber? Does this happen all the time or after a while it starts happening? Of you force close both apps does it work again?
EXPERIMENTAL ANDROID 14 RELEASE ANNOUNCEMENT
GrapheneOS is now based on Android 14. An experimental release based on Android 14 has been made available for broader public testing. Most of our features are already available. Certain minor features haven't yet been ported to Android 14. There may be more issues to address with the sandboxed Google Play compatibility layer to restore full app compatibility.
This release provides the full 2023-10-06 patch level for all supported devices along with the recommended security patches only included in Android 14.
Android 13 is no longer actively developed upstream and now only receives backports of the Android Security Bulletin patches, not the recommended patches included in the latest stable release of Android. Pixels are also now only supported via Android 14 and require Android 14 to achieve a patch level above 2023-10-01. Android 14 has had publicly available experimental releases since February 2023 and is already a mature OS. It also contains significant privacy and security enhancements which more than offset the attack surface from added features. These reasons are why we have so heavily prioritized porting to Android 14 and began to defer more and more of our other work until after Android 14 since around July 2023.
Please join #testing:grapheneos.org on Matrix if you want to help with testing the experimental releases.
The experimental releases are production builds of GrapheneOS signed with the official release keys. You don't need to reinstall the OS to test them and you'll continue receiving regular updates on the experimental releases via the
regular release channels. There will likely be a couple more experimental releases before we're ready to push out a release via the Alpha channel, Beta and then Stable as usual.
There are 2 ways to update to the new experimental release. You can either enable ADB within the OS and use it to override the update channel to the experimental channel, or you can sideload the update via recovery. Sideloading
the update via recovery is recommended if you don't already use ADB since it avoids needing to temporarily enable developer options and ADB along with temporarily trusting a computer with ADB access.
To install one by sideloading, first, boot into recovery. You can do this by holding the volume down button while the device boots to enter fastboot mode followed by selecting the Recovery option in the menu with the volume buttons
and then pressing power to activate it. You should see the green Android lying on its back being repaired, with the text "No command" meaning that no command has been passed to recovery. Next, access the recovery menu by holding down
the power button and pressing the volume up button a single time. This key combination toggles between the GUI and text-based mode with the menu and log output. Finally, select the "Apply update from ADB" option in the recovery menu and sideload the update with adb. For example:
[adb sideload felix-ota_update-2023100600.zip]
https://releases.grapheneos.org/felix-ota_update-2023100600.zip
https://releases.grapheneos.org/tangorpro-ota_update-2023100600.zip
https://releases.grapheneos.org/lynx-ota_update-2023100600.zip
https://releases.grapheneos.org/cheetah-ota_update-2023100600.zip
https://releases.grapheneos.org/panther-ota_update-2023100600.zip
https://releases.grapheneos.org/bluejay-ota_update-2023100600.zip
https://releases.grapheneos.org/raven-ota_update-2023100600.zip
https://releases.grapheneos.org/oriole-ota_update-2023100600.zip
https://releases.grapheneos.org/barbet-ota_update-2023100600.zip
https://releases.grapheneos.org/redfin-ota_update-2023100600.zip
https://releases.grapheneos.org/bramble-ota_update-2023100600.zip
To install the update over-the-air with the OS update client, enabling developer options, enable ADB, attach the device to a computer with ADB installed, run adb devices, accept the authorization prompt to trust the computer with ADB access and run the following command:
[adb shell 'setprop sys.update.channel experimental && cmd jobscheduler run app.seamlessupdate.client 1']
* Code Snippets above use square brackets remove but entering if copy/pasting.
SUPPORT FOR THIS RELEASE IS ONLY OFFERED IN THE TESTING ROOM ON MATRIX PLEASE DO NOT MESSAGE ME HERE.
