Day 3 of #NoRelays

I am using #FakeRelay in combination with #FakeFirehouse now to populate my federated timeline with statuses from servers I am interested in.

My posts have already a pretty good discoverability, due to having followers from many different instances.

Sad about this is, that discoverability in #mastodon is only one way. So gotta grab the content manually to not be socially excluded and to be able to participate 🙃

Thanks @g3rv4 and @raynor for those awesome tools.

#relays

Day 2 of #NoRelays

Feeling #disconnected again

- I found out that my federated timeline is more or less the same as my home feed
- My network is still not big enough to have hashtag trends or any other trend
- Relays are resource heavy, load average went down to 0.05 and lower

My takeaways so far: Choose small relays focusing on one topic. Big relays produced >30GB of data in 2 days

#MastoAdmin #FederatedTimeline #Experiment #ContentDiscovery #SingleUserInstance #Storage #lonely #GoodToKnow

Day 1 - No Relays

Right after my first night with no relays on my single user instance:

- Federated timeline is *much* less polluted, content seems more relevant
- Too early to explore hashtags, as they are still "polluted" from relayed data
- Hashtag trends going down, curious to see if they become more relevant too within the next days

I will keep this experiment running for a week before turning back on relays and fake relays.

#MastoAdmin #NoRelays #FederatedTimeline #Experiment

Now I start to understand why most Mastodon servers are topic based. The way the content discovery across servers works depends heavily on the servers user base and whom their users are following and interacting with.

So to actually have the most unbiased timeline possible and to discover the most interesting content for yourself, is to have your own single user Mastodon server?

This way it's all about you. Who doesn't like that? 🤣

#mastoAdmin #fediAdmin #fediverse #selfHosting #noRelays