jimbauwens

I don't think that the OOP system is that strange. While Lua has all the tools to do OOP, you need some helper functionality to make it easy and clean, which is what their 'Object' global function does. I myself maintain a small object library that I always reuse in my projects, so it seems fair that this is similarly done for a framework.

Additionally, it'll help you stick to a compatible model that'll work with the framework itself.

I agree that the Windows-specific concept is a bit odd .. but then again maybe it can be one layer of a larger multi-os compatible framework in the future.

Yes, you remove them completely from the oil and let them rest a bit. Mostly the fries are baked in 'fat' rather than oil though. Besides this, the type of potato that is used is pretty important too, as its consistency will impact a great deal too. The potatoes we use at home are called 'bintjes', they are a bit 'flowery'.

A virtual machine does not imply virtualization, and can use an emulated CPU.

Because Lua is much simpler than Python, but not in a way that makes it less powerful. You can grasp the entirety of Lua in your head, with all its semantics and behaviour, which is less easily done with Python (in my opinion).

Haha that's actually how I got started with this project. We had some printers with character displays, and I was creating small C programs that opened a socket to the printer to update the display. Used it to play pranks on my sister. At some point I wondered if it was possible to do it with HTTP requests and a PJL payload in the body.

Hi all. I noticed that there was some heavy discussion on local network scanning techniques using WebSockets. The ability to do these things exist from way before the WebSocket era though.

In the shared link you can find a demo that I made in 2011 that allows you to print directly to many local network printers. I tried it today, and it still work in both Firefox and Chrome. It uses an XMLHttpRequest to send a request to printers on port 9100. Most printers will receive the HTTP request and parse it as a raw print job. In normal cases, the printer will just print the HTTP headers, however I use some control characters to escape to the PJL (print job language) world, where I reset the page by drawing a blank box over the headers and move the cursor to the top left. Besides PJL, it is possible to send postscript data as well.

This is extremely scary, as most printers allow you to perform firmware updates and more over PJL. But, as the Chromium team told me in 2011, this WONTFIX as it is the fault of your printer for being insecure.

While it is clear that you did not have any bad intentions, you should never have published it on the web. Based on your earlier comment "It worked a little too well" it becomes clear that multiple users were tricked by your site and that you possibly even intercepted submitted forms ("I gasped when I realised I can actually capture all form submissions and send them to my own email.").

You misled people and breached their privacy. This is as simple as it gets, even if it was for an experiment (though leaving the site online in some other form still raises a lot of question marks..).

My advice for you is to perform future experiments locally, not on the web and make sure people participating in your experiment are aware.

Thanks, used the JSON files to quickly script a console version. Now I have a kitty giving me a nice quote with the time every time I open a new terminal :)