Live data from Hacker News

Viewing profile — sajal83

sajal83

HN member
Joined
Mon, Aug 23, 2010, 7:48 PM UTC
HN karma
1,569
Public activity
254 items

About sajal83

[ my public key: https://keybase.io/sajal; my proof: https://keybase.io/sajal/sigs/FRgz6WjRPcySo08oI3SNhMSFTWZlbqgxR9LZUck5MJM ]

Recent public activity

  1. story
  2. comment
    Comment #19702525

    Most, if not all websites require more than one round trip.

  3. story
  4. comment
    Comment #17464665

    > The subscriber must be directly network-accessible and is identified by its Subscriber Callback URL Does this mean the subscriber needs to have a forwarded port open to the inter…

  5. comment
    Comment #17455475

    I have a redundant 2 ISP setup, and use multipath TCP to use both of them at the same time. A very outdated post about my setup : https://www.sajalkayan.com/post/fun-with-mptcp.htm…

  6. story
  7. comment
    Comment #17062529

    My policy: if email is interesting/relavent. Do nothing. If I remember subscribing and haven't attempted to unsubscribe in the past, attempt to unsubscribe. Spending max 10 seconds…

  8. comment
    Comment #16980833

    I currently run my own (DNSSEC validating) Bind. But it has some drawbacks. For occasionally visited sites/tlds, my bind would need to contact root more often than if using a share…

  9. story
  10. story
  11. comment
    Comment #16920541

    https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad... Some traceroutes captured during the incident. The results that show "Target unreachable" were the ones seeing the h…

  12. story
  13. comment
    Comment #16916022

    https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad... Some traceroutes captured during the incident. The results that show "Target unreachable" are the ones seeing the hi…

  14. comment
    Comment #16912438

    The bad routes can be seen by agents: 219-YVR-Canana, 221-qeast, 16-TurboBytes, 6-VPS TH, 10-TurboBytes, 220-TurboBytes, 17-aks-seattle and 190-ATT-AS7018 From outages mailing list…

  15. story
  16. comment
    Comment #16892727

    Yeah I quoted that in the post. Regardless, I make the case for EDNS Client Subnet

  17. story
  18. story
  19. story
  20. comment
    Comment #16733732

    Fair enough, but most users won't care enough look it up and use 9.9.9.10 instead of 9.9.9.9 if they want better performance in exchange for allegedly lower privacy. It appears 1.1…

  21. comment
    Comment #16733519

    9.9.9.9 does not pass along EDNS client subnet resulting in wrong geo-located responses. It is their "feature".

  22. comment
    Comment #16733401

    Yep you are right right. ~# mtr --report --address 192.168.2.2 1.1.1.1 Start: Mon Apr 2 16:53:31 2018 HOST: apu Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.2.1 0.0% 10 0.9 1.1…

  23. story
  24. comment
    Comment #16733346

    https://pulse.turbobytes.com/results/5ac1f967ecbe4078c200ee4... Cloudflare consistently times out from these networks. Netherlands - AS13127 Philippines - AS135132 Thailand - AS175…

  25. comment
    Comment #16732992

    https://pulse.turbobytes.com/results/5ac1deefecbe4078c200ed8... Query times and rechability from 58 locations. 3 locations still can't reach 1.1.1.1, but for most users cached resp…