Forgot your password?
typodupeerror

Comment: Re:Bullshit. (Score 1) 180

by swillden (#47961985) Attached to: Secret Service Critics Pounce After White House Breach

I'm gay. I live in Belgium. Our Prime Minister is gay. I saw him in the club Friday night. It doesn't _have_ to be like it is in the US.

Maybe it does, maybe it doesn't, but your example really doesn't have much bearing. The US has 30X the population of Belgium. 40X the GDP, 56X the military personnel and probably 100X the impact on world events -- all of which means there are perhaps four orders of magnitude more people interested in killing the US President than the Belgian Prime Minister (these things scale non-linearly), even when the US isn't actively trying to piss off a lot of people. Which, unfortunately, it has been for several decades now.

Though on second thought, the fact that "Belgium" is the most offensive word in the galaxy (off Earth) may mean that there are more people annoyed at your country than we think. Perhaps Mr. Di Rupo should be more cautious. At the very least, he should keep a towel handy.

Comment: Re:More and serious threats (Score 1) 180

by swillden (#47961913) Attached to: Secret Service Critics Pounce After White House Breach

It's only since the Civil War that the federal government has started to play more of a role than state government in the every day lives of people.

More recent than that. Until the New Deal the federal government was actually smaller than most state governments, and definitely had less impact on most peoples' daily lives.

Comment: Do NOT Talk to the Cops (Score 1) 180

by Tenebrousedge (#47961809) Attached to: Secret Service Critics Pounce After White House Breach

You are required to identify yourself to a police officer who asks (per Hiibel v. Sixth Judicial District Court of Nevada). You are not required to show them identification documents. There is no good reason to do so. Do not do this. Tell them your (real) name. Certain states (not California, mind you) may have state laws requiring you to give the police such information as your address and date of birth; the Supreme Court has not ruled on the legality of these laws. I would probably not comply, but that one is up to you. Do not talk to the police. Do not assist them with any investigation -- you are not required to, and providing false information is an easy crime to get booked for. Do not answer their questions. Do not allow them to search you. There are nice cops who are just doing their job, but the potential downsides are not worth it. "Am I being charged with a crime? Am I free to go?" Those are the only things you should say to the police.

And if you get arrested, remember that, per the reprehensible miscarriage of justice in Berghuis v. Thompkins, you must explicitly invoke your right to silence in order for the police to stop questioning you. Police interrogations are so effective that perfectly innocent people have been known to sign confessions after extended interrogation sessions. Tell them you are using your right to silence, and that you will not answer questions without an attorney present, and do not say anything more until that attorney shows up.

Know your rights, and insist upon them. Do not cooperate with the police beyond strict necessity.

Comment: Re:This is supposed to be the *WAY* they do their (Score 1) 349

And you can always explain away any attacks of conscience by claiming you simply want everyone to be personally responsible for themselves, even as your policies take away the means to do so from the majority of people.

I wish I'd written that.

It's sort of like claiming your view represents the majority while trying to disenfranchise hundreds of thousands of legal voters.

http://www.bradblog.com/?p=852...

Comment: Reactive is an extension of event driven (Score 1) 82

by benjymouse (#47961563) Attached to: 'Reactive' Development Turns 2.0

As far as I can tell, this person (or persons) has discovered something that has a name already: Event-driven programming. It's been around for a very long time. It has many of the benefits of naive multi-threaded coding without the warts. But it introduces warts of its own, with event orderings being the big one.

What Erik Meijer discovered was that an event can be viewed as a sequence. Each occurrence of the event is an "item" of the sequence. What's why he wrote an article called "Your mouse is a database": The mouse is a sequence of multiple event types such as moves, buttons etc.

Once you start to view (and represent) events as "push" sequences interesting things start to happen: Suddenly you can *compose* events in the same way you compose collections/sequences.

Erik Meijer wrote the Active Extensions for .NET which does exactly that. Using LINQ you can transform, aggregate, group, partition, project/map, filter etc events.

Consider, for instance, stock market ticker values: Clearly you can see those as events: When a deal/offer it is an event. Multiple events is a stream/sequence. Now imagine you want to know each time a symbol has "peaked" - i.e. each time 3 consecutive values for any symbol has the maximum as the middle value. With Reactive Extensions and LINQ you would write:


var peaks = stockQuotes.GroupBy(sq => sq.Symbol).SelectMany(g => g.Buffer(3, 1).Where(IsPeak));

where IsPeak is defined as:

bool IsPeak(IList<Quote> b) {
        b[0].Rate < b[1].Rate && b[1].Rate > b[2].Rate;
}

Explanation:
1. stockQuotes is the IObservable stream of quotes.
2. GroupBy created a new stream of multiple streams. Each time a new symbol is encountered, a new group will be added (appear in the stream); if the symbol has already been encountered the quote is added to the end of the stream for the symbol.
3. Buffer creates a "sliding" buffers (increments of 1), each with 3 items.
4. Where filters the IObservable so that only "peaks" are let through.
5. SelectMany "flattens" multiple streams into a single stream again, i.e. creates a single stream of quotes regardless of their symbol (group)

Now, this is an IObservable stream with no subscribers (observers) yet. This also means that there is no subscription at stockQuotes. But as soon as you register a subscription like this:


                  peaks.Subscribe(Peaked)

It starts to invoke the Peaked method with peaks consisting of lists with exactly 3 items each. And this will go on and one.

Now imagine how you would write something like that using events and event handlers? It will probably take 10 times more code and be less readable than the above. (Yes, I know that it is not entirely straightforward if you are not used to RX and LINQ).

Comment: How much? (Score 1) 53

by fyngyrz (#47961545) Attached to: Trouble In Branson-Land, As Would-Be Space Tourists Get Antsy Over Delays

For a flight that doesn't reach orbit and stay there with the environment in 0G for at least a few orbits, I wouldn't pay anything. Heck, I won't pay a commercial airline to fly because the ratio of inconvenience to convenience+enjoyment is too high between the (id|patr)iot act's enforced paranoia and the seating designed by one-legged, one-armed engineers. Now an oceangoing cruise liner, that's something else again. I loves me a nice cruise. It's even worth going first class, which it definitely isn't in a commercial airliner.

However, for a flight that *does* go to orbit and stays a few turns, and doesn't require a spacesuit, and for which I could have a very private cubby with a view for two for the orbital duration, I might part with as much as five thousand for two seats, just for those few hours. They'd have to let me take my camera, though.

Which means I'm not going to get to go. :) Unless they build a space elevator or several in my lifetime. And apparently the materials science there is either too difficult, or nearly so. Oh well. There's always Firefly reruns.

+ - New revokable identity-based encryption scheme proposed->

Submitted by jd
jd (1658) writes "Identity-based public key encryption works on the idea of using something well-known (like an e-mail address) as the public key and having a private key generator do some wibbly-wobbly timey-wimey stuff to generate a secure private key out if it. A private key I can understand, secure is another matter.

In fact, the paper notes that security has been a big hastle in IBE-type encryption, as has revocation of keys. The authors claim, however, that they have accomplished both. Which implies the public key can't be an arbitrary string like an e-mail, since presumably you would still want messages going to said e-mail address, otherwise why bother revoking when you could just change address?

Anyways, this is not the only cool new crypto concept in town, but it is certainly one of the most intriguing as it would be a very simple platform for building mostly-transparent encryption into typical consumer apps. If it works as advertised.

I present it to Slashdot readers, to engender discussion on the method, RIBE in general and whether (in light of what's known) default strong encryption for everything is something users should just get whether they like it or not."

Link to Original Source

Comment: Re:Some details about the 3D printer (Score 1) 102

by CrimsonAvenger (#47960431) Attached to: SpaceX Launches Supplies to ISS, Including Its First 3D Printer

That's why you carry spare parts with you. And why you "design for maintenance". And why you do extensive development and testing beforehand to figure out what parts are most likely to break. And design parts to be reliable. And reinforce the parts where you can. And...

And after you do all of those things, sometimes something breaks that you don't have a spare for. And when the nearest replacement part is nine months away, you're screwed.

Being able to make spare parts is a GOOD thing. And the fewer things you have to carry along to make spare parts with, the better.

Comment: Re:kill -1 (Score 2) 313

by squiggleslash (#47960039) Attached to: Fork of Systemd Leads To Lightweight Uselessd

Must admit that's news to me. Kinda fed up of the subtle changes to shell commands we've seen over the last few years especially as this one conflicts with the kill -{SIGNAL} syntax we're used to.

Either way, this sounds like a non-issue. (1) if we're routinely trying to determine how to kill EVERY CORE PROCESS ON THE SYSTEM then we have bigger fish to fry than whether init/systemd is capable of working with that.

(2) It sound scriptable to me, assuming systemd itself isn't capable of doing it. /proc should give you all the information you need.

I worry that this is the kind of concern holding back adoption of systemd. Good reasons I understand. Bad ones, that seek to blame systemd for major system problems that exist under init too, are bad.

+ - Mark Zuckerberg Throws Pal Joe Green Under the Tech Immigration Bus

Submitted by theodp
theodp (442580) writes "A month after he argued that Executive Action by President Obama on tech immigration was needed lest his billionaire bosses at Mark Zuckerberg's FWD.us PAC have to hire 'just sort of OK' U.S. workers, Re/code reports that Joe Green — Zuckerberg's close friend and college roommate — has been pushed out of his role as President of FWD.us for failing to Git-R-Done on an issue critical to the tech community. "Today, we wanted to share an important change with you," begins 'Leadership Change', the announcement from the FWD.us Board that Todd Schulte is the new Green. So what sold FWD.us on Schulte? "His [Schulte's] prior experience as Chief-of-Staff at Priorities USA, the Super PAC supporting President Obama's re-election," assured Zuckerberg in a letter to FWD.us contributors, "will ensure FWD.us continues its momentum for reform." Facebook, reported the Washington Post in 2013, became legally "dependent" on H-1B visas and subject to stricter regulations shortly before Zuckerberg launched FWD.us with Green at the helm."

Professional wrestling: ballet for the common man.

Working...