Reported Behavior:
When login credentials for cross-posting services (e.g., Mastodon, Bluesky, etc.) become invalid (e.g., expired token, revoked access), the failure occurs silently. No error message or notification is presented to the user in the web interface or via email.
Expected Behavior:
Users should receive explicit and persistent notification of a cross-posting failure due to invalid credentials. This ensures they are aware their posts are no longer being syndicated and can take corrective action.
Suggested Resolution:
Implement a multi-channel notification system:
-
Visual Notification on Web Interface:
- Display a red dialog box upon each visit to micro.blog indicating which cross-posting service has failed.
- Include a checkbox option: “Do not show again for this service” to allow users to suppress the message if they choose.
- This dialog should require explicit user dismissal (i.e., not fading out) on first occurrence to ensure user awareness.
-
Email Notification:
-
Send a single email to the user alerting them to the cross-posting failure.
-
Email content should include:
- Name of the affected service.
- Timestamp of the failed attempt.
- Clear notice that this is the only email notification that will be sent unless the issue is resolved.
- Suggestion to retain the email until the problem is fixed.
-
Severity: Medium (impacts syndication without user awareness, breaking expected content reach)
Reproduction Steps:
- Connect a cross-posting service to a micro.blog account.
- Revoke access or allow the token to expire without refreshing.
- Publish a new post.
- Observe that the post does not appear on the connected service, and no notification is provided.
Environment:
- Web version of micro.blog
- Cross-posting services: Bluesky (in this instance - I had changed the password and forgotten to update it anywhere else)