Why "kbin"?
Why "kbin"?
Hi there! So I'm two weeks in to kbin and I think I have a layman's understanding of the fediverse, but I'm still not the most technical person, so I thought I'd just post my questions here.
So I know "fediverse" stands for federated universe, so does "kbin" also stand for something? I tried checking the FAQ but the about page just tells me it's a link aggregator, and google links me to a Japanese manufacturing site or those birth name meaning/ancestry sites. (can anyone tell me if lemmy also stands for something or is this just a word the developers came up with?)
Regarding defederation, does it affect previous posts? If there's a thread with comments by multiple people under different instances, does defederating break the chain?
In fact who "owns" a thread? Like, in which instance is it stored? If someone posts on kbin, and people from lemmy and beehaw comment on it, does kbin "keep" all of those stored away or do they stay in their respective instances?
And am I correct in thinking that instances who defederate essentially block off an instance, but that instance can still see their posts, but not interact? ie. Instance A defederates from B, so they can't see/interact with B, but B can still see A but not interact with them? Or is it a mutual blocking? Ergo they both can't see nor interact. I know beehaw defederated with lemmy recently, so...?
The whole concept of defederating is just so interesting to me. I know I have to read more about it but those were mostly my main questions.
I think the name kbin, which is officially /kbin, is a play on the term /sbin, which is a system directory on unix based systems that houses binary files which require root privileges to run.
I don't know how @ernest got from /sbin to /kbin though. Maybe he told the story somewhere but I haven't seen it.
Yeah, I was hoping I could find an old post from him regarding the name, but google just shows me code, and I didn't want to bother him because I imagine he's busy. 😅
He talked about it on the polish instance. Someone accused him of some serious stuff and he explained where all the naming came from in the comments: https://karab.in/m/fediverse/p/217281/The-reason-for-the-strange-naming-and-uncomfortable-images-on#post-comment-311421
he did say something like this, i think in relation to linux or something
The "k" could be for k-hole?
I remember many years ago, there was a popular Blogspot-style page called Internet K-Hole that did periodic massive dumps of random found photos from the 70s and 80s. Back in those days of slow DSL, the page took minutes to load. All images were old and from scans. Many Polaroids. Some of the images were pretty faded, giving a sense of patina. In some the camera was out of focus, so they were blurry. Peppered throughout were scans from erotic magazines that were already defunct at the time, such as Oui, Chic, High Society, Gallery, etc.
Internet K-Hole was the first page of its' type and size with that kitschy aesthetic sense. Whenever there was an update of images, word spread around the forums of the day, like Boing Boing and Slashdot.
Kbin is the software that runs the instance. Kbin.social is the instance (running on Kbin) run by its developers. Instances in the Fediverse can run on multiple types of content management frameworks, the most popular of which is Lemmy.
When an instance defederates from another instance, it stops talking to it. It stops reading and copying the defederated instance's posts and comments. The posts still exist on the original instance, and if posted before defederation, still exists on the copying instance. However, the two copies are no longer connected, so if someone posts a comment on the original post in the original instance after defederation, the defederated instance will not see it. Likewise if someone posts a comment on the copy of your post on the defederated instance, it will only be available on that instance, and not copied back to your original post on the original instance.
Essentially, the content fragments into two copies when defederation occurs, with each separately hosted and no longer in synch in terms of likes, boosts and comments.
I'm uncertain whether defederation is always a two way street. It's my undertanding that if instance A defederates from instance B, instance B can still read A's content unless it chooses to defederate from A as well. However, as instance A isn't accepting input from instance B, nothing that happens on instance B (comments, likes, boosts) will be shared with A.
So... Each instance has a copy of all the other instances' content? I thought they just had access to each other's content but not a copy?
If they each have a copy then how would refederation work? I assume they just sync back together. So if instance A has a post with several comment threads on it from other instances, and B defederates, then it gets a copy of the post. If the original author on A decides to delete their post, then their post stays on B's instance, but if B refederates, does their copy of that post repopulate or does it sync up to be deleted?
There's no retroactive syncing. So a regenerated instance would start seeing any new content from the moment federation is switched back on. It's the same if you're the first user to subscribe to a community on another instance (from your instance). Until that moment your instance doesn't know the community exists but one a user subscribes your instance starts copying new content from that community and other users from your instance will start seeing that content in 'all'.
Because you were invited to the naming party but you did t show up.
I would be happy to get invited though.