TryGhost / TryGhost/ActivityPub
Provide a way to reverse ActivityPub follower migration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 237
- Forks
- 35
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 60
Description
Ghost’s account migration settings say that migrating followers is “harmless and reversible.”
I relied on that statement when I moved my ActivityPub followers to my Ghost publication. However, I can’t find any setting or documentation that explains how to reverse the migration or move those followers out of Ghost.
There is an option to migrate followers into Ghost, but no corresponding outbound migration option. ActivityPub may support moving followers again at the protocol level, but that does not make the process reversible for Ghost users if Ghost provides no way to initiate it.
Could Ghost please:
- Add a way to migrate followers from Ghost to another ActivityPub account
- Document how to reverse an existing migration safely
- Explain what “harmless and reversible” currently means
- Provide guidance for people who have already relied on that statement
- Change the settings language if migration cannot presently be reversed through Ghost
I’m hesitant to disable Social Web or change the account because I don’t know whether that could make the followers more difficult to recover.
If Ghost’s own settings describe this operation as harmless and reversible, users should be given an actual, supported way to reverse it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Ghost’s account migration settings and the existing ActivityPub follower migration flow. Determine whether Ghost has a supported outbound migration path and what the “harmless and reversible” wording currently guarantees. Done means the reverse process, safety guidance, and settings language are consistent and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100