Client side atproto account migrator in your web browser, along with services for backups and adversarial migrations.

info

authored by baileytownsend.dev and committed by Tangled 00c7e032 baa6fa30

Changed files
+51 -11
public
+51 -11
public/info.html
··· 44 44 <ol> 45 45 <li><a href="#precautions">Precautions</a></li> 46 46 <li><a href="#help">!!!!!HELP!!!!!</a></li> 47 - 48 - <li><a href="#prep">Before you begin (recommended prep)</a></li> 49 - <li><a href="#how-it-works">How the migration works</a></li> 50 - <li><a href="#retries">Retries and partial runs</a></li> 51 - <li><a href="#performance">Why it can be slow</a></li> 52 - <li><a href="#liability">Liability and support</a></li> 53 - <li><a href="#devs">For developers</a></li> 47 + <li><a href="#why">Why doesn't PDS MOOver have xyz?</a></li> 48 + <li><a href="#done">Alright account migrated, now what?</a></li> 49 + <li><a href="#slow">Why is it so SLOW?</a></li> 50 + <li><a href="#open-source">Can I check out the code anywhere?</a></li> 54 51 </ol> 55 52 </nav> 56 53 ··· 75 72 </p> 76 73 </section> 77 74 78 - 79 75 <section id="help" class="section" style="text-align:left"> 80 76 <h2>!!!!!HELP!!!!!</h2> 81 - If you're having issues with PDS MOOver first of all, I'm very sorry. I have tested this to the best of my 82 - ability, but PDS migrations do come with risks. I would recommend getting with the owner of the PDS and 83 - seeing where the account stands with tools like <a href="https://pdsls.dev">pdsls</a> 77 + <p>If you're having issues with PDS MOOver first of all, I'm very sorry. I have tested this to the best of 78 + my 79 + ability, but PDS migrations do come with risks. I would recommend getting with the owner of the PDS and 80 + seeing where the account stands with tools like <a href="https://pdsls.dev">pdsls</a>.</p> 81 + 82 + <p> The tool is designed to be able to be re ran IF you set the Advance Options flags.For example, lets say 83 + if it created the account, repo is there but some blobs are missing. You can uncheck everything but 84 + "Migrate Missing Blobs", "Migrate Prefs", and "Migrate PLC record" and it will pick up after the account 85 + repo migration. It is odd in the fact that all the fields are required. That's just to cut down on logic 86 + to hopefully cut down on bugs. If you don't ever see the "Please enter your PLC Token" you can just 87 + forget about it and call it a day if it's too much. Your old account is still active and working.</p> 88 + </section> 89 + 90 + <section id="why" class="section" style="text-align:left"> 91 + <h2>Why doesn't PDS MOOver have xyz?</h2> 92 + <p>PDS MOOver was designed to pretty much be the goat account migration with a UI. Like in this <a 93 + href="https://whtwnd.com/bnewbold.net/3l5ii332pf32u"> post</a>. Keeping it simple and hard fails if 94 + anything 95 + goes wrong 96 + to 97 + hopefully cover most use cases. Rule of thumb if reading the goat migration blog post makes you nervous, 98 + you may not want to move to a new PDS with PDS MOOver till it has been battle tested.</p> 99 + </section> 100 + 101 + <section id="done" class="section" style="text-align:left"> 102 + <h2>Alright account migrated, now what?</h2> 103 + <p>Welcome to your new PDS! I recommend now re running the steps in <a 104 + href="#precautions">precautions section</a> along with keeping regular backups of your account. With 105 + the rotation key and backups you can almost always recover even if your new PDS disappears overnight. It 106 + may take a bit of know how, but it is very possible.</p> 107 + </section> 108 + 109 + <section id="slow" class="section" style="text-align:left"> 110 + <h2>Why is it so SLOW?</h2> 111 + <p>Everything happens client side, and the blob uploads take a while. Nothing runs in parallel. Blob uploads 112 + happen one at a time; once one is done, the next goes. This is done just to keep it as simple as 113 + possible and to hopefully limit the chance of failures on uploads. My personal account takes about 114 + 20-30ish mins to move with 1,700ish blobs at 800mb on a 1gig internet connection.</p> 115 + </section> 116 + 117 + <section id="open-source" class="section" style="text-align:left"> 118 + <h2>Alright account migrated, now what?</h2> 119 + <p>Yep! PDS MOOver is 100% open source and can find the code on <a 120 + href="https://tangled.sh/@baileytownsend.dev/pds-moover">tangled.sh</a>. Also, if you're a 121 + developer, 122 + and you want to fork the code for a new UI. PDS MOOver's logic is all in one js file. Just take it and 123 + its dependencies and have at it.</p> 84 124 </section> 85 125 </div> 86 126