36
So I did figure out that yes, #Mastodon can federate #Lemmy and #Kbin content. The problem
(cdn.masto.host)
So I did figure out that yes, #Mastodon can federate #Lemmy and #Kbin content. The problem is that Mastodon doesn't know what to do with it, so it (the group) looks like a user that boosts all posts and comments.
I found myself browsing the "federated group" @selfhosted over on https://kbin.social, as I think Kbin has a nicer UX for it.
I didn't really want to create a separate account for group stuff, but that might be what we do in the short term. π€
@Eddie If you include the group name (@selfhosted) it seems to work, but this isn't really practical.
Hm, that's very interesting. I wonder if the platforms will build upon each other with future updates or if they'll continue to remain "seperate" in terms of formatting and QoL. Very interested in the future of cross platform federation accounts.
@Eddie I would love more interoperability. π
It makes me wonder if the "thing" to dethrone #Mastodon will be an alternative server/client/app that speaks multiple #Fediverse application protocols? I'm jealous that a #Lemmy server requires a _fraction_ of the RAM that a #KBin or Mastodon server does.
(Obligitory @selfhosted for Lemmy to notice me)
That sounds to be the most attractive way to fit into the fediverse the way it's set up right now. I really like how kbin has support for microblogging and link aggregation however I find it hard to interoperate between different platforms like you can on lemmy/mastodon.
Once a platform nails all of this, I feel like that will be the thing to use in terms of a "master account to rule them all" type deal. That's what I want anyway >:)
If you want a personal microblogging server, run Pleroma or Akkoma, they are waaaAAAAAY less resource-intensive than Mastodon. Especially after some truly god-awful database queries were fixed in the last few months. (Load on my database server dropped by approximately a factor of 25x!!)
@ThorrJo @selfhosted lol, I can relate to thay π. I run an event & website that was notorious for its poor performance at the beginning and end of events. A few years ago, with our servers ready to fall over, I noticed a certain query was hogging the database server's CPU. I made the tiniest fix to correctly use indexes, and we instantly went from 400% CPU usage to at most 20% (across 4 cores). π
Though it's been fixed for ~3 years, I still see folks warning others about the slowness. π
@Eddie I know the kbin dev has been adjusting the federated backend to work better with mastodon. So I think it will all get better, it'll just take time.
Oh yes definitely. The exiting part isn't when it happens, but how it happens ;)