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 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!
@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)
@macallik
Absolutely. If this is true then for the other small to mid-size instances it's not just an existential threat philosophically but technically. They're expecting Threads onboarding might just knock out instances because of the traffic. Might as well limit or block just for your own performance metrics.
@NotTheOnlyGamer ah okay, i see where you're coming from. I'm still quite strident about it only because AP being open source, the current Fedi discourse is as much political as well as technical - and you're right, the era of corporate internet is not winding down just yet. But it's also not a given i can't advocate for better controls especially because fediverse means i have more control than a user of corporate socmed over which server to go and what software to use. It's slightly easier to feel that there is something that i can do because i think there is. We wouldn't be here otherwise (instead we'll tolerate what Twitter has become, what reddit continues to become). I come from the livejournal era, and that code was forked many which ways and the various journal clones became where the migration headed to when sixapart bought it (then later Russia via corporate proxy). But it was slightly too early in tech and user quality - but I feel like I'm reliving the days I'm on dreamwidth, still in touch with ppl who moved to insanejournal etc.
Because it's possible, I'm still motivated enough to talk about it. And you know, thank you. Despite posting it in the meta community for this instance, barely anyone engaged in these concerns, not even those otherwise active. Ernest I'm sure is busy, but now I'm concerned not even those who'd sum up what's going on here would talk about this. So I really appreciate the exchange.
@macallik and if you scroll down the comments, Byron from Universeodon, who did take the earlier meeting, did provide some vague points from the meeting. Relating to your point about big instances, it seems likely that FB wants to throw money at them so that they won't become overwhelmed by the ensuing traffic (unlike the rest of us, I guess...) so they can demonstrate that the Instagram bridge (it's an IG product) works.
@NotTheOnlyGamer that is definitely a good practice as an individual user. At instance-level, do you share my concerns tho?
I'm very sorry, atm it does sound the only thing left you can do is deleting his posts as it shows up on the blog
@crossmr the way it's set up (partly because the instance is meant to be proof of concept) is that every mag's name becomes a hashtag that will be slurped. Try looking at your magazine panel... Hold on... Once you're there then the tags tab should be to the right.
:( But I think this is definitely a flaw/worthy to raise a ticket because double-checking with mine, my magazine's name is not one of the tags i can delete.
@Kierunkowy74 yup that's a good move. But overwhelming traffic from legit users is still however an issue.
One rl illustration: https://ar.al/2022/11/09/is-the-fediverse-about-to-get-fryed-or-why-every-toot-is-also-a-potential-denial-of-service-attack/
@revampeduser assuming you've subscribed so that the community is now regularly fetched from/pushed to kbin.social, then it's likely a momentary hiccup with the federation which can be instance-specific