Most of your points seem to be spot on from what I understand as well. However, I believe that the GDPR requirements can and should be baked into Lemmy itself. This would prevent the fragmentation you mentioned. A guarantee of removing user data as requested while federated plus a guarantee to remove stale user data while defederated since requests won't get through in that case. That would "just" leave the list of processors. This one can be very tricky because you are not just sharing data with your home instance and their federated instances but also with the federated instances of those federated instances. The home instance has no way of learning about the 2nd degree federation. I have no idea how to get the network of data sharing GDPR compliant and I think this is the mich more complicated part that your proposal also suffers from.
Lichtblitz
If data moves away from an instance with whom an EU user has an agreement, those third party instances have to be bound by the home instance through agreements/contracts to follow the rules of the GDPR before giving away the data. Also the home instance would have to list all instances that have received data or that could likely receive data through such an agreement. Federation is not a solution to GDPR but it rather makes things incredibly complicated for the instance owners if they tried to comply fully. And from what I've read, Lemmy doesn't even have the technical capabilities to make it possible, yet. Maybe that's what compels Meta. They can just offload responsibility to the instance owners.
I wouldn't call it a good alternative. It is a viable, relatively low cost, non-destructive alternative. But for many people it will interfere with other dates cables and depending on the electrical wiring, it may also have intermittent connection issues.
I was able to find a video on YouTube for my model and it looks like there are some for yours as well where someone demonstrates the steps.
No, this doesn't work for ThinkPads. The password persists even without power.
Die Reibereien zwischen Militär und Söldnern wurden ja schon länger öffentlich ausgetragen. Diese Eskalation hatte ich jetzt aber nicht erwartet. Ich dachte eher, dass Mal wieder jemand aus dem Fenster stürzt.
Sure thing.
So there are two parts to all of this:
- Getting MediaWiki set up , properly configured and running.
- Having it securely accessible from the Internet (if needed), including SSL certificates.
Part 1 is well covered my the MediaWiki release already. You only need to worry about the correct configuration. When you download the current version from the official MediaWiki page, you'll notice that there is already a docker-compose.yml file in there. This gets you most of the way to your destination.
Read the file and set the values of all variables you wish to override in a separate ".env" file in the same folder. It could look something like this:
MW_SCRIPT_PATH=/w
MW_SERVER=https://your-url.com
MW_DOCKER_PORT=80
MEDIAWIKI_USER=Admin
MEDIAWIKI_PASSWORD=some_password
XDEBUG_CONFIG=
XDEBUG_ENABLE=true
XHPROF_ENABLE=true
MW_DOCKER_UID=1000
MW_DOCKER_GID=1000
Now you can just docker-compose up and everything will be set up when visiting your site for the first time, it should hold your hand, guide you through configuration options and finally offer you to download the LocalSettings.php file, that contains all the decisions you've made. You can review and adjust it futher and finally save it to the same folder as your docker-compose.yml file. Refresh the site and it should be accessible right away.
I would say for a closed audience, these are the most important options to set:
# The following permissions were set based on your choice in the installer
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['read'] = false;
These options will prevent people from creating their own accounts (you will have to create one for them from the UI) and it will block people from viewing any pages without being logged in.
If you do not wish to use SQlite but rather a dedicated DBMS (I strongle discourage you from getting into that trouble for smaller or even medium user bases), you will find more information on the page for alternative configuration recipes.
If you would like to go into part 2, just ask and I'll give you an overview of my setup here as well. I'm using docker-letsencrypt-nginx-proxy-companion.
Nothing. Are you saying there is something wrong with badass John Oliver? Or with evil John Oliver? Stop typecasting him. He is more than just his sexy looks!
~~As far as I can see, there is no search button. There is only a button for subscribed communities with a filter text box. You can't actually search anything there. Or am I missing something?~~
EDIT: I've tried it again and suddenly it does something other than filter subscribed communities. Weird that it didn't work before.
Windows 11 has some niche features that set it apart in amazing ways. One of them is that it natively supports Linux GUI applications almost the same way as native Windows applications. No need to have a dedicated remote desktop window. Just intermingle Linux and windows applications through WSLg. Granted, it won't mean much to many users but as it stands, Windows is becoming the top multi-platform OS. Who would have thought?
I'm running MediaWiki for a role playing group in docker. The difficult part was getting everything set up to get certificates from letsencrypt and offering https without leaving docker compose. The great thing about this is that creating a backup or moving servers has become trivial now. As long as you don't expect your users to perform dozens or even hundreds of operations per second, I'd strongly advise sticking with SQLite to make your admin life that much easier. If you want, I'll look up my full stack and post it here once I'm not on mobile any more.
Yes, I agree. This use case likely wasn't considered when the law was written. We'll see how things turn out in the future because at some point we will have enough very knowledgeable people regarding GDPR in the community who are willing and even keen on steering the project in the right direction towards compliance.