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

Support Move activities #8690

Closed
Gargron opened this issue May 16, 2022 · 5 comments
Closed

Support Move activities #8690

Gargron opened this issue May 16, 2022 · 5 comments
Labels
✨Feature This adds/improves/enhances a feature 🌌Federation The Federation/ActivityPub feature

Comments

@Gargron
Copy link

Gargron commented May 16, 2022

Summary

Support ActivityPub Move activities. When the object is an account (and it is the same account as the actor) and target is an account, and the target account lists the object account in its alsoKnownAs property, local followers of the object account should unfollow that account and follow the new one automatically.

@Gargron Gargron added the ✨Feature This adds/improves/enhances a feature label May 16, 2022
@Johann150 Johann150 added the 🌌Federation The Federation/ActivityPub feature label May 16, 2022
@nbsp
Copy link
Contributor

nbsp commented May 16, 2022

for reference, this is how Pleroma respects incoming Move activities:

  • there is a user-level toggle in the settings, to allow auto-follow when following account moves
  • if enabled, when an account moves, it auto-follows the new one and sends the user a notification that the account has been migrated. as far as I can tell Pleroma does not unfollow the original account

@Gargron
Copy link
Author

Gargron commented May 16, 2022

The reason for unfollowing the old account is to dissuade people from farming and then selling followers. If you do not unfollow the old account, the original owner can keep sending out Move activities to different accounts.

@robflop
Copy link
Contributor

robflop commented May 16, 2022

That's a good idea, and a feature I've seen people talk about wanting a few times already.

Logically speaking, successive moves should form a chain of moves from accounts where there is never a pair of successive moves from the same account in a row, so I believe the unfollow restriction handles that well.

@4ioskd

This comment was marked as off-topic.

@tamaina
Copy link
Member

tamaina commented May 17, 2022

Duplicate of #5475

@tamaina tamaina marked this as a duplicate of #5475 May 17, 2022
@tamaina tamaina closed this as completed May 17, 2022
@robflop robflop mentioned this issue May 17, 2022
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨Feature This adds/improves/enhances a feature 🌌Federation The Federation/ActivityPub feature
Projects
None yet
Development

No branches or pull requests

7 participants