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:

17K
active users

update:

- The kbin.social server is now federating with the Fediverse. You can follow/interact with kbin.social magazines & users from other Kbin servers, Mastodon & rest of the Fediverse. For example the TIL magazine is at @TodayILearned, the lead dev of Kbin is at @ernest

- There's a new Kbin server at readit.buzz which is run by the same people as the Universodon.com Mastodon server. It's open for signups, just click "log in" and then "register".

kbin.socialkbin.social - Explore the FediverseExplore the Fediverse

p.s. If you are browsing a magazine, thread or account from Kbin (or anywhere else on the Fediverse!) and you want to interact with it somewhere else on the Fediverse but you can't find it by searching, here's how to make your server notice it:

1. Go to Kbin in your web browser
2. Copy the web address of what you want to interact with
3. Paste that address into the search box on Mastodon (or any other Fediverse server type)

It will then appear on your own server where you can interact with it.

p.p.s. Several people asking in the thread about how to appear on the microblogging sections of Kbin magazines.

As far as I can tell, just include one of the magazine's listed tags in your posts on Mastodon etc. For example to appear on the Apple magazine's microblogging section include or or one of the other tags as shown at on the right side of the screen at kbin.social/m/apple

Microblogging is a separate tab from Threads, you need a Kbin account to start a new thread.

kbin.socialApple - kbin.socialA magazine for news and discussion about a small Silicon Valley fruit company....

@feditips if #kbin is already able to post content to #Mastodon, it would be very cool if you could sign up to kbin via your Mastodon account. To me that just makes sense since both platforms already have functionality overlap.

I don't know how technically feasible that would be, just thinking aloud here. kbin already has log in with Google and Facebook accounts, so why not Mastodon ones too? If it's not feasible, nevermind. If it is, that would be very cool.

FediTips has moved!

@cazzztle

I'm not sure what you mean by "signing up to kbin"?

Your account on the Fediverse only works with the server you signed up on, but your server lets you communicate with accounts and groups on other servers.

It's like with email: you can't use a Gmail account to sign in on Yahoo Mail, but you can still send emails between Gmail and Yahoo Mail accounts.

I don't think Kbin has Google or FB login by the way?

@feditips There are Twitter and Google sign in buttons for new kbin accounts.

I'm saying, if possible, it'd be very cool to sign in via your Mastodon instance too. That way someone who was tooting on Mastodon could easily jump into kbin, continue tooting, but then also have more involved kbin discussions too.

This may not be possible depending on Fediverse architecture design and complicated to implement, but I think it'd help make Kbin even more unique.

@feditips @cazzztle that’s always been a confusing bit for me. I had initially thought “federation” included SSO functionality, but that’s incorrect. It would be nice, especially with the various services popping up that are based on ActivityPub, but that’s not how any of this was designed.

@wholegroanoats @feditips I was hoping nobody would say that... 😭

Nevermind I guess. Maybe one day in the future that can be implemented

@cazzztle @feditips fwiw, matrix (federated chat) does let you set mastodon as an SSO provider, but I haven’t a clue about other services.

@wholegroanoats @feditips Ah so it's possible to implement then! Cool. That's I was trying to figure out. I might add Mastodon SSO to the Kbin Codeberg repo as a feature suggestion then.

@cazzztle @wholegroanoats

If you want to sign up on another server, why not just sign up on the other server?

If you want to communicate with the other server, why not just communicate with it from your current server?

I'm not sure what the advantage of an SSO system would be on a federated network? (Not being rhetorical here, this is a genuine question)

@feditips @cazzztle i think it’s a potential barrier to entry for users. from my perspective, i see a “service” as various platforms with a specific purpose. pixelfed for sharing images (a la instagram), peertube for video sharing, and mastodon for microblogging. whereas “federation” is being able to access content on other instances without having to leave your home “pane of glass”, ex: seeing kbin posts on mastodon.
SSO may reduce barrier to entry for discrete services if you want to use them.

@feditips @cazzztle I also am not sure if you can interact (post new content) to pixelfed / peertube / other fediverse platforms from mastodon (or vice versa)

@wholegroanoats @feditips Yeah pretty much this. I'm thinking about accessibility. Stumbling across kbin via Mastodon, then seeing Mastodon Login. +1 kbin account server storage space, quicker user access. Win win.

Fediverse access should be as simple as possible to encourage wider adoption IMO. I think as few accounts as needed would be ideal (i.e. one Mastodon account to interact with all Mastodon instances, one Kbin account for Lemmy and other Reddit-like instances etc).

@feditips User experience behind that federation is disingenuous at best: You can subscribe and "interact" from anywhere. Everyone keeps saying so, it must be true. But it isn't.

Subscribe to a kbin theads from mastodon. Now you get a firehose dump of every comment on every thread, chronologically, with no metadata (votes etc.)

If you can parse that stream, responding works fairly well.

Unfortunately, responding is not the same as actually *participating*. Up/downvote isn't a mastodon feature, so no voting or even seeing the votes. Same across other "federated" services.

To participate, I need a BUNCH of brand new accounts. Which part of "federation works everywhere" is that?

Off the cuff, it seems like the building blocks for account equivalency are in place. SSO + a modified account migration verification can create and maintain remote 'sessions'. That even lets my "main" server send me to a compatible remote client to do remote stuff with a simple hyperlink and OAUTH bounce.