How to Log In
To access Smoke Signal, you’ll need to enter your ATProtocol identifier in the login form. You can use either:
Your ATProtocol Handle (recommended)
- Examples:
ngerakines.me,alice.bsky.social,john.example.com - This looks like a website address or domain name
Your DID (Decentralized Identifier)
- Example:
did:plc:cbkjy5n7bk3ax2wplmtjofq2 - This is a longer, technical identifier that starts with “did:”
Login Process
- Enter your handle or DID in the login form
- Smoke Signal will resolve your handle and redirect you to your Personal Data Server (PDS)
- Enter your password on your PDS login page
- You’ll be redirected back to Smoke Signal to complete authentication
- You can now use Smoke Signal as an authenticated user
Smoke Signal supports both did:plc and did:web identity methods.
Common Issues and Solutions
“No DIDs resolved for handle”
Problem: Smoke Signal couldn’t find your identity information.
Solution: Double-check that you’ve entered your handle correctly. Make sure there are no typos or extra spaces.
“Invalid input format”
Problem: The handle or DID you entered isn’t in the correct format.
Solutions:
- For handles: Remember that ATProtocol handles look like domain names (e.g.,
username.domain.com) - For Bluesky users: Your full handle includes the
.bsky.socialsuffix (e.g.,alice.bsky.social, not justAlice) - For DIDs: Make sure it starts with
did:followed by the method and identifier
“Failed to parse DID document”
Problem: The DID document wasn’t found or couldn’t be parsed correctly.
Solution: If you entered a DID, double-check that it’s correct. This error means the system found your DID but couldn’t properly read the associated document that contains your identity information. Try using your handle instead, or verify your DID is accurate.
Tips for Success
-
Bluesky users: Don’t forget the
.bsky.socialpart of your handle -
Custom domain users: Use your full domain (e.g.,
username.mydomain.com) -
Having trouble? Try using your DID instead of your handle, or vice versa
Need More Help?
If you’re still having trouble logging in, verify that:
- Your ATProtocol identity is set up correctly
- You can log into other ATProtocol applications (like Bluesky)
- Your PDS is accessible and functioning properly