Amethyst v0.20.3: Notification parties for all
Merges 3 reaction types in one card.
Download https://github.com/vitorpamplona/amethyst/releases/download/v0.20.3/app-release-v0.20.3.apk
This dude is a mad man, Amethyst is literally getting drastically better every day on Android 👀
#[0]
Easy nyms for each group are probably the best feature in SimpleX for that, and the only real reason why group chats might be worth it to me.
I'd definitely be interested if they were able to provide a server for groups that offloaded the network/compute necessary as he mentioned them wanting to do! That might make it a solid fit for large groups as well, at least for those willing to host a simple server.
Such a cool feature, especially when you want to run as a full-on nym.
Love the though that's into it!
We did briefly touch on using it for group chats, he mentioned he doesn't recommend it for large groups for the reasons I mentioned.
The design decisions made just mean it's not ideal for large groups, but it doesn't need to serve that purpose. Why do you need anonymity, e2ee on each message, and contact isolation in a *public* chat? I think there's usually a lot of confusion on what benefits are provided by more privacy-preserving alternatives for large public group chats.
Definitely do need a round 2, though, and will absolutely be doing one!
Any more details on how exactly this works? Very curious to learn more!
Not that I know of ATM, but I'm not very high on group chats in apps like this.
We talked about it on the pod episode, but the network architecture is ideal for direct chats (or very small groups) as you have to have direct, two-way connections to each group participant.
Group chats don't really need anonymity or e2ee in the same way as direct chats (as they're publicly joinable) so I prefer using platforms like Matrix for that use-case.
I haven't had any issues like that so couldn't really ask about it.
Would recommend reaching out in their subreddit for help:
Not sure, what's the issue? Mine works like a charm on GrapheneOS, but I am on a Pixel 6.
Network-level encryption is via TLS, comms level encryption uses the same Double Ratchet approach that Signal uses.
Lots more with threat models broken down here:
https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md
As mentioned in the pod network-level privacy isn't a core focus right now, but there is native Tor integration (via SOCKS5 proxy) in SimpleX that can be easily enabled if that is a concern.
First time looking into this. The protocol doesn't seem to mention how the encryption is done ( https://github.com/simplex-chat/simplex-chat/blob/stable/docs/protocol/simplex-chat.md ). Also let's assume all data is encrypted - you will still have visibility into which IP address the connection came from & the timing, right?
Network-level encryption is via TLS, comms level encryption uses the same Double Ratchet approach that Signal uses.
Lots more with threat models broken down here:
https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md
New contact address in case you want to chat on SimpleX as well, which now includes my own SMP server:
Running a SimpleX chat SMP server now, anyone is welcome to use it and the architecture of the network means that I'll have no visibility into messages or who talks to who using it.
Address: smp://HWK6x65IcNpRyGDQUtOMSSofcQv2D72-NbEmqg-SwAE=
@smp
.sethforprivacy.com
Or use QR below:
If you want to learn more about SimpleX, you can listen in to my latest Opt Out episode:
https://optoutpod.com/episodes/s3e02-simplexchat/
Really loving just about everything to do with SimpleX recently.
Fixed address (formatting got broken somehow): smp://HWK6x65IcNpRyGDQUtOMSSofcQv2D72-NbEmqg-SwAE=@smp.sethforprivacy.com
Running a SimpleX chat SMP server now, anyone is welcome to use it and the architecture of the network means that I'll have no visibility into messages or who talks to who using it.
Address: smp://HWK6x65IcNpRyGDQUtOMSSofcQv2D72-NbEmqg-SwAE=
@smp
.sethforprivacy.com
Or use QR below:
If you want to learn more about SimpleX, you can listen in to my latest Opt Out episode:
https://optoutpod.com/episodes/s3e02-simplexchat/
Really loving just about everything to do with SimpleX recently.
Sure sounds a lot like Nostr in network setup, doesn't it 👀
Iris.to so far for me! Looking forward to a proper desktop client, though.
If you decide to try it, shoot me a message on there as I'd love to chat more and help test it, plus want to ask you about coming on the pod I run for Foundation to chat LN privacy soon :)
Agreed, I'm *extremely* wary of new messengers that pop up, but this one is really checking all the boxes for me so far as a Signal alternative/replacement for DMs.
The UX is quite incredible for something that is a more complex and privacy-preserving architecture than even Signal under the hood, and has been working quite well for me. As Evgeny mentions they're quite early in the dev lifecycle (he mentioned his thought is it's about halfway to where he wants it) and has come a very long way since I first checked it out a while ago.
They were purchased by Proton but remain a standalone entity.
Zeus operates on value for value donations. If you get value out of using Zeus considering sending that value back our way. We don't know what value that is, that's up to you!
You can zap us, send us an anonymous donation at https://pay.zeusln.app/ - or become a community sponsor and get your Nostr profile and pfp display on our website and in our app over at https://zeusln.app/about.
Thanks for your support.
If you use Zeus and love it as much as I do, please please please take a minute and consider sending some sats their way to support the incredible work they're doing!
#[1]
Happy to help every way I can, couldn't imagine using LN without Zeus!
Keep changing the future of self-sovereign LN 👊
If you haven't tried going fully self-sovereign with #[1] at the core of your LN usage, you're missing out.
They're changing the landscape for self-sovereign LN usage.
#[0]
Yeah, the current approach is already entirely reliant on DNS security, so OpenAlias would have the same concerns (and solution in DNSSEC) while removing the hosting/infrastructure requirements.
You can use the integrated LN-URL/LN Address, and then just need NIP-57 support added for Zaps to properly show in Nostr clients:
https://github.com/btcpayserver/btcpayserver/discussions/4642
👀
Could just reuse existing syntax like below in a TXT record for a given domain/sub-domain:
oa1:nostr recipient_address=58ead82fa15b550094f7f5fe4804e0fe75b779dbef2e9b20511eccd69e6d08f9
Thoughts on this as an extension of NIP-05, #[2]?
Yes, but it’s a lower risk, much less likely to get targeted (you’re just one of thousands of VPSs, instead of known to be using Nostr/NIP-05), etc.
Overall a better set of tradeoffs from a trust perspective.
Anyone know if there is a technical reason that NIP-05 couldn’t be done for a single pubkey via OpenAlias?
Would greatly simplify NIP-05 for anyone who has a proper domain name, and would be an excellent alternative option to serving a static JSON file via a web server.
More here:
And if you’ve never seen what it can be used for, it’s excellent for static addresses or reusable payment codes, like PayNym’s or as seen in Monero:
Would definitely love OpenAlias as another supported method, have used it for ages and it’s very under-appreciated.
No great native desktop clients yet, have been using iris.to on web and testing our coracle.social every now and then as well.
Good enough for the moment, but definitely looking forward to proper desktop clients (especially for Linux!)