Silk Road's Ross Ulbricht's Next Court Date Set For November 77
Daniel_Stuckey writes "Ross Ulbricht, the alleged administrator behind the illegal online drug marketplace the Silk Road, will get his day in court on November 3rd, according to a blueprint laid out today in New York's Southern District Court by Judge Katherine Forrest. Ulbrict, alleged by the government to be Silk Road founder Dread Pirate Roberts, is facing four charges (PDF via Wired) related to narcotics conspiracy, running a criminal enterprise, conspiracy to commit computer hacking, and money laundering (other charges have been brought against him regarding murder for hire in Maryland). Appearing today in court—clean-shaven, in a navy blue prison uniform—he pleaded "not guilty" to all charges. Next week, on February 13th, Josh Dratel, Ulbricht's defense attorney, will be handing over hard drives sufficient to hold eight to 10 terabytes of data, which is the approximate size of the evidence which the government has said it may use against Ulbricht. By Feb. 27, two weeks later, the prosecution must return the drives with Silk Road data the FBI collected from computers in a foreign and unnamed country, as well as a drive that holds the contents of the defendant's laptop, which was seized during his dramatic arrest at a San Francisco library in October."
Beta comment from an old-timer (Score:5, Insightful)
Obviously, I've been around the Internet and around here for a long time: started reading Chips & Dips and continued reading on a daily basis since then (overall, I don't think I missed a single story ever). I even (unknowingly) helped Rob with a Perl problem on comp.lang.perl when he was coding the original Slashdot (received a "Don't Fear the Penguins" T-Shirt when they made it into the big league - I still treasure it).
A couple of years ago, I switched to doing most of my reading on smartphones and tablets. One of the first apps I downloaded for my iPhone was the Slashdot app (I think it was branded by the then owners and included other sister sites) - it sucked though.
Anyway, I continued reading Slashdot daily through the RSS feeds and hardly ever logged on to the website itself. It wasn't just about the stories themselves - I got a lot of news and editorials from other tech sites as well (AllThingsDigital/Re-code, GigaOM sites etc). I loved reading the comments (trolls, shills etc included) and the RSS reader neatly provided the top 5 comments for each story which also enabled me then to drill through into parents, responses etc. Though I've always been more of a lurker, it is those comments that have made it a community that I've felt a part of for the past 17 years. I didn't mind crappy summaries, duplicate stories and other editorial failures - they were a part of Slashdot. About the only thing that I found annoying was the rampant islamophobia/xenophobia that developed over the past 10 years, supported by 1-2 editors, but it was mostly easy to ignore.
I've tried to support Slashdot whichever way I could. I clicked on ads on Slashdot when I wanted to buy something from those regular advertisers (Rackspace, ThinkGeek etc). I didn't even find Slashvertisments annoying as a lot of those introduced me to products and companies that I didn't know about - a good example was a video for Scottevest hoodies [slashdot.org], which I've been buying regularly since.
I read some rumblings about Beta in the comments recently and didn't fail to notice :-) a torrent of them over the past week or two, so I decided to check out the Beta site.
The beta site is fundamentally broken! I appreciate where the defensive story yesterday [slashdot.org] came from and I know that a lot of actual technical bugs with the new site can and will be fixed. The problem though is that the idea behind the new site itself is broken, so whatever is being built is being built on wrong foundations (and feel free to replace "foundations" with "intentions", depending on your level of paranoia about Dice's ownership/plans). The commenting functionality very much feels like an add-on (and it is reflected in the UI design as well) - at which point you may as well just run a Wordpress blog with comments or a commercial web discussion plug-in. The commenting functionality needs to be the foundation that the rest of the Slashdot is built on, not the other way around.
Based on my own experience, I know how these things go and I know that these (and others') comments will be ignored because a lot of effort would have gone into the current Beta site already. Something reasonably functional will eventually emerge, after many iterations and after a lot of effort, but by that time, a lot of users will have been needlessly turned away.
Death by a thousand cuts is sad :-(
Re:Beta comment from an old-timer (Score:2, Insightful)
>The problem though is that the idea behind the new site itself is broken, so whatever is being built is being built on wrong foundations
Re:Beta comment from an old-timer (Score:4, Insightful)
Wonder if an editor will reply to a three digit UID?
The solution is simple. Dump the beta and tell everyone that any proposed changes will come from the community (NOT "the audience").
Mourning Slashdot ;( (Score:2, Insightful)
I have been an active and paying member of Slashdot for the better part of 15 years. I am already mourning its demise, as I view it is on its deathbed in terminal condition.
Please, please don't make the beta live for everyone, even if there is a (let's face it) temporary classic mode ;(
This reminds me too much of FastMail's UI disaster of October 31st 2012 :(
Beta violates ADA guidelines (Score:5, Insightful)
The unnecessarily complex and excessively indented layout interferes with text->speech tools, and actually reduces legibility for people who heavily expand their screens due to visual problems. The current clean, well ordered, linear layout is easy to use, intuitive, and doesn't insert painful, confusing, or unnecessary complexity. The slashdot readers, and contributors, are here for the stories, not for the exciting newness of the GUI.
Does anyone know who actually _wrote_, or demanded, the Slashddot Beta? I'd like their names so we can warn our clients and colleagues _against_ their work.