Sooner or later I'll stop tooting from here that I've moved instances over to @Zach, an instance-of-one running #pleroma. It would be cool if I really "owned" my toots in the sense that they were portable and I could bring them with me. Perhaps it is possible to download my archive, parse it, and import it into my new instance just for historical record keeping. Anyway, in case you missed it, I'm over there now, not here.

I'm trying out a self hosted pleroma instance-of-one installed on a small VM. So far it's performing quite well on Google Cloud Engine's "always free" tier. Not sure how soon it will run out of storage, need to figure out how to monitor it automatically. Anyway, I'm @Zach over there, and if you like, you can follow me.

I'm trying out my single user pleroma instance, which I've finally configured correctly (I think). Going to follow a big group of you and see if it can keep up. If so, might consider switching over.

As #NotADeveloper, made good progress last night getting a #pleroma instance going on a google cloud engine VM. But having trouble getting started on SSL. Not sure if it's going to work without using App Engine or their load balancer, neither if which I want to do. Maybe my problem is I'm serving the root domain from Google cloud storage and I'm trying to serve pleroma from the VM running (I guess) nginx. Several error messages running pleroma to sort through.

Based on the suggestion of @scarlett, I installed pleroma. Still need to figure out what domain I'm gonna use, but it seems pretty easy to set up and at least somewhat low resource.

I'm considering setting up a single user instance, and I'm wondering if anyone has done any attempt at performance optimizations for single user servers. Specifically something to reduce the amount of memory the app needs. Reading here, there are a few configurations that can be done, but not sure how much it might help. https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Tuning.md #mastodon #SingleUserInstance