please do not propagate errors ... it is "Maccheroni"
Macaroni – a single HTML file messenger
51–60 of 93 posts
Re: Macaroni – a single HTML file messenger
#52please do not propagate errors ... it is "Maccheroni"
You might have heard of other languages. They tend to import words but adapt spelling and pronunciation. Sometimes even meaning. Your own language has them too. I also bet you spell quite a few place names and countries according to tradition, not by any official spelling.
Re: Macaroni – a single HTML file messenger
#53I wonder why this type of deployment is not more popular - pushing all resources inside a single HTML file, with a script tag, and inline resources as blobs.
It's very impractical. - you get a slower first load (cannot progressively fetch resources as they're needed) - can't reuse a stylesheet, script or image on a different page (each has to have their own copy) - can't cache commonly used files - can't make granular changes to specific parts of the code. user has to reload everything each time. - can't set a proper content security policy And many more! It's cool for a…
This is an example of a single html-file that I serve: https://basketball.4e4.in
It weighs in at around 30 KB including a favicon, and it's quite functional.
Re: Macaroni – a single HTML file messenger
#54I wonder why this type of deployment is not more popular - pushing all resources inside a single HTML file, with a script tag, and inline resources as blobs.
I do this whenever possible. As a separate issue, I also aim for That might just be an aesthetic choice on my part, but I often find that I am able to implement all the features I need in surprisingly few lines of code. e.g. the first version of my LLM UI was 200 lines and quite usable for my purposes. And my OpenClaw clone was 50 lines. Just a Telegram wrapper around Claude, but turns out that's all I needed.[0] Als…
Would be nice if you could make a version people can run in their browser..!
Re: Macaroni – a single HTML file messenger
#55That README got a few solid chuckles out of me. :)
Really cool project imo
Re: Macaroni – a single HTML file messenger
#56Earlier quoted context omitted.
That’s fair criticism of the current implementation. The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport. GitHub happens to provide one out of the box, which makes the proof of concept extremely easy to try. If I need to run databases, message brokers, servers and monitoring just to send my mom “please cook macaroni”, I’ve al…
> The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport. It's sharing this advantage with every other free, third party managed communication service I can choose to depend on. It's also sharing the weakness that it puts me at the mercy of whatever third party I am relying on. It introduces a new weakness in that the third part…
I don't think this was meant to be taken as seriously as you seem to be taking it
Re: Macaroni – a single HTML file messenger
#57I'm a fan of the license. https://www.wtfpl.net/about/
Besides other fun things about this license, using it effectively forbids Google employees to send patches to your projects. [1] [1]: https://opensource.google/documentation/reference/patching#f...
TIL
> The Hippocratic License is an ethical software license created to ensure that open source software is not used for harmful purposes, aligning with human rights principles
Re: Macaroni – a single HTML file messenger
#58Yes!
Now we need to build a messenger that uses pastebin exclusively as the backend.
Re: Macaroni – a single HTML file messenger
#59When docs say "no backend", but git (GitHub) is actually your backend :/
[deleted]
Re: Macaroni – a single HTML file messenger
#60Earlier quoted context omitted.
Besides other fun things about this license, using it effectively forbids Google employees to send patches to your projects. [1] [1]: https://opensource.google/documentation/reference/patching#f...
The paragraph doesn’t really explain the rationale for forbidding WTFPL and even Public Domain and CC0? They’re all fine for commercial use, aren’t they?
Only a guess, but it could be because WTFPL is effectively very similar to having no license at all from what I gather