You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: