@darius I started off into the Fediverse with a solo instance over five years ago, and never thought it was lonely (even though it was quite some work to find an initial group of contacts, and most threads I look at are full of holes even today).
But yeah, I'm pretty certain it's not a good choice for everyone (or most people even).

@evan @anildash

@darius Ah, great, thanks!

Have to admit I didn't check if the migration guide has already been updated before asking...

@darius Thanks for fixing this quickly.

Unrelated (other than I noticed a moment after restarting my Mastodon services following the update) - The "Hometown" - link on the error page on my instance ("We're sorry, but something went wrong on our end.") points to example.org instead of anything useful?

Is there some place where I can change that link?

@darius Ok, will do, after rechecking if I have some setup or config error somewhere.

@darius Yeah, I'd seen an issue where that is mentioned. The VM I use has 12GB with about 5GB available.

The file gets regenerated with the same content when I delete public/assets/500.html and run an assets:precompile - so at this point I'm pretty certain I must have missed some setup detail.

@darius Would I need to keep anything particular in mind when I wanted to migrate from Mastodon 4.0.2 to this new Hometown release?

@darius Thanks!

@darius The release announcement also mentions that Mastodon 4.0.x won't be supported after 2023-10-31...

Do you plan to rebase on 4.2 then, or is that still open?

@darius Great, thanks a lot!

@Gargron Hometown has reverted that behaviour, and clicking on the timestamp will open the link to the origin instance in a new browser tab (https://github.com/hometown-fork/hometown/releases/tag/v4.0.2+hometown-1.1.0#tweaks). So you keep your logged-in browser tab, and have the full thread on the origin instance in another one.
On a small instance, having a limited view of the replies is the more significant barrier.

@nelson @waldoj