Re: DNS only / No just porn!
There will be DNS made available such that it avoids the filters. Though I won't be providing such myself, I guarantee that it'll happen.
140 publicly visible posts • joined 15 Jan 2013
“Phone state and identity” is a very good example of one which needs to be split up. Knowing when a phone call is active is one thing; reading the phone nos. and device IDs is entirely separate and usually completely unnecessary.
Without checking further, I'm quite sure that there are others which should be similarly split.
Interesting re. downvoting. You also comment on exactly why you've downvoted…?
There are some where I've just kept the old version around. Reasons vary, but generally centre around “it's useful”, “the alternatives don't do what I want” and “the alternatives may be better, but they want even more access”.
Similarly connection speeds. These are dependent to some extent on the modem (again, buy a different one and you may see some difference) but mostly on the line itself and, when it goes bad, on the Openreach part of BT's schizophrenia – and quite possibly on them being hit over the head with a blunt ISP (assuming that their support people are competent).
I've just had a look at CyanogenMod – they pulled the fix in just yesterday. Here's the commit for the 10.2 branch.
I fully expect that they're not the only ones to have pulled it in.
See those two holes a little way to the left of the HDMI socket (towards the power socket)? You can solder in a couple of pins there then attach a standard PC reset button. Press it and, yes, one reset Pi.
(Unfortunately, older models don't have these two holes. No reset buttons for them…)
Regarding standards: http://xkcd.com/927/
Regarding DRM: well, if it prevents me watching content to which I should legitimately have access, like others who've posted here, I see no issue with using workarounds. But I do agree that if it's going to be around anyway, we do need to aim for least-worst.
Well… every story for which they actually have all of the audio and either video or replacement animation. Otherwise they'll have to make use of photographs taken during filming…
As for BBC4, good luck with watching it during the afternoon and not seeing either “programmes start at 7pm” or CBeebies…
Indeed. “While stocks last” and “subject to availability” are Useful Phrases for them to use.
That said, charging the difference in price between the usual price of the one which was on offer and what's actually (now) available would not be entirely unreasonable (although it might not fit in with trying to offload old stock, if that's what they were doing). I would still expect some (quite reasonably) not to take them up on that, though.
Again, the confusion over who got shouted at and who's complaining about it.
http://marc.info/?l=linux-kernel&m=137375525307177&w=2
Kees Cook wrote the patch in question and submitted it via Thomas Gleixner (who is the maintainer for the part of the kernel affected by the patch).
Thomas Gleixner did something like not properly test it or assume that it would be fine (presumably based on the past record of the submitter). He forwarded it, via a git pull request, to Linus.
Linus saw it, found a problem, and went into full technical flame mode.
Sarah Sharp saw it and evidently decided that it's one too many or a step too far or something like that. Result: complaint. Much coverage, click-bait and discussion follows.
Except that he isn't necessarily the one who committed the changes: they may have arrived via one or more git repositories (even if also posted to lkml). Also, commits tend to have at least one sign-off by various system or subsystem maintainers, and they should be checking patches and commits too. It works, but things will slip through sometimes.
(Linus is known to have learned the hard way about last-minute what-could-possibly-go-wrong changes…)
The changelog in iceweasel 21.0-1 (Debian experimental) contains this:
* browser/confvars.sh: Disable Firefox Health Report.
about:support works; it's just the calling-home bit that's disabled. (Crash reporting was disabled in 2008 and remains disabled; rightly so, since Iceweasel problems should be reported via the Debian BTS.)
It may be too early to make the claim that, with metadata removed, the work is as good as orphan – but it is definitely not too early to make people aware that that could happen.
However, I suspect that this aspect of the legislation under discussion is ‘merely’ to make common practice legal…
Subnetting using /48 isn't to do with MAC addresses. Subnetting using /64, however, is. And I recall reading something saying that the preferred allocation is now /56. (I have a /48, but I've yet to need more than a /60. Well, two /64s, really. I could get away with one but I need a publicly-routeable address on the external network interface and I don't have any sort of IPv6 address translation going on, not that anybody should need that.)
Why not /80? But then you couldn't have local addresses which don't contain something which could be a MAC address…