I originally built this tool to see what happened if one wrote a web server from scratch and made it face the public web (I also nudged some communities to crash it intentionally). It was a fun experience and I used that small server to host my website since then.
Over time, I learned about managing a VPS and the hassle involved with certificate management. I also wanted to host multiple websites on the same server. For these reasons I worked for about a year to add virtual hosts and automatic HTTPS by implementing the ACME protocol (RFC 8555). The new server is currently hosting https://coz.is
Hello hackers! This is a project I've been working on for fun, trying to mix the procedural paradigm of scripting languages with the declarativeness of HTML. Coming up with a good grammar was tricky, but I think I found a cool balance. I find it extremely fun to use! Looking forward for your feedback.
> I used to think (well, I still do) that getting a barebones service up and running using the system APIs at the lowest level like this is so satisfying. It's sort of magical, really
Totally agree. And actually using them is even more satisfying. I'm starting to get curious about email protocols..
> I'm kind of surprised that the vanilla poll() can put up numbers like you were seeing
Me too. I assumed I was going to go with epoll at some point, but poll() is working great.
I think it boils down to the ability of being able to divide a big problem into smaller parts and understanding in what order you need to takle them. The more you try building big things the better you get at doing it.
After getting into university I decided to build an interpreter[0]. For someone who didn't even have the notion of a parser, it just felt like an unaproachable task. Even though, I sticked to it and the architecture became clear in time. That's another thing, even if you try to build something and miserably fail at it at each iteration, you still get better at it. The feeling of the task being too vast and daunting is just a feeling and knowing there's something on the other side makes it easier to power through it.
> It wasn't clear from the article if you were planning on working on this further or leaving it as is
At the moment I'm working on it on and off in my spare time. I think I will continue that way until all major features are done and stable
> An HTTP/echo server you control is great for the bare essentials, but there are so many mind-boggling ways things can go wrong in the real world. I think the only way to catch those edge cases (and even so you'll never catch them all!) is to use it on as many different devices for as many real world applications as possible.
Yes, I'm realizing that. From the beginning I've been thinking about going the unit test route but couldn't find a way to make it work. Thanks for the feedback!
Hello HN! This is a project I've started this year to learn about sockets and network programming. Nothing serious, just a hobby project! I'd love to hear your opinions about it and feel free to ask questions
The problem is that when a map has animated tiles with different frequencies, the overall animation period of the map is the least common multiple of the periods of the single tiles. For instance, a map covered in tiles with 10 frames will also have 10 frames. But if the map has, say, both tiles with 10 and 11 frames, then the period of the map is 10*11=110. Basically, maps containing different animated tiles can potentially have lots of different screen states, while maps with the same tiles have a low number of screen states.
I think maps full of the same tile repeated wouldn't be a problem so the threshold might work in pretty much the whole game.
Hello fellow hackers! This is a language I've been working on for some time and was curious to know what you thought about it!
To me it's just a learning exercise so it's not aimed at being the next big thing. I figured others may find it interesting as an example of how one might go about building something like this. Although it's a hobby language, still I don't feel like calling it a toy language. I'm trying to build something which is usable and works well!
This is a tool I build to use in my own blog (where I mainly talk about C programming).
I considered using other available tools but they either:
1. used client-side javascript to work
2. only highlighted based on the keywords
3. only could be used online
so I thought It would be fun to write one myself. It turned out pretty nicely in my opinion!
Can AFL test network applications without the need to modify their source code? If not, it should be easy to call the parsing routine in a loop using AFL's persistent mode.
At this time xHTTP only parses the minimum amount of headers to work, so fuzzing might not find much yet
I originally built this tool to see what happened if one wrote a web server from scratch and made it face the public web (I also nudged some communities to crash it intentionally). It was a fun experience and I used that small server to host my website since then.
Over time, I learned about managing a VPS and the hassle involved with certificate management. I also wanted to host multiple websites on the same server. For these reasons I worked for about a year to add virtual hosts and automatic HTTPS by implementing the ACME protocol (RFC 8555). The new server is currently hosting https://coz.is
Previous discussions:
https://news.ycombinator.com/item?id=41642151
https://www.reddit.com/r/C_Programming/comments/1falo3b/usin...
https://www.reddit.com/r/hacking/comments/1fcc5hd/im_using_m...