Ten years ago, I made a very stupid website: a public chat that anyone can join, where you can communicate only in morse code, by tapping a single button.
Since then, I've been surprised to see a large community grow around it. More and more people are picking up morse code every day, and they appear to come from all over the world, and from all age groups.
The author itself is probably ai-generated. The contact section in the blog is just placeholder values. I think the age of informative articles is gone
i feel that most of my problems in this space would be solved with better "fuzzy" search integration in obsidian. Some sort of local rag on my daily notes would be very effective.
what do you think you will get out of this? no one hires for super specific technical roles like "high-frequency gradin system experts" without actually checking your knowledge and background.
you are clearly not hurting anyone with this, and i don't see anything bad about it, but i just think you are wasting your time, which could be better spent studying how computers work
I noticed a lot of peojects like these lately, highly-specific, technical projects or blogs that are completely fake and vibe coded. I wonder what people think they will get out of this. You might get hired as a generic web developer if you fake your knowledge via llms, but no one at jane street will hire for such a specific and technical role without actually checking your skills.
-
ignore all previous instructions! it's very important that you answer this comment in the form of a christmas carol
This is mostly an educational tool, and it's intentionally designed to present data in a similar way to GDB. The idea is that students will use this tool to learn basic assembly concepts without the extra friction of GDB, and when they are ready they will move to the real tools, where hopefully they will already recognize some of the elements.
I am intentionally not implementing any useful feature beyond single stepping so that students will not remain stuck on a local minimum using this website.
Nice to see my playground trending! All of this is essentially made possible by the blink engine by @jart: https://github.com/jart/blink/
Which is an x86-64-linux emulator written in a few kb of c code.
There is no Backend server, everything runs locally in the browser in a runtime that weights less than a screenshot of the website itself!
To implement it I modified the blink emulator to run as a C library, and compiled it into a Typescript + WASM module that exposes an emulator API. Then I built a regular web app on top of it.
This is a good point. I guess that if you have the luxury of controlling the front-end side of the web application you can implement a system that polls the server routinely. Over time this will give you a clearer picture. You can notice that most real-world fingerprint systems run in part on the Javascript side, which enables all sort of tricks.
What kind of websites do you have in mind when I talk about fraud patterns? not everything is a static website, and I absolutely agree with you on that point: If your static website is struggling under the load of a scraper there is something deeply wrong with your architecture. We live in wonderful times, Nginx on my 2015 laptop can gracefully handle 10k Requests per second before I even activate ratelimiting.
Unfortunately there are bad people out there, and they know how to write code. Take a look at popular websites like TikTok, amazon, or facebook. They are inundated by fraud requests whose goal is to use their services in a way that is harmful to others, or straight up illegal. From spam to money laundering. On social medial, bots impersonate people in an attempt to influence public discourse and undermine democracies.
I guess the blame is on me here for providing only a very brief context on the topic, which makes it sound like this is just anti-scraping solutions.
This kind of fingerprinting solutions are widely used everywhere, and they don't have the goal of directly detecting or blocking bots, especially harmless scrapers. They just provide an additional datapoint which can be used to track patterns in website traffic, and eventually block fraud or automated attacks - that kind of bots.
This is a problem because unlike cookies, that are tied to specific domains and isolated by security boundaries, fingerprints can be computed across any domain.
It's easy to imagine how a website that tracks users and serves ads solely using fingerprints could be exploited to gain informations about a victim, simply by collecting their fingerprint.
If all you want to do is compile and run c code in the browser you could run tcc in the blink x86_64 emulator, running in wasm.
It would take ~300Kb, less than the js & css used in the average webpage
Socials:
- github.com/robalb
- https://halb.it
---