Just an explorer in the threadiverse.

  • 0 Posts
  • 61 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle
  • I don’t have a link handy, but I saw this reported before and when someone went to lemmynsfw to check the posts, they actually had been properly marked as nsfw.

    My unsubstantiated theory is that federation is working pretty crappily right now and so lots of federation messages get dropped. When a new post or comment gets dropped you don’t notice because… well… you don’t see anything. But when a post makes it through and an edit gets dropped, that can be more visible.

    So likely what’s happening is that on some small percent but medium absolute number of lemmynsfw posts, someone makes an honest mistake and fails to tag it. They either notice themselves and fix it, or a mod asks them to and they comply… so on lemmynsfw it looks right. But the federation message with the edit gets dropped by your instance, and for you and others viewing from there it forever remains sfw in error, even though all the right steps were taken. I’ve also heard mods discussing this happening with post removal moderation actions, the post gets removed on the community’s home instance, but the federation message containing the removal gets dropped by some big instance and the post blows up there anyway where the mods are actually unable to shut it down.

    I don’t think there’s anything anyone can do about this other than maybe the lemmynsfw admins tuning their federation worker counts (though they may have already and that may no longer be needed in recent Lemmy versions), or the Lemmy devs working on federation scalability so a larger percentages of federation messages get reliably delivered.


  • This isn’t a terrible idea, but it’s also important to understand single-user and tiny invite-only instances as analogous to “leechers” in the torrenting world. The federation load that an instance instance imposed on other instances depends much more on the number of communities it subscribes to than the number of active users. If a user stops using Lemmy but leaves their instance up, it’s generating federation load for no reason.

    Tiny instances are inefficient, and while it is desirable for the network to be able to scale to the point where it can reasonably support lots of them anyway, right now federation queues are backed up and messages are frequently getting dropped. Encouraging lots MORE tiny instances is probably not the efficient thing right this second. Rather, we’d want more users joining mid-sized instances that are not overloaded locally and that are making efficient use of the federation load they generate by using it to serve 100-1000 users rather than 1 or 2.


  • Liability is not binary. There is a qualitative change in risk as you transition from “I subscribed to 100 actively moderated communities that I read and am familiar with” toward “I subscribed to everything there is including the worst of the worst and I didn’t realize I was doing so and don’t look at the results”.

    Also, moderation activities federate. So even if a rogue poster does “contaminate” the actively moderated communities on a well-admin’ed instance… when those mods and admins delete the offending material they’ll automatically cleanup your instance as well. As a result, it’s the creepy crawly communities that don’t clean up or don’t want to clean up that generate the lion’s share of risk.

    Is it 100% safe to sub to well-moderated communities, no. You have to know your local laws and protect yourself. Do you do yourself favors by running lemmony? Also no. These two statements can be simultaneously true.


  • The upsides are that you control your defederation list and you’re your own admin so you’re in control of whether your instance goes down and what it’s policies are.

    The downsides are:

    • Potential privacy leaks. Your all feed is public. If its full of creepy shit and you’re the only person in your instance, it’s there cause you subscribe to creepy shit.
    • You’re in control of whether your instance stays up. Security vulnerability gets mass exploited? Your problem.
    • Potential hosting liability. Your instance mirrors what you sub and serves it to the public unauthenticated internet. If you subscribe of stuff that’s questionably legal in your jurisdiction, that liability can become yours unless you’re familiar enough with your laws to know how to protect yourself.
    • All the standard self-hosting stuff like cost and hassle.

  • Folks should not use lemmony to bootstrap their subscription count. It’s not that hard to hit lemmyverse.net and just manually sub a bunch of stuff you’re actually interested in, or to visit a big instance and browse their all feed unauthenticated.

    But if you really want to automate community bootstrapping, lemmony is the worst of the scripts that doit because it defaults to subscribing to EVERYTHING, including all the porn, piracy, and hate communities on the most absent-admin’ed under-modded instances in the lemmyverse. Then your instance will mirror all those questionably legal communities and re-serve them to the public unauthenticated internet, creating hosting liability for you. Not to mention being a bad fediverse citizen and creating massive amounts of federation load on the instances forwarding you posts and comments from 20k communities that you don’t read.

    These two subscription bootstrapping scripts limit you to top subs by default… So you’re more likely to be in well-modded territory and just the number of subs is smaller you you can review them and back out of anything sketchy. Subscriber-bot’s docs do a good job of explaining the risks and problems of mass-subscription so you know what you’re getting into.


  • I mean, the mods are being chill about it so far. If they start dropping bans, the users trying to turn this into a support community won’t actually be users anymore and they can go create asklemmyaboutsupportbutalsootherstuffwhatever and mod it themselves. In this respect, lemmy communities differ from language evolution.

    For my part, I’m here for a discussion sub. I participate heavily in lemmy support communities, but that’s not why I joined here.



  • Do you realize that you’re advising OP to ignore a mod (in a reply to said mod) of this community who is being perfectly chill while informing OP about the published rule 3, which the community mods have stated they’re being relaxed about while so many new Lemmings are joining, but not giving up on forever?

    Rule 3 is quoted below, and helpfully directs people to active communities that are dedicated to support:

    Not regarding using or support for Lemmy: context, find help in the list of support alternatives below


  • Yeah, fair. I feel like I recall them mentioning an auto-updater that they hadn’t yet set up but planned to.

    Folks that want to get faster updates can certainly use the voyager Dev’s instance… it’s the source after all. For someone like me that doesn’t want to enter their credentials into a 3rd party proxy, I’ve been testing world install of voyager alongside Jerboa and Liftoff and it’s been a solid option.



  • Try these steps:

    1. Logout via Home -> Hamburger menu -> accounts are at the top, click there and sign out. Try signing in, did you win?
    2. If not, sign out again then long-press the app icon from your android launcher screen and select App Info, or find another way to get to the android settings screen for Jerboa and Clear Cache and Clear Storage. Try to log in again, did you win?
    3. If not, sign out again and sign back in. Did you win?
    4. If not, cry because I’m stumped. You could also try liftoff, which if you weren’t logged in prior to yesterday shouldn’t have a cached broken session. Or install the PWA from lemmy.world via Firefox mobile. Or use the brand new Voyager setup at m.lemmy.world again as a PWA via Firefox mobile. Of those, I like Jerboa and liftoff best.