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

got to reboot

authored by baileytownsend.dev and committed by Tangled baa6fa30 d9bfde62

Changed files
+94 -2
public
+3 -2
index.html
··· 124 124 <div class="cow-image"> 125 125 <img src="/moo.webp" alt="Cartoon milk cow" style="max-width: 100%; max-height: 100%; object-fit: contain;"> 126 126 </div> 127 - 127 + <a href="/info.html">Idk if I trust a cow to move my atproto account to a new PDS</a> 128 128 <form x-show="!askForPlcToken" id="moover-form" @submit.prevent="await handleSubmit()"> 129 129 <!-- First section: Login credentials --> 130 130 <div class="section"> ··· 227 227 <a href="https://github.com/bluesky-social/pds/blob/main/ACCOUNT_MIGRATION.md#%EF%B8%8F-warning-%EF%B8%8F-%EF%B8%8F">here</a>) 228 228 and that the creator or host of this migration tool is not liable and will not be to help you in the 229 229 event something goes 230 - wrong. 230 + wrong. I also have read over the <a href="/info.html">extended information from PDS MOOver about account 231 + migrations.</a> 231 232 </label> 232 233 <input x-model="confirmation" type="checkbox" id="confirmation" name="confirmation" required> 233 234 </div>
+90
public/info.html
··· 1 + <!doctype html> 2 + <html lang="en"> 3 + <head> 4 + <meta charset="UTF-8"/> 5 + <link rel="icon" type="image/webp" href="/moo.webp"/> 6 + <meta property="og:description" content="ATProto account migration tool"/> 7 + <meta property="og:image" content="/moo.webp"> 8 + <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"/> 9 + <title>PDS MOOver Info</title> 10 + <link rel="stylesheet" href="/style.css"> 11 + <script src="https://unpkg.com/alpinejs" defer></script> 12 + 13 + </head> 14 + <body> 15 + <div class="container"> 16 + <h1>PDS MOOver</h1> 17 + <div class="cow-image"> 18 + <img src="/moo.webp" alt="Cartoon milk cow" style="max-width: 100%; max-height: 100%; object-fit: contain;"> 19 + </div> 20 + <div class="section" id="top"> 21 + <p> This page is to help you decide if you want to use PDS MOOver to move your ATProto(Bluesky) account to a new 22 + PDS. 23 + One way or the other. TLDR (You should still read the whole thing), at least read and follow the <a 24 + href="#precautions">precautions section</a>.</p> 25 + 26 + 27 + <section class="section" style="text-align:left"> 28 + <h2>Alpha</h2> 29 + <p>PDS MOOver is a no frills' PDS account migration tool. Meaning you will find few bells and whistles to 30 + simplify the process and hopefully allow more successful account migrations for most users. The creator 31 + or host of this tool will not be able to help you recover your account if something goes wrong. So be 32 + advised you and your PDS admin may be on your own besides helpful answers and understand the risk you 33 + take in doing an account movement. The tool has been tested, and it has worked well, but it is still 34 + important to understand this. If you follow <a 35 + href="#precautions">precautions section</a> this will also greatly increase the odds of 36 + recovering from any issues. You will still need to have some know how, but it is very possible with a 37 + backup rotation key and backup of your account. I also recommend trying out an alt before you do your 38 + main account so you know what to expect.</p> 39 + </section> 40 + 41 + 42 + <nav aria-label="Table of contents" class="section" style="text-align:left"> 43 + <h3>Table of contents</h3> 44 + <ol> 45 + <li><a href="#precautions">Precautions</a></li> 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> 54 + </ol> 55 + </nav> 56 + 57 + <section id="precautions" class="section" style="text-align:left"> 58 + <h2>Precautions</h2> 59 + <p>Before you even run PDS MOOver I STRONGLY suggest you add a rotation key and have a back up of your repo 60 + and blobs. With both of these you are not guarantee a full recovery if something goes wrong. But it will 61 + greatly increase your odds.</p> 62 + <h3>Rotation Key Backup</h3> 63 + <p>I recommend using <a href="https://atpairport.com/ticket-booth">atpairport.com</a> to add a new rotation 64 + key to your PLC. or you can follow <a href="https://whtwnd.com/bnewbold.net/3lj7jmt2ct72r">this blog 65 + post</a> to do it with goat. PDS MOOver will not use this rotation key at this time, but if 66 + something happens, it helps to have this in the meantime. 67 + <p> 68 + <h3>Repo & Blob backup</h3> 69 + 70 + <p>I also recommend taking a back up of your account with <a href="https://boat.kelinci.net/">boat</a>. You 71 + want to <a href="https://boat.kelinci.net/repo-export">"Export repository"</a> and <a 72 + href="https://boat.kelinci.net/blob-export">"Export 73 + blobs"</a>. Both just take your 74 + current handle and download those exports to your computer. These are your posts, pictures, and videos. 75 + </p> 76 + </section> 77 + 78 + 79 + <section id="help" class="section" style="text-align:left"> 80 + <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> 84 + </section> 85 + </div> 86 + 87 + </div> 88 + 89 + </body> 90 + </html>
+1
public/style.css
··· 17 17 font-weight: 500; 18 18 color: #646cff; 19 19 text-decoration: inherit; 20 + text-decoration: underline; 20 21 } 21 22 22 23 a:hover {