When I started using SailfishOS few weeks ago, I noticed there was not a single Mastodon client available (on Jolla store, per my lame search attempt back then). I was expecting this ecosystem having at least 7 of them. So here’s my piece.
I have to be frank with you all, I make it mainly for myself, to have one client that’s just perfect for me. So while I might be keen to work on features you need, I might also skip them with not much explanation.
Warning: this project is in usable state, but it’s fresh and unpolished. Many features are missing, I can expect a lot of bugs appearing. If you find some bugs please report them on Codefloe or here in this thread.
I have multiple Mastodon accounts, so as you probably guessed, this is optimized for this use case. I might do some improvements in the future for a single-account users, but this is low in my backlog of stuff I want to implement.
Stores
At the moment it’s only on Storeman. I’ll add it to official Jolla store once this project reaches v1.0.0.
Commitment
I intend to develop it until v1.0.0 which will be a version when I consider if feature complete. Then I will maintain it as long as I use SFOS personally.
Build
I build it on Codefloe.com CI/CD, those rpms are then uploaded to the repository releases and manually to OpenRepos.net. I do not build it on my own machine.
What it can
- Log in, log out. Multi accounts.
- See the feed, open threads.
- Reply, quote boosts, boosts.
- Composer with @mention picker, polls, images with alt tags.
- See your profile, edit your own posts.
- Like
Backlog
- Bookmark.
- Profile gets a menu tab with: my likes, my bookmarks.
- Search with your own instance and masto.kukei.eu API.
- Notifications (with Foghorn?) - currently slowly cooking this one.
Known missing features, low in priorities
- Keeping auth tokens in SFOS secrets keychain, I tried it it exploded the whole project and usability was also questionable (like e.g. SFOS asks for permissions on each boot which is insane).
- UX focused on lists.
- Pushing boost, like and other buttons into post list (feed) - I want myself (and my users) to think twice before reacting on posts, so this extra tap to open a post in an original thread is a way for a timeout, this habit saved me few times of liking or boosting something I took out of context, like some answer that looked worth boosting but meant something completely different when seeing the whole discussion.
Credits
I tested following apps while working on it, I did not check any source code of any of those apps, nor my LLM reached it (actively, I suspect they might be in models training sets).
Tooter
Much respect, it is really cool, but no multi-accounts.
Meridon
Cool.
AI Disclaimer
AI Disclaimer follows the /c/selfhosted guidelines. All communication I do, including this forum post, I write by myself, with no LLM involvement whatsoever.
Design - architecture, system design
App icon generated, UI/UX design made by human. No AI involved.
Implementation - production code
~90% code generation by LLM model (OpenCode + Ollama Cloud, Claude Code). All code reviewed by human. Some code edited by human.
Testing - writing tests, test plans, and QA.
This project follows YOLO test pattern as unit testing setup on SFOS SDK is not there yet.
Documentation - Docs, comments, README, change logs
This README is fully written by human. Commit messages made by human, changelog is generated during CI/CD based on commit messages.
Comments in code mostly made by LLM.
Review - Code review and pull request feedback
Code review always by human. In some cases an LLM model might do a review too to find the gaps I didn’t find.
From time to time LLM is asked to check the overall code to find some bugs or potential problems.
Deployment - CI/CD configuration.
Made by LLM with human editing. No human should write yaml files.
