[bug] followers-only posts being delivered to domain with no followers #546

New issue

Open

opened 2023-05-25 23:51:40 +00:00 by a · 0 comments

a commented

2023-05-25 23:51:40 +00:00

Your setup

OTP

Extra details

pl.nulled.red

Version

3.7.1-0-gfef4bae

PostgreSQL version

idk

What were you trying to do?

make a followers-only post

What did you expect to happen?

post goes to my followers only

What actually happened?

a non-follower replies, from an instance where no one follows me

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

etc

<trwnh> under what circumstance might a private post be delivered to an instance without any followers on that instance
<trwnh> i had someone from berserker.town reply to a privpost and they don't follow me
<trwnh> no one else does either
<trwnh> in fact i have berserker.town domain-blocked
<trwnh> so it seems like the backend is delivering to berserker.town for some reason, maybe there was a follow at some point in the past before i domain-blocked them?
<trwnh> but even though the follow relationships appear to be severed, they are still getting my followers-only posts
<trwnh> i domain-blocked them as a user, they're not in the reject list
<trwnh> i'm suspecting a bug in the user "block this domain" logic because the only scenario that makes sense is that someone followed me, i domain-blocked their instance, and akkoma destroyed the follow relationship but is still sending my posts to the user-blocked instance

basically the situation variables are like this:

instance.example/someone follows you (assumed to have happened in the past)
you domain-block instance.example
someone's profile does not show them as following (anymore? via the API only?)
you make a followers-only post and someone replies, implying that your instance delivered your followers-only post to instance.example, and instance.example might still think someone is following you

### Your setup OTP ### Extra details pl.nulled.red ### Version 3.7.1-0-gfef4bae ### PostgreSQL version idk ### What were you trying to do? make a followers-only post ### What did you expect to happen? post goes to my followers only ### What actually happened? a non-follower replies, from an instance where no one follows me ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere. ### etc ```text <trwnh> under what circumstance might a private post be delivered to an instance without any followers on that instance <trwnh> i had someone from berserker.town reply to a privpost and they don't follow me <trwnh> no one else does either <trwnh> in fact i have berserker.town domain-blocked <trwnh> so it seems like the backend is delivering to berserker.town for some reason, maybe there was a follow at some point in the past before i domain-blocked them? <trwnh> but even though the follow relationships appear to be severed, they are still getting my followers-only posts <trwnh> i domain-blocked them as a user, they're not in the reject list <trwnh> i'm suspecting a bug in the user "block this domain" logic because the only scenario that makes sense is that someone followed me, i domain-blocked their instance, and akkoma destroyed the follow relationship but is still sending my posts to the user-blocked instance ``` basically the situation variables are like this: - `instance.example`/`someone` follows you (assumed to have happened in the past) - `you` domain-block `instance.example` - `someone`'s profile does not show them as following (anymore? via the API only?) - `you` make a followers-only post and `someone` replies, implying that `your instance` delivered your followers-only post to `instance.example`, and `instance.example` might still think `someone` is following `you`

a added the

bug

label 2023-05-25 23:51:40 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#546

No description provided.