Given how easy it is to move to a different Mastodon instance, it will be interesting to see in the coming months to see how many new folks will live in the "big cities", how many will move to small towns, and how many will start their own homesteads. #fediverse
@kyle I honestly thought about setting up my own instance - I ran one briefly in 2017 as proof-of-concept. But holy crap, I hate administering email - running an instance just doesn't sound "fun" in this day and age for me anymore.
@kyle @Wildbill @shawnp0wers I’m planning to give masto.host a try for the podcast when it opens back up.
@shawnp0wers @kyle @Wildbill isn’t all software? 🤔😂
@katherined @shawnp0wers @kyle Truth.
@shawnp0wers @katherined @kyle yeah. The setup — even back when I did it in 2017 — was the easy part. Ongoing maintenance cuts severely into my fucking off time these days. I value my vegetative time.
@Wildbill @shawnp0wers @katherined Interesting! At least for my own server the maintenance has been relatively minimal. Mostly the kind of things you'd expect running any small service.
@kyle @katherined @Wildbill The maintenance doesn’t seem bad at this point. I just fear trying to repair it when something goes wrong.
@shawnp0wers @katherined @Wildbill When it "goes off the rails"
@kyle @shawnp0wers @Wildbill I see what you did there. :)
@katherined @kyle @shawnp0wers Yeah, I'm pretty sure it's not a big deal to do it, I am just in the mode of jettisoning all non-essential things for me to monitor and worry about. If someone else can do it 95% as good as me or better, I'm gonna let them. :)
@katherined @kyle @Wildbill The setup, following the directions on their site, wasn't too difficult.
The part that is... uncomfortable is that it uses a lot of Ruby, and while it seems pretty stable, I don't understand the underlying infrastructure enough to really trust I could troubleshoot it when stuff goes wrong. It also uses yarn to install javascript stuff... it just feels like a house of cards a bit.