• Maya
    6·
    4 years ago

    This would be a great candidate for federation, I think! I wonder if they could use some help getting that in place

    • moksha256
      5·
      4 years ago

      I need to learn more about it and how it works. Part of the reason I picked Lemmy over other options was the possibility of federation.

      • nutomicA
        1·
        4 years ago

        Have you read the documentation already? I’m linking to git because thats not deployed to any instance yet. If you still have any questions after reading that, just ask :)

        • moksha256
          2·
          4 years ago

          Ah thanks for the link! I was about to ask anyway. Actually the reason I even discovered this thread in the first place is that I came here looking for the thread you posted a few days ago about federation testing…then I saw this thread, replied, and forgot why I came here :D

  • Halce
    4·
    4 years ago

    Hopefully they will link to the modified source code sometime too…

    • nutomicA
      5·
      4 years ago

      FYI they legally have to publish their source code according to AGPL (the license under which Lemmy is published).

      • AgreeableLandscape
        4·
        4 years ago

        Maybe it’s time to contact them asking for the source code. I doubt they’d be very reluctant to release it since it’s a fork of an open source project anyway.

    • Maya
      1·
      4 years ago

      Is it that you want to request a copy?

    • SirLotsaLocksOP
      4·
      4 years ago

      They’re working on it, seems like its rate limited or something like that, if you refresh a couple times you might get in.

        • moksha256
          1·
          4 years ago

          Yeah sorry guys, I was blindsided by the default Lemmy rate limits and was NOT expecting front-age HN so…it was down for like an hour :(

          Should be good now though.

          • nutomicA
            1·
            4 years ago

            Are you passing X-Real-IP and X-Forwarded-For headers to the backend? We had a problem with rate limits due to that recently, the backend was counting all the requests towards the internal IP of lemmy-ui. We fixed it in our repo, but you might be missing that.

            Edit: here’s the code

            • moksha256
              2·
              4 years ago

              Thanks, looks like I’ve got that.

              FWIW, in my case, increasing the value for message in the rate_limit section of lemmy.hjson as well as removing the limit_req_zone parameter in the nginx config did the trick for yesterday’s traffic burst. I’ll probably put them back (or at least reduce them to saner values) once the spike dies down a bit.

        • abbenm
          3·
          4 years ago

          “data” is a very open ended term so it’s not super clear what you mean. It’s also a bit unclear because I don’t see why that’s especially true in this particular case. I take it you are saying some sort of precautions should be in place to stop bots from running rampant. And sure, that’s fair enough. I think that’s true of all of lemmy and any activitypub project though, and will depend on how they handle moderating.

          Is there any reason you think a site focused specifically on 5+ year old content is uniquely vulnerable to spam bots?