[pi@raspberry]# sudo su
Just saying, not everyone needs session management...
jarfil
joined 1 year ago
"do one thing well"
Arguably, Systemd does exactly that: orchestrate the parallel starting of services, and do it well.
The problem with init.d and sys.v is they were not designed for multi-core systems where multiple services can start at once, and had no concept of which service depended on which, other than a lineal "this before that". Over the years, they got extended with very dirty hacks and tons of support functions that were not consistent between distributions, and still barely functional.
Systemd cleaned all of that up, added parallel starting taking into account service dependencies, which meant adding an enhanced journaling system to pull status responses from multiple services at once, same for pulling device updates, and security and isolation configs.
It's really the minimum that can be done (well) for a parallel start system.
It's not a bug, it's a feature. Think of it like this:
- Instances: define some ToS and Code of Conduct
- Communities: define a theme and a sub-Code of Conduct
By having multiple instances, you aren't bound by a single ToS or Code of Conduct, you can pick whatever instance you want that matches the content you want to post to a community.
For example, the same "Technology" community could be on:
- an instance directed to kids
- an instance that allows visual examples of medical procedures
- an instance that discusses weapons technology
Having the community limited to a single instance, would never allow the different discussions each combination of instance:topic would allow, even if the topic is technically the same in all cases.
Forcing communities from multiple instances to merge, would also break the ToS of some of them.
So the logical solution is for the user to decide which instance:communities they want to follow and participate in, respecting the particular ToS and Code of Conduct of each.
On Reddit, the r/Technology community needs to follow a single set of ToS and Code of a Conduct. If you try to discuss something that meets the topic but is not allowed, then you will get banned, possibly from all of Reddit.
It's not a bug, it's a feature. Think of it like this:
- Instances: define some ToS and Code of Conduct
- Communities: define a theme and a sub-Code of Conduct
By having multiple instances, you aren't bound by a single ToS or Code of Conduct, you can pick whatever instance you want that matches the content you want to post to a community.
For example, the same "Technology" community could be on:
- an instance directed to kids
- an instance that allows visual examples of medical procedures
- an instance that discusses weapons technology
Having the community limited to a single instance, would never allow the different discussions each combination of instance:topic would allow, even if the topic is technically the same in all cases.
Forcing communities from multiple instances to merge, would also break the ToS of some of them.
So the logical solution is for the user to decide which instance:communities they want to follow and participate in, respecting the particular ToS and Code of Conduct of each.
On Reddit, the r/Technology community needs to follow a single set of ToS and Code of a Conduct. If you try to discuss something that meets the topic but is not allowed, then you will get banned, possibly from all of Reddit.
You tell me, you sent me away.
I think data protection, retention, access, rectification and deletion laws are going to hit anyone hosting an instance. The EU is also in the process of introducing a "data migration" law, that is mostly targeted at "large" social media, but we'll see what ends up getting approved.
I'm not a compliance expert, but what I know about these laws makes me fear setting up an instance just to get hit by whatever fines.
I know how to program, I also know how to wonder how many instances are running off the docker-compose with publicly exposed postgres... that would make import/export really easy, wouldn't it? ๐
Anyway, would you say this isn't the right place to discuss this stuff?
That's kind of wrong though, isn't it? What about stuff like GDPR data exports? Users should be able to export their data, then import it into another instance, effectively migrating instances.
Their system has "triggered successfully", great news everyone! ๐๐
/s