I tried to block a couple communities from reaching my timeline and got the 500 error. These are the URLs the browser tried to visit when clicking the “block” button:

  • https://fedia.io/m/castiron@lemmy.world/block
  • https://fedia.io/m/humor@lemmy.world/block

I’ve had no problem blocking lemmy.world communies in the past. It’s just a problem today. And today I had no problem blocking communities on other Cloudflare instances (e.g. lemmy.zip) and non-CF instance lemmy.ml.

  • e-five@fedia.io
    0·
    10 months ago

    Just to follow up on this a bit I took a look at the code to try to understand why this has always been a problem in /kbin/Mbin. It seems like from cursory reading it will try to send out unsub/unfollow requests on blocking magazines/users even if you aren’t subbed or following them. Assuming this is accurate, this has some benefits to make sure the remote removes you, but has the downside of calls to the remote needing to be working in order for a block to happen. I’ll try to take a look at making it only send those unsub/unfollow requests if you currently are according to local and see if that makes sense to others