[fediverse.blog]Investigate and experiment how to keep federation while moving instance #9

Open
opened 3 years ago by KitaitiMakoto · 1 comments
Owner

Setting up

  1. Run plume01, plume02, mastodon01 and make federate each other
  2. Post, comment to, fav and reblog some articles
  3. Move plume01 to another server
  4. Change DNS record and wait for update
  5. Interact with new server

Check points

  • Previous messages and images are shown?
  • Can comment? From remote?
  • Creating, updating, deleting posts are federated?
  • Mentions in posts are federated?
  • plume02's post federated to plume01?
Setting up 1. Run plume01, plume02, mastodon01 and make federate each other 1. Post, comment to, fav and reblog some articles 1. Move plume01 to another server 1. Change DNS record and wait for update 1. Interact with new server Check points * Previous messages and images are shown? * Can comment? From remote? * Creating, updating, deleting posts are federated? * Mentions in posts are federated? * plume02's post federated to plume01?
Poster
Owner

https://nya.social/notes/817b45b6dc5f89f56536a9b6

@KitaitiMakoto@bookwor.ms all three support an outgoing queue, so failed requests will be retried later. the queue lifetime varies, so it depends on each instance's settings, but if you're only down an hour or two, you can generally expect to not lose anything. it can take a few hours for posts to come in again (just whenever it decides to retry) and the timeline may appear with old posts at the top while it's catching up

https://nya.social/notes/817b45b6dc5f89f56536a9b6 > @KitaitiMakoto@bookwor.ms all three support an outgoing queue, so failed requests will be retried later. the queue lifetime varies, so it depends on each instance's settings, but if you're only down an hour or two, you can generally expect to not lose anything. it can take a few hours for posts to come in again (just whenever it decides to retry) and the timeline may appear with old posts at the top while it's catching up
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: Plume/infra#9
Loading…
There is no content yet.