I wonder if the latest version solves some of that. I am not receiving that many crash reports anymore via the PlayStore. But happy to debug if you want to send me a stacktrace.
The receiver has set up their profile incorrectly. A Lightning Address looks like an e-mail from the wallet provider. Mine, for instance, is vitorpamplona@getalby.com
The LNURL*** that is there is just a format that has been phased out of user configuration fields. They just need to get their e-mail-style address and replace the LNURL** stuff in their profile.
There is too much mumbo jumbo in DriveChains. If the stuff you are working with is too complicated to be digested by your peers, it's probably not ready for prime time. Keep building it, though. You will get there one day.
GM.
Lol.
### #Amethyst v0.74.5: BugFixes and coroutine updates
- Fixes loading of GiftWraps URIs as intents in the app.
- Fixes Thread's search for root to go backwards in the e-tag stack for backward compatibility.
- Fixes TopBar's and extended header's padding issues.
- Fixes a crash when not using play services with notifications by nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5
- Adds user info to the header of single-user GiftWrap chat rooms
- Breaks user-created-At UI line for communities and groups into two
- Moves community description and rules texts to a single Translateable text
- Fixes the Note ID copy to clipboard function of a GiftWrap message
- Fixes the feed refresh after adding an image on stories
- Fixes the divider presence in the Discover and Notification tabs
- Filter follow lists with the entire list of participants for Live Activities
- Only shows the notification dot on the discovery tag when the notification comes from follows.
- Fixes unfollowing hashtags to be case insensitive
- Minimizes the creation of new coroutine scopes
- Moves coroutines of BundledUpdate and BundledInsert to a managed model.
- Broadcasts all replied, quoted, and mentioned events together with the main event.
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.74.5/amethyst-googleplay-universal-v0.74.5.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.74.5/amethyst-fdroid-universal-v0.74.5.apk)
Wow sounds good! How ready is this to implement in clients?
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s have you looked into offering this as an option for translations?
nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 has been playing with it for a while.
It's probably good for public posts. We can always enable it if the local translation fails. But I am not confident translations will be much better.
For private events, things get a little more complicated because we need to make sure people understand they are exposing the details to one or multiple third-party sites.
It's similar, but social. The idea is to not incentivize combative replies and focus on collaboration in the platform.
Ok, I won't call it a PR. I will call it a Google Doc suggestion :)
Yep. Edits are fine if you show the history.
Notes could have their own PRs. Picture this scenario: you write a note, share it, and then one of your friends spots a mistake and submits a patch to rectify the error in your note. You merge it and it replaces the original note.
That's the real social app.
GM.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z hey, just curious, why aren't the timelines on amethyst "New Threads" and "New Threads+Conversations" but "New Thread" and "Conversations"?
any other social network clients use latter as far as i see
We tested including new threads on conversations as well many months ago but people didn't like it as much. If you already saw the post on New Threads, there is no need to see it again in conversations. It feels better.
