Whoever is in charge of that instance, STOP.
It’s an instance that crossposts posts from Reddit, except it also makes a new user for each Reddit account it came from. So if /u/hello123 made a post, it makes that post under a new account called hello123. That makes it impossible to block posting bots.
Not only that, it makes posts look like they’re posted by real people, with many question and text posts being copied as well. I was very confused as to what these posts were until I realized they’re crossposts.
Examples:
https://lemm.ee/u/pocalyuko@alien.top
https://lemm.ee/u/ItzMeRocket@alien.top
https://lemm.ee/u/CaptainCapp-n@alien.top
I strongly believe Lemmy isn’t the place for mirroring content from other websites. You can host your own alternate Reddit frontend like LibReddit, there’s no reason to spam the posts to everyone using Lemmy just because 5 people asked for it. Not to mention there are already enough instances mirroring posts, this is getting obnoxious.
I’m from lemmy.ca too, and while I’m conflicted about the project, I’d rather limit defederation unless it’s about something very clearcut
After v0.19 drops, users can block instances which should fix the problem for everyone that might want it gone
Alien.top is a spam instance. This is as “clearcut” a reason to defederate as it gets.
While it likely is spam for the majority of users, I imagine the mods are looking at de-federating an instance that fulfills a specific need for a small number (keeping alien.top users updated on reddit). Because of that, it will likely have a bit of push back to de-federate entirely vs. a request to create the ability to block users/platforms. Think of it like newsletters, we need the ability to unsubscribe/block them, but we shouldn’t necessarily ban them outright.
Spam implies it’s useless but it seems I can read my content from Reddit on that instance? While also staying on a single app and getting my regular lemmy threads.
Not sure why it’s a problem other than resource intensity, if the users have the option to block an instance as a whole it’s fine.
I don’t agree with them creating bot accounts and commenting on other instances posts though. Everything should be maintained within the instance.
Not sure why you added preserving metadata like username, pfp and timestamp(I guess ts in preserved too) and called it “creating bot accounts”. And as I understand bridging communities on other instances is opt-in.
I will say that as it is 0.19 isn’t going to be the holy Grail people think it is because the instance level blocking only affects communities hosted on those instances it does not hide users from those instances. So for instance is that are still Federated to hexbear it’s not going to remove the hexbear user spam and it likely won’t help in cases like this either.
It’ll mainly help in cases where the communities on the instance and not the users are the problem. Things like the NSFW instance.
If this is true then I indeed misunderstood v0.19
All I want is to be able to block an instance completely as a user. How hard can this be? I really had my hopes up for v0.19. This needs to be built into Lemmy asap because the idiocy of some instances is getting on my nerves hardcore. I mean, why not go back to reddit if I have to take shit anyway? At least I know the communities are larger over there and if I need to suffer bullshit then by all means, I’ll suffer over there. This is not good for Lemmy tbh…
How can you as user block votes from one instance?