Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential directory registration consent violation #11125

Open
MrPetovan opened this issue Dec 30, 2021 · 1 comment
Open

Potential directory registration consent violation #11125

MrPetovan opened this issue Dec 30, 2021 · 1 comment
Labels
Bug Privacy Communication privacy related issues

Comments

@MrPetovan
Copy link
Collaborator

We've received a report on the Friendica Directory repository that a node meant to be private ended up registered in the official directory and as a result got overwhelmed by tens of thousands of requests from remote nodes suddenly aware of its existence.

I'm not sure how this could happen but I'd like us to make sure that this can't happen again.

@MrPetovan MrPetovan added Bug Privacy Communication privacy related issues labels Dec 30, 2021
@bkil
Copy link

bkil commented Jan 16, 2022

As a related question that is mentioned there and also came up on chat, do you know why certain Friendica installs ping other instances so aggressively (both in case of success and failure)?

Whatever the root cause (maybe their instance is spinning on an error condition) I think we should have safeguards against this, like soft-start, rate limiting, exponential backoff and sending email notifications about it channeled towards the operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Privacy Communication privacy related issues
Projects
None yet
Development

No branches or pull requests

2 participants