The post that claimed they blog with "raw HTML" was sending markdown to the front-end with a bunch of javascript for an entire markdown engine that then converted it to HTML
This post claims they blog with raw txt files but it's just really bare HTML with a <pre> tag for the text.
But browser can display .txt files. Both of these posts claim they do something that's simple to do and then don't do it.
Also I'm gonna call it here before it happens. The next post is gonna be "I blog with raw pdfs" and they're gonna ship a whole React SPA with some library that lets you embed a pdf display. It's probably gonna use a metaframework like Next.js for absolutely no reason. Instead of you know... just serving the f'n pdf file
seangrogg 31 days ago [-]
The HTML and <pre> tag is your browser's doing; most browsers are configured to make raw data files easier to digest (FireFox does similar prettification for raw JSON files, for example). The actual data being sent over the networking tab is a "text/plain" document that has no such HTML.
lgas 31 days ago [-]
To elaborate a little more, the commenter above must've done an Inspect Element or otherwise navigated to the live DOM view which is what has the html and pre nodes. If you view source (or look in the network tab) instead, you'll see the plain text.
"having a blog used to put constraints on my poor connection, so I removed the css and html formating for this english version."
What kind of constraints I wonder, bandwidth constraints or CPU constraints client side or server side,? A simple static hugo blog offers similar data reductions
"And one day, my server might be powerful enough to handle a successful html-powered blog, but that day hasn't come."
So which device isn't powerful enough to serve static html? An Arduino can, an intel 486 and a stm32 or esp32 as well. There isn't any difference in serving plain text and html server side wise
porridgeraisin 31 days ago [-]
The whole article is parody.
esperent 31 days ago [-]
What makes you think that? It seems genuine from a casual read.
dusted 31 days ago [-]
I write my blog in regular old plaintext files, I have a script that adds the header text to a file named with todays date and opens it in VIM.
I wrote a small script that renders the file in HTML and CSS, does code highlight and so on, but the goal is that blog-posts should look just fine in raw text, so that it is also usable on Gopher.
That is where I blog, maintenance is very easy, just edit locally and scp to the site. Or you can edit directly using tramp in GNU Emacs.
smackeyacky 31 days ago [-]
I blog with a hex editor so boo
vespergo 31 days ago [-]
refreshing to see this and inspiring as weird as it sounds.
indigodaddy 31 days ago [-]
It's parody
glenstein 31 days ago [-]
That's too bad because I think it's actually quite a good reading experience and I think the web HSA overcorrected away from brutalism so I experience it as refreshing and as a positive signal about authorial intent (focus on content and simplicity of publishing process.)
So maybe I missed the memo but I don't know why this is being parodied.
This post claims they blog with raw txt files but it's just really bare HTML with a <pre> tag for the text.
But browser can display .txt files. Both of these posts claim they do something that's simple to do and then don't do it.
Also I'm gonna call it here before it happens. The next post is gonna be "I blog with raw pdfs" and they're gonna ship a whole React SPA with some library that lets you embed a pdf display. It's probably gonna use a metaframework like Next.js for absolutely no reason. Instead of you know... just serving the f'n pdf file
I see no HTML tags, <pre> or otherwise.
"having a blog used to put constraints on my poor connection, so I removed the css and html formating for this english version."
What kind of constraints I wonder, bandwidth constraints or CPU constraints client side or server side,? A simple static hugo blog offers similar data reductions
"And one day, my server might be powerful enough to handle a successful html-powered blog, but that day hasn't come."
So which device isn't powerful enough to serve static html? An Arduino can, an intel 486 and a stm32 or esp32 as well. There isn't any difference in serving plain text and html server side wise
I wrote a small script that renders the file in HTML and CSS, does code highlight and so on, but the goal is that blog-posts should look just fine in raw text, so that it is also usable on Gopher.
Here's how it look when it's rendered: https://dusted.dk/pages/phlog/2024-05-23.txt
And you can ask for the raw version: https://dusted.dk/pages/phlog/2024-05-23.txt?raw
That is where I blog, maintenance is very easy, just edit locally and scp to the site. Or you can edit directly using tramp in GNU Emacs.
So maybe I missed the memo but I don't know why this is being parodied.
https://misc.l3m.in/txt/
Edit: your post about spamming spammers made me chuckle