Thursday, 2024-01-11

LouisDKGood Morning07:50
rainemakGood morning07:56
MatiasGood morning!07:56
rainemak#startmeeting Sailfish OS, open source, collaboration -- 11th Jan 202408:00
sailbot_Meeting started Thu Jan 11 08:00:09 2024 UTC. The chair is rainemak. Information about MeetBot at
sailbot_Useful Commands: #action #agreed #help #info #idea #link #topic.08:00
*** sailbot_ changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:00
rainemak#info Meeting information and agenda can be found here:08:00
rainemakI am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and bee-hive.08:00
rainemak#topic Brief introduction (5 min). Please prefix your name/handle with #info08:00
*** sailbot_ changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:00
rainemak#info Raine Mäkeläinen, sailor @ Jolla, chairperson today08:00
ViGe#info Ville Nummela - sailor@Jolla08:00
rainemakPleased to see many topics. Last late submission was already postponed as we have topics for an hour (schedule wise already too many). If it looks that we're running out time, I may postpone a topic or two from the end.08:00
* LouisDK community member08:01
ExTechOp#info Otto Mäkelä, community08:01
nephros#info nephros, Community08:01
LouisDK#info communiy member08:01
Matias#info Matias, community08:01
sebix[m]#info sebix - community08:02
flypig#info David Llewellyn-Jones, Community08:02
Crabster#info Crabster - lurker08:02
poetasterah, now08:03
* nephros is actually joining from work ( ;) ), so answers *may* be delayed.08:03
poetastergood morning.08:03
ExTechOp(Good morning, and in case I don't see ya, good afternoon, good evening, and good night)08:04
flypigMorning poetaster!08:04
rainemak#topic XDG-Desktop-Portal specification: interesting for Sailfish OS?  (10mins -- asked by nephros)08:05
*** sailbot_ changes topic to "XDG-Desktop-Portal specification: interesting for Sailfish OS? (10mins -- asked by nephros) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:05
poetasterMorning flypig!08:05
rainemak#info <Jolla> This is rather long question. Thus, let’s use original message from the forum08:05
rainemak#info <nephros> Here's the question:08:05
rainemak#info <Jolla> Certainly, having common APIs is a good idea. More planning is08:05
rainemak#info <Jolla> needed and putting down mentioned high-level guidance. We could08:05
rainemak#info <Jolla> plan this on a separate forum post. Worth to analyse how much XDG08:05
rainemak#info <Jolla> Desktop Portals could eventually help on mobile.08:05
rainemakOr forum wiki page maybe.08:06
rainemakBig part of this would be in implementing the backend... something like xdg-desktop-portal-sailfishos08:07
rainemakBig part of this would be in implementing the backend... something like xdg-desktop-portal-sailfish08:08
flypigSo, XDG-Desktop-Portal would help with Sandboxing; porting; and just generally staying consistent with other distros. Does that sound about right?08:08
flypigWhen I say "porting" I mean porting apps.08:08
nephrosIt could yes. It's its intention.08:08
rainemakYeap, that's about right.08:08
nephrosBut its made by the Flatpack guys, so some implementations may bve specific to them. Still, having an API spec is good IMO.08:09
rainemakThis would grow about from the Flatpak similarly as xdg-dbus-proxy did08:09
nephrosExample: Portals specifies a DBus call for taking screenshots.08:09
poetasterthe question of getting 'secure' dbus communication is also adressed by xdg-dbus-proxy?08:10
flypigIf there are problems with the spec for non-Flatpack scenarios, that might be something they'd want to knwo about.08:10
nephrosI think first step could be identifying where there is overlap of existing functionality and specification.08:10
nephros(and identifying which parts of the spec are not interesting to SFOS).08:11
rainemak#info API reference is extensive08:11
flypignephros: a sort of mapping between existing dbus interfaces and xdg-desktop-portal interfaces.08:12
rainemak#info <flypig> XDG-Desktop-Portal would help with Sandboxing; porting; and just generally staying consistent with other distros. Does that sound about right?08:12
nephrosBTW, newer versions of Mozilla use Portals plus PipeWire for video chatting08:12
rainemak#info <nephros> I think first step could be identifying where there is overlap of existing functionality and specification.08:12
rainemak#info <nephros> (and identifying which parts of the spec are not interesting to SFOS).08:13
poetasterthe use case from rinigus puremaps talking via dbus to osm server, for instance?08:13
rainemakpoetaster, I don't see how this would help with that08:13
nephrospoetaster: I don't think there is a Portal spec for that.08:14
poetasterhe's just using dbus08:14
rainemakdo we have this one covered?08:14
poetasternephros, he mentions it on the page you linked08:14
flypigPresumably there could be a community-driven effort to implement something like the screenshot interface, to see how it might work?08:14
poetasterrainemak, it's currently not sailjail compatible and so puremaps from harbour is gutted.08:15
rainemak#info Presumably there could be a community-driven effort to implement something like the screenshot interface, to see how it might work?08:15
poetasterrainemak, that's a good ida.08:15
nephrosSo a SFOS-portal-dbus-proxy?08:15
rainemakLet's move on to next topic.08:15
flypigCool find nephros.08:15
rainemak#topic Unlock via dbus (10mins -- asked by piggz)08:16
*** sailbot_ changes topic to "Unlock via dbus (10mins -- asked by piggz) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:16
rainemak#info <piggz> I made a fun little hack which allows a user to auto-unlock the08:16
rainemak#info <piggz> phone if some configured BT device is connected (GitHub - piggz/08:16
rainemak#info <piggz> harbour-smartunlock 3). Unfortunately it required a nasty hack in08:16
rainemak#info <piggz> nemo-qml-plugin-devicelock to allow unlocking via dbus (GitHub -08:16
rainemak#info <piggz> piggz/nemo-qml-plugin-devicelock at dbus-unlock), I can envisage a08:16
rainemak#info <piggz> setup where the user enters the unlock code into some settings, and08:16
rainemak#info <piggz> a dbus method that accepted the code could do the unlocking, which08:16
rainemak#info <piggz> would be a bit better. This currently works great on the08:16
rainemak#info <piggz> PInephones, but not on my phone which uses sailfish-devicelock-fpd.08:16
rainemak#info <piggz> That closed part does link to /usr/lib64/ and08:16
piggzoh, im here, but have to do school run in a few minutes :)08:16
rainemak#info <piggz> exposes the same dbus method, but replies with an Auth error before08:16
rainemak#info <piggz> hitting the modified code in MceDeviceLockAdaptor::setState() I08:16
rainemak#info <piggz> think this is because it statically links the library, so my08:16
rainemak#info <piggz> override in the dynamic lib doesnt work. Would you be interested in08:16
rainemak#info <piggz> adding some real way to auto-unlock a device? What are your08:16
rainemak#info <piggz> thoughts on this? My use case is to not need to unlock the phone if08:16
rainemak#info <piggz> it know im “close by” … eg, if connected to my watch or my car"08:16
rainemak#info <Jolla> Yes, there some interest to support community with something like08:16
rainemak#info <Jolla> this. Your patch touches the same function we have modified in some08:16
rainemak#info <Jolla> in-house hacks / demos – so it is one control point that could be08:16
rainemak#info <Jolla> used. But it is also very much against the rule of thumb: anyone08:16
rainemak#info <Jolla> can lock device, only device lock daemon can unlock it based on08:17
rainemak#info <Jolla> something user does. Pure sw unlock easily becomes a backdoor. At08:17
rainemak#info <Jolla> minimum such possibility should be limited to privileged processes08:17
rainemak#info <Jolla> (our patch allows only root to unlock). Preferably user should08:17
rainemak#info <Jolla> still be in control over something like this – say setting allowing08:17
rainemak#info <Jolla> unlock over D-Bus , bit similarly to relaxing rules about package08:17
rainemak#info <Jolla> installation works. Or limiting such functionality to named client08:17
rainemak#info <Jolla> binaries. The smaller the hole the better but nevertheless there08:17
rainemak#info <Jolla> will be a hole. Does the possibility for increased convenience for08:17
rainemak#info <Jolla> some justify decrease in security for all?08:17
rainemak#info <Jolla>08:17
rainemak#info <Jolla> Another way might be to implement this as authentication method08:17
rainemak#info <Jolla> that device lock daemon would then use for unlocking (when user08:17
rainemak#info <Jolla> wakes up the device). But given that daemon is closed source08:17
rainemak#info <Jolla> monolith, it would need to be implemented in-house for foreseeable08:17
rainemak#info <Jolla> future. And we’d need ability to grade authentication methods08:17
rainemak#info <Jolla> somehow to differentiate between “can be used for unlocking device”08:17
rainemak#info <Jolla> and “can be used to identify user” and so on.08:17
rainemakany comments?08:18
piggzjust reading....08:18
piggzsmart-unlock is a feature on android ... perhaps you could consider adding such a thing?08:19
piggzim quite happy to not have to make my own hack08:19
piggzjust for the "connected device" use-case08:19
rainemaklet's see how this develops08:20
ExTechOpIt would be nice if the user could select how "hard" security they want/need on their devices, instead of having it hardwired by the operating system.08:21
flypigSo the obvious downside as mentioned is potential privacy violations; either allowing criminals or the state-level to get access?08:21
flypigExTechOp, your suggestion would mitigate that.08:21
piggzflypig: but if the uses opts to not-lock if their watch is in vicinityl then thats fine08:21
rainemak#info <ExTechOp> It would be nice if the user could select how "hard" security they want/need on their devices, instead of having it hardwired by the operating system.08:22
flypigpiggz, yes, understood. I guess I'd just personally not want it to weaken security protections when it's not used.08:22
poetasterpeople pay with cards at stores with nothing more than a swipe these days. not secure at all.08:23
piggzi wouldnt want to weaken security for all, but just add some convenience for some with little downside08:24
rainemakI don't think that's a same analogy08:24
poetasterI'm suggesting that pairing nfc, bluetooth are MORE secure.08:24
poetasterthat's all.08:24
nephroswhich kind of device are you using at the moment to unlock?08:24
rainemaktime flies...08:25
piggznephros: my use case is basically ... if my watch is connected, which is on my person, then allow unlock automatically08:25
rainemaklet's continue this one the general discussion if we have time left. ok08:25
poetasterpiggz, ble?08:25
piggzhappy enough for this to be considered, have to go to school now :) thx rainemak08:25
nephrosMaybe it can be constrained to BT MAC + must be a HID device + must have a button + button press unlocks?08:25
rainemak... on the general08:25
rainemakthanks piggz08:25
rainemak#topic Inclusion of FolderListModel in harbour (5mins -- asked by poetaster)08:26
*** sailbot_ changes topic to "Inclusion of FolderListModel in harbour (5mins -- asked by poetaster) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:26
rainemak#info <poetaster> I recently, somewhat belatedly, noticed that I had disqualified08:26
rainemak#info <poetaster> a number of packages I already have in harbour by adding08:26
rainemak#info <poetaster> FolderListModel. (the labs one). Is it possible to allow this?08:26
rainemak#info <poetaster> Or am I missing an equally convenient mechanism. I have my08:26
rainemak#info <poetaster> ‘own’ python based version but that’s a hack.08:26
rainemak#info <Jolla> There isn’t really any good reason for not allowing08:26
rainemak#info <Jolla> Qt.labs.folderlistmodel in Harbour. In fact, we were already08:26
rainemak#info <Jolla> planning to allow it in 4.5.0 release, but unfortunately the change08:26
rainemak#info <Jolla> just missed the window. It will be allowed when the next Sailfish08:26
rainemak#info <Jolla> OS release comes out.08:26
poetasterOh, cool! Yeah!08:26
flypigGreat news :)08:26
rainemakthis is should be clear and straightforward :-)08:26
poetastershort topic. not like me.08:27
nephrosIs there a significant difference between the labs one, and the one from Silica (or is it Nemo)?08:27
rainemaklet's move on08:27
rainemak#topic AAS System Webview (5mins -- asked by Matias)08:27
*** sailbot_ changes topic to "AAS System Webview (5mins -- asked by Matias) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:27
rainemak#info <Matias> SFOS AAS comes with Android System Webview version 83 which is 3.508:27
rainemak#info <Matias> years old by now. This causes certain banking apps and potentially08:27
rainemak#info <Matias> other Android applications that rely on a more recent version of08:27
rainemak#info <Matias> webview to stop working and it is also a bit of a security risk.08:27
rainemak#info <Matias> Installing and activating a different webview implementation08:27
rainemak#info <Matias> requires superuser rights (infeasible) or signature spoofing08:27
rainemak#info <Matias> (which nobody seems to have tried in the context of webview yet).08:27
rainemak#info <Matias> With the reorganization over I was hoping someone could shed some08:27
rainemak#info <Matias> light on this.08:28
rainemak#info <Matias>08:28
rainemak#info <Matias> So, is there an update for AAS/Android System Webview somewhere08:28
rainemak#info <Matias> down the pipeline?08:28
rainemak#info <Matias>08:28
rainemak#info <Matias> Links/references:08:28
rainemak#info <Matias>08:28
rainemak#info <Matias> 1. Rabobank app stopped working08:28
rainemak#info <Matias> 2. Old Android WebView (74.x) --> update needed, ideas?08:28
rainemak#info <Matias> 3. Make updating Android (System)Webview possible 208:28
rainemak#info <Matias> 4. GeckoView instead of Android System WebView · Issue #167 · mozilla/geckoview · GitHub 108:28
rainemak#info <Jolla> We are using Webview from current Android version and it is updated08:28
rainemak#info <Jolla> always when we update AppSupport Android base version. We have08:28
rainemak#info <Jolla> AppSupport update for next Android version in pipeline but not yet08:28
rainemak#info <Jolla> sure when can we release that out.08:28
rainemaksorry, nephros I just changed the topic... please raise your question again on the general discussion.08:28
MatiasI see. Would it be possible to whitelist other webviews in the system image to allow the user to choose other ones if they so desire? Just an idea.08:30
rainemak#info <Matias>  Would it be possible to whitelist other webviews in the system image to allow the user to choose other ones if they so desire? Just an idea.08:30
rainemakMatias, I'll ask around08:31
MatiasThank you! It's greatly appreciated.08:32
rainemakI doubt that I get answer for this meeting08:32
rainemaklet's speed up a bit08:32
rainemak#topic Mobile data in Italy with Xperia 10 III not working ( (5mins -- asked by Valorsoguerriero97)08:32
*** sailbot_ changes topic to "Mobile data in Italy with Xperia 10 III not working ( (5mins -- asked by Valorsoguerriero97) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:32
rainemak#info <Valorsoguerriero97> Mobile data not working under WINDTRE (ITALY) on 1008:32
rainemak#info <Valorsoguerriero97> III. Same APN setting on my 10 works ok. Not here. I08:32
rainemak#info <Valorsoguerriero97> can only call and receive sms… not mobile data. What08:32
rainemak#info <Valorsoguerriero97> about this bug? Can you give me an estimated time for08:32
rainemak#info <Valorsoguerriero97> resolution?08:32
rainemak#info <Jolla> You replied to the forum already with a solution. Good that this got sorted out.08:32
rainemak#info <Jolla> Summary: Ask the operator to disable VoLTE on your contract/line.08:32
rainemakthere operator specific issues are tricky08:33
rainemakmoving forward08:34
rainemak#topic Jolla community dinner @ FOSDEM '24 (10mins -- asked by Louis)08:34
*** sailbot_ changes topic to "Jolla community dinner @ FOSDEM '24 (10mins -- asked by Louis) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:34
rainemak#info <Louis> There has been a Jolla community dinner after FOSDEM on Saturday in08:34
rainemak#info <Louis> the previous years at non-COVID times. I personally miss the08:34
rainemak#info <Louis> Moroccan restaurant La Kasbah (the host at 2019 and 2020) as I08:34
rainemak#info <Louis> found it quite suited? Anyone from Jolla up for the planning or08:34
rainemak#info <Louis> should it be done by time community. Also if anyone have better08:34
rainemak#info <Louis> suggestions I’m open for it.08:34
rainemak#info <Jolla> We’re thinking that this would be more like Community event this08:35
rainemak#info <Jolla> time. That said, it’s under planning. We’re still checking suitable08:35
rainemak#info <Jolla> place, but it should be such that it encourages to discuss and serves08:35
rainemak#info <Jolla> food. Central location it’ll be and likely scheduled to Saturday08:35
rainemak#info <Jolla> 7:00 PM giving everybody enough time to move from FOSDEM venue.08:35
rainemak#info <Jolla>08:35
rainemak#info <Jolla> There’s also a forum topic about the dinner but no post yet08:35
rainemak#info <Jolla> regarding this Community event.08:35
rainemak#info <Jolla>08:35
flypigI'm already looking forward to it!08:35
LouisDKflypig, good to hear. Just want to know if anyone from Jolla wants to plan it.08:36
LouisDKI could also step in if needed08:36
rainemakLouisDK, we're planning it already08:36
LouisDKrainemak: Nice. Do you have a resturant in mind?08:37
rainemakLouisDK, not yet selected.08:38
rainemakWe'll post to the forum when there's info to share08:38
flypigIf I recall correctly, last year was Café Georgette, before that it was La Kasbah like you said LouisDK.08:39
flypigQuite different experiences :)08:39
LouisDKflypig: Yes. It's sww what rainemak comes up with.08:39
flypigYes, indeed :)08:40
rainemakDo you want to continue still or is it ok to move forward?08:40
flypigI shall hold the question until general, but I'm interested to know if anyone else here will be at FOSDEM.08:40
LouisDKrainemak: Just continue.08:41
rainemakTrying save some time for general discussion08:41
rainemak#topic Jollas future plans regarding Alien Dalvik  (10mins -- asked by Louis)08:41
*** sailbot_ changes topic to "Jollas future plans regarding Alien Dalvik (10mins -- asked by Louis) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:41
rainemak#info <Louis> What is the situation regarding Jolla and Alien Dalvik. Does Jolla08:41
rainemak#info <Louis> have “enough rights” to expand the development and offering of08:41
rainemak#info <Louis> Alien Dalvik to eg. community ports? (Eg. sell it under an “as-is”08:41
rainemak#info <Louis> agreement without any official support from Jolla)08:41
rainemak#info <Jolla> Let’s correct the name first, it’s not Alien Dalvik but Android08:41
rainemak#info <Jolla> AppSupport. Not quite sure what you trying to ask with “enough08:41
rainemak#info <Jolla> rights” but yes, we have all rights to the AppSupport. This has08:41
rainemak#info <Jolla> been discussed on several occasions in the past, see links below.08:41
rainemak#info <Jolla> Proposed as-is is likely not a good idea with current Sailfish X08:41
rainemak#info <Jolla> pricing model.08:41
rainemak#info <Jolla>08:41
rainemak#info <Jolla> It's worth noting that Android AppSupport for community ports is08:41
rainemak#info <Jolla> more than just providing the relevant packages. No need to repeat08:41
rainemak#info <Jolla> answers again, please check “Ability to buy/enable Android08:41
rainemak#info <Jolla> AppSupport for community ports” topic from 2023-02-16 log and08:41
rainemak#info <Jolla> “Standalone AppSupport license for ports” topic from the 2022-06-0908:41
rainemak#info <Jolla> log.08:41
rainemak#info <Jolla>08:41
rainemak#info <Jolla> If we were to do this, it wouldn't be in the immediate future.08:42
rainemak#info <Jolla>08:42
LouisDKrainemak: Answer accepted. Just move forward08:42
rainemak#topic Mic issues under AOSP and SailfishOS (Xperia 10 ii + iii) (5mins -- asked by Louis)08:42
*** sailbot_ changes topic to "Mic issues under AOSP and SailfishOS (Xperia 10 ii + iii) (5mins -- asked by Louis) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:42
rainemak#info <Louis> 3rd party caller my be able to hear their own voice due to a bug in08:42
rainemak#info <Louis> AOSP. Any updates on this from Jolla? Echo during calls on Xperia08:42
rainemak#info <Louis> 10 II using Loudspeaker 1 and [LENA][11][4.19] Echo cancellation is08:42
rainemak#info <Louis> not enabled for voice calls · Issue #771 ·08:42
rainemak#info <Louis> sonyxperiadev/bug_tracker · GitHub08:42
rainemak#info <Jolla> Not really updates. Officially we’re stating Android 11 as required08:43
rainemak#info <Jolla> stock Android version and clearing Android 12 as ok. That said,08:43
rainemak#info <Jolla> without guarantees you could try to update your Sony Xperia 10 III08:43
rainemak#info <Jolla> to Android 13 before flashing Sailfish OS and check if it’s better08:43
rainemak#info <Jolla> – please note that Android 11 binary blobs are still needed from08:43
rainemak#info <Jolla> Sony’s web site. Bear in mind that if you upgrade stock Android08:43
rainemak#info <Jolla> version to 13 before flashing Sailfish OS and there are other kind08:43
rainemak#info <Jolla> of issues and you want to downgrade, you need to flash Android 1208:43
rainemak#info <Jolla> with Windows and use Emma.08:43
rainemakmoving on...08:44
LouisDKrainemak: The issues does still presists with Xperia 10 iii  flashed with Android 12 and 13 prior to Sailfish.08:44
LouisDKJust move ahead08:45
rainemakLouisDK, that's what we expected08:45
rainemak#topic Open PR discussion (5 mins -- asked by Jolla)08:45
*** sailbot_ changes topic to "Open PR discussion (5 mins -- asked by Jolla) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:45
rainemak#info <Jolla> Any open PRs to discuss?08:45
rainemakI had none prepared for this...08:45
flypigWithout Damien's update I'm lost :(08:46
rainemakLet's skip open PRs for today... .-)08:46
rainemakflypig, yeap08:46
rainemak#info <topic> Bug reports by the community bug coordination team (5 min -- asked by Jolla)08:47
rainemak#info <Jolla> The Community Bug Coordination Team have done a superb job once again this fortnight.08:47
rainemak#info <Jolla> As a result of their work, we now have:08:47
rainemak#info <Jolla> 6 high quality bug reports now recorded internally and tagged as "tracked".08:47
rainemak#info <Jolla> 1 bug report missing “tracked” tag.08:47
rainemak#info <Jolla> 3 marked as duplicates and closed.08:47
rainemakLet's move on to the general discussion.08:47
rainemak#topic General discussion (8 min)08:47
*** sailbot_ changes topic to "General discussion (8 min) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:47
flypigKudos to the bug team again!08:48
rainemakflypig, you had some general topics...08:48
rainemakflypig, Yeap! Once again08:48
flypigOh, well, I'm curious to know who else here will be at FOSDEM.08:48
rainemakI'll be08:48
LouisDKI will for sure.08:48
ExTechOpThe last time, I asked about SFOS future plans, has there been progress that could be made public?08:48
MatiasI'd love to visit FOSDEM sometime, but probably not this year :(08:49
rainemakExTechOp, not really, you can trust that we share those when ready08:49
poetasterI can't make FOSDEM either. Family, winter school break collide.08:50
flypigI'm looking forward to seeing you there LouisDK, rainemak :) Sorry to hear that though poetaster (I think you mentioned it previously, but it's still a shame).08:50
poetasterflypig, ah, just checked. I'm wrong. 3-4 fossdem, 5-9 school free. hmmm. depends on what we plan for that week.08:52
flypigWell, if things change and you can make it, it will be wonderful to meet up :D08:52
poetasteryes, I'd really like that! I never get out :)08:52
rainemakMatias, got some input regarding the AAS WebView08:52
flypigpoetaster: :D08:53
rainemak#info "Why are there security restrictions on which apps can be used as a WebView implementation?" ^08:54
rainemaklet's schedule next meeting next...08:55
rainemak#topic Next meeting time and date (5 mins)08:55
*** sailbot_ changes topic to "Next meeting time and date (5 mins) (Meeting topic: Sailfish OS, open source, collaboration -- 11th Jan 2024)"08:55
flypigSo on a standard Android device, does that mean it's not possible to upgrade the Webview?08:55
flypignephros, earlier you asked: "Is there a significant difference between the labs one, and the one from Silica (or is it Nemo)?" What is the labs one?08:55
flypigSorry, I spilled over; you can ignore me.08:55
MatiasIt's possible to update the default Google system webview on regular Android devices, where it is whitelisted in the system image and available in the play store, I think.08:56
flypigThank you rainemak!08:56
rainemakMatias, yeap it could be possible via Play Store08:56
flypigGot it, thank you Matias!08:56
rainemakProposing Thursday 1st February at 08:00am UTC due to vacations so right before FOSDEM.08:56
MatiasThank you too for the extra info rainemak!08:57
nephrosThere is Nemo.FileManager::FileModel08:57
ViGeflypig: Yeah, the one which rainemak linked is the labs one. There isn't any in Silica and we don't use the one from Nemo.08:57
nephrosok understood.08:57
ExTechOp2024-02-01 works4me08:57
flypigThanks ViGe.08:58
rainemaknephros, it's a matter of choice and both could be available for Harbour use08:58
poetasterflypig, my better half says I should just go to fossdem :)08:58
flypigYay! You have a very wise better half :)08:59
rainemak#info Next meeting will be held on Thursday 1st February 2023 at 08:00am UTC: 2024-02-01T0800Z08:59
rainemakThank you everyone for the meeting!09:00
poetasterok, so I wasn't aware of the Nemo FolderListModel ... research.09:00
poetasterthanks all!09:00
flypigThank you rainemak, all!09:00
nephrosthanks! See ya around!09:00
MatiasThank you all!09:00
MatiasFirst time, I was quite nervous :)09:00
rainemakI think now we peeked number of topics... one less would be better, let's improve a bit.09:00
flypigNice work Matias, did great ;)09:01
ExTechOpThank you, everybody!09:01
rainemakMatias, don't be you did well! Welcome09:01
sailbot_Meeting ended Thu Jan 11 09:01:30 2024 UTC.09:01
sailbot_ Minutes:
sailbot_ Minutes (text):
sailbot_ Log:
*** sailbot_ changes topic to "Next meeting will be held on Thursday 11th January 2024 at 08:00am UTC: 2024-01-11T0800Z"09:01
*** ChanServ changes topic to "Next meeting will be held on Thursday 1st February 2024 at 08:00am UTC: 2024-02-01T0800Z"09:42

Generated by 2.17.1 by Marius Gedminas - find it at!