Most effective method for me has been to use 1 e-mail address alias per service. If that address starts receiving spam then you know who is to blame for the leak, can move that service to a new e-mail address and then blackhole all e-mails sent to the old address. That obviously means having to setup a new address for every service though so I usually setup 20 at a time and hand them out as needed.

Fingers crossed this can be a viable replacement for Collabora Online with Nextcloud, which has been a nightmare.

You would need a way of verifying that the SHA256 is a true copy of the site at the time though and not a faked page. You could do something like have a distributed network of archives that coordinate archival at the same time and then using the SHA256 then be able to see which archives fetched exactly the same page at the same time through some search functionality. I mean if addons are already being used for doing the crawling then we may be mostly there already since said addons would just need to certify their archive and after that they can discard the actual copy of the page. You need need a way to validate those workers though since a bad actor could just run a whole bunch at the same time to legitimise a fake archival.

Until the other penny drops and makes federation impossible: making it so users on other instances are treated as your users if they interact with your instance. If such a law was introduced I’d imagine they’d carve out an exemption for e-mail since that would cause utter chaos.

Loving the transparency on this post! It would be lovely if you could specifically fund the work which would allow Matrix to have those more gamer-foused features.

Main issue with Rufus is secure boot unfortunately, otherwise Rufus is easy enough that I gave a couple “click here, then here, then here and here are some screenshots” to a friend they were able to navigate it just fine. At this point I swear Rufus is easier than using the official installer provided Secure Boot is off.