Follow Slashdot stories on Twitter


Forgot your password?

Comment: Post headline is false (Score 1) 49

by saizai (#45535801) Attached to: FEC Will Not Allow Bitcoin Campaign Contributions

The FEC did NOT say that PACs can't accept Bitcoin. They pretty much unanimously agreed during the meeting (audio) that PACs *can* accept Bitcoin, and the Libertarians and some candidates already were and continue to do so.

They just couldn't decide *how* PACs should accept Bitcoin, and CAF (the requester) didn't ask about accounting standards or the like, so they didn't approve the request. FEC decisions are ternary: yes, no, and nil. This is nil, not no.

Full disclosure: my PAC's comments explaining a bunch of problems with the proposal were one of the primary reasons why they didn't rule on it, and we're intending to file a new request in the very near future. (Comments welcome on our draft of a new safe harbor policy.)

+ - Private Address Forwarding proposal to USPS->

Submitted by saizai
saizai writes: I've proposed the USPS adopt Private Address Forwarding, and the USPS' comments are in.

tl;dr proposal: Google Voice for postal mail. The USPS assigns you a unique ID, you tell them where to forward that ID, and they can't disclose who or where it goes it belongs to without court process or your permission. You could get mail that's just addressed to "PAF 13JS-00EG-C, United States", and it'd automagically get routed to you. You can also choose to give UPS, FedEx, etc permission to access the forwarding info if you want.

tl;dr benefits: Getting mail while preserving your privacy; never having to update your address w/ everyone when you move (just w/ the USPS); cheaper & easier than PO boxes.

Take a look & tell them (and me) what you think. :-)

Link to Original Source

Comment: Re:OP here. (Score 1) 525

by saizai (#43328425) Attached to: Fighting TSA Harassment of Disabled Travelers

Context matters.

Disclosing it to the TSA makes me subject to discrimination and retaliation in an official context, and violates 4th amendment rights.

Disclosing it here is me trying to stand up for those rights, so that others don't have to be subjected to the same kind of mistreatment. If people weren't willing to do that, nobody would ever speak up, and everyone would continue to be abused.

Comment: Re:OP here. (Score 1) 525

by saizai (#43325657) Attached to: Fighting TSA Harassment of Disabled Travelers

No doubt it's more complicated. However, turns out there are actually standards for reasonable response times, and they're more like a month. If they don't respond to me, I can get a court to make 'em.

Definitely not my preferred route, and I actually like the contact person I have in their FOIA office, but I'm not interested in being ignored.

Comment: Re:Yawn (Score 2) 525

by saizai (#43324019) Attached to: Fighting TSA Harassment of Disabled Travelers

(OP subject here)

I'm very sorry to hear about your friend. Anomic aphasia is pretty bad; having Wernicke's would be horrifying to me. I can testify that it's frustrating enough just dealing with my mutism.

FWIW, my condition is a production problem, not aphasia. I just can't make my voice work sometimes (couple times a month, lasts a few hours). I can still sign, write, type, etc just fine so long as my arm isn't physically spasming too badly or the like, and I still have full cognition / linguistic ability / etc.

I figure that as neurological disorders go, I'm pretty lucky. There are people who have it way worse than me, and your friend's one of 'em.


+ - Apache Warns Web Server Admins Of DoS Attack Tool->

Submitted by
CWmike writes: "Developers of the Apache open-source project warned users of the Web server software on Wednesday that a denial-of-service (DoS) tool is circulating that exploits a bug in the program. 'Apache Killer' showed up last Friday in a post to the 'Full Disclosure' security mailing list. The Apache project said it would release a fix for Apache 2.0 and 2.2 in the next 48 hours. All versions in the 1.3 and 2.0 lines are said to be vulnerable to attack. The group no longer supports the older Apache 1.3. 'The attack can be done remotely and with a modest number of requests can cause very significant memory and CPU usage on the server,' Apache said in an advisory. The bug is not new. Michal Zalewski, a security engineer who works for Google, pointed out that he had brought up the DoS exploitability of Apache more than four-and-a-half years ago. In lieu of a fix, Apache offered steps administrators can take to defend their Web servers until a patch is available."
Link to Original Source

+ - NASA Creating Laser Communication System For Mars->

Submitted by techtribune
techtribune writes: NASA is in the process of developing a new technology under project Laser Communications Relay Demonstration or LCRD which will allow them to provide faster means of communications from Mars. The Mars Reconnaissance Orbiter (MRO) currently can only send at speeds of around 6 Mbps or about like a DSL modem here on Earth. At this rate, it can take upwards to 90 minutes to transmit a single high resolution image to Earth from Mars. With the MRO outfitted with the new technology it would be able to transmit the same high resolution image back to Earth at over 100 Mbps and only taking about 5 minutes to do so.
Link to Original Source

+ - Can Google Save Us From Crappy Internet->

Submitted by
CoveredTrax writes: "As part of the beta test of their new gigabit fiber network, Google has provided Stanford University with mouthwateringly high-speed Internet. Since the program was announced, the service, which is now being provided free to students and faculty in the Palo Alto area, has got a lot of people to asking (sometimes begging) that their city be next on Google's list for communication salvation. But can Google save us all from inferior web access? And more importantly, is it a good idea to let them?"
Link to Original Source

If I have not seen so far it is because I stood in giant's footsteps.