(They/Them)

This is my main lemmy account.

Admin of lemmy.cloudhub.social

I can also be found elsewhere on the fediverse at @jax@cloudhub.social

  • 4 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle

  • Currently using Nextcloud AIO and it’s pretty decent, though I’ve got 16 vCPU and 32 GB of RAM allocated to it right now, though it’s only using 10% CPU and ~7 GB of RAM at the moment.

    I think it takes a while to warm up once you start adding data to it, especially depending on the plug-ins you add and amount of data.














  • Just because it’s not public facing doesn’t mean that it’s not an issue. It might be less of an issue, but it is still a massive vulnerability.

    All it takes is one misconfiguration or other vulnerable system to use this as a jumping off point to burrow into other systems. Especially if this system has elevated access to sensitive locations within your network.



  • I don’t think it’s worth the devs’ time to implement e2ee for DMs, there are lot of other things that need to be fixed first. Not only that, but if it’s implemented in Lemmy, it’d make Lemmy non-interoperable to DM users from other federated platforms such as Mastodon or KBin. Which, I’m not sure works right now, but in theory would be possible.

    Also, yes, that is generally the case.


  • I highly doubt it will, there are many much better solutions available, and as it says when DM’ing someone, you can you Matrix for e2ee. In fact, there is even an option in the profile settings to provide your Matrix username.

    Implanting e2ee within DMs is massive scope creep and also really difficult to do properly.

    The general rule is basically “never implement your own encryption/security, just use what’s already been implemented by people who actually know encryption/security”.