Hiking to the center of the region's coldest tundra, you finally find it: The Ice Rock. It radiates with an unknowable energy.
You reach forward and touch it, wiping away a layer of snow. The ice is crystal clear, so it's not difficult to see that something is frozen inside it.
A laptop computer is running, despite no obvious source of power, and messages are occasionally printed to a terminal window. If you squint, you can just about make out what they say...
Okay one person says they restarted their PC and the errors seem to have stopped so if you're getting intermittent cert errors, try closing your browser all the way? And if that doesn't help try doing a reboot maybe?
If you're still having issues with intermittent cert errors, maybe try this?
No idea if it will help but it's an idea. Haven't been able to reproduce any problems yet.
You may notice that the instance just went down for a little while. Normally, I would have loved to make this announcement first, but this wasn't exactly planned downtime. The instance just... went down. In fact, I started typing up an announcement on my backup account (@monorail) in case anyone remembers that, but I was partway through it when g.s came back up.
But, while it was down, I did something I've been putting off for a while: I've upgraded the VM that g.s runs on!
This should hopefully, hopefully, be enough. I don't think it'll be going down randomly in the near future.
Knocking on wood, though.
As I've been saying recently, things are broken and I'm planning on basically rebuilding the whole instance from scratch (no data will be lost, though, we're keeping the database)
There is one last thing I've realized I need to do before I can really get working on that and it will mean probably about an hour of downtime. Maybe more, maybe less.
In about 5 hours from this post, 10 PM EST, the instance will go down for a little while. That seems late enough to avoid the most active hours.
My apologies for the inconvenience. This should be the last significant downtime before at some point in the next couple days, things are actually sort of fixed around here.
Okay so things are broken and I don't really understand why, and they're even more broken on the back end. My current plan is actually to spin up a new instance and then restore a database backup from this one onto that one and then everything will be good
Please ignore things like the huge avatars on user pages, I know, I can't fix the individual things so a huge fix for everything all at once is coming
Hey everyone! It's been... actually too long since I updated this instance, so I'm planning on working on that today. I'm going to get started on that fairly soon but it means doing some merge conflict resolution and stuff that always takes longer than I expect it to.
Expect a little bit (~a few minutes) of downtime when I actually apply the new version, but, uh, prepare for more than that if something goes wrong and I have to work out how to fix it. The Mastodon codebase is, well, it's something.
As always, if anything does break, you can find me at @monorail where I'll probably be swearing into the void as I try to put the pieces back together.
Hi, sorry for the recent instability, I didn't think it was going to last long enough for it to be worth making an announcement. Just an in and out thing. But no, everything is harder than it has to be.
As a consolation prize, a feature that has been broken for ages and ages now works again! glaceon.social is now available from any subdomain!
The reason this is nice is that your cookies won't carry over. You can be logged on to multiple accounts and choose which one to use based on your subdomain! For example, I'm logged into my main on glaceon.social, but I'm typing this from admin.glaceon.social. No need to juggle incognito mode, or anything like that.
Again, sorry for the instability, but things should be doing okay for now!
This is a jortage issue apparently
Back to bed
Hey everyone! Quick update about something I've been meaning to do for a while but hadn't gotten around to until just now.
This instance no longer has markdown lists! In theory, anyway. The code that prevents them is kind of a hack.
Anyway, markdown lists provide almost no value over plain text, and unlike other formatting which is just lost on instances without rich text, markdown lists caused entire toots to be mangled beyond the point of readability.
I've been escaping my lists for a while now, anyway, but now it's done automatically. So you no longer have to worry about lists screwing up on other instances!
That said, please let me know if you do manage to create a markdown list! It would be interesting to see.
I'm genuinely surprised by how smooth that was. It was so easy it's actually suspicious. Hmmm.
If you notice anything broken, let me know at @monorail!
Instance suspension announcement/recommendation
Just got a spam DM from a user on crypto-group-buy.com, an instance that came into existence this month and who's users seem to have posted a grand total of 0 times. I find it hard to believe that it's currently being used for anything other than spam.
glaceon.social defederation announcement
We'll be suspending https://witches.live on Monday. every user here who follows someone there has been sent an automated DM letting them know to reach out to anyone there that they'd like to maintain ties with before then.
Official glaceon.social announcements account
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!