In my view, the fact that VI uses the wrong home keys (or at least, different home keys than all keyboard manufacturers and the rest of the world) is *bad*. It is a relic of ancient 1970s terminals that would better be changed.
The "natural typing position" should be JKL;, not HJKL. That's why all keyboards have a tactile hint on the F and J keys. This is even more relevant for a programmer, who uses lots of symbol keys from the right part of the keyboard.
I'm a mathematician. I am a "creator", paid by your taxes to produced good research ideas that are later put on arXiv.org and on my website for everyone to download. This system seems to work well, at least in our field. Just sayin'...
I don't see why any of this wouldn't be possible with text logs. Yes, you can write GUIs that parse text log files. Yes, you can write an utility that does all the grepping and sorting for you. Yes, you can filter out logs from the previous boot. I don't think the performance loss would be noticeable.
So your arguments in favor of binary log files seem quite moot.
So, just curious to know. The previous sync version had client-side encryption, i.e., Mozilla did not know what data you upload on their servers. In order to do authentication with a Mozilla account, I presume this has to be changed and now the Mozilla people have full access to an unencrypted version of your bookmarks/passwords etc.
U.S. keyboard, of course, sucks for writing in German.
Suggestion: I have successfully switched to the US-international-altgr layout, which is essentially an US layout with lots of extra chords for typing international characters. With that I can comfortably program and type in English, German and Italian without horrible efforts, both on Windows and Linux.
GrüÃYe! (no, it's not me hitting the wrong keys, it's the slashdot Unicode support).
I fail to see how it's relevant. My point is that FDE does not come with a "forgotten password? Nullo problemo, tell me your mother's maiden name" function.
The main reasons for pulling the change logs was the fear of putting the software in a bad light and risking ridicule, especially from the competition.
We should call this practice stability through oscurity.
Certificate forgery? Not even close to being that sophisticate. In the mailing list messages linked in TFA, it says that he put on a spoof captive-portal authentication page in pure HTTP (instead of the original HTTPS one).
Slashdot Mirror
In my view, the fact that VI uses the wrong home keys (or at least, different home keys than all keyboard manufacturers and the rest of the world) is *bad*. It is a relic of ancient 1970s terminals that would better be changed.
You keep using that word. Notepad is "simple". This is not. Powerful, yes. Simple, no.
The "natural typing position" should be JKL;, not HJKL. That's why all keyboards have a tactile hint on the F and J keys. This is even more relevant for a programmer, who uses lots of symbol keys from the right part of the keyboard.
Clearly, it should've been _GNU_LINUX_SOURCE.
I'm a mathematician. I am a "creator", paid by your taxes to produced good research ideas that are later put on arXiv.org and on my website for everyone to download. This system seems to work well, at least in our field. Just sayin'...
*points at summary*
Oh, if only a large company like, say, Google would adopt the drivers and support their development...
Ten points to Gryffindor!
Incentive, like, for instance, a boatload of luxury cars waiting to be stolen?
Please? Can we have it in major distros? Makes a lot of sense from a user's perspective.
So, this raises the question: is there a meta-cheat that cracks the DRM?
Angela Merkel: "Screw Obama. I'm going to build my own internet, with blackjack and hookers. And privacy."
I don't see why any of this wouldn't be possible with text logs. Yes, you can write GUIs that parse text log files. Yes, you can write an utility that does all the grepping and sorting for you. Yes, you can filter out logs from the previous boot. I don't think the performance loss would be noticeable.
So your arguments in favor of binary log files seem quite moot.
So, just curious to know. The previous sync version had client-side encryption, i.e., Mozilla did not know what data you upload on their servers. In order to do authentication with a Mozilla account, I presume this has to be changed and now the Mozilla people have full access to an unencrypted version of your bookmarks/passwords etc.
Is this correct? That seems a worrisome change.
Now, a very good question for a non-Italian to ask would be "why on hell do more than half of the tickets go unpaid?"
Suggestion: I have successfully switched to the US-international-altgr layout, which is essentially an US layout with lots of extra chords for typing international characters. With that I can comfortably program and type in English, German and Italian without horrible efforts, both on Windows and Linux.
GrüÃYe! (no, it's not me hitting the wrong keys, it's the slashdot Unicode support).
I fail to see how it's relevant. My point is that FDE does not come with a "forgotten password? Nullo problemo, tell me your mother's maiden name" function.
Especially considering that the average lawyer uses Windows XP with no antivirus and a dozen toolbars installed...
Full disk encryption says hi.
Sure, it will come in a box, as did the previous stable version.
We should call this practice stability through oscurity.
Certificate forgery? Not even close to being that sophisticate. In the mailing list messages linked in TFA, it says that he put on a spoof captive-portal authentication page in pure HTTP (instead of the original HTTPS one).
When you are a postdoc and do a postdoc at the same time, it's called the two-body problem.
(Jokes aside, why is 50% of the summary devoted to this nitpicky grammatical distinction?)
I was thinking exactly to this. Or Ubuntu dash online shopping search, for that matter.
Yup. Some workarounds needed though. There is a practical 99-pages forum thread on that.