mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

18K
active users

„It actually doesn’t matter which mastodon server you choose“

How am I supposed to explore a specific Mastodon community (AI/ML in my case) if I’m not allowed to see follows and followers of users from another mastodon server/instance?

And why is it, that I only see a subset of posts of a user from another server? See screenshots of @yaringal where it says „13 posts“ in the user info but I can actually only see a single post and a single post-reply he has made. Does this have something to do with the fact, that he is on a different server or is this a bug?

@NivReggev interesting, it seems to be “working as intended” then. Weird choice though as this make, as you also mentioned, exploring a community across servers almost impossible without a lot of effort.

On top of that, this still doesn’t explain why I only see a certain subset of the users posts? Do you have any clue about this?

@slang my guess - you can only see toots that have been boosted by users in your specific instance, or something of that sort.
I’m on a small instance, and I suspect it’s impossible for the instance to store all the info on the big instances. social is definitely a big one.

@NivReggev how did users of my specific instance explore those toots in the first place then if I’m not able to see them?

I actually started at mastodon.social and saw that it’s under heavy load, then following @feditips recent toot and moved to another instance.

FediTips has moved!

@slang @NivReggev

The way servers federate is this:

If one person on your server follows someone, all of that person's posts from that moment on will be visible to everyone on that server.

If no one on your server has followed a person, and none of that person's posts have ever been shared with anyone on your server, then their posts won't be visible.

Servers only show posts that they've been told to "notice", either through an account being followed or a post being shared.

(1/2)

@slang @NivReggev

The reason it works like this is because it's impossible for every server to store all posts by all users on all other servers. The costs would be huge, data would be duplicated on thousands of servers and most never used.

So, servers notice what they need to notice.

A solution to the problem you raised would be that once an account is followed, the server should backfill older posts. This is the second most requested feature on the Mastodon github:

github.com/mastodon/mastodon/i

GitHubBackfill statuses from remote accounts when first subscribed · Issue #34 · mastodon/mastodonBy Gargron

@feditips @slang so, unlike often said, choosing a specific instance does matter.
Not super user friendly at the moment, I hope that will change

@NivReggev @slang

Well, you will see the same thing happening on any instance where an account hasn't been followed by anyone.

Hopefully the backfill would be implemented, but once an account has at least a few followers it becomes very widely seen because each follower's entire server notices them.

This problem is much worse with brand new accounts, and less of a problem with accounts that have been around long enough to make connections.

@NivReggev @slang

This doesn't happen on centralised social networks, but as soon as they become popular centralised social networks tend to be bought out by terrible people who exploit their users.

Federation allows anyone to run their own server, allows people to change server without giving up their followers, and prevents anyone buying the network out.

More at fedi.tips/mastodon-and-the-fed

fedi.tipsMastodon and the Fediverse: Beginners Start Here | Fedi.Tips – An Unofficial Guide to Mastodon and the FediverseAn unofficial guide to using Mastodon and the Fediverse

@feditips
While I sympathize with the need to highlight the advantages compared to the other network, and did read about it before opening this account, this doesn’t make it easy for users who have less tolerance for a prolonged adjustment period.

It might be part of the point for some people, of course, but is currently not highlighted at all.

@NivReggev

All I can say is that this problem goes away after you spend time on here. It is intially a learning curve, but it pays off with safety in the long term.

If you want to escape Elon Musk and people like him, this kind of method is what's needed. Every popular centralised network has eventually been bought by amoral exploitative people.

It's up to each individual to decide what their priorities are: the convenience of a centralised network or the safety of a federated one?

@feditips @NivReggev @slang While I get that it would be nice, I find easy enough to visit the original profile when I encounter a too empty one. It is usually a click away…

@marcelcosta @feditips @slang
Not when you are using a dedicated app - if you know an app that does that, I’d be happy to know!

@NivReggev @feditips @slang In Husky (or Tusky, from which is based), there is this button, which redirects to the original profile in the browser.

@marcelcosta I figure it’s only a matter of time now. Many ppl are trying it out now. Things will probably be different as early as next month

@marcelcosta @NivReggev I just checked and on Metatext (which you appear to be using) you can click the “share” button on a profile and select “open in browser”.

@slang @NivReggev

p.s. A workaround is to open the public version of a person's profile, by visiting their profile on the website version of Mastodon and clicking on their profile picture. This will open their profile remotely on their own server, which will show all their posts ever. You can remotely interact with specific posts from there.

@feditips @NivReggev thanks for chiming in and explaining what’s going on. This is actually quite unintuitive for new users. I thought that only the servers store their users and toots from these users. But apparently that’s not the case and there is some form of content fetch between servers instead of server <-> client.

So in the end I “just” need to wait longer until someone from my server has boosted a toot from a user I’m interested in such that I can see that toot?

@slang @NivReggev

The servers only store data that is needed.

You don't have to wait for a toot though!

Log in through the website or a third party app like Tusky, go to the user's profile and click their profile picture. This opens their profile in a new tab.

You can interact there remotely, or copy/paste URLs of particular posts (or profiles!) into search box on your own server. This forces your server to notice that post, and it will remain visible on your server in future.

@slang @NivReggev

The official app is quite immature compared to the third party apps. The third party apps have more features as they have been around for years while the official app only came out this year.

@NivReggev @feditips okay but this is only a problem for previous toots, right? If a user from a different server that I now follow toots something new, I will see this toot?

@feditips @slang @NivReggev
So what's the best way to discover new folks outside of your own server?

@thecesspit @slang @NivReggev

When you're starting out with a totally empty timeline, the directories are probably best:

fedi.directory
communitywiki.org/trunk
fediverse.info/explore/people

Once you've got some people in your timeline, you'll see posts shared and people mentioned in discussions.

There's the Explore tab (on the website) or the magnifying glass 🔍 icon on the official app.

Also, when it's relesed, following hashtags will help a lot.

fedi.directoryFedi.Directory – Interesting accounts on Mastodon & the Fediverse
More from FediFollows
@feditips @slang @NivReggev there's also another slightly janky way of bootstrapping yourself or smaller instances.

You can use the explore or hashtag pages on bigger instances even without an account e.g. https://mstdn.social/tags/TwitterMigration

Clicking any of the buttons that would interact with the statuses will open a dialog that will let you import that status to your instance.