Quick Hack Will Now Alert People When The Supreme Court Quietly Changes Rulings On Its Site
from the but-only-if-they're-updated-there dept
A few weeks ago, we covered a NY Times article about how the Supreme Court was quietly changing rulings well after they had been released -- and often doing so without notifying anyone other than a few big legal publishers. Because of that, many people were still relying on the old and outdated versions. A few people suggested setting up an automated system to just check the Supreme Court website for changing documents and monitor those changes -- and that's exactly what someone has done.Lawyer David Zvenyach quickly hacked together a system to check the Supreme Court's website every five minutes for any opinion that changes, and to then automatically tweet out an announcement @SCOTUS_servo. He then follows it up with a manual explanation of the change, and recently added a feature that will highlight the actual change in the document.
This is great -- though, it assumes that the Supreme Court will always update its website with the latest rulings. As the original article pointed out, that doesn't always happen. Still, it's a step in the right direction, though there's absolutely no reason that the Supreme Court doesn't do this itself. And, in the meantime, as I discovered earlier this week in looking up a certain case, it's not just the Supreme Court that does this, but many other courts as well. Perhaps we'll need to get Zvenyach to set up similar feeds for each of the different circuit appeals courts as well...
Here's the change. pic.twitter.com/nwh3txJ06C
— SCOTUS Servo (@SCOTUS_servo) June 12, 2014
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: changes, court rulings, david zvenyach, supreme court
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in thread ]
source control
[ link to this | view in thread ]
MAUDE Reports
[ link to this | view in thread ]
Good idea, dubious implementation
That may make it accessible to the people dumb and careless enough to hand personal data over to Twitter, but it hardly makes it accessible to everyone. Nor does it guarantee that it will be archived or indexed.
A much better way to do this would be to use Mailman to set up a (public) list and send the announcements there. That way they're available at minimal privacy cost (either subscribe from a throwaway or just monitor the web version), they'll get indexed by search engines, and if the site owner gives permission, the site can be mirrored. Plus: gateway it to a Usenet newsgroup so that it gets global propagation and archiving. Plus: set up an RSS feed.
Setups like this ensure long-term online preservation of data and they do so in a way that (a) makes it nearly impossible for anyone to take it down and (b) make it possible to read the data years later. (I presume everyone knows that email and Usenet archives from 30+ years ago are completely readable and usable today using standard Unix/Linux tools. And even if they weren't, the formats are simple enough that a decent Perl/Python/Java/etc. programmer could write a parser for them in a day.)
They also (c) remove it from the control of corporations like Twitter, who have recently indicated that they will censor anything for anyone on demand because, of course, they're run by spineless cowards. How long do you think it will be before those "few legal publishers" do what legal publishers usually do and try to crush any effort that threatens their monopoly status?
[ link to this | view in thread ]
Re: Good idea, dubious implementation
Hate on it all you want but it provides a simple method for achieving most of what you seem to want.
[ link to this | view in thread ]
[ link to this | view in thread ]
Re:
[ link to this | view in thread ]
Re:
[ link to this | view in thread ]
Re: Good idea, dubious implementation
Fantabulous - please go ahead and build something better to replace it and let us know when it is done.
In the meantime, I am going to thank David Zvenyach rather than bitch that his solution doesn't use services and technology that I find adequate.
[ link to this | view in thread ]
Re:
Let's eat, grandma.
Punctuation can be important.
[ link to this | view in thread ]
Re:
[ link to this | view in thread ]
Re: source control
- The US Government
[ link to this | view in thread ]
Stupid computer trick...
[ link to this | view in thread ]
Re: Stupid computer trick...
https://www.techdirt.com/articles/20140526/06271527358/supreme-court-quietly-changes-rulings -after-releasing-them-refuses-to-reveal-what-those-changes-are.shtml
It points out some instances of them changing significant parts of the rulings.
[ link to this | view in thread ]
No reason
Do you mean no good reason? Because obviously there is at least one reason why they don't do it (otherwise they would be doing it).
[ link to this | view in thread ]
Re: No reason
[ link to this | view in thread ]
Re: Re: Good idea, dubious implementation
If you want things to last on the Internet then you need to use open formats, open services, open protocols, open source. Even doing all that isn't a guarantee: things can still go wrong. But it's the best way to stack the deck in your favor -- as decades of history have shown.
No, I'm not going to bother to fix this particular thing. I only have time to contribute so much -- and I do. I'm going to point out this design flaw and stop there. Maybe it'll get fixed. Or maybe not. (Maybe the author doesn't care about long-term preservation, in which case the point is moot.)
[ link to this | view in thread ]
Re: Re:
[ link to this | view in thread ]
Re: Re: Re:
[ link to this | view in thread ]
Re: Re:
[ link to this | view in thread ]