You only need to block the "ooyala.com" domain through NoScript.
I allow scripts in general, but specifically block domains. That helps to stop breakage.

My turn to say "huh?"

The post I replied to was talking about SystemD listening on network ports. In that context, socket activation _is_ everything. Any bug in the network listening code of SystemD cannot be triggered, if the software ain't listening in the first place.

Honestly, kids these days. I blame the music they listen to. Turns the brain to mush.

Actually, it's pretty simple to stop SystemD from listening on network ports. It's called "socket activation". Look it up. It's pretty neat. All you need to do is stop the specific socket service, and then edit the appropriate socket file.

You'll also be interested to know that the Debian install of SystemD doesn't use socket activation by default. Not yet, anyway.

As for systemd security auditing, from what I've heard, the people at Redhat run the source code through various tools designed to pick out bugs. Also, I've read of at least one person doing an independent audit of the code. I presume there would be many more than that. So, as far as security testing is concerned, it's far from having nothing done.

There's always a workaround. Even for SystemD.

I take it back. Deleting the video element didn't stop the download, as I just realised when I restarted my browser.

Adding ooyala.com as an untrusted source in NoScript worked fine.

To stop it, I had to use Firebug to select the video element, and dynamically delete it off the page.
Otherwise, it was sucking up my bandwidth pre-downloading the video. Definitely annoying.

I could write a Greasemonkey script to automatically stop this in the future. We'll see how often it happens.

You get a kernel panic, once a month, on Debian Testing?! That's _very_ unusual. I've run Testing on a dozen or so different systems, for over a decade, and have never had a kernel panic. Not once.

Are you using the Debian sourced kernel, or compiling your own? Compiling any third party drivers into it?

Anyway, whatever works for you. If FreeBSD is stable for you, and does everything you need, then go for it!

Feels the same with me and housework. I guess I can sympathise with him.

Spoken like a true anonymous coward. I certainly wouldn't want to sign my id alongside that sentiment and mistruth.

You condemn humanity as a species that hates others, yet you yourself display a misanthropic attitude.

I think it's your attitude that colours your perception. Yes, there are humans that kill others, but the vast majority do not. There are cultures that rate sport or musical ability more important than general learning. Then there are many that do not. Humanity is many many things. Focusing on one facet does not reflect the whole.

If an advanced civilization stumbled across us, I think they'd be fascinated by the variety and complexity of the life on this planet. They'd certainly study us. In fact, they may just be doing so now.

Gosh, who woulda thought that Debian Unstable is not stable.

If you don't want to go stable, I suggest you use Debian Testing, which, according to the bug report comments, was not affected.

I've always found it curious that people hit out with the words "fuck you".

It's like saying "You are completely and utterly wrong, and I believe I should have sex with you".

Well, I suppose it does match the philosophy of making love, not war.

Want to encourage the creation of creative works?

It's well known that creativity flourishes with experienced adversity. The irony of the copyright system is that it's actually discouraging this creative seed. Artists are way too comfortable, living off royalties, to knuckle down and start producing stuff.

I say we cut copyright to a bare minimum. A year at max. That'll get those lazy artists off their collective arses, and provide plenty of encouragement to create something at least once per year.

Remember kids, nothing speeds productivity like poverty.

Yeah, like I'm going to click on that link you posted! Can't fool me.

You may have an out of date version of systemd. The "noauto" option works fine for me.

There is Choice. Users can install the systemd-shim package, if they want to use other packages that are dependent on systemd.

Haven't tried it myself, but from all reports, seems to work pretty well.