DavidBuchanan
Joined 10 years ago
Karma
249
Submissions
28
Member since
Oct 3
Recent submissions
Comment · 5 years ago
It's with HostUS. I got a coupon a few years ago (via LowEndBox), and it's been renewing at the same rate ever since. I have no complaints about them, but I'm not sure you can get the same pricing today.
Comment · 5 years ago
Server seems fine, I think it just doesn't work on Safari
Comment · 5 years ago
Author here - this was just a quick PoC, I'm pleasently surprised that it seems to be handling all the HN traffic.
It's served from a python script using aiohttp, behind nginx, on a $16/year VPS.
I might make a github repo with more details, but in the meantime, here's the server script: https://pastebin.com/ykUeppqc (apologies for pastebin, I don't have access to my github account at present)
Just in case the server dies, there's a video of it here: https://twitter.com/David3141593/status/1388602027484356614
Comment · 5 years ago
This is my "textbook" implementation of AES128, which follows the FIPS specification as closely as possible (in python): https://github.com/DavidBuchanan314/aes-playground
It also includes from-scratch Galois field arithmetic functions.
Comment · 6 years ago
Here's my writeup/solution for the same challenge, represented as a diagram:
Comment · 6 years ago
This was recently suggested to me on Twitter, I'll have a look at implementing it tomorrow.
Comment · 8 years ago
It isn't massively complex, but it did require some custom encoding/decoding logic. I plan to write a blog post on this some time soon...
Comment · 8 years ago
Not quite, ICC profile chunk size limits.
Comment · 8 years ago
And yet, nobody has done the same for Twitter until now.
The difference is that twitter applies a series of operations to all uploaded image, stripping EXIF data, recompressing, etc., which would normally be difficult to work around.
Comment · 8 years ago
> The main issue with RDTSC is that task-switches may cause your thread of execution to change cores or mess up your timing
I got around this by running my benchmarks in a kernel module, with interrupts disabled. Obviously this is only possible under certain circumstances.
I also disabled caching via the CR0 register for maximum repeatability, although of course that isn't at all reflective of "real world" performance, so it depends on what you're actually trying to measure.