cendawanita

joined 2 years ago
[–] cendawanita@kbin.social 1 points 2 years ago

@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

[–] cendawanita@kbin.social 3 points 2 years ago

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

[–] cendawanita@kbin.social 4 points 2 years ago (1 children)

@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!

[–] cendawanita@kbin.social 1 points 2 years ago

@CarlsIII aye no worries - fair ask

@Friend

[–] cendawanita@kbin.social 2 points 2 years ago* (last edited 2 years ago) (2 children)

@CarlsIII try click on More at the original post and select Copy to Fediverse. That'll get you the originating url. This works for every type of post and comment.

@Friend

[–] cendawanita@kbin.social 1 points 2 years ago (2 children)

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

[–] cendawanita@kbin.social 3 points 2 years ago

@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)

[–] cendawanita@kbin.social 2 points 2 years ago

@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.

[–] cendawanita@kbin.social 0 points 2 years ago (1 children)

@YourClarke hahaha don't worry. I've really only been on Fedi since Nov 22 and kbin at the same time as you guys set up this Lemmy instance. I think the redditors will get the hang of it, certainly faster than Twitterjaya (I'm in perma-eyeroll mode since you guys arrived, because those are my gang. I'm even here cos someone made a big fuss about Elon. Guess where they are at now? Twitter ppl are babies. Mastodon as a platform was at least a few years old and they whined so much. Boo hoo have to pick instance, dunno who to talk to, feed so empty blablabla. But look at you guys! Most of the two major protocols are still held together by string lmao and you make it work.)

The main thing about Fedi protocols is that janji we can roughly talk to each other. Some functionalities across the microblogs pun not shared (I've only mentioned a couple), but it's doable, we make it work. Since joining my to-read tabs blew up and there's less Main Character discourse. So it's been a real nice change. But i was missing Malaysia content and community A LOT (hence my eyeroll at Twitterjaya). The current kbin state of things pun (like how when I'm logged on my kbin.social account i can see who upvoted) is probably because of what i explained above but also it's not even three months old. Lmao the dev is just some Polish kid. Lemmy is much older but a lot of ppl avoided because the main instance and devs are full-on tankies. The Reddit wave made it moot since you can always 1) make your instance; 2) fork the programme if tak puas hati with those devs and maintain your own codebase.

In any case for your example you get Lemmy features when your account is on an instance running Lemmy and kbin when otherwise but not both at the same time. Takpe, it's not gonna be too hard. And besides monyet.cc is set up, so at least you know how to hang out here. And from here, if you're signed in as monyet.cc accounts, you absolutely can find other comms such as kbin ones too. Can one can one :)

[–] cendawanita@kbin.social 1 points 2 years ago* (last edited 2 years ago)

@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.

[–] cendawanita@kbin.social 5 points 2 years ago (3 children)

@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.

@giallo @madjo @nameless_prole @stevecrox

[–] cendawanita@kbin.social 0 points 2 years ago (3 children)

@Annoyed_Crabby oh no, downvote also I can see, being a kbin user. It's the other microblog protocols that won't register anything. (if you feel nak lepas geram, this may be useful info, if you're adding any fedi accounts to your timeline/stream/subscription view (I assume you guys have this)

@imaginelizard @dcx

 

I originally posted this in m/kbinMeta: https://kbin.social/m/kbinMeta/t/73476/How-do-kbin-instances-and-all-aggregator-protocols-work-to

Not sure what's the etiquette on splitting discussions, but fwiw here's the key para from my post:

I'm bringing this over to the kbin side because of the three concerns: political (extend, embrace, extinguish playbook means standards-setting work will be under threat of an eventual oligopoly); privacy (data scraping and surveillance capitalism is a known thing, legal or otherwise); and infrastructure (the full blast of new Threads accounts and the way AP and esp Masto does JSON will mean the perpetual fetching will overwhelm smaller instances) - the most particular for threadiverse is on technical capacity.

most instances are still finding their feet. What measures are already in place short of defed to help admins not get overwhelmed? What measures are being worked on?

kbin does scraping posts very well. Even untagged posts end up here on kbin.social because the 'random' magazine was created. What can instances do to not become a risk vector for at-risk persons who probably didn't realize this protocol (that's not even a year old) has been quietly slurping their posts in machine-readable forms all this time?

 

This is going to be kbin focused because that's the infra I'm most familiar with, but if any part of this is relevant to Lemmy and other upcoming aggregators it's worth a think too:

  • in the more microblogging part of fedi, it's been about week and some of active discussions because of the reveal that FBMeta is developing its own Project 92, or Barcelona, a competing service to Twitter (called Threads) that supposedly will be using ActivityPub

  • it's followed up by confirmation that there's been overtures to those running big (in size) instances esp on the Masto protocol to meet (Eugen never confirmed but in deleted posts talked about the idea of a meeting even with NDA positively; Universeodon definitely confirmed taking a meeting. Universeodon admin also runs a threadiverse instance (kbin). No one else, and in fact more confirmed they didn't: Dan who does Pixelfed and runs the Fedi database; Chris who's one of the admins of calckey.social; Jerry who does infosec.exchange and also runs a kbin instance)

  • the big discussion is if then Fedi instances should federate with Threads. There's a Fedipact now of those who won't and will outright block. There's more who's being cautious and have decided on preemptively silencing (so conditional following). There's those who wants to wait and see.

  • I'm bringing this over to the kbin side because of the three concerns: political (extend, embrace, extinguish playbook means standards-setting work will be under threat of an eventual oligopoly); privacy (data scraping and surveillance capitalism is a known thing, legal or otherwise); and infrastructure (the full blast of new Threads accounts and the way AP and esp Masto does JSON will mean the perpetual fetching will overwhelm smaller instances) - the most particular for threadiverse is on technical capacity.

  • most instances are still finding their feet. What measures are already in place short of defed to help admins not get overwhelmed? What measures are being worked on?

  • kbin does scraping posts very well. Even untagged posts end up here on kbin.social because the 'random' magazine was created. What can instances do to not become a risk vector for at-risk persons who probably didn't realize this protocol (that's not even a year old) has been quietly slurping their posts in machine-readable forms all this time?

I've been super enjoying my time here, and if i know where we can collectively stand on this, it will take a load off of my mind.

 

IDK you guys might be interested in the fedi-wide music competition (inspired by Eurovision season) - voting is just DMing the bot... I'm pretty sure even the L/k accounts can do it via message (but I'm not even sure how to access writing one.... I've been receiving them fine though).

view more: next ›