@LollerCorleone it's not online yet, but Chris Trottier is developing spacehost with that purpose iirc.
@haubles @vvuksan @renchap @piotrsikora @ernest @Nougat @bourbonmakesitbetter
cendawanita
joined 2 years ago
@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.
And just to provide an example, copying straight from my comment here https://mefi.social/@cendawanita/110585975153683699:
Yup that's happening rn. It really got driven home for me when my kbin account gave me a comment alert... For this account. It went to the correct person because the usernick is the same. Also the comment is to a post that is uh untagged 🙃 https://kbin.social/m/random/p/498351/I-m-thinking-once-there-s-a-protocol-i-really-like-just
@Otome-chan@kbin.social oh yeah, definitely some kind of copy primacy/conflict issue for sure. I have no idea how to describe it well enough for the codeberg ticket tho - definitely worth raising.
@Otome-chan@kbin.social yeah, that's what needs to be tested:
-
Is the originating instance the true copy? Or is every copy of equal status? Kbin's handling of having local copies is probably the issue here because other fedi protocols don't choose to do it this way (and it's probably because this reduces the load from all the fetching; big fedi accounts have been known to induce DDOS-like results when a post gets popular)
-
If that can be confirmed/clarified, is the mod log a universal log only but specific instance changes not propagating? I think Q1 is going to be the pickle here - because it implies a lot in terms of coordinating copies across the kbin infra at least (not sure with Lemmy I've not poked around at all). Copy conflict is going to be inevitable at this point....
@Otome-chan@kbin.social what's probably happening is that the mod action, like edits to a post do get federated along as well. The only time you won't see the changes propagate is if a federated mag is on an instance that gets defed, then no future changes will occur. Not sure if you've had a fedi account before this but if you do, it's like when you boost a post and the post owner edited it and you get a notification that your boosted post has been edited and you see the new text. So the kbin copy (this is where the threadiverse differ, in having local copies. One reason why 'copy url' has two versions, the instance copy and the original copy) may have the instance owner as the delegated owner of the mag but the original mod actions can still travel. So the mod is still the mod of the magazine in all federated copies of their community/mag.
ETA: I'm letting my comment stand but just noting, i didn't answer your question at all, i think. OTL
@AngrilyEatingMuffins lmao i was about to ask you to spell it out to me, because that's not my culture so it's not at the forefront of my mind, but i think I see it?? Lolllll rip to all Seans but we're southeast asians 😂
@readbeanicecream I've started @magASEAN (direct link: https://kbin.social/m/magASEAN/) for Southeast Asian stuff across the fediverse (especially) - there's still stuff the tag-scanning doesn't pick up well. But it's also shaping up to a more general interest magazine with a regional bent.
@Tigrezno one way what you might be looking for exists is on the microblogging side of the fediverse: over there discoverability is strictly on hashtags only and most protocols (or clients) enables you to track hashtags only and it shows up on your timeline. That's closest to what you're looking for, though dependent on ppl using hashtags.
@Tigrezno yes you've misunderstood - what i mean to say is that what you're noticing is absolutely a feature of multiple instances/servers being able to speak to each other. You can access their posts, and they can come in their own communities of the same interest. If you mean to say local content as in (for example) gaming @ kbin dot social and you're on that instance but you'd like also read gaming @ lemmy dot ml, then yes. In that case, gaming @ kbin is the local content, and the Lemmy one can be accessed on federated basis. But you can post comments to both. The key thing to understand is in a decentralized system, there's no 'global' version or hub. You're basically visiting branches or chapters of say, the same set of hobbyists.
@NotTheOnlyGamer it's still worth worrying. Like, in the examples i gave in the comments, i can't login to kbin.social with my other account, and i can't delete my posts. (ETA: but the larger problem is the flood of traffic and kbin hasn't had time to sort out proper instance blocks yet. Spam is already an issue)