#? UTF-8

Welcome on my "website".

Here, your computer won't find anything to execute silently.
Files you have on your computer won't be read in any way by
this server (cookies).
One day, there might be some limited HTML/CSS stuff, but I
do not see it in the foreseable future, because those
file formats are a pain to handle.
The main reason I could see to use them is the fact that
they indicate the encoding, and thus are able to handle
non-english text.
As a workaround for that very specific issue, you'll find
a "shebang-like" 1st line in documents indicating their
encoding, most often it'll be UTF-8.
Note: I used a different syntax than shebang to avoid
risking confusing whatever program you'll use to read.

The 2nd most important reason I could see for that is to
embed images in texts. The solution for that will also be
pretty trivial: I'll use pdf documents, probably, along
with their LaTeX source code when said source code is under
FOSS licence.

Also, for wannabe crackers, let me inform you that I used
a sane HTTP daemon, named darkhttpd.
This daemon is *not* able to run any form of code, so don't
waste your time trying to find a flaw in an SQL database
(there is none) or in the scripts running this site (there
are none).

Why would one want to not have a "website"?

Because web sucks.
Not only the text-based format it uses (HTML) is very heavy
(a lot of text is duplicated by the specs, for nothing),
but today, nobody is still able to write an actual renderer
from scratch, or maintain one.
Even Microsoft stopped trying!
So, it's hard to implement a client. That could be ok.

But it's also very hard to actually create content, and that
is a lot less ok to me.
Nowadays, people use generators, tools that generate code
from some random text format. Take a look at whatever website
using, for example, hugo (a static site generator) and look
at how many data you need to download before being able to
access information.
Remember that even if the result is (discutably) "nice to see"
it implies that every 4 years, the world have to throw away
huge amounts of electronics components "just because".
Those code generators are shitty.
You want more proofs? Use the context menu on one of them,
and take a look at it.
Remember: every double space is semantically (and renders)
the same as a single space, newlines means (and renders)
nothing.
But those useless octets are *still* downloaded.
They *still* require bandwidth, *still* require energy for
transfer between your terminal and the server, and that,
for *every* electronic system in-between.

I don't accept that state of things.
I tried to build my own generator, but I was stuck with the
CSS side, because even the simpler layout requires several
hundreds lines of code.

Thus, this place will probably contain mostly raw text files
for long, with the exception of the git's repositories.

Since I won't use HTML, there won't be hyperlinks.
Instead, I will put URIs in my texts, that you will be free
to read, copy and use whatever tool you want to access them.
To access other documents here, I'll use one of the older
but most efficient ways I know: a directory tree.

Enjoy or leave.