You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 10, 2025. It is now read-only.
I'm not sure that this is a "bug", per se, but probably worth noting for anyone getting authentication errors upon import.
When populating the .env file, the BLUESKY_USERNAME= requires your username. When you actually login to Bluesky, you're able to use your basic username by itself (i.e. - Cinqio, PoorOldLu, etc.), but running the import will give an authentication error. Instead, use the full Bluesky profile name (cinqio.bsky.social) or use the email address tied to your Bluesky account.
I'm not sure that this is a "bug", per se, but probably worth noting for anyone getting authentication errors upon import.
When populating the .env file, the BLUESKY_USERNAME= requires your username. When you actually login to Bluesky, you're able to use your basic username by itself (i.e. - Cinqio, PoorOldLu, etc.), but running the import will give an authentication error. Instead, use the full Bluesky profile name (cinqio.bsky.social) or use the email address tied to your Bluesky account.
I hope that helps someone else☺