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
Users should be able to have twitter-to-bsky connect to their Bluesky accounts either:
after asking for their passwords for them on the command line* using a secure entry field or
using some kind of Bluesky API token
instead of having to provide the program with their user name and password in a plain text file. Storing passwords in plain text files is always a bad idea.
* twitter-to-bsky should also prompt users for their account user names at the command line if they haven't provided them via configuration file.
The text was updated successfully, but these errors were encountered:
You can use an app password and that should alleviate most of your concerns. As this is only intended to be run once to import your tweets, I don't think there's much need to make this more complicated with other functionality
You can use an app password and that should alleviate most of your concerns. As this is only intended to be run once to import your tweets, I don't think there's much need to make this more complicated with other functionality
Users should be able to have twitter-to-bsky connect to their Bluesky accounts either:
instead of having to provide the program with their user name and password in a plain text file. Storing passwords in plain text files is always a bad idea.
* twitter-to-bsky should also prompt users for their account user names at the command line if they haven't provided them via configuration file.
The text was updated successfully, but these errors were encountered: