A point people seem to be over looking is that the developers of systemd are employees of red HAT who in turn is an employee of the U.S. government

the non systemd distros are slackware
none of the other distros on this forum are non systemd

they can't outlaw linux IBM's main frames,servers and supercomputers are running a fork of slackware matter of fact all of the 500 fastest computers on earth run linux
with all of the bugs and problems with systemd I doubt any of them has systemd on them

about android that comes form google I doubt that google would refuse do what ever include what ever the U.S. government want's
hell there may already be a U.S. government package of malware built in to android

systemd is still open-source though, so anyone can make a fork if they're unhappy with what the default one does. In fact they wouldn't even need to do so manually per update: Just setup a script to fetch the latest systemd source code, automatically remove the intrusive module, compile, and publish to your custom software repository!

Even if this wasn't possible, distros could either create a systemd alternative or stop using it like slackware, if and when systemd did anything bad.

it already has it has bricked 000s of motherboards
and cleaned out root on 0,000s of linux installs

YES systemd is OSS but it's huge way too big to audit it's
it's in control of the whole
pre-alpha quality software each bug is a potential back door or worse
it's tightly integrated there are no modules to it that's why it can't be debugged AND it will never be debugged
it is now and will always be pre-alpha quality
the only debugging it gets is to make it compile
(maybe the built in cyber weapons get tested )

if you, rob.rice, really want to convince us of something, then please take the time to make your argument.

i'm not saying you are wrong, but the way you've written it now, it's just angry and unsubstantiated rant, the sort of thing one might hear in a pub, after a particularly hard week at work, after the third beer.

"bricked", "cleaned out root", "can't be debugged", "pre-alpha" and esp. "built-in cyber weapons" - can you substantiate these claims?

until you do, i call BS & FUD.

Focus your ire on the post before that, from the original poster, that would be the one which actually asserted that it's the only way to go with the "like it or fork it" troll. systemd can't just simply be forked because a) its the wrong approach to the problem it was marketed for, that was as an init system, which it clearly not, b) it spread not on technical merit but by namecalling and other logical fallacies so the code is a problem even above that c) as everyone can see it is too big and complex and undocumented for auditing or even casual work, requiring not just serious programming skills, but also an excessive time committment. So, in fact, forking a distro (Devuan for example) is the only way to address it at any level and that also requires also excessive amounts of effort and time, both of which grow as systemd gets deeper hooks into strategically infected distros, but unlike systemd, distros are still modular and the work can be divvied up to various skill levels and skill sets.

As to the stage of readiness it's definitelhy pre-alpha. I read almost every other or every third week of new features being planned. You may recall that alpha is the stage long after when the functionally was established and has more or less been added, but there is usually a bit to go before functions are complete.

Now to tie that back the original question about web site filtering, it positions itself as a quasi-kernel between the real kernel and the userspace. So, it is within the realm of possiblity now that it can choke off the I/O as is needed for digital restrictions (DRM) which is the first major prerequisite for serious mandatory web site filtering. Since back in 2012 it has been touted as the whole core of the OS above the kernel. Systemd is working towards the pre-requisites for DRM from the system level and, if allowed to continue, will eventually meet in the middle the prereqisites coming from the direction of the hardware / firmware.