[bug] Brand new Akkoma instance receiving posts from unfollowed remote users. #374
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#374
Loading…
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
Ubuntu Server 22.04.1 LTS
Version
Akkoma v3.5.0
PostgreSQL version
14
What were you trying to do?
Just started up a new Akkoma instance (brand new database and hostname) and followed the unique and first user from my Mastodon account at mastodont.cat, with the intention of building step by step my federation.
What did you expect to happen?
I want build my federation, not be forced to receive posts from unfollowed users of unfollowed servers by the software I'm running.
What actually happened?
Look what Akkoma did, it updated the metadata of the server from the first remote follower but it started creating other servers metadata and started federating with them.
The Whole Know Network is plenty of posts from not followed remote users and not followed at all remote instances and some of them were written 6 days ago (!?)
My brand new Akkoma instance now has a lot of unknown peers that I'm not following at all or interacting with them at all.
I guess this behaviour comes from Pleroma's backend but it's really bad be unable to build the federation at will of local users.
Logs
Severity
I cannot use the software
Have you searched for this issue?
not a bug, entirely intended design, other instances know of you, so they are sending you activities - if you do not want this, enable the
Accept
MRF to restrict federation