How to Embrace the STR:
Most of the time, devs are aware of bugs and issues. If they're not, submit an issue on the project's GitHub or tag them on Nostr.
It helps to provide as much information as possible. That said, I've been guilty of just taking a screenshot and tagging nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug 🥹 Sorry!
If the devs aren't fixing your issues, it could be because of several reasons. They could not want to fix it simply because other issues exist and they're working on those instead. And sometimes it's because a new shiny object has their attention and priorities have shifted. If this happens, you could try asking them how much it's going to cost to motivate them to fix it and Zap them to get it resolved. Devs like money too.
What if your favorite app doesn't have the feature that you'd like to see? Well, following the same path as the above for issues, you can ask developers, talk to them on Nostr and submit feature requests on GitHub. You can also put up a bounty for it too. Again, devs like to be paid for their work. I remember paying a bounty sometime last year to get a feature added to Amethyst. It worked well.
Now, not every feature will get added to every app. From a user standpoint, this may seem like it sucks, but remember that Nostr is open and anyone can build whatever they'd like to see. That means we'll have many different apps and use cases and not all of them will be the same. That would be boring. The most popular and most useful ones will probably be replicated across all major clients. And if it not, well, there's always the opportunity for you to build it yourself or again submit a bounty to get someone to build it for you.
If all of this sounds very disorganized and hard to navigate, then you're absolutely right! Nostr is decentralized, meaning no one is in charge - but it does work! Somehow, with everyone essentially doing their own things, all of this works and is interoperable.
You see, Nostr has no development team or design time, but we do have various freelance developers and designers working for themselves or very small teams, where most of them are hacking away on Nostr in their spare time. While some do work on Nostr full time, it's still a lot of work for one person to do non stop, without getting burnt out.
Nostr is very far along and improving all of the time across many clients, considering how early we are in the whole process and Nostr's inevitable future. Embrace the STR. No one said it was going to be smooth and easy.
What do you think about adding an optional event kind parameter to signer calls, allowing signers to show the user what the app is attempting to encrypt/decrypt.
They should implement unified push and/or syncing notifications with nostr
Yes, no idea why most apps don't encrypt lists or give the user the option
Can you test the 1.1.0 beta to see if it this issue?
## 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)
I see now. If I just force close amethyst it works but force closing both I can reproduce
nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck 1.0.9 still prompts me for permissions pretty much once every 30 minutes when I load up amethyst btw, just bumping since there was a new version since last time :)
Yeah I still could not find this bug.
Maybe nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug already fixed.
What version of amethyst you are using?
Long press the zap icon in any note
I think not but I'll check if it's not installed and show a message
The free version doesn't use play services it uses unified push and for that to work you need to install another app called ntfy
And what version of amber you are using free or play?
What screen is pushing the ui up?
Did you changed the default relay?
If you are using a local relay you need to change the notification type to direct connection
nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 Yes, i also believe that you can update and with backwards-compatible . 🤣
Maybe we can discuss more details in github.
Actually, I have completed the development and tested the version you have implemented. If you decide to make a change, I can assist you in testing both the old and new versions.
Yes I checked it and I believe only 0xchat is not checking if is a hex key or npub
Hello guys. I have some changes to NIP55, but some of them might be breaking changes. Can we discuss them?
1. Change some fields ```pubKey``` to ```pubkey```, just other nips does.
2. When transmitting information, other nips use pubkey, but here npub is used, and npub is changed to pubkey.
3. Add a function ```get_relays``` just like other nostr signer [NIP-07](https://github.com/nostr-protocol/nips/blob/master/07.md) and [NIP-46](https://github.com/nostr-protocol/nips/blob/master/46.md)
You can see the detail from this https://github.com/haorendashu/nips/blob/nip55-fix/55.md
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl
If you look at the signer provider file in amber there's a version tag I used in amethyst.
I think you should create a version tag in the intents to so we can change this without breaking clients
Amethyst already has zapraisers just a tag in kind 1
## 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)
Is there a tool to fix duplicated follows? Someone is having problems because a client duplicated his list 4 times and he's now following 8k npubs
The no relays found is happening using amethyst?
In the permissions screen press the application and it will open a dialog with a relay button. Check if some application doesn't have a relay.
