Notices by Masto.host (mastohost@mastodon.social), page 4

@smallsees Great! This one was pretty smooth :)

Upgrade finished!

All instances on Masto.host are now running v2.8.2

Let me know if you run into any issues.

Thanks 🐘

Upgrade to v2.8.2 for Instances hosted by Masto.host will be starting now.

Expected downtime should be less than 30 seconds.

You can find the upgrade details in the official release page of Mastodon https://github.com/tootsuite/mastodon/releases/

@Matter sure :) no problem

@Matter Hello! You are mixing up domains :) my domain is Masto.host and you are having trouble with Mastodon.host

Mastodon.host is not managed by me or has anything to do with me or my service Masto.host

@pvols1979 glad to help :)

@nh Hello!

Well you can go directly to PayPal and cancel your subscription or you can email me requesting the cancellation and I will do that for you.

Notice that as soon as you cancel your subscription your instance will go offline.

Let me know if you have any questions or need help with something.

@c0debabe @gingerrroot If Glitch-Soc offered stable releases I could consider it. The last time they made a stable release was in 2017: https://github.com/glitch-soc/mastodon/releases

@katre You need to ask Keybase from my end all is ready

@mike FIrst time I came across that and several other instance hosted with me already have it in place. Ins't there a work around?

@mike from my end all is ready for Keybase.io, you need to ask them to include your instance as a valid Mastodon instance on their end.

@Stoori yes, no problem, if you have suspended accounts they will not count for the plan limit.

@Stoori Mastodon doesn’t allow for username reuse. Full suspension is the highest level of “deletion”, all data is deleted and the user cannot login but the username cannot be reused by another person.

@hugo from what is explained here https://blog.joinmastodon.org/2019/04/mastodon-2.8/ “Keybase is slowly rolling this feature out on their side, and it will eventually be available to all Mastodon servers.”

So probably this is just a case of waiting, doesn’t sound like there is a need to do anything specific for each instance.

@keybase

@hugo well but that should be for any instance it doesn’t matter if it’s hosted on on Masto.host or not, right?

@keybase

@hugo I haven’t tested but I am running vanilla Mastodon so it should work. If you test it please let me know if it works for you or if you have any problems and I can look deeper into it.

Upgrade to v2.8.0 for all instances hosted in Masto.host finished!

Let me know if you run into any issues.

I will be starting the upgrade to v2.8.0 for all instances hosted in Masto.host

There should be under 1 minute of downtime.

v2.8.0 brings a lot of changes, you can read about it here: https://blog.joinmastodon.org/2019/04/mastodon-2.8/

Or the changelog: https://github.com/tootsuite/mastodon/releases/tag/v2.8.0

@BurungHantu @jonah As the automatic update is still going to take a while and you were so eager for v2.8.0 I have upgraded social.privacytools.io manually :)

@BurungHantu @jonah I will be doing some testing and if all goes well I should have migrated all instances to v2.8.0 in about 12 hours.