[bug] Remote instances that reuse domains and nicknames cause Akkoma to generate excessive requests #419
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#419
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
NixOS 22.11
Version
3.5.0
PostgreSQL version
15.1
What were you trying to do?
A remote instance, at some point in early January, has installed Mastodon (Hometown fork) on a domain that previous held a Misskey install, with no migration. At least one nickname (webfinger address) was reused: it used to point to a Misskey user, and now it is pointing to a Hometown user.
My instance was aware of the remote instance prior to the reinstall. My
instances
table includes an entry for the instance with cached nodeinfo data that mentions Misskey. Myusers
table also includes two different rows for the user.What did you expect to happen?
I expected things to break, I did not expect them to break as terribly.
What actually happened?
At some point my instance apparently tried to refresh its data about the remote user. It appears to have hit a database constraint related to the nickname being duplicated. It then continued to attempt to fetch the data, apparently multiple times per second, apparently with outgoing Web traffic for every attempt. It only stopped after a VM reboot (for unrelated reasons).
Logs
I do not have logs of this starting, since this has produced dozens of lines per second for hours and earlier logs got pruned.
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
this should be fixed