Live data from Hacker News

Viewing profile — justDankin

justDankin

HN member
Joined
Sat, Jun 13, 2020, 4:40 PM UTC
HN karma
263
Public activity
29 items

About justDankin

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. story
  4. story
  5. comment
    Comment #24653725

    I work as a researcher at the The Centre for Internet and Society (CIS), where we've been actively studying internet censorship in India over the last year. We've built CensorWatch…

  6. story
  7. comment
  8. comment
    Comment #24635639

    We released a subset of the data along with the paper (~5K hostnames), can be accessed at https://github.com/kush789/How-India-Censors-The-Web-Data The app uses a more updated list…

  9. comment
    Comment #24635581

    Unfortunately we don't have the expertise or bandwidth to make that :/

  10. comment
    Comment #24635191

    I'm one of the authors of the paper in the post, we're trying to extend this work by crowdsourcing censorship measurements from different vantage points in India. We've compiled th…

  11. comment
    Comment #24628334

    Ah yes, my bad. I meant to say ESNI Read https://gfw.report/blog/gfw_esni_blocking/en/ some time back, recalled it incorrectly

  12. comment
    Comment #24628030

    You never know. Could be a mistake where they were trying to block a certain path due to some search result of copyright infringement, but ended up banning the domain itself. One c…

  13. comment
    Comment #24627923

    Well, they could block TLS1.3 entirely (which would force hosts to drop down to 1.2 for connections) GFC does this, I really hope it doesn't happen here

  14. comment
    Comment #24627884

    Haha yeah, I've been procrastinating for the last 5 years now

  15. comment
    Comment #24627454

    Yes! That's a great observation However, the reason I went for probing the entire path is because the TTL itself can be spoofed

  16. comment
  17. comment
    Comment #24627264

    Yeah there was a huge outcry about it on Twitter some time back. P.S. From the screenshot, it looks like you're trying to connect to [http]://duck.., hence shifting to https works.…

  18. comment
    Comment #24626990

    Yes, that was the case

  19. comment
    Comment #24626924

    I haven't been able to test that yet, neither am aware of any research which answers that question. IMO the only way to do that would be to either (i) block the IP (high collateral…

  20. comment
    Comment #24626690

    Using the TTL, we figured out that the censor kicks in at the kth hop. This kth box belonged to Airtel. If a box was censoring after Airtel, we would have received a clean response…

  21. story
  22. comment
    Comment #24615509

    Thanks for running it! We are in the data collection stage at this moment, will definitely be publishing our findings and releasing the data publicly. P.S. Our previous paper talks…

  23. comment
    Comment #24614440

    I'm new to HN(3 months, low karma). Maybe that's the reason? Not sure what would be the correct way to "fix" this Thanks for vouching!

  24. comment
    Comment #24614315

    You can delete it after running. Each run on an (ISP, state) combination gives a new test point. Thanks!

  25. comment
    Comment #24613963

    DoH just by itself won't help unfortunately, since it just fetches the DNS (btw, only Airtel, ACT, BSNL, and MTNL bother with DNS censorship). ISPs have been looking at the clearte…