I was sure that I fixed the certificate reloading issue last time that it happened, but it happened again. I'm sorry
@Gargron 👏 I was worried.
@Gargron it's okay. These things happen :)
@Gargron It is ok, no system is perfect
@Gargron install OpenBSD
@mathias both on IPv6
@horia ah cool, almost no one in France can visit them then.
@Gargron Are you the only one with admin access?
@ondra I am not, but the other person didn't react either
Ah that old chestnut. I've fallen foul of it a fair few times myself
@Gargron *presses rewind on the recording, presses stop, hits play button, several seconds of tape hiss* did you use --nginx
@Gargron It's okay... I'm not mad at you for that.
What I am mad at is that both #Firefox and #Chromium refused to allow me to add an exception and blocked the site entirely before the issue was fixed! Seriously, what the heck: Are our web browsers babysitting us and restricting our access to websites by force now?! Are we 5 year olds while they are our parents?
@ondra Thanks. I primarily use Firefox... for which I found a workaround, though it required editing a file in your user directory. I figured I'd just wait at that point.
The annoying thing is that web browsers deliberately strip users of their choice after warning them. It's just laughable: We never asked browser developers to protect us from our own choices.
@MirceaKitsune I think it is primarily because of the HSTS header Mastodon.social sends which specifically forbids clients from accessing it through unsecure channels.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!