I followed some popular communities from a Mastodon server ages ago, and then unsubscribed when I was satisfied that it was working.

However, lemmy seems to have some problem with the way Mastodon sends an ‘Undo/Follow’, so it’s still been sending traffic ever since. Recreating it on a lemmy server I booted, journalctl shows this error:

WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Unknown:
0: lemmy_apub::insert_received_activity
        with ap_id=Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("activitypub.academy")), port: None, path: "/e97071d0-54e4-4527-9865-e44cf1a55970", query: None, fragment: None }
          at crates/apub/src/lib.rs:191
1: lemmy_apub::activities::following::follow::verify
          at crates/apub/src/activities/following/follow.rs:78
2: lemmy_apub::activities::following::undo_follow::verify
          at crates/apub/src/activities/following/undo_follow.rs:66
3: lemmy_apub::http::community::community_inbox
          at crates/apub/src/http/community.rs:50
4: lemmy_server::root_span_builder::HTTP request
        with http.method=POST http.scheme="https" http.host=38ec-77-100-144-83.ngrok-free.app http.target=/c/test1/inbox otel.kind="server" request_id=70c556c1-9f2c-421d-90f3-826e9d12879c http.status_code=400 otel.status_code="OK"
          at src/root_span_builder.rs:16

I reconfigured the JSON that Mastodon sends to be more like a Lemmy one, signed the http request with a new set of keys, and sent it via a command-line script. Technically, this works, in that I can use the script to subscribe and unsubscribe from lemmy communities. Unfortunately, it doesn’t work with the private key for the old Mastodon user and lemmy.ml (which rejects the http requests). I don’t know why, but it has stalled my attempts to unsubscribe from my side.

As you’re likely aware, lemmy.ml has bouts of sending out an absolute firehose of info at times, and it’s a waste of your resources sending them to me (who’s resorted to 403ing everything, so they don’t overwhelm the ActivityPub server I’m building).

So, if possible, can someone have look what a user from lemmon.website is still subscribed to (memes and asklemmy, certainly) and unsubscribe them please?

I can provide some credentials on lemmon.website if you require.

Thanks.

    • freamonOPEnglish
      2•1 year ago

      Reading your link, a defederation is just blocking the traffic from my end, which I’m already doing by having nginx reject everything with a 403 code.

      I’m hoping that I can stop the traffic from being sent in the first place.

      • @breadsmasherEnglish
        2•1 year ago

        Are you using anything like cloudflare, something with an external firewall? You could block incoming requests there before it reached your backend?

        • freamonOPEnglish
          1•1 year ago

          I’m not no, just the cheapest VPS I could find.

          The requests never reach my backend, 'cos they’re blocked by nginx rather than it reverse-proxying them like it does for the traffic I’m interested in. So, thankfully for my poorly-programmed backend, it doesn’t have to process the deluge from lemmy.ml. It’s a bit of blunt instrument though, 'cos it just blocks everything. In the future, there’s likely to be some quieter communities on lemmy.ml I’d like, but right now, I can’t follow them without also getting everything from ‘memes’ and ‘asklemmy’.

          I’m also thinking about how lemmy seems to get behind on it’s federation activities, and it would maybe help if they didn’t generate them in the first place for recipients who don’t want them.

          I’m essentially asking someone to stop coming to my house and knocking on my door. I could ignore the knocks, or put a sign up, or employ someone to stand in my garden and stop them. These are strategies to cope with the problem, but I think the real solution would be if they just stopped coming.