see subject

So, you start to watch a movie or TV show online. After 15 minutes, Comcast throttles you causing lower quality, stuttering, and/or buffering delays. They inflict this punishment even if they otherwise have plenty of bandwidth available.

Comcast wins in 2 ways: (1) they save a bunch of bandwidth by killing this emerging use and (2) they kill the threat this emerging use represents to their cable TV business.

Your options are (1) ditch Comcast and go with DSL if possible (noticeably - DSL rarely has the ongoing malarkey associated with cable ISPs) or (2) resort to Bit Torrents where it may not be streaming, but it is no cost, commercial free and immune to this particular harassment (Comcast will eventually "get you" with caps).

I don't see any good solution for VAserv or their users.

Even without the death of the lead HyperVM developer the flaws could not be remedied quickly. There are apparently a lot of flaws and the time needed to fix and test each one will push out a security update for weeks if not months.

On the other hand, VAserv can not simply change to something else. Their infrastructure, experience, and services are all dependent on HyperVM. To rollout something else would take at least 6 months to get right.

Simply bringing everything back as best they can only puts them where they were before the attack - obviously vulnerable.

SCO proposal: split software business from litigation business.

BUT, doesn't the software side now owe Novell $2,547,817 as of July in unpaid royalties? Would not a suitor of the software business have to assume that liability (and any continuing appeals of that award)?