Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment a nice gesture, but Swartz's chapter is not good (Score 1) 87

I have great respect for Aaron's accomplishments and the depth of thought he brought to most problems, but his contribution to Open Government isn't his best work. In particular, its nearly-complete dismissal of transparency as a meaningful intervention suffers from a failure to consider likely counterfactuals. Transparency's impact is probably greatest through deterrence. It shifts equilibria. Aaron's view of it -- at least the one expressed in this chapter -- was ploddingly instrumentalist. Virtually any policy is going to be unsatisfying when viewed through that kind of lens.

I'll admit that my opinion on this is shaped by both personal and professional considerations, but I really do think that Aaron got this one wrong. More here, if anyone's interested:

Comment Re:Screw CSS (Score 1) 146

My point is that *in practice* the specifics of the exemptions don't matter. They establish a foothold, and a gray zone of consumer use in which even tools that violate the DMCA are available. Put another way: how many people reading this thread will now be ripping DVDs that weren't before Monday's announcement?

Yes, the law matters, and no, it's not good to break it. But the point is that the DMCA's mechanisms create a situation where consumers aren't prosecuted for circumventing DRM, but rights-holders are still empowered to suppress innovation. It's a strange, muddy situation, and an inappropriate way to run a legal system.

With that said, those who point out that the DMCA is unlikely to change through legislative action are of course correct; the article makes an argument, but it's not a call to action. At this point the courts and increasingly-broad exemptions are the best hope for improving the legal situation created by the DMCA.

Submission + - DMCA Exemptions Don't Matter (

sbma44 writes: The American Prospect has an article up that argues that focus on specific DMCA exemptions is silly — the practical upshot is about zero, and the underlying law remains as rotten as ever.

Submission + - Treasury Dept. Restricts Data with EULA (

Andurin writes: "The U.S. Treasury Department has imposed restrictions on the way Americans (and others) can use and analyze data developed about the Troubled Asset Relief Program. The "terms of use," which are subject to change at any time, require users to cite when writing about the data, and to state that the government doesn't vouch for the authenticity of the data once it's been downloaded. The Sunlight Foundation's policy counsel writes that the terms are similar to an EULA and are inconsistent with the Administration's recently announced Open Government Directive."

Comment Re:newness is not an excuse in this case (Score 1) 207

You might want to reread my post. You're making the same points I did: namely, that the data on the website is poor due to problems with the underlying systems. This is not the fault of the website (though the GCharts mistake is a bit sloppy). However, the same agency is responsible for the site and for collecting the underlying data. It's time for them to correct the more fundamental problems with the system rather than continuing to repackage it.

Comment it wasn't (Score 1) 207

actually, the contractor that maintains is REI Systems, based in Herndon, VA. They're not faultless, but the real problems with the site have to do with the underlying data; unfortunately, REI can't do much about that.

Comment newness is not an excuse in this case (Score 5, Informative) 207

I work at the Sunlight Foundation, where we're pretty familiar with the people and data systems powering I've seen a lot of comments here saying that the important thing is that the government is publishing something, and that it's understandable that their first pass might not be perfect.

But this isn't their first pass. The underlying data systems -- FAADS and FPDS -- have existed since the 90s, and have been riddled with errors throughout their existence. Instead of fixing the problems, OMB continues to slap new coats of paint on the same lousy data.

It's nice that we've got a new, and I agree that it would be a mistake to put too much emphasis on a buggy visualization. But the underlying data is terrible, and so far no one is showing the will to fix it. Just look at USASpending's "data quality" tab -- it talks about the completeness of each row. Well, that's great, but it tells you nothing about the thousands upon thousands of missing rows, nor about the rows that massively under- or over-report their dollar amounts.

At Subsidyscope, the project on which I work, we've delved into these problems in more depth. Those who'd like to learn more about the shortcomings of the data systems powering USASpending can find a discussion of the relevant issues here.

Comment we agree! (Score 3, Insightful) 100

I work at the Sunlight Foundation (though not on this project), and I feel I can safely say that we completely agree with you that the government *should* be issuing this data in a more easily usable format.

To be fair, though, it's not always as easy as all that: when you introduce such an infrastructure you need to make sure there are staff resources to handle the data entry, training available to help them do it, and somebody checking the overall data quality. My project's been looking at a lot of grant data, and we've consistently found that the central grant data directory -- a data set called FAADS -- is of lower quality than the reports issued on each program's website in excel, PDF, HTML tables or who knows what else. It doesn't make a lot of sense to people like you and me, but centralized systems really do introduce an added layer of difficulty for the data entry people. Just keeping track of the endless requirements imposed by legislation can be pretty daunting.

...none of which is to say that this shouldn't happen. It should! But it does explain why "publish earmarks" and "publish earmarks in a central location, in a machine-readable format" are two different things, and why the latter is more difficult to successfully ask for. We'll get there, though.

Comment actually, it's even less than 1% (Score 1) 100

Earmarks make up about 1% of *discretionary* spending. Which is considerably smaller than the overall budget (which includes things like Medicare and Social Security). And if an earmark didn't exist, that doesn't mean the money wouldn't be spent. It just means that the person administering the program under which the earmark falls would be able to allocate that money more freely (presumably to a more efficient use than a senator's pet project).

Earmarks are very easy for journalists to write up as news stories, though, which accounts for them getting so much attention.

Comment Re:This is why (Score 1) 427

Mod parent down. He clearly doesn't understand that the idea of capitalism is to produce new wealth via the use of invested capital. As a sibling poster pointed out, the economy is not zero sum.

I'm hardly a market triumphalist -- personally, I think we ought to be working toward a socialist democracy modeled on Northern European nations like Denmark -- but you need to be at least a *little* informed before you start making radical critiques of the market system.


Submission + - NYT editorial on software patents (

sbma44 writes: "Tim Lee has a great editorial in the New York Times providing an overview of the case against software patents. There's not much that the /. crowd won't have heard before, but it's great to see the issue being covered in the Paper Of Record."

Slashdot Top Deals

"In the face of entropy and nothingness, you kind of have to pretend it's not there if you want to keep writing good code." -- Karl Lehenbauer