httptoolkit | 2 years ago | on: The Journey from WebSockets to HTTP Streams
httptoolkit's comments
httptoolkit | 2 years ago | on: Beeper Mini is back
In India alone, whatsapp MAU already reaches nearly 50% of imessage MAU worldwide, and rapidly rising.
httptoolkit | 2 years ago | on: Managing State with Signals
httptoolkit | 3 years ago | on: Barcelona-style “superblocks” could make cities greener and less car-centric
There's definitely some short term pain from all the construction works, but they're making steady progress, the city has already become noticeably more walkable & cycleable in many places, and I'm quite convinced that moving away from cars within the city is the right direction in the long term.
httptoolkit | 3 years ago | on: Barcelona-style “superblocks” could make cities greener and less car-centric
The superblocks concept is that they'd be grouped together into 3x3 grids, by changing traffic rules and building urban furniture to block off streets, creating new squares and one-way systems. The goal being that everything would be far more walkable and you'd see far more local community - i.e. less of the cookie cutter shops you describe.
httptoolkit | 3 years ago | on: EU Passes Law to Switch iPhone to USB-C by End of 2024
httptoolkit | 3 years ago | on: Ask HN: Am I going insane or is there genuinely no value in blockchain tech?
Not at all - it's a verifiable audit log. Git is an example of exactly this.
httptoolkit | 5 years ago | on: Show HN: PHONK, JavaScript scripting for Android devices
httptoolkit | 7 years ago | on: Show HN: Ballpoint SVG editor
Personally, the most obvious limitation I can see here is font choices. Is there a way I can use custom fonts? Really just being able to pick from google fonts would be amazing.
httptoolkit | 7 years ago | on: Show HN: A Developer's Business Card
Cool demo nonetheless though.
It'd be really neat actually (and more practical) if these were autogenerated and available more widely with something like `npm whois [username]`
httptoolkit | 7 years ago | on: Show HN: Avoid GDPR by blocking EU visitors
Seriously, _most_ of GDPR is good practice don't-screw-your-users' personal data steps. Don't store personal data for uses that isn't strictly necessary without their consent. Make sure users can find out what data you do store, and how you'll use it. Have a way they can ask you about it, or ask you to remove it.
If complying with GDPR isn't reasonably practical with your product/business model it's a _huge_ red flag imo, EU or no.
Either it has to have a very low body buffer limit and reject anything more (making it impossible to download any files through the proxy, or do anything similar) or it's trivially vulnerable to DoS where any client or server involved can crash the whole caboodle.