A shamed. There’s actually a lot of good stories if you are able to view the older threads on this magazine. See for example https://kbin.social/m/maliciouscompliance@lemmy.world?p=3
I usually browse just the local communities
Ditto, except it’s kbin.social in my case rather than lemmy.world
I probably would have never read this story if it only existed on kbin
I would presume the instance is important here?
That can be the case, sometimes issues with federation can cause threads to get lost across instances, and a new instance may not get all the existing threads on a pre-existing magazine.
However, it looks like both your account and this magazine are hosted on lemmy.world - since you’re both on the same instance, you should have been able to see the older posts on this magazine. (Note: magazine is the kbin term for lemmy communities - i prefer it as the term community can be ambiguous). I’ve never used lemmy proper so am not sure how that works, but on kbin you can view the older threads on a magazine quite easily.
Hmm so it seems like that deleted the comments old the older post from others too. Didn’t expect that to be honest.
Mostly was just curious why this one in particular was chosen to be reposted twice.
Didn’t you already repost this last month?
https://kbin.social/m/maliciouscompliance@lemmy.world/t/26161/REPOST-Ex-s-divorce-lawyer-Send-3-years-of-complete-financials
I prefer the interpretation where BIN = Buy It Now. So get into kbin now, basically.
Their admins fight over who does what to whom and apparently they close subs then threaten themselves demanding that they reopen them.
What? Where and when did this happen?
Ideally there would have been a way to merge threads and preserve the comments from both. Too late now I guess, but something to keep in mind next time something like this happens I suppose…