# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 13
# self = https://watcher.sour.is/conv/m2ecxva
@prologic So what do you recommend regarding migration of data from one pod to another?
Basically I'd like to build an "idiot proof" way of migrating an account/feed from one pod to another. So I'm thinking you'd go to your new pod's Settings page, click "Import Feed" or something. Then you'd be prompted to enter a unique, hard to guess and brute force string to your old feed, your new pod will verify this, if they match, will suck that feed down and merge it with your ned feed on your new pod.
Basically I'd like to build an "idiot proof" way of migrating an account/feed from one pod to another. So I'm thinking you'd go to your new pod's Settings page, click "Import Feed" or something. Then you'd be prompted to enter a unique, hard to guess and brute force string to your old feed, your new pod will verify this, if they match, will suck that feed down and merge it with your ned feed on your new pod.
In addition as mentioned in https://twtxt.net/twt/znxnqqq I'd also like to add a "Moved To" feature to the account deletion process (_user offboarding_) that lets a user effectively delete their account on one pod (_because they've migrated to another pod_) and set a 304 Moved Permanently redirect in place.
Thoughts? cc @lyse @jlj (_and any other multi-user pod owners_)
In addition as mentioned in https://twtxt.net/twt/znxnqqq I'd also like to add a "Moved To" feature to the account deletion process (_user offboarding_) that lets a user effectively delete their account on one pod (_because they've migrated to another pod_) and set a 304 Moved Permanently redirect in place.\n\nThoughts? cc @lyse @jlj (_and any other multi-user pod owners_)
In addition as mentioned in https://twtxt.net/twt/znxnqqq I'd also like to add a "Moved To" feature to the account deletion process (_user offboarding_) that lets a user effectively delete their account on one pod (_because they've migrated to another pod_) and set a 304 Moved Permanently redirect in place.
Thoughts? cc @lyse @jlj (_and any other multi-user pod owners_)
@prologic Moved Permanently is HTTP 301. Maybe go for the newer and clearer HTTP 308 Permanent Redirect. If I recall correctly the older status codes have the confusion whether to switch the HTTP verb or not, the new ones clarify that. Although in this case that should not be any problem since we're just GETting anyways. Other than that, your proposal sounds quite nice! The question is, how could one even delete this forward once not needed any more? This migration should obviously also work when not moving to yarnd but some different system (e.g. just an Nginx). So not sure how that would work then with this proposal.
@lyse The pods can safely remove it over time as requests for the old uri approach zero
@lyse The pods can safely remove it over time as requests for the old uri approach zero
@prologic I mean if the former user decides to leave the twxt world entirely for example. Or just wants to get rid of the forward for whatever reason.
@prologic I like the idea with the request counter approaching or reaching zero, though. Not sure what time to chose here.