Greetings!
After the NextCloud open sourcing, we continued open sourcing by published Sailfish Accounts components and Sailfish svg2png converter to GitHub. Please read also the fortnight newsletter Sailfish Community News, 13th November 2025 - xdg-shell.
Find repositories here
Please report issues to GitHub Issues (feel free use Forum Bugs as well).
Happy hacking.
Kind regards,
Jolla Crew
Thank you @Jolla ! (20 characters)
Brilliant!
With Accounts and the implementations in the Nextcloud repo (as well as libsocial and friends) I believe we have now all the various components available to build and use third-party social account support.
Fediverse integration here we come?
Almost, I would say. Please, correct me if I’m wrong, but as far as I understand what is in sailfish-components-accounts, it contains UI components to list providers and to list created accounts on device.
If we add a new provider, and want to enable the creation of accounts for this provider, and be integrated in the settings, the elements for this account creation are still closed sources. I mean, we’ll have to create QML pages for this specific new provider (obviously), but we can’t put these new pages in an open-source repo that will make them available in the setting application.
This is not an issue, I think, when adding new providers, one can still use a stand-alone application to interact with the account system (assuming the right sailjail authorisations). And the newly open-sourced components aleviate most of the binding work with libaccounts-qt. So yeh, it’s nice ;- )
Ah, but here the open-sourced Nextcloud thing can come to the rescue:
sailfish-account-nextcloud/tree/main/settings/accounts
can be used as a template for these components. Of course, something created with these will not be able to get distributed via Harbour (for several reasons) but that’s a different issue.
The NextCloud repository has an excellent example (rather complete) for Settings app integration under settings/accounts. That example uses Sailfish Accounts components. Surely, settings pages can be in open source repository. Given that the sw component license is good, we could surely take it from there to the platform offering (having a mirror in between). Further, we can create an account repository under Sailfish OS · GitHub if you like so. All the bells and whistles needed for account integration you can find from the NextCloud repository.
Cool.
I have a somewhat working prototype of Integration of GitHub (with Event Feed of its Notifications) with Sailfish OS.
If I find time to get it into a submittable state, I shall take you up on that repo creation offer.
I didn’t look close enough to the NextCloud sources. That’s nice. So you’re right the path is complete then. I’m eager to see what will come out of it.
@rainemak FYI, both repos have issues enabled on github - I believe you’d prefer the global issue repo to be used?
ssu ar github-cli https://cli.github.com/packages/rpm
devel-su pkcon refresh
devel-su pkcon install gh
gh auth login ### ... do the OAuth
gh repo edit sailfishos/sailfish-svg2png --enable-issues=false
… because there’s no reason why you shouldn’t be able to manage your Github stuff while on the bus to work!