It was in the very early days, but we did.
Notifications tab is not the mood for follow and detailed info. This is more for a regular feed, when you are in the "get more details about this post I just saw mindset". On notifications, you already recognize most of the faces. "It's all duplicated". There is no need to explain or occupy more space than needed.
Organically, in over 100k downloads, no one has ever asked me to add a button to follow in that page or display the about info, which should speak volumes about the need since it's one of the most used tabs in the app.
So, you have to click on each section to see who zapped and each reaction? Sounds like a click too far for me.
And why does it display people's about info and follow button? I am not there to follow people. I just want to see how people reacted.
This is weird.
I wouldn’t seriously consider switching until there’s a nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 version.
Sometimes I’m not in a party mood, I just want to scroll my notifications without everyone bumping into me and spilling their drinks.
Show us how Damus display the same notifications. Now I am curious to see why is it so much better.
Ohh interesting. Thank you!
The back button does not work in the sense that Instead of returning one step the whole app goes away. Here I opened it, navigated to this post and then press back once.
https://nostr.build/av/cfdb89a9471b462930a3080eaab8f1cb1002624c8abf1a31431bcf4102ba0880.mp4
That is very weird. It should definitely work. I will investigate.
Does it stay on after you Mark it all as Read? Sometimes very old messages arrive and they are all the way back in the list, but they are still unseen for that person.
Back button? That's new. Any particular place?
Same risk as using SimpleChat with the same outgoing IP for all contacts, right? The relay can bundle your messages/queues.
Simplex doesn't want to have a link to a known identity like Nostr would have.
We can rotate keys, but if you discard them, you won't see the messages address to that key anymore. In all cases, you will need a collection of all your past receiving keys to move to a new phone, for instance.
Not if you need to save all these keys somewhere (locally or on the cloud) to see the same feed in another client or device. That's what SimpleX does with the local database. Keys don't leak randomly. They leak when you are inserting them in a new device/client or when somebody gets access to it. If you keep your keys and the local db together, the attackers gets both.
The new idea does use ephemeral keys to send. We could do ephemeral keys to receive as well, but I am not sure if it actually adds much security.
I don't see it. As long as there are two clients doing DMs, we are going to have this issue. We only need two good ones that compete well and people will be lost. It gets attenuated when people use a client on the desktop or a tablet and another in the phone. They want to see the same feed in both, at all times.
SimpleX chat relays do keep your messages for a while just like Nostr does. And the receiver also has a copy of your messages. So, it's not that different than in Nostr (with the new idea, dropping step 4).
I am not so sure. In practice, the security is as faulty as with Nostr keys. The things that would cause a key leak in Nostr would also cause a chat database leak in SimpleXChat. And since on Nostr, people want their DMs in every client, there will be a lot of export and import happening, which yields bigger chances for leaking the entire thing.
People can opt out of the 4th step if they don't want to recover their own sent messages.
I am not sure if there is a practical solution for the DM history leaking issue. If people want to keep their history between clients, they will keep whatever is needed to recover the history together with the key. Once the key leaks, the rest is also leaked. :(
Yeah, I need to figure out how to use less memory. :(