I Blog with Raw Txt | Hacker News Reader

I Blog with Raw Txt

misc.l3m.in

32 pointssimonpure17 comments

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

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.

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.

Wow you're right. Thanks for the correction!

> view-source:https://misc.l3m.in/txt/raw_txt.txt

I see no HTML tags, <pre> or otherwise.

I don't get:

"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

The whole article is parody.

What makes you think that? It seems genuine from a casual read.

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.

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

The next step will be gopher and/or gemini :)

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.

I blog with a hex editor so boo

refreshing to see this and inspiring as weird as it sounds.

It's parody

OP has raw text submissions from this domain on HN dating back a few years, so not it’s genuine enough!

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.

I don’t think it is - the whole blog is in txt

https://misc.l3m.in/txt/

Lol. At least I don’t see runtime JS converting the font to courier new from system, but this burns my eyes to hell.

Edit: your post about spamming spammers made me chuckle

Reply on news.ycombinator.com