4 ms·
I didn't whitelist anything, maybe that was a source for issue. > Disagree. Sure, UX can be improved, but compromising here defeats the purpose of why we’re do
by kuon 5y ago
I didn't whitelist anything, maybe that was a source for issue.
> Disagree. Sure, UX can be improved, but compromising here defeats the purpose of why we’re doing this in the first place.
The thing is, as I ran my own server in my office, SSL (with no E2E) is already a good privacy. And even with that setup, the server users got "harassed" by the UI asking them to sync devices keys.
For many users, a single prompt about security is enough to discourage them.
- CameronNemo 5y agoSo you are asking for a client setting (in Element I presume) to stop nudging users to set up e2ee? Did you file an issue for that?
- kuon 5y agoIf I try again to "convert" non technical people around me, I'll try to document properly what is wrong in the UX and experience. (but maybe it will all be fixed)
- 3np 5y ago> And even with that setup, the server users got "harassed" by the UI asking them to sync devices keys. I think Element is the only client doing this. So if you don’t care about E2EE, there are several options. My point is, this is something that should be addressed in the client UX, not on the server- or protocol level.
- 3np 5y ago> I didn't whitelist anything, maybe that was a source for issue. Should have mentioned: I think my approach works fine for single-user or small-closed-community servers. Nobody should do this on servers with public rooms and/or open registration as it will lock out minority servers and cause further centralization.