@crossmr I've never had to try this to a blocked account but... For your microblog, do you have posts that're posted directly there. Like you know it's posted there. You can even do a test one (Add new post - that type will always go to blog).
Then, click on More of the test post and select copy to Fediverse. That URL takes you to the original version of the post. If the test post confirms the magazine as it's original URL, now do the More+copy to Fediverse to that post and see what's the URL. If it exists back on his home account, then yes, might as well ping Ernest or add an issue ticket. That's a critical flaw for mods.
@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.
@NotTheOnlyGamer ah ok, you haven't seen either the posts here, or on the fediverse magazine, or just the fact the fedidb (who tracks usage stats) had to pause on their count for threadiverse accounts because spam accounts inflated the count, or lemmy.blahaj.zone having to take a minute to delete all the spam accounts...
But fundamentally you're still not wrapping your head around what federation means. Just before Reddit Migration, the biggest and flagship instance mastodon.social, were put on silence or defed a few times this year because their open signups caused spam being sent across the fediverse.
@beexcellenttoeachother in principle as that's the point of federation, it's value-neutral to participate in such comms.
But say you're concerned about downtimes or culture or you're anticipating that instance will not be reachable or even it increases traffic load, then maybe you'll find it sensible to support a local community or magazine
@crossmr can you confirm that he's posting direct to microblog or is the microblog slurping his content because it matches a tracked tag? If the first it's a bug, if the second it's a built-in flaw.
@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)
@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.
@LegendofDragoon do you mean to ask how to follow a whole instance or specific accounts in that instance? For the second, you just search the same way (@ user @ instance) or click their names from the posts that end up on your microblog and add from their profile. For the whole instance, the kbin functionality doesn't have it yet (and the typical fediverse clients i know are optimized for pure microblogging protocols for now, or else I'd recommend client-side solutions)
@AnnoyedCrabby ayeee no worries! The basic functionalities for the link aggregation protocols (Lemmy and kbin) are roughly the same with slight differences only (kbin has an additional microblog function that's allowing it to also federate well with protocols like Mastodon, but that's just technical stuff lol). Anyway, this means for any subs, anyone with a federated-by-ActivityPub account can access and participate.
@AnnoyedCrabby the fetching is only for new messages/posts onwards, if you're viewing remotely/as federated content. The usual option for any of the fedi accounts is basically open in browser to see full public content
@AnnoyedCrabby no need! As long as the two instances are in federation, us in kbin.social can post and comment and vice versa from our respective accounts :)
@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.
@crossmr I've never had to try this to a blocked account but... For your microblog, do you have posts that're posted directly there. Like you know it's posted there. You can even do a test one (Add new post - that type will always go to blog).
Then, click on More of the test post and select copy to Fediverse. That URL takes you to the original version of the post. If the test post confirms the magazine as it's original URL, now do the More+copy to Fediverse to that post and see what's the URL. If it exists back on his home account, then yes, might as well ping Ernest or add an issue ticket. That's a critical flaw for mods.
@NOOBMASTER