A webcam with the lens cap on works for that kind of thing. (I'd link to lavarnd.org, but it is mysteriously down...)
Linux Mint, if you want a distribution geared towards the same kind of modernity and ease of use that made Ubuntu so popular to begin with.
Or Debian, if you want to pick a distribution whose organization is least likely to fuck it up or sell out.
Are all of those actually necessary, or do they overlap enough that one or more is redundant?
Just add a Bluetooth keyboard [to an iPad] and you have rebuilt the laptop...
I actually have Iceweasel and Chromium configured to run that way on an old laptop with 256MB of RAM. It's still slow anyway.
Links2, by the way, is entirely incapable of rendering modern websites in a readable way.
So are you saying that new functionality breaks the extension API every time? 'Cause if it doesn't, then even new functionality can be a minor version number.
I will point the insurance companies who offer annuities -- which basically is the same thing as a pension. While insurance companies blew up the policies did not. You have a choice -- you can either make high contributions to a low risk plan or one can make low contributions to a high risk plan.
...Or one can make stupid contributions to a high-fee plan (which is what most, if not all, annuities are).
Yes, Qubes is useful. I was pointing out how to accomplish a fraction of the security of said OS with existing tools.
Oh, okay. I was under the impression that Qubes was "existing" (I've seen people on Slashdot claim to use it, but haven't tried it myself). It does have a version labeled "release" on its download page, so I assume it's at least somewhat usable...
Clearly you underestimate the significance of being able to quickly refactor code. Of course, if you always write 100% correct code flawlessly the first time, this may not ever be an issue for you.
That's not a sufficient condition. Your code has to be 100% correct and your design has to be 100% correct and your requirements can't ever change and your (target and development) environment can't ever change.
There is always the next step up -- a VM.... Long term, this complete sandboxing functionality should be in the OS.
Did you read my post? Running everything in (separate) VMs is exactly the point of Qubes OS, with the advantage (compared to Windows or VMWare) of being Free Software.
I don't see how. Nothing is retained in Incognito mode. Every time you launch it you have a totally new profile.
You make the implicit assumption that you're relaunching often, which may not always be the case (especially if you're using it all the time, instead of only occasionally).
The only way they could build said "shadow profile" is based on IP. But they can't tie the IP to a given twitter user name if you never sign into twitter on that device.
- Point 1: The Twitter user name is probably the least important piece of information they're trying to connect.
- Point 2: You only have to slip up once in order for your shadow profile and your named profile to get connected, permanently. It's way too risky.
Although it may be good enough for stopping Twitter, the trouble with Sandboxie is that it still relies on Windows, which cannot be trusted for other reasons. IMO, if you're going to the trouble of sandboxing everything anyway, you might as well just skip straight to Qubes OS.
You can block it in two ways... either a) never sign into twitter in your browser unless in Incognito mode, or b) Block third-party cookies and trackers using Ad Block. I do the latter.
The first method would still allow Twitter to build a "shadow profile." It may not be explicitly linked to your Twitter ID, but it's still just as identifiable. Therefore, only your second suggestion is an actual solution, in my opinion.
Then move to some other country where "liv[ing] in a Mad Max style dystopia" isn't a Constitutional right.