jedschmidt
Joined 16 years ago
Karma
1,259
Submissions
127
Member since
May 15
http://jed.is
View on Hacker NewsRecent submissions
Comment · 1 month ago
i do the same for Content Security Policy: `default-src 'none'` by default, then add what i need when i need it.
Comment · 3 months ago
agreed. i think the economics of ramen make less sense outside of japan, where it’s more expensive and turnaround is slower because folks linger longer (often to amortize the cost of waiting to get seated in the first place).
Comment · 3 months ago
this reminds me of a naive and happier time in tech, when i built a game called ramendan with twitter’s open API. you had to eat ramen every day for dinner, and tweet proof with the hashtag #ramendan, link to a photo (this was before twitter supported images), and geotag it so that we could make sure it was after sundown in your timezone.
https://www.pechakucha.com/presentations/the-savory-month-of...
Comment · 9 months ago
i went super deep on 140-byte code golfing[1] back when twitter was taking off, and it changed the way i think about code. for a brief while we had a small community collaborating on byte-squeezing techniques[2], and i was constantly amazed at the creativity that this constraint brought about, from mandelbrot renderings to sudoku solvers. possibly the best part was more than a decade later when i found my golfed UUID implementation[3] deep in my employer's codebase.
[1] https://youtu.be/JsAetmgJRss?si=AxIFySX7ktzu5GL5&t=193
[2] https://github.com/jed/140bytes/wiki/Byte-saving-techniques
Comment · 2 years ago
In my experience, as long as a controlled window is communicating with the SW, the connection will remain alive.
Comment · 2 years ago
A service worker would work fine; the connection would be instantiated from the SW and each window/worker could communicate with it via navigator.serviceWorker.
Comment · 4 years ago
Instead of adding a non-standard API to opt-out of existing networking functionality, it would be great to see a lower-level networking primitive to unlock these kinds of use cases. I wrote more (with a proof-of-concept) here: https://readable.writable.stream
Comment · 7 years ago
If there's demand for it, would love to look into that.
Comment · 10 years ago
Sure, as it could with any part of your app, including wherever your JSON.parse code lives.
Comment · 10 years ago
Not _quite_ arbitrary; the only code run is that generated by lave. Arbitrary code present in functions is parsed, but not run.