I just miss that it was mainly text and could be used in a terminal without missing much.
More content density, better S/N ratio.
More content density, better S/N ratio.
All the HTML takes 2-4 kB on average, but you might not get much use from the site in a terminal :)
I wish everyone who pined for the 25-years-ago days of mostly text pages would, instead of pining, just go out there and produce that content they want to see.
Instead of pining, start writing. Hosting is cheap or free, browsers still parse simple HTML, there's nothing stopping anyone from creating a return to that simpler form.
# I Bought a Book About the Internet From 1994 and None of the Links Worked - Motherboard
#motherboard
Quantcast
[p?c1=2&c2=8568956&cv=2.0&cj=1]That's what you are suggesting.
No need to spend any money.
For one, it was largely un-monetised. There were no banner ads, no ad trackers, no giant shopping sites, no market-driven content design.
But many ISPs offered free web space, and HTML 1.0 was so simple almost anyone could hack together a basic site with a plain vanilla text editor.
So people did. For fun. Lots and lots of them.
It looked like crap, but it was weird/hilarious/insane/inspiring in equal measures in a way that's impossible to reproduce today.
What? It's not at all impossible. Get a server, put whatever you want on it. No one is going to force you to monetize or market anything, or use a Node.js backend with AWS and React, or whatever the kids are doing these days. Basic HTML in a plain text editor still works just fine.
Not in Germany. There is a set of laws called "Impressumspflicht" (https://de.wikipedia.org/wiki/Impressumspflicht) which forces you to add a mandatory imprint on your website. If you do something wrong or forget to include some mandatory information (what is mandatory also depends on the kind of website), you can easily get sued (and this has often happened). In other words: It is not easy for a layperson to set up a website in a way that will not easily become a risk of becoming sued.
It just happens that people add unnecessary complexity to their projects nowadays because 1) they use frameworks and tools that facilitate it and 2) it looks better on their resumes.
The laws introduce lots of complexity, which leads to lots of requirements in the code. So this is no contradiction.
> It just happens that people add unnecessary complexity to their projects nowadays because 1) they use frameworks and tools that facilitate it and 2) it looks better on their resumes.
And 3) because the law requires such complications (in my personal perspective the largest problem that causes the most headaches). Just to give another, "more EU/less German" example:
> https://en.wikipedia.org/wiki/Privacy_and_Electronic_Communi...
which requires that the user has to explicitly opt-in before a cookie is set. This of course has to be coded - otherwise risk being sued.
There were, however, tons of animated 'under construction' banners, which gave the same 'visual noise' problem.
If you very badly want to rip off the theme, it's stealable from my GitHub copy of my site: https://github.com/KeenRivals/brashear.me/tree/master/themes...