Testing and Bug Reports

Thanks for trying out fedtail! It is currently in active beta, and user feedback is essential to track down edge cases and fix breakages quickly.

What to Check First

Tree-view Threads. Open any conversation (click the “Thread” button or click on a post timestamp): it renders as an indented tree with comment numbers /1 /2 …. Responses your home instance never received are fetched directly from the author’s server via ActivityPub after a brief moment.
Nothing Lost. Press Esc to close lanes and leave the app running overnight. In the morning, unread badges appear on the left, and opening a lane resumes at your exact previous position.
Replies and Thread Subscriptions. Click “Subscribe” above a thread or run S #abc in the bottom command line: new comments in followed discussions show up even if you weren’t directly mentioned.
Notifications. Test system notifications via Menu ≡ → “Debugging” → “Send a test notification”.
Command Line. Focus the bottom prompt with Ctrl+L (enter ? for help) to experience Point.im-style rapid interaction.
Multiple Accounts. Right-click your avatar in the status corner to switch between isolated profiles.
Themes. Customize colors and appearance via the ui.theme key in config.toml.

If you encounter a bug or unexpected behavior:

Open an issue on GitHub Issues.
Briefly describe what you were doing, what you expected to happen, and what actually occurred. A screenshot is always helpful.
Attach the latest.log file:
- Access it via Menu ≡ → “Debugging” → “Open the log folder” (typically ~/.local/share/fedtail/<profile>/logs/).
- If running a single-binary build: enable debug logs first with debug.mode = "on" in config.toml (or launch with --debug).
- Or generate an all-in-one diagnostic bundle with:
  bash
```
python3 -m fedtail --bug-report
```
  The bundle will be placed in your home directory.