Thanks for the reply. I see the request has been posted by someone else and has been acknowledged/tagged. I guess it is just waiting for the feature to be implemented now.
the cross-post button is the correct way to do it, but sometimes I do delete the > at the start of each line to remove the quote block
currently the “cross-posted to:” thing is based on the link URL, so text-posts don’t have that for now, but any link post will get it automatically if you used the cross-post button
(easy solution is to have a url for every post, even if it’s just a simple image)
Ok, there’s your instance, instance A, that hosts your personal account. There’s the instance that hosts the community, instance B, and a random instance that your content has federated to, but doesn’t host you or the community directly. This is instance C.
If an admin on A (instance A mods can’t remove this post) removes your post, it gets removed on other instances too, including B and C.
If an admin or community mod on instance B removes your post, it gets removed on other instances too, including A and C.
However, if an admin on C removes your post (a moderator on C can’t), then it is only removed on instance C. Instance A and B and any other instances the content has federated to aside from C, continue to see replies, edits, votes etc
One final point. My example above only works if there are no mods for the community on instance C.
If there is a community mod on instance C, that moderator can remove the post and the removal will federate, even when an admin removal on instance C will not (unless that admin is also a community mod for the instance B community)
Right, so a user on C could be a moderator for !community, and could then remove it on instance B and it would federate; but if they deleted it only on instance C, it would not.
Not quite. An account on instance C that has moderator privileges on a community hosted on instance B can’t take any direct actions against instance B content.
All that can do is remove it in instance C. However, because they’re a moderator, that removal will federate to instance B, which will remove it there, and then federate that removal to any instance that the post federated to originally.
I think the best way to visualize it is in terms of who owns what and who has the authority to perform moderator actions.
As a user, you own the post, so you’re allowed to delete it no matter what. That always federate.
An admin always has full rights on what happens on their instance, because they own the server. The authority ends at their instance, so it may not federate out unless authorized otherwise.
An admin can nominate any user from the same instance to moderate any of its communities, local or remote. That authority also ends at that instance. In theory it should work for remote users too, but then it’d be hard to be from lemmy.ml and moderate lemmy.world’s view of a community on lemmy.ca.
The instance that owns the community can also do whatever they want even if the post originated from elsewhere, because they own the community. That federates out.
The instance that owns the community can nominate anyone from any instance as moderator. They’re authorized to perform mod actions on behalf of the instance that owns the community, therefore it will federate out as well.
From those you can derive what would happen under any scenario involving any combinations of instances.
Sync can mark read on scroll but can’t automatically hide read content, you have to press a button to refresh with read content hidden. Would prefer automatic.
It's definitely from other instances voting on it. For example. I'm on the @kbin.social instance but I'm commenting on your post from @jeemy.jeena.net
Also, this doesn't really have to do with your point but it's interesting none-the-less, it's really hard to keep view count numbers accurate when you've got multiple servers involved. The view count is accurate and every view is being counted, but any time you look at it, it's not exactly correct. If you think about how each server might get a view count update from the server at different times, and then add the views that only it sees to the view count, and then when it goes to add it's view counts to the central count and get a new updated number there may have been dozens of other server that have updated the view count at various times between then and now.
It all gets very complicated but I think it's kind of neat that a view count number can be accurately kept track of and yet every time you look at it, it's not exactly correct.
Please don’t start with that again. PC master race is a perfectly fine name and I’m glad they didn’t change it. I’ll just have to make another account.
I see your point, but context matters. The title is saying: “PCs are a superior kind to consoles (and macs)”. Saying that a certain type of technology is superior to another is absolutely okay, even though the same can’t be said for people. Banning certain phrases in spite of the way they’re used will do more harm than good to us in the long run. Additionally, people who constantly get so worked up about the usage of these phrases and words are the same ones who grant them the enormous power they hold over us.
I wondered that when I saw whitepeopletwitter and animetitties in my feed. You can name communities anything you want here! You don’t need to use subreddit names that were created in protest of other subreddits. Just name them Tweets and World News.
If you scroll through the community bans of World News@lemmy.ml, you’ll see there’s a mod going crazy handing out months long bans for having the wrong opinion on the current conflict. Mods aren’t beholden to anyone but themselves, so if that’s how they want to mod then that’s how it’s going to be. Thankfully, Lemmy has hundreds of communities discussing the conflict so you might find better mods in one of those communities.
There’s no shadow bans. It’s possible that you’re interacting with an instance that has defederated from your home instance or vice versa. You won’t be told this. Everything just appears empty. Same if you’re banned from a community/instance. You won’t be told this unless the moderators message you.
Since I can see their content just fine it doesn’t appear to be defederation. But if they did ban me and there is no way for me to know, isn’t that a shadow ban?
What’s the instance and community you’re having problems with and I’ll tell you what’s going on. You would know you were banned by viewing your profile on that instance. You can find reasons in the modlog too if they added any.
The one I noticed it the most with is hexbear. I know they have a bad rep but I like to keep an open mind and tried a bunch of times to chime in whenever I saw one of their posts pop up on the all feed i felt I had something relevant to add to.
I also know they are a bit echo chamber-y so I assumed they might have a special hidden restriction in place for non-approved instances. I would be surprised if they actually banned my personal account because I don’t think I wrote anything they might consider controversial.
But the fact remains that (as far as I understand) my feed would not show any of their content if my instance was not federated with them, no?
This could be a long shot, but since your instance is running on a .zip TLD it could be blocked at a webserver level (the whole .zip TLD not your instance specifically) like a lot of admins did when they were launched.
Interesting, how can I see this for myself? I suppose using a client for Lemmy since day 1 made me not learn these basic things and I want to check some other instances where I suspect the same.
No idea what I did to offend but I guess I can safely block their instance from my feed then. It’s a bit annoying the user isn’t warned or straight up prevented from participating when banned.
Good mods/admins send a message along with their banning/removals. If you add /u/GregorGizeh@lemmy.zip to the end of any Lemmy domain you can see your profile on that instance. Scroll down, tap modlog and search for your name if you want a timeframe/reason.
Sure doesn’t seem like it. I went to a lot of effort to make the best of the mod API calls that are available and they go and remove a useful chunk of it. 😒
Good to know that microblog posts show up on lemmy, although it's a bit awkward that (if I'm seeing that correctly) they show up as regular threads there. I might mention them in a thread that's not as closely directed to them instead. Thanks for the reply. :)
I think they're specifically wondering if using @<username>@<instance> mention syntax will result in a notification popping up for the user on Lemmy.
I've been wondering that too (in the context of threads though) -- and if it does work, are there limitations regarding visibility between instances that people should be aware of. e.g. what happens if I @ someone in a post to a community on a lemmy server that is defederated from their home instance? Or, in a community that no one on their home server has subscribed to? Will they still get a notice?
I guess I don't really have a good mental model for how @ works on the Fediverse.
I will verify it thoroughly tomorrow, and if there is any issue on the /kbin side, I will have some free time to fix it. I'm almost certain that it used to work correctly in the past.
The number is displayed on the instance the post is on, so it doesn’t matter which instance you view it from (or if you’re not logged in at all), the number is calculated from the active users who are members of the instance you’re viewing.
lemmy_support
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.