[–] 9 points 1 day ago (1 child)

we have just implemented an instance quarantine that will ban new users from that instance by default. we will have to review whether there are legitimate users on that instance before we consider defederation.

  • source
  • [–] 5 points 2 weeks ago (1 child)

    Hello, all alternative frontends should be available again now. Something caused the box to run out of memory, which started killing things. Had to do a hard reboot. I'll look at which services caused this to ensure we have more strict memory limits in place.

  • source
  • [–] 4 points 3 weeks ago

    Hello,

    we're currently experiencing some issues due to Lemmy containers frequently running out of file descriptors, and we haven't had the time to properly investigate the root cause yet. For the time being limits have been increased and we've already triggered multiple restarts over the past few days to reset the consumption.

  • source
  • [–] 1 point 2 months ago (1 child)

    You should persist the auth token, rate limits are by IP. They also don't exclude successful logins currently. This is a limitation in Lemmy. We have currently configured it to allow 5 logins per IP per day, but if you're lucky you can exceed that, as the consumption is not synchronized between backends at this time.

  • source
  • parent
  • context
  • [–] 3 points 2 months ago (3 children)

    Then I don't know where you're seeing Cloudflare CAPTCHAs. There shouldn't be any on any of the API paths.

    I've checked both URLs you mentioned above and only saw a Python user agent getting blocked with a browser integrity check on one of them in our CF logs. I've now added a dedicated rule to skip browser integrity checks on all API paths.

  • source
  • parent
  • context
  • [–] [S] 19 points 2 months ago

    Given the amount of false notices in the past (not to us, in general), there is absolutely a ton of automation without human oversight in there, and that was already the case long before AI.

    Companies like "CTW Anti-Piracy 2" and "Altitude Film Sales" or "Altitude Film Sales 2” (not sure if there are multiple types of Altitude Film Sales, the Lumen notice lists them with a 2 but the complaint text without) clearly don't care about the damage they do to their own reputation. In the end, most people won't care anyway and it won't meaningfully harm their reputation even if they fuck up on a significantly larger scale. It's not like they'd have to fear any legal repercussions for these false statements either, as the only part they swear under penalty of perjury is that they are authorized by the copyright holder.

  • source
  • parent
  • context
  •  

    The apparent rightsholders of the "motion picture recording of 'Coyote vs. Acme'" believe that it is in their best interest to send DMCA takedown notices to Google for free advertising of their movie.

    The company "CTW Anti-Piracy 2", acting on behalf of "Altitude Film Sales" or "Altitude Film Sales 2", believe that people should not be allowed to share trailers or news articles related to the movie 'Coyote vs. Acme' and have therefore decided to send a DMCA notice to Google to remove 19 post URLs on Lemmy.World from Google search results, as this is clearly "unauthorized distribution".

    I'm mostly mildly infuriated by them only sending this to Google, not to us, as I'd gladly take down any free advertising for them should they desire this, instead replacing it with posts about their malicious abuse of DMCA.

    I'm obviously not going to appeal this to Google, as I neither care about Google nor am I willing to spend any time on restoring their free advertising in Google results.

    Listed URLs:

    Lumen notice: https://lumendatabase.org/notices/95982857

    [–] 3 points 2 months ago (1 child)

    Hi, it's transferred back.

    I think Lemmy might still have some federation issues with that, it's unlikely to be specific to LW or .ca.

    There is a chance it would have fixed itself after some time (24h?), I'm not sure if a mod list refresh is part of the community metadata refresh.

  • source
  •  

    cross-posted from: https://lemmy.world/post/45612469

    Hello everyone,

    as of today, lemmy-federate.com has been handed over to the Fedihosting Foundation, the foundation behind Lemmy.World, PieFed.World and other Fediverse instances.

    During the migration, the table containing information about communities that were successfully subscribed already has unfortunately been lost. It looks like this is already slowly starting to get backfilled, but it will likely take some time to catch up on all communities.

    All other data has been migrated successfully, and we don't expect any other complications from this.

    The Git repository for the version running on lemmy-federate.com is now located at https://github.com/Fedihosting-Foundation-Forks/lemmy-federate. If you plan to submit pull requests, please target that repository from now on.

    Just like before, Lemmy Federate is welcoming PR contributions for for improvements, like adding PieFed support, which is something a lot of instances are interested in. If you're interested in giving this a shot, one option proposed by @iso@lemy.lol was to integrate https://github.com/aeharding/threadiverse as library for interacting with Fediverse instances to simplify the logic within Lemmy Federate for supporting more software.

    The new primary community for Lemmy Federate is !lemmyfederate@lemmy.world.

    Big thanks to @iso@lemy.lol for creating and running this service until now!

     

    Hello everyone,

    as of today, lemmy-federate.com has been handed over to the Fedihosting Foundation, the foundation behind Lemmy.World, PieFed.World and other Fediverse instances.

    During the migration, the table containing information about communities that were successfully subscribed already has unfortunately been lost. It looks like this is already slowly starting to get backfilled, but it will likely take some time to catch up on all communities.

    All other data has been migrated successfully, and we don't expect any other complications from this.

    The Git repository for the version running on lemmy-federate.com is now located at https://github.com/Fedihosting-Foundation-Forks/lemmy-federate. If you plan to submit pull requests, please target that repository from now on.

    Just like before, Lemmy Federate is welcoming PR contributions for for improvements, like adding PieFed support, which is something a lot of instances are interested in. If you're interested in giving this a shot, one option proposed by @iso@lemy.lol was to integrate https://github.com/aeharding/threadiverse as library for interacting with Fediverse instances to simplify the logic within Lemmy Federate for supporting more software.

    The new primary community for Lemmy Federate is !lemmyfederate@lemmy.world.

    Big thanks to @iso@lemy.lol for creating and running this service until now!

     

    slrpnk.net is currently experiencing an unplanned outage. the main admin has shared the following information:

    Due to what appears to be a hardware failure of the main firewall router, all servers hosting slrpnk.net and related services are currently inaccessible remotely. Sadly due to work related committments the main admin can't physically access the servers for some weeks which makes it extremely hard to fix.

    due to the instance being down, this post will currently only be visible from lemmy.world.

    see also https://feddit.org/post/13613230

    view more: next ›