Emil Mikulic
unix4lyfe.org · Personal blog · on HN since 2011
Emil Mikulic writes about small C programs and systems topics, and is the author of the darkhttpd web server.
What HN saysHN links it for "Time, What Every Programmer Should Know" and for darkhttpd, which commenters compare with other minimal HTTP servers.
18HN people shared it
9linked it in comments
10stories submitted
952story points
5 years agolast shared
2011people per year2026
Most-shared posts
- 1An HTTP server in a single .c file9 people · 289 points · first shared 2014 · 98 comments on HN
- 2What every programmer should know about time5 people · 452 points · first shared 2011 · 126 comments on HN
- 3Some Notes About Time2 people · 211 points · first shared 2013 · 113 comments on HN
- 4Ale1 people · first shared 2016
- 5Dct 1d1 people · first shared 2020
What HN people wrote when they linked it
espeed · 2011-07-15
Another good time read is "Time, What Every Programmer Should Know" (http://unix4lyfe.org/time/) -- in short, it's usually best to store time/dates as Unix time (it's UTC and a single number).
souenzzo · 2022-04-12
Is it smaller than darkhttpd?
https://unix4lyfe.org/darkhttpd/
cogburnd02 · 2021-06-08
What are your thoughts on darkhttpd?
https://unix4lyfe.org/darkhttpd/
Scoundreller · 2021-04-02
Looks like darkhttpd's website: https://unix4lyfe.org/darkhttpd/ is NOT hosted on a GPS/LTE modem and has been hugged to death.
raxxorrax · 2020-12-15
Very interesting problem. Naively I would have thought every keystroke sounds the same aside from special keys like space or enter. Apparently this is not the case.
Like the other comment suggested, a frequency analysis might help.
Here is a good explanation you could quickly use in C++:
https://unix4lyfe.org/dct-1d/
Otherwise popular libraries like openCV have tools to convert signals, but most are focused on imaging (2d signals).
nullc · 2016-11-01
There is an old free software package ALE ( https://unix4lyfe.org/ale/ ) that does some of the processing like this. It was much easier to get working if you had linear light images... and registration of really noisy images was quite hard on it.
jorams · 2015-10-03
If you're looking for a quick tool to serve static files from a directory, darkhttpd[1] is also pretty good.
[1]: https://www.unix4lyfe.org/darkhttpd/
dtx1 · 2021-04-02
It uses darkhttpd
https://unix4lyfe.org/darkhttpd/
e12e · 2014-10-05
> purely for static files
While I do see the need for both small and big servers, this one has support for cgi, and via cgi ssi -- so it's not entirely accurate to say "purely for static files" (as far as I can tell, there's no easy way to completely remove cgi support via the ./configure script -- I could be wrong).
As others have mentioned, openbsd transitioned to a new httpd based off of relayd. Not sure if/how one might compile that for Linux -- I'm not familiar enough with how openbsd organizes its code. I figured out one could get the relevant source with:
cvs -d [email protected]:/cvs get src/usr.sbin/httpd/
but as far as I can tell, there is no support for any OSs other than openbsd at this time. I'd love to be wrong, but "httpd" (where "httpd" is supposed to be not apache httpd, but new openbsd httpd, which as far as I can tell, is just called, "httpd") isn't very easy to search for...
Anyway, openbsd httpd has support for fast-cgi -- so a truly simple server, would be something like:
http://unix4lyfe.org/darkhttpd/