• 0 Posts
  • 188 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle



  • Think of it this way, when you make a post that post will be automatically distributed by your server to everyone who is a subscriber, depending on the type of platform that could mean subscriber to the community, or it could mean to your user account in the case of things like Mastodon. When the post is received it will be copied and re-hosted on all the servers which have subscribers.

    Exceptions to this happening are in the case of a user being banned or server being defederated, in which case the request is denied and the post isn’t re-hosted by the instance with the ban or defederation against the user or server who made the post. It should be known that bans and defederation only typically happen in extreme cases such as defending against spam, hate speech, or abusive users.

    Might be a more simple explanation but I’m trying to keep it more simple since it helps people better understand the process.



  • Couldn’t disagree with you more, the thing about federation is that it isn’t viewing the content on the server it was posted on, it is crossposting it to all other federated servers. That means you are when federating remote content you are literally platforming it. That also means you are liable for it if it’s objectionable or illegal content. So being able to not accept those crossposts is important. Honestly defederation and limited federation are not as big of issues as you and others think they are, you can ignore the majority of the defederated servers and it’ll be fine, the issue comes when people want the world and aren’t entitles to have it, like I said in my other comment.

    Email is an example of a successful federated platform and it barely has defederation support.

    You are insanely naive for saying this. If you’d used non-corporate email servers, like the much smaller email providers out there (which are basically extinct at this point) you’d know just how wrong this actually is. Most smaller email providers out there are blocked or limited by the big ones and the ones that are blocked your mail will never reach the inboxes of people on the big servers, not even the spam folders on those servers. They won’t bounce it back to you either, so it’ll just go into the void.

    Most email these days is used primarily by the all mighty trinity: Gmail, Outlook, and Yahoo, and a Few on Hotmail and AOL and while there are a few smaller companies out there like Proton, when it comes to something that isn’t a company or is self-hosted you can expect a lot of problems with domains being blacklisted, IPs being blacklisted, or both. And it’s actually much worse than defederation.

    Perhaps that is how at least the non-threaded fediverse should work… However, that would also mean that some instance hosting heinous shit would keep being visible to everyone. It’s a tricky problem.

    You’re beginning to realize why the decision to limit spam and illegal shit was chosen over catering to the people who want the whole federated world instead of what they’re allowed access to. Ultimately it is better for everyone if the depraved shit and spam gets blocked, than it is for the people who want the whole world to have their way. If you want the world, go to Nostr, you’ll learn why most people do not want the world.




  • I don’t know if I would agree with that assessment entirely, yes Lemmy.world has the same starting Jerk to not jerk ratio. However on Lemmy.world the amount of jerks who aren’t banned is higher than instances like blahaj.zone, dbzer0, or pawb.social. So there are more jerks on Lemmy.world, not because it attracts more jerks or has more users but also because it doesn’t ban them as often as other instances do.

    I’m using jerk kind of loosely but I’ll clarify because people will think I’m trying to say someone should be banned for a rude moment but I’m not. When I say jerk, what I really mean is alt-right troll, transphobe, sealioner, climate-denier, etc. Someone who isn’t obvious enough to be caught as a spammer would but who is still bad for the community.


  • Lemmy.world has kind of awful moderation, which means people who are trolls or bad actors have lived here for a very long time despite multiple reports. It was only recently that Linkerbaan (the most notorious one of all) was banned, and it took a thread complaining about bans in [email protected] and dbzer0 admins messaging them to get their attention.

    There are other people here like that which never receive permanent bans for consistently horrible behavior. It’s not great, and while I don’t agree with Beehaw’s decision to defederate over it I do think that things could be better. It does degrade user experience to have known trolls and assholes running wild and only getting a slap on the wrist when they do something horrible.






  • I don’t know how it is on mbin but on Lemmy the best thing to do is message the admins directly, and not bother reporting. This is because Lemmy’s developers give way to much credit to the legitimacy of forum moderators and do not allow a way for reports to only be sent to administrators, meaning that community mods like these can easily dismiss reports before they are seen by admins. So best thing to do is message them directly at the current time.


  • Something I didn’t consider when answering earlier is that even if Firefox did have good RAM usage limiting built-in I probably still wouldn’t use it or recommend it, because one of Firefox’s biggest problems is that it leaks. And memory leaks will not be negated by Firefox’s built-in RAM limiter but they will be by systemd’s (or anything else you might be using instead) Firefox would still crash in the event of a leak but it’s still better than it taking gnome or other apps with it, or freezing your system entirely.




  • No, it just limits the amount of RAM that Firefox (or whatever other application you launch with these parameters) will see.

    A few Firefox tabs may crash occasionally as a side effect. And obviously if Firefox eats up all of the 8GB it’s allocated it may crash itself though usually it doesn’t and tabs will crash before the browser crashes.


  • That’s good to know, I don’t know how well it would work though I feel like I enabled something about closing background tabs to reduce memory load (it might have been what you said, it might have been something else I don’t really remember) and it helped a little bit but it still ended up chewing up a lot of memory.

    Setting the limit though did help immediately. And stop the overconsumption problems, occasionally a couple of tabs crash here and there but it doesn’t freeze or worse cause other apps to slow down and freeze. Which did happen before.