Ice Rock

we are back

Heads up, in a few hours there will be a bit of downtime on glaceon.social while I upgrade the server itself. We're running up against the edge of what 8 gigabytes of RAM will get us, and this is also a server I like to use for some of my own stuff, so I'm just going to throw some more memory into it. Shouldn't take long I don't think, but heads up that it will be happening. Let's say... 9 EST, two hours from now.

The things I do for this place...

That's an image of me compiling ImageMagick, a dependency that Mastodon uses to work with images. But more importantly: It's an image, images are back :D

Hi everyone, I'm going to be updating glaceon.social today. I've been meaning to for a little bit; we're not too far behind but it's nice to keep up. Might as well do it before the merge conflicts become a huge and difficult problem.

If you see a little bit of weirdness in the near future, that'll be why. I don't expect too many issues, but if something goes wrong and you can't access glaceon.social, my backup account is @monorail@chitter.xyz where I'll be posting profanities into the void while I try to get it working.

EDIT: That looks to have gone extremely smoothly! Please let me know if you run into problems.

images are broken. i'd love to tell you i'm working on it but actually what i'm doing is hoping someone smart tells me why images are broken

Hey everyone! I'm going to be updating the instance at 5:00 eastern, about two and a half hours from when this post is being sent.

This update is going to be a little bit more involved than most of them are due to a couple breaking changes in stuff on the backend, but I don't anticipate major problems. Still, it is going to mean at least a little bit of downtime, and I can't make promises about exactly how long. Let's be really conservative and say an hour, though it'll probably be less than that.

If I have anything I need to say while the instance is down, I'll be saying it on Amy's account at @amy@efdn.club.

Sorry about the downtime, it's been fixed.

If you've noticed that this happens about every January 20th or so, then you would have fixed it faster than I did.

Hi! Nothing new to bring up today. I just thought I'd answer a question I've received a few times, as a resource for the future.

You may have noticed that you can't see any toots or users from mastodon.social (or mastodon.online) from glaceon.social. A few times, I've been asked about this technically, with reports of errors or requests for help resolving the issue. Unfortunately, this is the intended behaviour. The flagship instances are suspended here, meaning that glaceon.social refuses to accept accounts, posts, interactions, etc that come from those servers.

For future reference, you can see a list of all suspended instances at https://glaceon.social/about/more.

If you'd like to know why the flagship instances are suspended, there will be a reply to this toot detailing the reason.

If this is a dealbreaker for you: I get it! No hard feelings if you feel that glaceon.social isn't a good home for you, for this reason or another. There is a process by which you can migrate to a new account on another instance, optionally bringing over your followers (but not posts), as long as the instance on the other end also uses Mastodon or one of its forks. I'll detail the process in another reply, since it's not super intuitive.

sorry sorry i'm trying to fix it