The platforms should provide inter-protocol bridging natively. Now we have to follow an unrelated (to either) account and hope that it not fails silently*. This should be a switch in the UI.

*at least one can follow bridged accounts from elsewhere without bridging oneself.

OP is on lemmy.world, and default feed is All (sorted by Active) there

kbin.social did lift off. Maybe even too much for this software at the time?

If Mbin is meant to be a “Lemmy and Mastodon client” alone, then it is a quirky Lemmy “app” and less responsive Mastodon “app”.

But it shines only when it scales. This, however needs more users taking use of eg. magazines’ custom CSS (and these don’t even federate!), keeping track on most popular Mastodon & co hashtags, adding these tags to Mbin magazines, following outside accounts to federate them to instance, etc…

All the Great Exodus fledditors, people craving for non-tankie Threadiverse service, and also curious fedinauts from outside made this happen on kbin.social, and this is what I loved in it the most.

Mbin happened when kbin.social was already crumbling, but many of its users (me included) still hoped for it. When kbin.social definitely collapsed, the previous kbinauts were already aware of not-tankie Lemmy instances, like sh.itjust.works (hosting MeanwhileOnGrad), sopuli.xyz, or generic lemmy.world.

Maybe the more aggresive Mbin marketing (have you seen the sidebar of this community - it still mentions “KBin”…) would help Mbin - but only at cost of making drama with existing kbinauts. With Lemmy’s toxicity problem being talked much recently (and instances being closed because of it) I am glad, that things did not go that way.

Some mobile apps support Mastodon and Bluesky at the same time - like SoraSNS or Openvibe

I just don’t wasn’t then to waste their time locally blocking a clear spam account, that should (and usually will be) removed by the originating instance in a couple hours.

I am afraid, that removal of spam account does not necessarily federate to another instance. On Mastodon activities federate mainly to instances an account, which made/edited/deleted the post, is followed from. (Or an instance can subscribe to relay, which exchanges all activities between all participating instances).

Report always landing to your admin may be something good in light of this…

1. ^ Jess (17 July 2025). “A lot of people don’t know this, but the original Unix was called nix. But rather than the 1.0, 2.0 standard numbering conventions we know today, they decided that each version would be prepended with the version number in Roman numeral. So it was(…)”. Infosec Exchange. Retrieved 18 July 2025.

horsesh.itjust.works

!Dodgeball@lemmy.world

@this@sh.itjust.works

Individual Mastodon (et al.) instances may provide their own status pages. But nothing Mastodon-wide.

The distribution format based on single app files is actually called AppImage. Flatpaks still need to download several libraries.

You would love kbin.social.

It combined posts from Lemmy and Mastodon, allowing to browse and sort both of these like on Reddit. Mastodon toots were matched to respective magazines (like Lemmy/Piefed communities) based on their hashtags. And multireddit-like feature (called Collections there, and recently reimplemented in federated form by PieFed as Feeds) allowed any user to combine several magazines, Lemmy communities and Guppe groups in a single view.

All of these has been inherited by Mbin (a /kbin fork), outside of Collections/Feeds.

Largest instances are https://fedia.io/ and https://kbin.earth/. There are much smaller, than flagship /kbin instance have been, though, so both will be aware of less posts…

OP wants to sort posts by popularity and unfortunately Mastodon does not allow that :( Trending posts exist but only instance-wide

Brutalinks (HN/Lobsters clone, one-community per instance), lotide (minimalist, RIP), Prismo (RIP)

This probably won’t help you, but there was Flockingbird. However its attempt to index Mastodon’s job offers ended up in drama as Mastodon generally does not like being indexed…

Just use Mastodon.

You probably want to use another Lemmy instance to search for this content.

(and actually Sepia Search is simply a search engine for PeerTube and that’s it. You are still getting the video only after you visit the instance…)

Updated, thanks!

I blame this on an UX blunder.

Bluesky users are taught not to enter their Bluesky passwords to enter different apps, but rather create a different “app password” for each one. Then Frontpage went OAuth which directs users to Bluesky login page. Bluesky brings us a different login page for OAuth use :/ and obviously does not remember that we are already logged in in the same browser.

This of course means that we have to enter a Bluesky password to a slightly different-looking website - a somewhat fishy way to authenticate a user…

Or even 33% as we should count PieFed and Mbin too (this makes 48k MAU overall). All 3 “apps” make one network.