Please note new time slot
Schedule: Thursday 2026-06-04T16:00:00Z 
Sailfish OS Community Calendar (ICS format)
Even if you do not participate, topics tend to generate discussion. I want to see discussion happening. Thus, Iām proposing that weād use 10mins as minimum topic duration. Maximum 6 topics a week. Weāll continue with the extended 90 mins meeting duration.
Jolla to check action points from the previous meeting. We agreed today that weāll start to follow up action points on each meeting.
Topic proposals for the meeting:
- Add your name/nick using the template below to suggest a topic.
- Indicate how much time youāll need so we can time-box the meeting accordingly.
- Please be as thorough as you can with your question/topic.
- If you canāt make the meeting please ask and name a substitute.
It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.
We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isnāt clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!
Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.
Template for topic proposal: (post your topic proposals as comments to this forum topic).
- Name/IRC nick:
- Topic:
- Some details about the topic:
- Approx. time needed:
- Substitute (optional):
Open Pull Requests:
If you have, or know of, a pull request thatās been open for at least 3 weeks, but which you think deserves attention, please add a comment using the template below and weāll consider it during the next meeting.
- Name/IRC nick:
- Open PR URL:
4 Likes
Name: @ThijssjihT
Topic: SFOS merch
Some details about the topic: The community wants merch. It will be good for brand recognition, and you will get some small profits as well. Questions:
Approx. time needed: 10 min.
Substitute: I probably wonāt be able to attend, but I read every meeting text.
Copied from Community meeting on 21st May 2026 - #5 by ThijssjihT
7 Likes
-
Name/IRC nick: Peter Leinchen,@peterleinchen , peterleinchen
-
Topic: Defender and itās Harbour compliance, Benefit for all new users, expected to come soonā¢
-
Some details about the topic: harbour-defender, the privacy guard is a tool that
-
- Let the user choose from a list of internet available ad-blocker
- It works on domain based blocking via /etc/hosts. For this it needs -obviously- to modify the hosts file. This is not allowed AFAIK, so for this it would need an exception!
- It is a pure qml app ( with a one-liner cpp) running as defaultuser (nemo) and does not have and does not need root rights.
- (Root, where needed) functionality is purely implemented in python and only available as function calls.
- Furthermore it deals with the sailfish-browser cookies.sqlite DB file. It can delete cookies from blacklist (or not whitelisted). And persist the DB by setting the file to read-only. Most probably another exception needed!
- Setting the domain blocking in /etc/hosts works as well for AlienDalvik/AppSupport. Which of course means its /system/etc/hosts is modified also. The service can be restarted via menu item.
- PublicDir and browser is used for error messages.
- Right now I still use /var/log and /tmp but could relocate those files to .config or .cache??
- A config file written to /etc (on purpose, so that Jane Doe cannot modify)
- Ah, and one more: the update is scheduled with a timer service (which should be okay, or?)
-
Approx. time needed: 25 min
-
Substitute (optional): @nephros
As I cannot participate in general and @nephros as well not on June 4th, this topic is to be discussed on next meeting, where @nephros will discuss it. Nevertheless I put it already here to have it announced. And maybe Jollyboys could make their mind already If they would allow Defender with those exceptions.
(That is the reason for the probably longest topic announcement 
)
And again, I am personally fine with having Defender on Chum. But for all newbies to arrive, such a tool from a trusted source could give trust to them.
āedit:
- another topic: usage of a permission file (right now I shifted all back to a permission and avoiding profile as it did not work as expected)
- and I would need some help/guidance how to avoid the looong start time due to whitelisting lots of lib directories (only 10 I - V devices affected).
2 Likes
You know you can remove that āone-liner cppā and have .noarch rpms? Just include Application{ in the main qml in app root, point to firstpage.qml and you can skip rebuilding for 3 arches forever
2 Likes
Hmm good luck with custom object models 
the ui thread will thank you if you keep them on the native sideā¦
That one cpp file is just a skeleton for working on c++/qml apps, as whole app is just qml/python and no cpp you can just remove it and skip the whole bulding for three arches exercise, youāll get noarch rpms
Not really sure what the benefit is.
(It would have been quite some years ago when I developed rpm-rebuilt Defender directly on device.
But now with having it built on OBS automatically?
Each noarch rpm package is distributed under every arch tree in the download area.
Nevertheless I tried and after some iterations with sailjail (!? ) and the desktop file it works.
Thanks for the hint.
But what is now ābetterā?
1 Like
Thanks for addressing my question, again apologies I could not be present.
Not the answer Iād hoped for but the answer I had expected nonetheless. At least I now have it in writing.
Yeah I think so. Not shipping a pointless binary seems respectful to end usersā storage, skipping a compiler step should speed up building (even if obs rebuilds noarch rpms three times so little storage gain there, thatās still x3 savings in faster builds), if/when you reach harbour should let you upload a single rpm (and maybe save even reviewersā time too), if a user uses the chum github.io frontend for some reason would make the choice easier, and reducing complexity seems also good in and of itself
2 Likes
Well, yes and no. I did some tests between QObjects made via javascript and used in WorkerScripts vs. c++ objects. Depending on size, c++ has little advantage. If you have a large number of rows of data it does matter and you want to be able to do paging without sorting stuff in js. This is an issue with Tidings currently where one data structure is not dealt with in the backend where it should be.
The very primitive way itās done in tooter (not my original code) is still responsive, generally being faster than the web interface, though the browser does not make for fair comparisons.
In the main, the QML/js side is surprisingly efficient
My point was about qml being single threaded; whereas if you manage objects on the c/c++ side it will keep the UI thread slick and responsive
Yes, I get that. But WorkerScripts keep the UI slick and responsive āto a pointā. For loading 20 toots itās fine. If youāre loading 100s of objects, itāll block. The way tooter works is that the Workerscript is called for different views and you can scroll around and reply without noticing that loading is going on, which is the point. Thatās the whole object model being produced in the workerscript which seems to be optimized as itās the only object you can pass between he workerscript and the qml.
Workerscripts are an excellent concept; the interface is perhaps limited (string-based lists) and should be improved IMO.
1 Like