Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Privacy Your Rights Online

WikiLeaks Case Reopened 25

JediLow brings news that the judge who signed the order to take down WikiLeaks.org is now reconsidering his actions. Judge Jeffrey White ordered a new hearing to be held on Friday morning to answer further questions about the case[PDF]. Meanwhile, WikiLeaks has responded harshly to the recent statement issued by the bank Julius Baer.
This discussion has been archived. No new comments can be posted.

WikiLeaks Case Reopened

Comments Filter:
  • Responded harshly (Score:3, Interesting)

    by gazbo ( 517111 ) on Friday February 29, 2008 @05:16AM (#22598136)

    Meanwhile, WikiLeaks has responded harshly to the recent statement issued by the bank Julius Baer.
    Am I the only one who read that "harsh response" and heard little more than "we were treated unfairly in court!"? Especially poor was the section that could be paraphrased as "They said we posted confidential bank records, but they weren't - they were Word files! And quite old! And maybe just a bit confidential! Did we mention Word?"
  • Re:A simple patch (Score:4, Interesting)

    by n3tcat ( 664243 ) on Friday February 29, 2008 @05:40AM (#22598230)
    A popular site like this was able to get their ip address widely public. What I feel concerned about is those sites which are less known and possibly suffering similar situations. What do they do to get users to their site? TOR? Distributed DNS? How do we go about preventing this kind of censorship in the future?
  • by Anonymous Coward on Friday February 29, 2008 @07:14AM (#22598538)
    Deploying NAT rather than deploying IPv6 would destroy the internet - it would never be able to improve, as NAT violates end-to-end. Every protocol has to be specifically handled by the NAT layer, so if you're using an out-of-date NAT solution, it will simply corrupt packets by not knowing how to recalculate whatever new protocol's inner checksum is in use. This is already a major problem trying to deploy DCCP, a protocol that's years old. Previously, 'deploy' would have been something that could happen the same day you'd implemented the stack, the 'traditional internet' working the way it is supposed to. Today, it'll likely be 10-20 years before existing NAT devices that don't support it fade away and it can be relied on - same goes for any new protocol. Don't make this a bigger mess than it already is by proposing doing it on a global scale. Use IPv6 like you're supposed to and stop breaking the damn internet.
  • Re:A simple patch (Score:5, Interesting)

    by Opportunist ( 166417 ) on Friday February 29, 2008 @08:42AM (#22598776)
    Mirror it. In as many different countries as you can. In China, if you can. While they really love to keep their own dirt under the rugs, they're just outright helpful and very "free speech" when you try to publish the dirt of people and organisations they don't like.

    I'm quite aware that someone will cry now "But most people won't find it there". Right. But, and that's the catch, those "most people" don't care either. Go out on the street and ask anyone what he thinks about WikiLeaks. If you're lucky the response you get is "Huh? You mean Wikipedia?". If you're less lucky, the respsonse is just "Huh?".

    People that do care will find it, and they will crosspost it to topical boards that deal with certain specific issues, when the issues discussed there touch what WikiLeaks is about.

It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.

Working...