aptronymic!

Mattermost isn’t e2ee, but if the server is run by someone competent and they’re allowed to see everything anyway (eg it’s all group chat, and they’re in all the groups) then e2ee isn’t as important as it would be otherwise as it is only protecting against the server being compromised (a scenario which, if you’re using web-based solutions which do have e2ee, also leads to circumvention of it).

If you’re OK with not having e2ee, I would recommend Zulip over Mattermost. Mattermost is nice too though.

edit: oops, i see you also want DMs… Mattermost and Zulip both have them, but without e2ee. 😢

I could write a book about problems with Matrix, but if you want something relatively easy and full featured with (optional, and non-forward-secret) e2ee then it is probably your best bet today.

Ente doesn’t seem to require a CLA.

It turns out, they do have a CLA (with full copyright assignment 😢).

They’d need to implement something like SRP.

Update: I contacted the developers to bring my comment to their attention and it turns out they have already implemented SRP to address this problem (but they haven’t updated their architecture document about it yet).

It is, but in this case I think it isn’t actually a weakness for the reasons I explained.

That’s complicated to do correctly. Normally, for the server to verify the user has the correct password, it needs to know or receive the password, at which point it could decrypt all the user’s files. They’d need to implement something like SRP.

What I proposed is that the server does not know the password (of course), but that it knows a thing derived from it (lets call it the loginSecret) which the client can send to obtain the encryptedMasterKey. This can be derived in a similar fashion to the keyEncryptionKey (eg, they could be different outputs of an HKDF). The downside to the server knowing something derived from the passphrase is that it enables the server to do an offline brute force of it, but in any system like this where the server is storing something encrypted using [something derived from] the passphrase the server already has that ability.

Is there any downside to what I suggested, vs the current design?

And is there some reason I’m missing which would justify adding the complexity of SRP, vs what I proposed above?

The only reason I can think of would be to protect against a scenario where an attacker has somehow obtained the user’s loginSecret from the server but has not obtained their encryptedMasterKey: in that case they could use it to request the encryptedMasterKey, and then could make offline guesses at the passphrase using that. But, they could also just use the loginSecret for their offline brute-force. And, using SRP, the server still must also store something the user has derived from the password (which is equivalent to the loginSecret in my simpler scheme) and obtaining that thing still gives the adversary an offline brute-force opportunity. So, I don’t think SRP provides any benefit here.

edit: the two issues i raised in this comment had both already been addressed.

this was the developer’s reply on matrix:

1. We do have a CLA: https://cla-assistant.io/ente-io/ente
2. We will update the iOS app to offer you an option to point to your self hosted instance (so that you can save yourself the trouble of building it): https://github.com/ente-io/ente/discussions/504
3. The portion of the document that deals with authentication has been outdated, my bad. We’ve adopted SRP to fix the concerns that were pointed out: https://ente.io/blog/ente-adopts-secure-remote-passwords/

There is a version of VLC for the Nvidia Shield, but it has a somewhat irritating UI and I don’t know if it can actually read the menus like the desktop version can.

Fuck both of these companies, but, how can it make sense to sue Citrix for this? The article says they released an advisory and patch for the problem six days prior to when Xfinity says the breach happened, so, it sounds like Xfinity neglected to install their software updates.

cloudflare’s service puts them in the middle - so, HTTPS doesn’t encrypt traffic between the browser and your server anymore, but instead between the browser and CF, and then (separately) between CF and your server. CF is an antidote to intelligence agencies’ problem of losing visibility when most of the web switched to HTTPS a decade ago.

cloudflare is an intelligence company who’s flagship product involves them mitming your TLS.

why bother self-hosting, if you do it from behind cloudflare?

…so you can avoid sharing your phone number with your contacts.

they are not planning to let you use Signal without having a phone number and sharing it with their (Amazon’s) servers.

There are at least four companies listed here selling new laptops with coreboot preinstalled: https://doc.coreboot.org/distributions.html

garner a community of support ensuring that there is an audience for the project

I’m sure this is true for certain kinds of communities. Personally I’ve never been tempted to try using Discord, because any project that uses it is obviously built by and for people with (imo) very poor taste in technology.

Thanks for the effort, but, unless I’m missing something, this is unnecessary because you can simply make a relative link like [this](/c/lemmy@lemmy.ml) (this) and get the same effect. Also, as of 0.18.0, a string like /c/lemmy@lemmy.ml automatically becomes a relative link, like this: /c/lemmy@lemmy.ml

However, these relative links unfortunately don’t work on non-lemmy activitypub sites like mastodon and kbin.

imo, despite this, for now an easy improvement that should be made is that lemmy’s autocomplete functionality (when typing !communityname...) should be changed to generate relative links.

I haven’t followed the discussion closely but there are multiple github issues about this problem. One is here and from it you can find some others.

their admin says clearly that “racism, bigotry, sexism is allowed" there.

the “push service tokens” for threema is a fun one, i wonder what those get used for

it’s disappointing seeing so many people here excited about something that is not (and apparently not planning to be) free open source software :(