37 contributors poured their hearts into #Amethyst this year, delivering 10 major & 69 minor releases packed with new features, performance improvements, and privacy and security boosts, including:
+ NIP-17 DMs (Audited NIP-44v2)
+ Feed Algorithms with DVMs (NIP-90)
+ Edits and Edit Proposals
+ Drafts (NIP-37)
+ Embedded Tor
+ OpenTimestamps (NIP-03)
+ NcryptSecs (NIP-49)
+ Wikis (NIP-54)
+ Git (NIP-34)
+ Torrents (NIP-35)
+ Comments (NIP-22)
+ Seed Words login (NIP-06)
+ Medical Data and FHIR Records
+ Bech32 embeds
+ Blossom (BUD-01, BUD-02, and BUD-03)
+ Video Events (NIP-71)
+ Picture Feeds (NIP-68)
+ Build Your Own Adventure posts
+ Outbox Migration (NIP-65)
+ Pokey Integration
+ Local and Private Relays
+ Negentropy
+ Spreadsheets
+ Structured Curriculum Vitaes
+ Relay NOTIFY commands
+ NFC Transient accounts
All this was made possible by our amazing contributors on a #Value4Value model!
Click that "Zap the Devs" button and give them a nice gift these holidays. We got much more coming for 2025.
Replies (39)
That is impressive work,
@Vitor Pamplona!!
Legends
Congratulations 👏
Os caras são foda mesmo 💚🥹
Vitão, queremos adm a comunidades, mudar cor, posição dos ícones, filtros, suporte a Liquid e Depix☝🏻🤓até final do ano
I will donate a few sats if you explain what Garnet (the Amethyst fork with Monero tips) would need to do to get merged with Amethyst & also just generally draw some attention to the fact that Garnet needs a maintainer since I don't see any recent posts about it from you and it's needed a maintainer for months
zzap to the best nostr app and the people that make it possible 🤙
It's been a good year for rapid development! Cheers everyone! 🍻
Frankly, I have not looked at their changes. They can send a PR if they want us to consider merging. Garnet is a separate project. It's up to them to maintain it.
If they don't want you to consider merging, others do. It's all open source and based on your work, you don't need their permission
Not wanting to call for help maintaining a separate project is fair, but you could at least still make a post making clear what the community would have to do to make a merge easy for you
Their code is extremely old at this point. I would have no idea how to bring it back into Amethyst. Somebody would need to spend the time to bring it up to speed.
They have added a few external n native dependencies that I have never seen and don't know exactly what they do. Somebody will need to convince me that that external code is not trying to steal anything from the user before any merge.
Also, it feels like they added the full code of an XMR wallet inside of Garnet, which creates a LOT of regulatory problems for us. I don't know exactly how to manage that, but I would prefer that Amethyst just communicated with an external wallet instead of becoming one.
Brilliant
Thanks for the wonderful Client. I hope the whole team has a happy new year!
No. We are not developing an iOS app. We want to focus our time on Android and iOS wouldn't allow us to do what we want do do anyway, like having separate apps for signing, notifications and relays.
This is amazingly beautiful #v4v.
Totally forgot about my PR to fix some small detail almost a year ago, and now receiving some sats for that makes me feel that this really is the way.
Zap the Devs according to their contributing efforts in a given period or certain release makes my motivation to keep building go through the roof.
Let's make this the standard,
@Zapstore 😉 😉
Merge it so that you can send monero tips in addition to LN from an external wallet is the way. You don't want to be a regulatory target and Monero can live happily hiding in a crowd.
Can someone convince
@Vitor Pamplona its not stealing user data.
Thanks for the opportunity to contribute to something as phenomenal as #amethyst 🙏
What if you could set a budget of some sats / month in
@Zapstore that is being distributed among all apps that have been installed on the device?
This is the way
Just a couple of issues:
@siamstr.com down at the bottom took a few attempts with my fat finger.
@VictorieeMan is missing out.
Ohh good catch!
T Y Vitor/*
@Jon Gordon @Avi Burra We can try dentistry as well
Definitely thinking about all this
Amethyst supports negentropy?
TIL
We do, but most relays don't... So... We haven't fully integrated yet.
Cannot mass zap, using
@Amethyst
I think this would be the simplest and most straight forward way to do it. Maybe bring up a QR code to scan the address too.
strange
I've been donated sats from others through last few days
maybe something #minibits related? if it's at my receiver end. A bit to New years eavy for me to dive into atm
I forwarded this and error logs to
@calle 💯 & #minibits
&& changed to an alternative lightingadress in the meantime.
== Best if ofc. if fixed so Amethyst don't halt a zap due to one out of gizzilion people have a broken adress.
You can try a mass zap again; if you want :)
Happy new year!
& thanks for reporting.
It works now, however I have to zap each person individually, is there a way I zap just once and it distributes the zap to everyone with equal amount?
Maybe I'm asking too much, I just thought it would work that way
I reply on the screenshot!
I think a single tap -> many zap works in Amethyst if you got a getalby-wallet connector setup. Otherwise it will have to ask your lightning app for permission on each transaction.
I can't make a test atm. But that's how I remember it working.
@Vitor Pamplona might have more current input on this.
Yeah; I checked the source code and it seems like this is it.
If 'account.hasWalletConnectSetup' is true it seems like it batch sends and split your zap send by itself.
Otherwise it enters some 'onPayViaIntent' logic, that I think is the list you had to click through
I've checked it. Your minibits lightning address returned error because you had dozens of unpaid not yet expired invoices (likely never paid zaps) and they hit the limit set as a dos attack precaution.
I've increased the limit few times up, so should not be an issue anymore.
Is there a way we can create invoices that expire? For zaps, the invoices should be really short term.
I used to have 30 min expiry on minibits mint when used lnbits as a node middleware but now the mint is directly integrated to lnd with their 24h default.
Raised an issue to nutshell to enable to set custom expiry but not yet implemented afaik.
That's why I raised significantly the unpaid invoices dos limit per address yesterday.
For when your wallet device is separate from your nostr device
