On sitectt
By OctoSpacc
Caution
The content of this page has been entirely machine-translated into English, from Italiano. Therefore, it might contain any kind of errors.
This here was initially the home page of the site, but it has become so problematically long that… never mind, everything is explained on the new home. Here, therefore, is the classic series of loose information regarding the ✨sitoctt✨ (some of it old, it will be updated based on what’s new)! 😊
✨sitoctt✨
✨sitoctt✨
✨sitoctt✨
Where does the name ✨sitoctt✨ come from? From the fact that it’s literally my site, because I’m octt and so site + octt = ✨sitoctt✨ (pronunciation: “sitòctt”). If you prefer, you can call it sitocto. Or even postoctt! This is still a place - my place - even if virtual!
Site status and how to navigate
Despite already having a bit more substance, all this ambaradan is still heavily under construction. And it always will be, because I will always have new stuff to share. And, when I am dead, it will still be unfinished because in my life I will not have written all the universal knowledge theoretically possible on the sitectt.
Updates to the site are of different types: the publication of new blog articles happens, well, 3 times a month, it is a good idea to use feeds which I make available; changes for normal pages are continuous and happen at random, so you should check the ones that interest you perhaps every week, if you expect news.
To keep in mind (from Web): when the following buttons are on the screen, it is because they can hide collapsible menus.
They can be in different positions on different pages, because I like to experiment with different themes; but I try to keep their meaning consistent throughout.
A stack of books emoji icon (📚) signals the menu main page of the site, essential to be able to navigate by jumping between completely different and unconnected pages.
Instead, the icon with the emoji of a sheet with a bookmark (📑) indicates the list of sections of the current page - it is not essential, but can be useful for jumping between different parts of a long text.
Client-side scripting
The website does not use any client-side scripts for basic functions, because I don't want to force those (for valid security reasons and otherwise) who don't want to enable JavaScript to have a degraded experience. Regarding this thorny issue, I also wrote an article: 📄 Documents should not become applications.
Anyway, though.. to provide some extra functionality, I have to have some JS, there is little you can do. Below is the list of what I use. All files are uploaded from my site's servers, so it is difficult for malicious entities to hide malware inside.
List of client-side scripts used in the website (Expand)
- Internal scripts, written by me:
Auto-expanding menus on sitoctt themed pages in desktop mode(I'm trying to fix this..), Full screen display of page backgrounds. li> -
Polyfill to support AVIF images on older browsers: avif.js by Kagami a>(Not activated yet...it will be soonwhen the hell will I do it? I've been putting it off for months, the problem is that it's not a plug-and-play solution, I have to understand it first and then create a wrapping script 😭)
Below, I put my ranking of the possible ways to view this site, from best to worst. By standardization, they all assume full color support (where possible).
My useless digressions on absolutely absurd ways of consulting the sitectt (Expand)
- • Web browser, with full CSS3 support
- (Perfect!)
- • Print on holographic paper, fully rendered GIF and CSS3 where possible
- (Requires moving the paper by hand but excellent!)
- • Web browser, with incomplete CSS3 support
- (Meh, OK..)
- • Print on plain paper, CSS3 animations and non-rendered GIFs
- (Boo, animations are missing..)
- • Old browser (Old Web, Text Web, or Gemini) / Print on plain paper, no CSS support
- (What is this rubbish?!?!)
But what is it about?
On this Internet space of mine I will put everything. I hope.
For now, I definitely put up shallow pages on specific topics, but also long, conversational blog posts. I also want to put up lots of collections on the things I like, in both textual and media form. A kind of gallery of things that are valuable to me.
In addition to the actual contents, however, I want the site (the Web version, obviously) to be a gallery of itself. I want to create something that has its own unique character, like the amateur websites of the years 1995-2005, where every place on the Internet always had a different atmosphere from everything visited a moment before.
The rise of social media as we have them today has unfortunately ruined the web from this point of view, leading to complete standardization and the death of creativity expressed through form.
I want this web space of mine is different from all the others, characterized by monochromatic text and recycled themes, because it is a shame to have very powerful tools and not really exploit them.
For this reason, I will constantly try to invent ways to embellish the pages with CSS, not only with layout or fixed text effects, but above all with animations.
To the rest of the form, such as the tree order of the pages on the site or paragraphs on the pages, I won’t think much, otherwise I get distracted from creating content and the desire passes.
Site availability
At the moment, this site is available for browsing on various different addresses (the contents are always identical). For those who don’t know, however, the name changed a month ago to sitoctt from postoctt, because the old name gave me the impression of some postal service… I should also think about many other cloud mirrors from different providers (obviously free), if I want the site to survive octt itself and stand the test of time… But this is a long question.
Web
The website is available from several sources.
- On the clearweb HTTPS, on the GitLab servers: sitoctt.octt.eu.org.
- On the Onion Web (Tor), on Replit servers: sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd.onion. In the end it is no longer hosted in my house, but maybe it's for the best, it's one less load for the poor little makeshift server I have (at the moment,
a Nintendo Switch console with Ubuntuthe Raspberry Pi 3).
💾 Compatibility options for obsolete or exotic systems (Expand)
- • Basic HTTP version
- The site includes complex and relatively modern CSS functions, in order to provide epic graphic (and functional) effects. Ironically, although viewing the pages on really old browsers, which lack total or almost total CSS support, everything looks ugly but is readable... on browsers that are both too old and too new very serious bugs appear, which make it impossible to use some menus or even read the text!
In addition to the fact that (where possible) I want to support old systems, these damned problems also appear on less popular but current devices, like the Kindle! In short, for too many browsers that do not include a setting to completely disable CSS, it was a must to do what I did: to the path /Plain on my domains clearweb there is a parallel root, and pages with the same content but CSS reduced to the bare bones. - • Unencrypted HTTP
- To avoid problems I dedicated a dedicated subdomain to it, keeping HTTPS forced on the main one; but, since it doesn't require maintenance, I made sure that from the fifth (!) level domain "http" you can access the site via unencrypted HTTP ( hosted by GitHub, this time): in short, the address is
http://http.sitoctt.octt.eu.org
. The contents are identical, of course, but finally you can browse the sitectt on stuff like Internet Explorer 4 directly by contacting the server.
Gemini
From now on, the CTTT site is also available as a Gemini capsule. To go there, you have to use a Gemini browser.
Obviously (for those who know Gemini), everything is more neutered, and the form is not exactly the best because all the pages are a direct conversion from the HTML of the website ( and the program I use to do it is a bit broken, too).
Go to the octocapsule, kindly hosted by koyu.space: gemini://koyu.space/octt
Feeds and notifications
From now on the site (the blogoctt and the MicroBlog, specifically) has integrated feeds, which are automatically updated when I publish a new article!
Atom Feed (modern, recommended, contains complete posts): feed/atom.xml
RSS feed (obsolete, available for compatibility): feed/rss. xml
You need a compatible feed aggregator to use them.
- On desktop PC I recommend Thunderbird o SeaMonkey Mail.
- On Android I recommend Feeder or Simple Rss.
- If you want to use a device like an e-ink e-book reader, the only universal software that - among other things - includes a feed aggregator, which I know and can recommend, is KOReader.
- Tip: If you use Friendica, you can copy the link to the feed and paste it into the search bar, to be able to follow it as if it were a profile!
Furthermore, if you use any platform of the Fediverso ActivityPub (Mastodon, Pleroma, Misskey, ...) you can follow the bot of the ctt site, so as to receive new posts in your Home feed: < a href="https://botsin.space/@sitoctt" rel="me noopener" target="_blank">@sitoctt@botsin.space! For some complications that started at the end of August 2022 , the bot is not accessible from the largest Italian Mastodon instance, mastodon.uno, so it is almost practically useless now. I'm not taking it away just because it would cost me more to do that than to leave it where it is :P; However, I would have to create a new one, sooner or later.
Sources and licenses
Content Licenses
All content on this site that I created (my own writing, original media, and most source code) is licensed under "Creative Commons Attribution - Share Alike 4.0 International" (CC BY-SA 4.0) ( ), a free license that promotes sharing, and does not affect the legitimate rights to culture and collaboration of humanity in general. p>
However, there are also contents that are not mine.
In any case, if something comes from my hand, it will not have any indication of credits nearby.
For the borrowed stuff, however, the source from which I took it and the license will always be indicated, whether this is in the public domain, Creative Commons, or not specified.
Be careful, the credits for I often just leave the HTML and CSS stuff in the page's sources. So, just in case, check there for these kinds of credits. For things like images or texts, however, any credits are often a visible part of the page, close to the borrowed object (like a description); other times, the same object is a link which, if clicked, takes you back to the source. However, I thought of creating a section of the page below , dedicated to special credits (which I fill in when I remember).
Source code
Speaking of site sources, the HTML source of the actual page loaded by the browser may be difficult to read. This is because I don't actually write the complete HTML directly to compose the pages. Not only would it be a mess to replicate my various navigation bars and sections across all the pages, and if I have to make changes to these then it's a hell to replicate this anywhere, but the HTML syntax is dirty and hard to write.
Precisely for these reasons, I created my own static site generator (also, like this site itself, incomplete but updated from time to time when I need it), which preprocesses my source code to include my bars in all the pages, generate the sections of the page (which appear in the menu on the right), generate the list of pages of the site (from the menu on the left), and other little things. Important step, any Markdown or Pug files are translated into HTML to be understandable by normal browsers, and here you go.
Ah, yes, I'm saying "other little things" because this is stuff that at the time of writing this chapter the page is absent or incomplete, and by writing as I write I cover my ass and don't have to make future changes.
H and h .
Take it all!
To finish, find all my sources on the respective Git repos.
Those of my site (divided into multiple repos to keep the history clean), under the conditions described above: gitlab.com/octtspacc/sitoctt; sitoctt-assets.
The ones from my generator, also released under a free license, the AGPL: gitlab.com/octtspacc/staticoso. p>
Another thing: in case it is of interest, to immediately preserve and/or share (excluding files that are on separate repositories, because they are absolutely linked) offline copies of the site, you can download a zip containing all compiled pages here!
Special credits
List of credits and special thanks to those who borrowed material (Expand)
- List of client-side scripts, including some third-party scripts
- Waaaves animated title: Waaaves by jh3y
- Font family: Space Mono by Colophon Foundry
- CSS emoji package: Twemoji from Twitter, via Twemoji Astonishing
- Some non-identifying 88x31 buttons: 88x31 GIF Collection by cyber.dabamos.de
Confidentiality and transparency
As my legitimate interest, I use an analytics service on this website; both to improve what I do and to satisfy my pure curiosity to discover data.
The analytics service is based on completely free and open-source</ a>, hosted for free for low traffic sites by GoatCounter.com.
Apparently, with GoatCounter you don’t need to include an on-screen warning that disturbs users to comply with the GDPR (see goatcounter.com/help/gdpr), but, for honesty and transparency, I’m writing this paragraph anyway.
Only non-personal data is collected, anonymously, for the sole purposes of general statistics, and not for individual tracking. The service does not use cookies, and the data is not transferred to third parties. For further information, I can only recommend reading the GoatCounter privacy policy.