And all of that existed with upstart, daemontools, many worked with inetd, and in general many other systems solved the same problem. Systemd's danger is its insistence on doing _everything_, including replacing logging, DHCP, NTP, and numerous other already working and well understood components. Its proponents have made clear that they intend to replace all of /etc.

Discussing systemd as if it were only an init script replacement is missing out on why people are upset about it.

BSD got its automatic live self-defragmenting code from OS X. Then there's libdispatch/GCD, LLVM, and so on.

Yeah. I was there at the time, writing patches for the Minix kernel... Linus specifically wanted support for 386 protected memory and virtual memory. AST wouldn't do it, because it would mean Minix wouldn't run on 68000-based systems like my Atari ST. So Linus went away and hacked together his own 386-only replacement kernel over a weekend.

First time in a long while I've seen intelligent commentary about testes on the internet. I have to admit that it's well written, though the thought of a "bell curve of average testicular temperature" did make me giggle internally a bit. I suppose at some time a group of scientists had to have mapped that out, but I wonder what the sample diversity was.Google actually comes with up an an interesting article regarding the curve of temperature in rat scrotums (wider ranging than humans by quite a lot, but then rats are fairly large in that area) and the thermal receptors therein

they have no expectation to value my privacy

That's not true. They do care about privacy, which is why they have that tracking antifeature that I mentioned before. You can't discount that! The only difference between what they're doing and what you apparently want them to be doing is that they don't assume that just because something is using an unnecessary permission it means it's violating the user's privacy. You can argue that maybe they're wrong for failing to assume that, but you have to acknowledge that there's a difference between F-Droid not being perfect vs. F-Droid not giving a shit.

Have you ever tried bringing this issue up with the F-Droid folks? If you haven't, I wouldn't be surprised if they're more receptive to it than you think, especially since you have patches to submit instead of just an idea.

No, it just means that you are not actually doing anything of any importance or interest.

'The page "Mircowaves" does not exist. You can ask for it to be created, but consider checking the search results below to see whether the topic is already covered.'

So I'm guessing you still meant microwaves, which - in the case of the oven - are emitting radiation sufficient to cook food within a rather short'ish period of time. I suppose there's not enough heat in a short time to cook ones testes but I'd rather not be standing there when the door opens.

What I am getting from the videos is that this test was a success but that there was indeed an engine failure and the system recovered from it successfully by throttling off the opposing engine. There was less Delta-V than expected, max altitude was lower than expected, downrange was lower than expected, and that tumble after trunk jettison and during drogue deploy looked like it would have been uncomfortable for crew.

This is the second time that SpaceX has had an engine failure and recovered from it. They get points for not killing the theoretical crew either time. There will be work to do. It's to be expected, this is rocket science.

It sounds to me like the launch engineers were rattled by the short downrange and the launch director had to rein them in.

They flag git apps for having github integration with giant "promotes non-free services" ads, even if there is no actual promotion, just API support, and yet they have versions of things where the effort has been made to compile without google libs, but that still ask for device ID. For example, their version f the google sky map app, they go to the trouble to compile with certain libraries replaced, but they leave in the part where it asks for the device ID, etc. It is a totally passive app with no legit use at all for device ID. No warnings.

I've just done a search in F-Droid for 'git' and looked through all the results. I found the following:

• Github, the "official Github Android App" has a red warning that says "This app promotes non-free network services."
• OctoDroid, described as a "GitHub Client" (not a "git client," a "GitHub client") which says that it "supports all the basic github.com features" does NOT have a red warning.

Having never used either app I don't know how fair F-droid's choice to display the warning in one case but not the other actually was, but it at least seems plausible to me that the "official" app would be more likely to "promote" the service than other apps.

As for Sky Map, if the program is indeed using the Device Id for some nefarious purpose, I'd expect a red warning saying "this app tracks and reports your activity" (or whatever message was appropriate). In the absence of such a message, I would assume that either the app isn't actually doing anything (and the F-droid people think it's sufficient to let the Android permissions dialog handle informing the user of a permission that doesn't matter) or the lack of warning is an oversight on F-droid's part (I mean, clearly, if F-droid has an tracking anti-feature, failing to mark an app that does tracking with it is certainly a bug).

I would also say that even if we don't *know* that the app is doing something nefarious, the existence of unnecessary permissions itself merits a red warning message (or at least a yellow caution message), and would like to see such a policy/feature implemented. However, I don't think the lack of such a feature constitutes "false claims" on the F-Droid maintainers' part.

The bottom line is that if your allegations about F-droid are true, then you're justified in being upset, but I'm not sure those issues deserve to be ascribed to malice when there's still enough reasonable doubt (IMO) to ascribe them to accident.

Enough radiation to be measured on the outside equipment? While I'm sure the equipment is - by necessity - quite sensitive, that still doesn't sound particularly healthy for anyone in front of the microwave when it was opened.

The guy that works in the local corner store also has a non-zero probability of getting shot when he goes to work in the morning. Yes, it's terrible when bad things happen to cops, but it doesn't mean that we should ignore that a not insignificant number of bad things are committed by cops. Keep in mind that 1.4% is just reported incidents, and that there are probably plenty of "better keep quiet or you'll get a worse beating" situations out there.

Don't let them give you a set-top box. Make them give you a CableCard instead, and take a stand for the spirit of "any lawful device" (which should have been applied to cable companies, but hasn't).

Also, they'll tell you the box is "free," but if you swap it for a CableCard they should give you a discount.

I'm honestly not even sure where the cable box is; I asked them not to send me one but they did anyway.

Send it back and demand a CableCard. Not only is it a good "fuck you" to those who hate the idea of people having the audacity to hook up their own equipment, it should also get you a small discount (because contrary to what they tell you, that first cable box is only "free" in the sense that the rental fee is built into the advertized price).

Which opens you up to all kinds of high circumstantial evidence prosecution. Evidence that you may have been involved in a crime coupled with a psychotic behavior in which you put your computer data at severe risk to handle an unexpected seizure?

How do they prove removing the USB drive caused the shutdown? The script is on the computer and thus unvailable with all other data. The USB drive itself can contain any data, giving you a perfectly nonpsychotic reason to keep it attached to your wrist.

They *still* haven't implemented compressed downloads. During the Alpha, that was understandable, but come on now.