Yst Domain

Alexand(er|ra) Yst's home on the Internet

TLS certificate update

I've been evicted from Opal's server.
For now, this website is now on GitHub's server.
That means that I can't control the TLS certificate, due to the way GitHub's hosting operates.
Furthermore, GitHub's certificate doesn't match the host name of this website.
That means that there is necessarily a certificate mismatch here.
Even if GitHub allowed the use of custom certificates though ...

StartCom is closing down.
With no other viable gratis certificate authority as far as I know, I would have to go back to using self-signed certificates soon.
There does not seem to be a viable way for me to keep the website running on my budget and still avoid TLS certificate errors.
A certificate mismatch warning doesn't look any scarier in a Web browser than a self-signed certificate warning, so there's really no reason for me to even bother looking for a solution to the GitHub certificate issue for the time being.

I can't say GitHub is one of my Git hosts of choice or anything, but their website hosting made moving away from Opal's place quick and easy.
I'm open to other ideas (no dependencies on individual persons, please), but this seems like the best option until I have time to look into getting a VPS.
With a VPS rented, I should be able to host more than just my website; I should have the clearnet entrance to my tiny IRC network back, as well as (once I have time to set it up) a Minetest server.
For security reasons, I can't get the onion address back up on a VPS (hosting on hardware you don't control should be considered insecure, so I can't risk my onion keys being jacked by the hosting provider), but connecting to the network from Tor exit nodes will be allowed.
(Even if I had the onion address working, connecting over the clearnet from Tor exit nodes would be allowed; after all, I'm not a monster.)

Redaction

My school has requested that I remove my coursework submissions from this website.
I have done as requested, and in addition, have removed any unnecessary references to the school itself.
Vague mentions such as "in class, we studied {X}" references remain intact, but unnecessary specification of which school I even attend have been corrected.
What school I attend is still no secret though, and can be found on any of the multitude of take-down notice pages that have replaced pages previously containing coursework submissions.
Hopefully the school will be satisfied by this level of redaction.

According to the school's policy, the coursework archive can go live again two calendar years after my final term here.
If everything goes according to plan, I'll graduate mid-2020, meaning the archive can and will go live again on 2023-01-01.
As of last website update, that'll be in 1766 days.
That's right: we even have an automated countdown for the event!
I can't predict what my normal update schedule will be at that time, but I'll likely throw in a special update on that day just to reopen the archive and present new things that will have been literally waiting years to be released.

Canary update schedule

I used to try to update my canary daily, but I have too much on my plate to make that feasible.
During busy periods, I'm now updating once each week on Wednesdays.
During slower periods, I'm resting a bit and not updating the canary at all.
Just before my break periods, my canary chirp will be delayed by one day, falling instead on a Thursday.
Don't be alarmed if a scheduled update is missed, there are reasons this might happen.
However, if the canary doesn't chirp in over a month, something is definitely wrong.
(Though unlikely, the "something wrong" might be as minor as a technical error.)
Currently, the predicted canary update schedule is as follows: