MSP Social Users @mspsocialusers@mspsocial.net

Hi! I've decided I'm going to try using this account for server-admin related announcements, so they don't make up such a big portion of what I post on my regular account.

Welcome, new users!

One of the big benefits of Mastodon is a locally administered server—the admins are people you can actually talk with directly—AND there is a "local" timeline. You can see local users and what they're talking about by checking out https://mspsocial.net/web/timelines/public/local

This is being posted from the new server! If you can see this, resume normal activities.

There may still be some broken things, or things that need to be adjusted after the upgrade, but by and large and fingers crossed the big disruption is past.

(2) we do not waste time fretting about whether or not to suspend (defederate from) or silence (turn off notifications and public posts from) entire instances.

If a bad actor appears to be representative of an instance, or the instance is not itself moderated consistent with our CoC, the whole instance will likely be silenced or blocked. The list of silenced/blocked instances is here: https://mspsocial.net/about/more

One thing that is probably worth being aware of is that this instance is actively moderated.

This means a few things: (1) your reports of bad behavior get read and acted on, typically within minutes or hours. Use the report button to keep other people safe.

Images on MSP social are acting odd, the image server itself is not responding... I think it's a Digital Ocean thing. I will investigate, but may have to wait for them to fix.

I'm working my way to upgrading MSP Social to Mastodon 3.1.4, and then I will migrate to Hometown.

There may be some downtime. Possibly I get the bulk of this done today. I will carry forward as many of our local changes as I can, but my primary goal is to make the switch and I'll work on pulling local modifications forward over time.

Local users that use the web interface, refresh to see new features, including bookmarks and announcements. There's probably other stuff too, idk.

I'm going to be patching up to the latest version in a little bit. There may be some downtime, I hope to keep it to a minimum.

For people playing with the MSP social code on GitHub, the branch I am working on is local_3.0.1 .

Master is broken and will need to be fixed at some point.

Image description icon is back (looks like it needs a little tweaking). Emoji picker is nicer again.

Bigger emoji are back.

I'm going to be working on restoring some of our local features today, so the site may go up and down a bit while I make the attempts.

Monday 10/28 between 6 and 7 pm, Digital Ocean will be performing network maintenance.
They say "there may be a brief period of connectivity loss and increased latency while we shift traffic to redundant devices. We will endeavor to keep this to a minimum for the duration of the change."

For example, right now scrolling back a little bit crashes the web interface. This is stock 3.0.1 so I have no idea where to begin debugging that. Probably a bad dependency?

I apologize if things are a little unstable for a while. It's sort of why I was putting off upgrading... It was very stable and now ... Bugs.

Polls are now available.

You can now set the default web view to be one-column if you don't like the tweetdeck-style interface.

For now i think I will leave it here.

I had to put aside all our local quality-of-life mods because one of them was causing a bug that prevented the page from loading at all.

Over time I will roll them back in, but it might take a while. In the meantime, no local-only toots, no described image icon, and that horrible default emoji picker icon.

Right now for whatever reason it looks like things work okay on mobile but neither of the desktop browsers I'm using. Working on it.

Local only test

I am going to start upgrading the Mastodon software. Expect intermittent downtime as updates are applied and services are restarted.

Also after the upgrade some of our local features might need to be debugged. I have tested on my dev machine, but chances are I didn't catch everything. Let @lawremipsum know if something isn't working right and I'll try to figure it out.