07:00:04 <sledges> #startmeeting Sailfish OS, open source, collaboration -- 21th October 2021
07:00:04 <sailbot> Meeting started Thu Oct 21 07:00:04 2021 UTC. The chair is sledges. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:00:04 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
07:00:15 <sledges> #info Meeting information and agenda can be found here:
07:00:18 <sledges> #link https://forum.sailfishos.org/t/community-meeting-on-irc-21st-october-2021/8423
07:00:24 <sledges> I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and teacher's pets.
07:00:27 <sledges> #topic Brief introduction (5 min). Please prefix your name/handle with #info
07:00:31 <sledges> #info Simonas Leleiva -- privateer for Jolla
07:00:52 <ExTechOp> #info Otto Mäkelä -- community
07:01:00 <thilo[m]> #info thigg --- community dev
07:01:03 <ViGe> #info Ville Nummela -- sailor@Jolla who almost forgot the meeting
07:01:40 <dcaliste> #info Damien Caliste, community
07:01:56 <abr> #info Andrew Branson, sailor@Jolla
07:02:06 <chriadam> #info Chris Adams, privateer at Jolla
07:02:32 <lolek> #info lolek - sailfish user
07:02:38 <cartron> #info cartron - community
07:03:03 <flypig> #info David Llewellyn-Jones - sailor @ Jolla
07:03:11 <Cy8aer[m]> #info cy8aer - community
07:04:25 <flypig> Glad you could join us Sepelius.
07:06:18 <sledges> and onto the 1st Q!
07:06:19 <sledges> #topic ui experience/accessibility (15 min -- asked by lolek)
07:06:27 <sledges> #info <lolek> Sailfish need some minor improvements so one hand usage will be better. There are lot of locations in the sailfish that requires to use second hand while it would be just a small ui change to improve this. One has to realize that all lists, should start from the bottom to the top not the opposite way.
07:06:37 <sledges> #info <lolek> For example the notes, the first note is located in the top left corner of the screen, impossible to reach there using one hand without fiddling with the phone. The same apply other places. There are of course other issues, some described by me here:
07:06:47 <sledges> #link https://forum.sailfishos.org/t/one-hand-usage-accessibility-improvements/8406
07:07:01 <sledges> #info <Jolla> This is very true. Devices have grown bigger and displays taller, and what worked for Jolla 1 is often no longer the case e.g. Xperia 10 II. Pulley menu allows accessing page action easily, but accessing the most recent items on the top has become unnecessarily difficult.
07:07:13 <sledges> #info <Jolla> Inverting sorting order of lists and grids is not trivial since people naturally read (=scan) information from top to bottom, and since we need to keep consistency with the other mobile operating systems (for many enterprise users Sailfish OS is not the only mobile device they use).
07:07:30 <sledges> #info <Jolla> We want and need to evolve Sailfish UX further, but as mature product and supporting existing user base we need to be careful with the changes we apply, which need to be applied consistently across the interface and verified empirically that we are going in the right direction.
07:08:29 <lolek> Yes, true, the idea of reverting is by no mean bad and this can be skipped. But following others is also not a good idea since for example Android usability is really awfull. To contrast iOS done it a bit better bit still there are some obstacles with it
07:08:42 <ExTechOp> One could say a couple of things about the user interface consistency in any case, there are a few places where the "Jolla experience" reverts to something very android-like.
07:09:40 <abr> I think it would be nice if launcher folders were pinned to the bottom of the screen instead of the top
07:09:42 <lolek> The first thing that comes to my mind is the browser. Just open it up without any cards. Then if you'd like to go to private mode you need to reach to the top, then you can use the pulley menu to open a new card of... the new card button is on the bottom this should be reorganized
07:10:02 <lolek> here's something more. A bit old article but showing the finger problem: https://www.scotthurff.com/posts/how-to-design-for-thumbs-in-the-era-of-huge-screens/
07:10:39 <sledges> browser aspects you could contribute yourself (is opensource and Nico know how to build it:)
07:10:47 <lolek> So one has to realize that peoples has different hand sizes, and because of new devices being extra big it's difficult to sometimes even hold them with one hand
07:11:16 <lolek> so sadly the software has to try at least to help those peoples
07:12:21 <sledges> #link https://www.scotthurff.com/posts/how-to-design-for-thumbs-in-the-era-of-huge-screens/
07:13:34 <sledges> how about (boldly) displaying notifications in the middle of the screen? 8)
07:13:41 <lolek> Jolla: I know you're targeting enterprise users and that's great - at least hopefully this won't be another toy on the market :) But accessibility is quite important especially with those phones. I'd like to also remind about the odd way of handling the network selection as also the permission window. When I saw it first time I was quite surprised that it's so different from the system and that it doesn't use some swipes to
07:13:45 <ExTechOp> How difficult would it be to consistently make the menu position a configurable setting in the UI, that way people could configure it depending on their device and hand sizes?
07:14:08 <flypig> Also, as Joona mentioned in his presentation, the Browser UI is evolving right now. Not that the future changes will necessarily fix all of these issues, but just to bear in mind.
07:14:11 <lolek> I'm quite surprised why I have to touch the [x] on the minimized app instead of just swiping it away?:)
07:15:56 <chriadam> ExTechOp: menu position?  which menus?  Do you refer to pulley menus or something else?  Pulley menus are problematic for any case where the main content is a listview or other flickable view, because you need to scroll to content bounds before menu activation is possible, for example.
07:16:22 <sledges> android (11) is doing some things/gestures better already, yet some things worse because they started as a buttoned UI. Jolla in mobile is like Tesla in EV world - started straight from gestures, so in a unique position, shouldn't let loose of that!
07:16:39 <chriadam> also, anywhere that layouts exist, attempting to dynamically change the position of something important in the layout, is likely to have considerable knock-on effects.
07:16:51 <ExTechOp> chriadam Yes, I meant pulley menus.
07:17:23 <lolek> sledges: I have android 11 somwhere it's still a weird expirience for me at least, not to mention the hamburger menu in the top left corner of the screen - impossible to reach for me no matter how I'd hold the phone in right hand, welll ok maybe I should be left handed for android phone?
07:17:54 <jpetrell> yeah these positioning options may seem simple, but often have quite big ramifications
07:18:29 <ExTechOp> chriadam I realize I didn't quite get what element "launcher folders" was referring to
07:18:56 <sledges> lolek: hamburger menu is sadly on near every mobile version of any website
07:19:06 <flypig> Didn't Android (maybe a Samsung variety) try to fix this some time ago by making their headers really huge? That worked quite well on a vertical-scrolling page.
07:19:27 <jpetrell> yeah Samsung's UI handles this quite well
07:20:00 <lolek> sledges: true, same problem on every page :/ Sometimes I got a feeling that no one from the guys that make it is actually using it
07:20:04 <jpetrell> the most recent items in apps should be reachable one-handed, making header larger and/or allowing them dragging down is one solution
07:20:20 <lolek> to compare the BlackBerry OS10 browser is imho the best one hand usage example
07:20:48 <sledges> 1min left
07:20:52 <sledges> need more tim?:)
07:21:03 <lolek> the hamburger menu is on the bottom, the address bar on the bottom, everything is on the bottom, even the options that you got from hamburger menu, are ordered from top to bottom but are glued to the bottom not to the top
07:21:20 <jpetrell> I really loved Blackberry 10. never understood why they made the overall UI style so dull (I guess because it is "serious corporate" phone), but design and implementation-wise it was great
07:21:42 <lolek> sledges: yeah give me a min please
07:22:15 <abr> the way the browser menu scrolls up from the bottom is a good pattern, especially as you have to flick it again to access the less used options
07:22:44 <lolek> One question to Jolla then, can we expecte some improvements in the new permission window as also the network selection to at least add there some shortcuts, and also think about adding gestures to easily close running aps without trying to reach the [x] icon there?
07:23:22 <thilo[m]> abr: that could use a small indicator that there are options however
07:23:43 <thilo[m]> more options
07:23:56 <piggz> jpetrell: my bb10 is locked with one of them picturepassword/grids :D
07:24:00 <lolek> jpetrell: one great feature of bbos10 browser is the quick scroll to bottom, you just top the top of the screen on the webpage titlebar ;)
07:24:00 <abr> yeah good point. funny that the browser has the best new one-handed UI in that, and the worst in the tab screen
07:24:25 <sledges> lolek: top-edge swipe closes the app if enabled in options (you probably know of)
07:24:38 <sledges> doesn't help with one hand use though:)
07:24:46 <lolek> :)
07:24:46 <abr> we could definitely used a quick scroll-to-top, but not a titlebar :)
07:25:17 <thilo[m]> sledges: are there any idea to replace the top edge swipe with something else?
07:25:32 <lolek> well the browser is quite odd on SFOS. The address bar when page loads is in the bottom - great, but when you want to open new page the address bar is in the top... o.O why it's not glued to the keyboard?
07:25:41 <sledges> thilo[m]: well android replaced it with swipe-up-to-close in the task switcher:)
07:26:16 <lolek> sledges: I think that following android is not so great idea especially considering their rules regarding the hamburger menu :/
07:26:30 <sledges> pick'n'mix
07:26:52 <lolek> here's older article: https://www.uxmatters.com/mt/archives/2013/02/how-do-users-really-hold-mobile-devices.php
07:27:07 <thilo[m]> sledges: but there is no task switcher in sfos
07:27:10 <jpetrell> lolek: when the keyboard is open you can also filter history and bookmarks with the input
07:27:13 <abr> the address bar is probably higher up because you don't need to tap it - it just takes the keyboard input. unless you're selecting/editing which is rarer
07:27:16 <sledges> they are catching up with sfos, just look at how they replaced back button with gesture, nice idea, but so many sad corner cases
07:27:43 <abr> my biggest issue with it right now is that you have to load a page to get to any other option when you start it up.
07:27:49 <lolek> jpetrell: need to dig into that but what's odd for me is that on the new tab the address bar is in the top of the phone - hard ot reach there
07:28:03 <jpetrell> true
07:28:14 <lolek> well ok if I'd hold the phone in the middle yeah but when I tried I was having problems with finger - started to hurt so it's a no go
07:28:15 <ExTechOp> sledges https://knowyourmeme.com/memes/look-what-they-need-to-mimic-a-fraction-of-our-power
07:28:21 <sledges> thilo[m]: home screen, and that's what lolek said about 'x' buttons. to change how to close an active app in sfos clashes with other edges that gestures been established for way too long
07:28:30 <abr> heh
07:28:31 <flypig> lolek, but abr makes a good point: why do you need to touch the address bar on a new tab?
07:29:00 <jpetrell> also browser is going through iterative improvements, and a bit in-between the old and newer designs
07:29:06 <lolek> I won't tell you know need to startup the phone
07:29:39 <rinigus> address bar on top while entering address is fine - it feels natural that the items filtered by it are below the filter
07:29:40 <sledges> lolek: time to wrap up, let's compile next questions for next meeting aye?:)
07:29:45 <Thaodan> flypig: or why can't we no longer close tabs with swipe :)
07:29:50 <jpetrell> our focus is currently on other areas, but I hope we can come back to one-handed use and improving the overall navigation in the future (like a gesture to close apps on Home)
07:29:55 <lolek> yea
07:30:02 <rinigus> Thaodan: +1
07:30:38 <sledges> and bring back the close button:) https://github.com/sailfishos/sailfish-browser/pull/905
07:30:40 <lolek> flypig: ok got it sometimes I didn't got the keyboard opened right away
07:31:00 <Thaodan> We have a gesture for closing apps on home: hold and pulley menu
07:31:33 <lolek> Thaodan: but it's cloasing them all not particular one
07:31:38 <flypig> lolek, okay, I understand. In that case I can appreciate the need, but I think that shouldn't be necessary.
07:31:47 <sledges> it's time to move it move it
07:31:56 <lolek> yeah nothing for me for now, thank you!
07:32:01 <lolek> *from
07:32:03 <flypig> Thaodan, I guess swipe-tab-close is taken by swiping page back.
07:32:29 <flypig> But I wasn't that always the case?
07:32:50 <Thaodan> flypig: Not really if you can wipe to the side that does not has a swipe
07:32:55 <sledges> flypig: could work in other direction though
07:33:17 <sledges> #info (discussions about app closing and browser improvements, the latter you can contribute yourselves;)
07:33:21 <sledges> #topic VoLTE implementation details (15 min -- asked by ApB)
07:33:28 <Thaodan> lolek: You can close only particular apps by pressing the x button
07:33:39 <sledges> #info <ApB> As we've seen in the slides from Berlin VoLTE is planned for early 2022. Some questions arise and mainly how Jolla is going to approach the issue. Will the solution be open or closed? Which devices are going to be supported?
07:33:56 <sledges> #info <Jolla> The cellular middleware used in Sailfish OS oFono is open source and developed openly, but there are device-specific parts of the implementation that we may not be able to share publicly. Xperia 10 II is the first device we are planning to support, but we are looking to expand to other newer devices.
07:34:00 <lolek> Thaodan: yes and this is something I don't understand, why there's no gesture for this instead I need to click on a small button
07:35:08 <ExTechOp> Another thing about the UI is that at least for me, it's not obvious why sometimes unlocking the device gives you the app you last used on top, and occasionally not (you get the tasks screen)?
07:35:18 <sledges> ExTechOp: general discussion pls:)
07:35:34 <rinigus> does it mean that this VoLTE implementation would have to be done for each device separately? any idea on how we could extend it to ports?
07:37:47 <Cy8aer[m]> yeah, if VoLTE is not implemented for e.g. XA up this will not be very lasting. So hope for XA2 be a "newer device"
07:38:48 <rinigus> any details on what can prevent public release? do you have special agreements with Sony in place?
07:39:37 <jpetrell> ExTechOp: sounds like a bug
07:42:39 * sledges quoting Friends: "I got nuffin'!":))
07:42:41 <abr> rinigus: I think it's a bit early to know tbh. I don't think we know how reusable pieces will be yet.
07:44:31 <rinigus> abr: please correct me if I am wrong - I think sony AOSP does support volte. do you plan to base implementation on that?
07:44:52 <rinigus> (but I must say I haven't tested it myself)
07:46:27 <abr> I don't know enough about the ongoing work to say. It's like Tesla's lab in there. Lightning everywhere.
07:46:34 <sledges> 2more mins
07:46:52 <sledges> or lightning cables :P
07:46:58 <rinigus> does anybody else know?
07:47:18 <sledges> a question for next meeting?
07:47:21 <rinigus> who is on the meeting while volte discussion is on
07:47:53 <rinigus> sledges: we had a question now
07:48:17 <sledges> we answer meeting questions since Monday internally in the company
07:48:31 <sledges> if you got follow-up ones we cannot answer during meeting, please relay to the next
07:48:51 <abr> I think today's question has been answered as best we can right now
07:49:05 <rinigus> ok, understood
07:49:14 <sledges> and time's up for this one
07:49:24 <sledges> #topic Aptoide is still/again pushing an untrusted client why is it still in Jolla store? (5 min -- asked by KeeperoftheKeys)
07:49:40 <sledges> #info <KeeperoftheKeys> The aptoide store client seems to push dangerous and compromised software, this is either the second time this happened or it never stopped happening since last time. As the saying goes "Fool me once shame on you, fool me twice shame on me", why is this clearly untrustworthy party still in the Jolla store endangering us?
07:49:45 <sledges> #link https://forum.sailfishos.org/t/aptoide-untrusted-again/7650
07:50:17 <sledges> #info <Jolla> Aptoide is a 3rd party marketplace in Jolla Store, but we have contacted Aptoide about these issues. We are no longer supporting the Sailfish-branded Aptoide and recently added up-to-date version of F-Droid, which provides privacy-respecting and open source apps for Android.
07:52:08 <ExTechOp> (side note, why do I repeatedly get "The site at https://forum.sailfishos.org/t/aptoide-untrusted-again/7650 has experienced a network protocol violation that cannot be repaired." and have to reset cookies before it works again?)
07:53:41 <flypig> ExTechOp, just on that page, or any forum page?
07:54:15 <ExTechOp> flypig forum.sailfishos.org generally, no such issues on other websites
07:54:29 <flypig> Strange, I've never experienced that myself.
07:55:19 <abr> me neither. quite a nasty sounding error.
07:55:28 <sledges> wfm (looks like we're transitioning into general discussion:p)
07:55:38 <ExTechOp> Then when I remove 3 (rather huge, 2.7M) cookies from forum.sailfishos.org it works again
07:55:46 <sledges> #topic General discussion (15 min)
07:55:50 <sledges> ViGe: ^
07:56:04 <ViGe> ExTechOp: Which firefox version are you using?
07:56:40 <ExTechOp> ViGe 78.14.0esr (64-bit)
07:57:06 <ViGe> ExTechOp: Any chance you could upgrade to 81.0.2 or above?
07:57:10 <ExTechOp> That seems to be current on CentOS Linux release 7.9.2009 (Core)
07:59:12 <sledges> jpetrell: ExTechOp: regarding swipes from lockscreen, could the bug be a collateral of https://forum.sailfishos.org/t/4-1-0-23-events-quick-access-swipe-is-from-the-wrong-side/6253/18 ?
08:00:27 <rinigus> ha, as we are in bugs. what about fixing order of ambiences selection? show starred first and the others later
08:00:49 <rinigus> is that bug tracked? fix in pipeline
08:00:49 <ExTechOp> ViGe I'll leave that as unresolved for now, and get back once the OS browser updates
08:01:16 <dcaliste> thanks rinigus for raising this one, it's been here a long time now.
08:01:39 <sledges> is it in forum?
08:01:46 <rinigus> someone filed it in forum as well,
08:02:01 <jpetrell> sledges: hard to say, but definitely could be. that particular issue should now be fixed on newer releases
08:02:12 <flypig> I guess it's this one? https://forum.sailfishos.org/t/ambiances-are-not-ordered-with-favorites-first-regression/6614
08:02:13 <sledges> yes that one is fixed in 4.2.0
08:02:56 <rinigus> flypig: yes, that one. don't see that fixed in 4.2
08:03:00 <sledges> (my answer was to jpetrell)
08:03:04 <sledges> #info ongoing regression:
08:03:06 <sledges> #link https://forum.sailfishos.org/t/ambiances-are-not-ordered-with-favorites-first-regression/6614
08:03:23 <flypig> No, I think sledges was referring to something else. But we do have a bug recorded about this internally too.
08:04:07 <rinigus> great! looking forward to the fix :)
08:04:18 <flypig> Same here :)
08:04:20 <jpetrell> cannot reproduce the ambience sorting issue. favorites are shown before ordinary ambiences, the list is sorted according use, the latest on top
08:04:48 <ExTechOp> sledges Dunno. I had some strangeness with fingerprint unlocking just yesterday, even after rebooting it was not operational, and when I went to settings to check it out the fingerprints available the selection was empty.
08:04:51 <ExTechOp> However, when I entered my security code to add new ones it complained about "insufficient memory" or some such, but suddenly the fingerprints were again there and unlocking started working.
08:05:07 <sledges> #info <ExTechOp> sometimes unlocking the device gives you the app you last used on top, and occasionally not (you get the tasks screen) -- this might be an aftermath of fixing https://forum.sailfishos.org/t/6253
08:05:09 <dcaliste> jpetrell, not for me : the four SailfishOS 4 ambiences are always first (except the current).
08:05:43 <thilo[m]> Is it a known issue that the bindings of the Mediaplayer in QML are a bit buggy? Signals are sent sometimes and sometimes not. This makes developing multimedia apps a bit of a pain
08:05:52 <thisisme> Hello! Edge swipes are noticeably more difficult with 4.2 as described here: https://forum.sailfishos.org/t/release-notes-verla-4-2-0/7092/51?u=thisisme   . Any ideas why?
08:06:08 <dcaliste> jpetrell, if you cannot reproduce, but I can, then, I'll try to give a look myself to the issue.
08:06:21 <rinigus> jpetrell and dcaliste : for me , sfos 4 ambiences first, then the current one and then the other starred one
08:06:24 <jpetrell> dcaliste: sorry actually now can reproduce. was only using the Sailfish OS 4 ambiences to test...
08:06:27 <sledges> dcaliste: jpetrell: wfm too, but maybe that's because we never changed favourited ones
08:06:41 <jpetrell> ouch, definitely needs fixing
08:06:53 <abr> jpetrell: I can, both in the settings app and top menu. the elemental ambiences are always first.
08:07:09 <thilo[m]> Regarding Qml, Multimedia: Was this issue noticed? https://forum.sailfishos.org/t/qtmultimedia-property-bindings-not-working-initially/8366
08:08:01 <sledges> ExTechOp: https://forum.sailfishos.org/t/fingerprint-record-lost-randomly/6283
08:08:13 <dcaliste> jpetrell, indeed. It's borring. At first I thought it was by design ;) to promote the new ambiences, so I convinced myself to accept this non-ideal situation !
08:08:39 <ExTechOp> sledges Thanks!
08:08:55 <jpetrell> sailfish 4 ambiences should be in the top on clean device, but then user's preferences should win
08:09:32 <sledges> np, restart sailfish-fpd should do in most cases:)
08:09:42 <dcaliste> Good that we agree on design :D
08:10:09 <ExTechOp> sledges With the suggestion is that bluetooth may be causing this, I have my car auto-connect to the bt handsfree every time I go driving.
08:10:34 <sledges> ExTechOp: nice, i'll check myself if there's correlation, thanks:)
08:10:50 <sledges> at first i thought it happens after low mem situations (when lkmd kicks in)
08:11:26 <ExTechOp> It could still be, I'm sure establishing the bt connection takes up some memory?
08:11:36 <sledges> thilo[m]: let's see if abr spots this, if not then this warrants a separate topic
08:11:47 <sledges> :)
08:12:04 <abr> I have no idea sorry :)
08:12:10 <thilo[m]> sledges: ty, i gonna post to the next meeting if this receives no attention in the forum
08:12:21 <sledges> just mentioning because we spoke about playbackRate the other time abr:)
08:12:43 <sledges> jpetrell: looks like edge swipes regressed on all devices, not only on x10ii, did we change something globally? https://forum.sailfishos.org/t/release-notes-verla-4-2-0/7092/51?u=thisisme
08:12:49 <abr> yeah that was fixed, but the bindings weren't touched afaik. must have already been broken
08:13:10 <thilo[m]> I can help there analyzing it btw, Im dug deep into multimedia because of podqast right now, just ping me
08:13:18 <sledges> woo!
08:13:23 <thilo[m]> abr: yeah was already broken
08:14:34 <sledges> any final words from Belin meeting before we wrap up? :)
08:14:45 <thilo[m]> sad i couldnt be there, was sick
08:14:56 <thilo[m]> but sounds like you had a great time!
08:14:56 <sledges> :[ hope you better now
08:15:23 <ExTechOp> Another thing is that using Situations (to switch the device to silent in the night etc) it seems to flake out after around a week, causing alarms/wakeups to be missed and/or be unacknowledgeable. I'm sure you understand it's a bit difficult to debug this.
08:15:27 <thilo[m]> yeah, i was better that day, but you dont go out with the least symptoms in these times, especially not to such an event ;)
08:15:34 <sledges> aye
08:16:00 <sledges> ExTechOp: could you try another app that does similar?
08:16:11 <thilo[m]> but im in for the 20 years celebration :P
08:16:20 <ExTechOp> sledges Suggestions on such an app for the Xperia 10II?
08:19:41 <ViGe> thilo[m]: Join us in Helsinki next week? :)
08:20:09 <thilo[m]> thought about it but flying would kill my co2 bilance ;)
08:20:13 <ExTechOp> ViGe Are there invitations going around?
08:20:21 <thilo[m]> but im in helsinki next year, do you take visitors? :)
08:20:23 <sledges> ExTechOp: Situations flaking out cause built-in alarms to be missed because it fails to get the phone out of silent mode?
08:20:35 <ViGe> ExTechOp: https://forum.sailfishos.org/t/join-our-10-year-celebration-in-helsinki-on-28th-october/8686
08:20:49 <sledges> #link https://forum.sailfishos.org/t/join-our-10-year-celebration-in-helsinki-on-28th-october/8686
08:22:58 <sledges> and don't forget to read the SFOS paper, new issue just dropped this morning:)
08:23:01 <sledges> #link https://forum.sailfishos.org/t/sailfish-community-news-21st-october-2021/8710
08:23:07 <sledges> and on that bombshell, it's time to end!
08:23:09 <sledges> #topic Next meeting time and date (5 min)
08:23:13 <sledges> Proposing Thursday 11th November at 8am UTC
08:23:21 <sledges> summer time over :((
08:23:36 <sledges> Hope to finish that meeting at 2021-11-11 11:11:11 Finnish timezone ;)
08:24:06 <ExTechOp> Thanks!
08:24:16 <chriadam> thanks everyone
08:24:18 <flypig> Yeah, thank you sledges+all.
08:24:27 <ExTechOp> And yes, that time would work
08:24:34 <flypig> Ditto.
08:24:41 <sledges> eleven eleven .. eleven it is
08:24:48 <sledges> #info Next meeting will be held on Thursday 11th November 2021 at 8:00am UTC:  2021-11-11T08Z
08:25:00 <sledges> thanks y'all!
08:25:02 <sledges> #endmeeting