Phew, the media storage usage for my Mastodon hosting finally went down. I was getting a bit worried I'd have to upgrade my little solo instance again 😅

I uh, might have gotten carried away adding some more relays this time around - they work great! but if you add too many it'll ramp that usage up 📈

I do wish there was a way to view what relay is doing the most damage, perhaps there is, I just don't know where to see it.

#SoloInstance #MastoHost #Mastodon #MastoAdmin

Giving https://relay.fedi.buzz/ by @astro a try, with a couple of hashtags and instances added.

Also https://combine.social/, by @anders

In an effort to alleviate the lonely feeling I'd sometime's have on a solo-instance, where my hashtag searches are less populated, and I'd nearly always be missing a bunch of replies.

I hope this combination introduces me to more awesome folk across the Fediverse, and saves me clicking through a bunch to "open on original page" 😅

#Fediverse #SoloInstance

Picked up a new domain and will be changing Mastodon instances soon, sorry in advance for any "Followed you" notifications that'll appear.

Nothing major, just going from .garden to .social - and will also run my project accounts from there, like design@ which will share a whole bunch of design stuff, blog@ which will share new posts, and more in time.

#MastoHost #SoloInstance #Instance

So begins the search for a new #Instance to migrate to. No problems at all with my host (@mastohost), but I do feel a bit lonely on my #SoloInstance .

I seem to lack replies on posts for a whole bunch of folk - and having to click through to their instance just to check is getting tiresome.

Hashtags too, I ran a quick test a couple of weeks back - larger instances like hachyderm.io returned 63 people for a topic of interest - whereas mine was only 11.

Open to suggestions 💚

I’ve seen a couple of posts recently from people thinking of setting up their own solo Mastodon instances.

When I set mine up with Linode, these were the steps I took, using docker:

https://github.com/davidgarywood/linode-mastodon-kickstart

#SoloInstance #Mastodon #Fediverse

So this is the error I get trying to deploy my Wildebeest Mastodon instance. I’m on a pay-as-you-go plan so I should be good on durable storage, and not seeing anything I need to opt-into in my account. The link in the error gives me a 404 error. I also see its reporting an issue with an old version of node.js, not sure if that’s an additional error or what #mastodon #cloudflare #soloinstance

Trying to set up my own Mastodon instance using Cloudflare’s Wildebeest. Once you opt-in to about $10 per month of services needed to support it, their steps on GitHub are dead simple to follow through.

Ran into a snag. My action to setup my worker is failing, because it’s saying I need to agree to pricing for Cloudflare Durable Object, which I thought I did with Workers Unbound pay-as-you-go plan. Feels like I’m missing something simple. #cloudflare #wildebeest #soloinstance #githubactions

I found out today that my admin reads all my DMs on here 👀 🥁

#SoloInstance

A solo instance is cool and all, but also some things feel... off?

I think it's the lack of replies on some posts (not mine, others). A few times now I've checked and I will see zero replies my end, but when viewed on their original page, it will have many.

I've not had a problem with discoverability (I think), though hashtags feel a bit less populated too 😕

I'll keep it going for a month and see, might run some tests then consider what to do next.

#SelfHosted #SoloInstance #MastoHost

Today I made the jump to turning off boosts and replies on home, but leaving federated wide open. p.s. I am #selfhosting #soloinstance #personalinstance