I didn’t want to eta, so addition: what is being federated right now is readability and participation - with your kbin account you can absolutely interact with other fedi posts. But on the client-side options for a cross-platform one that can also be useable with a threadi login is still unavailable.

@adonis

@adonis the quickest answer is that the clients you’ve explored are optimized for a specific fedi software. Pre-reddit meltdown most clients developed were designed for Mastodon and its forks or close cousins whose backend are coherent like Pixelfed. This includes the Mastodon app itself. There are other microblog softwares, like Calckey - they also don’t parse the same way so most fedi clients for microblogs can’t log you in to your Calckey instance.

With the threadiverse softwares, none of them are rendered the same way as Mastodon, so that’s why you can’t login with those clients. And with the threadiverse clients, currently what’s available are software-specific - jerboa only works with Lemmy for example. Interoperable threadi clients are in heavy development though, if you don’t mind waiting. At the moment there is no Kbin-optimized clients.

Sooooo for today, if you have a Masto-flavoured account, it’s almost a given any of the popular clients can log you in. Hope that helps!

@xtremeownage Downvotes do nothing here to trigger deletion or admin action.

@CynAq you don’t have to defed entire instances, if the instance themselves are willing to keep to their own principles. If that’s not kept or they’ve changed their position, it is actually Fedi culture to date, to defed (this is on instance to instance basis). Federation isn’t being connected to everyone, it’s practicing the right to associate. That’s why if you don’t agree with your instance, unlike closed systems, you have the right/freedom to move.

(The problem is the moving so far only carries your social graph not post history. So yes there is a penalty - but this also incentivize users to also push their admins to act more representatively. Assuming that’s what the majority wants)

@furrowsofar very much this point. There’s an additional issue related to (kbin) infra as well, it does fetch content and present it as tho that person posted on the microblog here and short of contacting an admin, no user-level way to delete it (since they can’t actually login)

@asjmcguire the user-level block means you the user can’t see the post. It’s still being fetched at instance level. So in terms of avoiding hate speech (political problem), good and quick step to do. In terms of overwhelming an instance with traffic (the technical problem), not so much.

@asjmcguire i was talking about kbin. The AP programming language (eta: yes it’s called protocol or standard as well iirc) is definitely old :)

The fact that kbin does fetch posts from originating instances without instances having the setting to allow or disallow is a problem once something with the computing power of meta and its userbase comes on board. Because mastodon for example doesn’t have whitelists, only blocklists.

@neonfire scheduled posting would also be good, to stagger the cross-posting imo