Twitter measures tweets in characters, not in bytes. Japanese is not 2x denser than English in bytes, but it's 2x denser than English in characters, and that's what Twitter cares about.

Try writing a few tweets (or tweet-sized snippets) in English and in Japanese sometime, see for yourself.

140 characters isn't enough ... in English. You should see the novels that Japanese people post on Twitter. Japanese is about 2x denser per character than English, so you can fit in a lot more stuff. I was amazed when I was able to compose an elaborate explanation for someone in Japanese and it still fit in one tweet (I'm learning the language).

SDKs are useful to investigate and develop homebrew exploits (they provide information on the system architecture), but they are not useful for actually developing homebrew unless you want to end up with a situation like the Xbox 1 (the original) where all homebrew (except for Linux) was basically illegal because compiling it meant using the SDK and the resulting binaries were not legally redistributable. As a counterexample, the Wii has a fully open source homebrew SDK (though some bits have a questionable history and are arguably non-cleanroom reverse-engineered SDK code from games, but that's a much finer point than outright using the official SDK).

Given what I've heard of the Xbox One security architecture, it's going to be a tough nut to crack, SDK or not.

It was not possible with consolekit, great that there was progress with consolekit2.

There is no way to refute conspiration theorists. It is a self-contained believe system, that functions outside of the real world. I won't bother to argue with that.

What got vdev/udev to do with running xorg as non-root? Yes, that does initial setup of device nodes, but all the rest is handled by systemd-logind.

You are brandishing the wing stick:-)

That person is bitching that everybody and their dog start to depends on systemd. That is your evidence right there.

Of course you have to do the dating assumption that devs do whatever they like... It kind of crumples if you assume that there are systemd hitmen traveling the world, forcing developers to depend on systemd.

That consultation mongering in that link is indeed laughable.

The absense of CVEs can mean the absense of people looking, and with the x11 being a quagmire of protocols, often contradicting each other as new stuff gets added over the decades, there are very few people that can even understand the code. One guy started to look last a while back and he is finding appalling bugs, check the recent CVEs and his presentation at last years chaos communication congress (30C3).

Making this swamp a bit dryer by not having it have root priviledgea is something that was work in progress ever since xfree started to run on Linux.

Now you come here and tell me that this sour spot for the last thirty years is better to keep around than having a much smaller, much cleaner codebase where almost all parts run in their own security context -- usually with privileges way lower than those you have as a user. Right.

Mid term devuan has just one chance: Make it easy for developers to provide solutions that work with multiple int systems. Systemd does bring quite a few improvements for developers. That is the reason why systemd becomes entrenched: Developers like it and start to depend on it since it makes their live easier.

If devuan wants to keep a manageable distribution they need to make it similarly easy to tackle issues in a convenient and reliable way when using multiple init systems. If they manage that, then I am pretty sure developers will support their interfaces in favor of systemd. No developer wants needless ties.

Unfortunately it is much harder to provide generic solutions than it is to provide a specific one. So devuan is in a very challenging position to make things easier for developers.

Is they blow this, then they will have more and more software that depends on systemd-only interfaces and more and more work to remove those dependencies.

This fan fic already has a few episodes in the can. And it's so good, that even the most horrible episode in the bunch (the one with the Orion slavegirl), is simultaneously unwatchable, and completely watchable on its merits as a very faithful recreation of a typically bad episode from the original series. These guys have got it down pat. They know exactly how to faithfully remake an honest homage to an average bad episode from the original series. And it's certainly doesn't hurt that the episode's guest star was none other than Lou "The Incredible Hulk" Ferrigno. As an Orion slave trader. In full body green makeup!

It's eery watching Chris Doohan in this series. The guy is a spitting image of his old man. Looks like a younger Scotty. Close your eyes, and you can't tell it's not Scotty. I thoroughly enjoyed watching the episodes as they came out. They were far more entertaining than either of the two terrible reboots. I refused, on principle, to pay money to watch the crap reboots in the theaters. But if these folks ever manage to crank out a reel, and it makes it down to my local megaplex, I'll be the first in line to buy a ticket.

My favorite ploy is the agencies who stalk me on LinkedIn. When I move to a new contract, they call my old employer to ask if they need any additional help.

I found a very easy solution to this problem, a long time ago: I simply do not provide enough details to precisely identify any of the companies I've worked for in the past, on my publicly visible LinkedIn profile, and I locked it down so that nobody, except me, can see my connections, and try to figure it out. All that anyone sees is my connection count, and nothing more.