Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

bluesky-account-migrator

Package Overview
Dependencies
Maintainers
0
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

bluesky-account-migrator - npm Package Compare versions

Comparing version 0.2.0 to 0.2.1

2

package.json
{
"name": "bluesky-account-migrator",
"version": "0.2.0",
"version": "0.2.1",
"description": "A CLI for migrating Bluesky accounts from one PDS to another.",

@@ -5,0 +5,0 @@ "repository": {

@@ -44,2 +44,17 @@ # bluesky-account-migrator

### Gotchas
#### Custom handles
You cannot submit custom handles—i.e. ones that do not end with `.bsky.social`—
as your new handle.
Bluesky's PDS implementation requires that all handles are a subdomain of the PDS
hostname.
For example, if your PDS is hosted at `pds.foo.com`, new accounts must have handles
of the form `*.pds.foo.com`.
If you already have a custom handle, you can configure it for your migrated account
after the migration.
See e.g. [this discussion](https://github.com/bluesky-social/atproto/discussions/2909)
for how to do this.
### CLI

@@ -46,0 +61,0 @@

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc