| [07:53:57] | <mstenta[m]> | Huzzah! First blog post merged! Thanks symbioquine! 🎉 |
| [07:54:08] | <mstenta[m]> | https://github.com/farmOS/farmOS-community-blog/pull/1 |
| [07:54:28] | <mstenta[m]> | symbioquine paul121: I made you both maintainers of that repo (in addition to jgaehring and I) |
| [07:54:40] | <mstenta[m]> | If anyone else is interested in helping to maintain, let us know! |
| [07:55:30] | <mstenta[m]> | I also opened a second PR to propose that we organize blog posts into sub-directories by year: https://github.com/farmOS/farmOS-community-blog/pull/2 |
| [07:58:00] | <mstenta[m]> | I'll also add an item to the next monthly call agenda to get some more balls rolling on this! |
| [07:58:05] | <mstenta[m]> | Exciting!! |
| [08:07:37] | <mstenta[m]> | (I also bumped this one: https://github.com/farmOS/farmOS.org/issues/25) :-) |
| [08:07:54] | <mstenta[m]> | (Other people still use RSS, right? Am I the only one??) |
| [08:09:11] | <FarmerEd[m]> | 🦖 |
| [08:10:45] | <FarmerEd[m]> | Probably not the only one 😁 |
| [08:15:55] | <mstenta[m]> | I wonder how easy it would be to automatically publish a Tweet to the @farmOSorg twitter account when we publish new blog posts 🤔 |
| [08:16:24] | <mstenta[m]> | And/or a Toot! We should probably start a Mastadon account, huh? |
| [08:18:18] | <mstenta[m]> | https://github.com/farmOS/farmOS.org/issues/56 |
| [08:18:22] | <FarmerEd[m]> | I think RSS is far from dead to be fair but Twitter could well disappear before it depending on what Elon does to it. |
| [08:18:22] | <FarmerEd[m]> | Can't image it being too hard to Automate, |
| [08:19:16] | <mstenta[m]> | I would love to set up an official Mastadon account and automate some of this so it just broadcasts stuff to both. |
| [08:19:24] | <FarmerEd[m]> | I'm sure the API will be well documented both official and unofficial sources |
| [08:19:41] | <mstenta[m]> | I'll add this to the next monthly call agenda too ;-) |
| [08:33:18] | <mstenta[m]> | Also opened this: https://github.com/farmOS/farmOS-community-blog/issues/3 |
| [08:33:32] | <mstenta[m]> | (Sorry for the flurry! I'm excited about this now haha) |
| [08:53:07] | <FarmerEd[m]> | Where do we find this new blog section? Is there a PR to be completed to create a farmOS.org link under communities? |
| [08:54:49] | <mstenta[m]> | Yea there is a PR open here: https://github.com/farmOS/farmOS.org/pull/49 |
| [08:54:55] | <mstenta[m]> | Not published yet :-) |
| [08:55:45] | <mstenta[m]> | But if you are interested in starting a post feel free to do it as a PR for this repo Farmer Ed https://github.com/farmOS/farmOS-community-blog |
| [08:56:01] | <mstenta[m]> | You'll see symbioquine's post in there, as well as a `test` branch with two other examples |
| [14:03:41] | <symbioquine[m]> | mstenta: I think we might be ready to go with merging; |
| [14:03:41] | <symbioquine[m]> | * https://github.com/farmOS/farmOS-community-blog/pull/2 |
| [14:03:41] | <symbioquine[m]> | * https://github.com/farmOS/farmOS.org/pull/49 |
| [14:03:41] | <symbioquine[m]> | * https://github.com/farmOS/farmOS.org/pull/57 |
| [14:14:56] | <jgaehring[m]> | symbioquine: want me to add another commit for the `baseURI` etc? or are you already on it? |
| [14:16:50] | <symbioquine[m]> | Hmmm, I don't know what the motivation for changing "blog" -> "posts" was... it certainly seemed redundant as the folder name within a repo named "farmOS-community-blog" |
| [14:17:13] | <symbioquine[m]> | If that was the problem being solved, then it doesn't need to change elsewhere |
| [14:17:49] | <symbioquine[m]> | but if the goal was to make the posts show up under something which could encompass "not quite blog-ish" content, then maybe it does |
| [14:20:21] | <jgaehring[m]> | oh, maybe it isn't necessary |
| [14:20:22] | <symbioquine[m]> | I certainly don't feel strongly about it either way :) |
| [14:21:06] | <jgaehring[m]> | should have documented `site-data.js` config options better myself, but I was thinking that was why the blog post is not displaying |
| [14:21:14] | <jgaehring[m]> | don't think that's it though |
| [14:22:11] | <symbioquine[m]> | ACTION uploaded an image: (86KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/YyTwveUaWiQ... > |
| [14:22:39] | <symbioquine[m]> | That's what I get when i do `npm run build && npm run serve`. Is the problem you're talking about exhibited there? |
| [14:23:09] | <jgaehring[m]> | oh, I hadn't run it locally, just basing on the preview blog, but there may be other reasons that's not working |
| [14:23:26] | <jgaehring[m]> | s/blog/build/ |
| [14:23:38] | <symbioquine[m]> | `npm run start` doesn't seem to be working for me, maybe that's a similar issue |
| [14:25:01] | <mstenta[m]> | Ah hey! Just catching up... had a few meetings |
| [14:27:18] | <mstenta[m]> | > Hmmm, I don't know what the motivation for changing "blog" -> "posts" was... it certainly seemed redundant as the folder name within a repo named "farmOS-community-blog" |
| [14:27:19] | <mstenta[m]> | Oops I snuck that one in 🫣 |
| [14:28:42] | <mstenta[m]> | Yea that was roughly my thinking though. `/posts` felt a bit more flexible I guess. But just a very mild preference. If anyone feels strongly otherwise we can change it |
| [14:29:30] | <mstenta[m]> | Oh maybe I misunderstood... are you all trying to debug something? |
| [14:29:37] | <mstenta[m]> | Still catching up on the issues etc |
| [14:29:41] | <jgaehring[m]> | I like `posts` FWIW but no strong opinions |
| [14:30:38] | <mstenta[m]> | Still OK to merge https://github.com/farmOS/farmOS-community-blog/pull/2 symbioquine ? |
| [14:30:51] | <mstenta[m]> | (that changes `blog` -> `posts` AND organizes by year...) |
| [14:31:31] | <mstenta[m]> | (poor form on my part to combine them, I know I'm sorry) |
| [14:32:13] | <symbioquine[m]> | mstenta[m]: Yep |
| [14:32:26] | <jgaehring[m]> | we'll have a fresh preview of PR #49 in a moment, I just merged symbioquine's PR on my fork: |
| [14:32:26] | <jgaehring[m]> | https://github.com/jgaehring/farmOS.org/pull/1 |
| [14:32:50] | <mstenta[m]> | Merged! (https://github.com/farmOS/farmOS-community-blog/pull/2) |
| [14:32:51] | <jgaehring[m]> | in the meantime, I'll spin up my local server and see what's up |
| [14:33:23] | <jgaehring[m]> | hmm, yea, still doesn't see to be working in preview: |
| [14:33:23] | <jgaehring[m]> | https://deploy-preview-49--gracious-brattain-bdd606.netlify.app/blog/ |
| [14:34:10] | <symbioquine[m]> | The only issue needing troubleshooting that I know of is `npm start` not working and that could be something specific to my environment - though weird for that to not work, but `npm serve` to work. |
| [14:34:45] | <symbioquine[m]> | > <@jgaehring:matrix.org> hmm, yea, still doesn't see to be working in preview: |
| [14:34:45] | <symbioquine[m]> | > https://deploy-preview-49--gracious-brattain-bdd606.netlify.app/blog/ |
| [14:34:45] | <symbioquine[m]> | Oh, weird |
| [14:35:26] | <jgaehring[m]> | hmm, not working on my local either :-/ |
| [14:37:25] | <jgaehring[m]> | symbioquine[m]: huh, that is weird, `npm run build && npm run serve` _does_ work for me |
| [14:37:29] | <jgaehring[m]> | 🤔 |
| [14:40:01] | <jgaehring[m]> | even weirder, now `npm start` _is_ working for me |
| [14:40:05] | <jgaehring[m]> | 😅 |
| [14:40:31] | <symbioquine[m]> | What if you do `npm run clean` does it stop working again? |
| [14:42:39] | <jgaehring[m]> | symbioquine[m]: good thought, but after running `clean` then `start` again, it still works |
| [14:44:03] | <mstenta[m]> | npm version differences? |
| [14:44:15] | <symbioquine[m]> | Yeah, could be |
| [14:44:29] | <symbioquine[m]> | We probably have pretty different environments... |
| [14:44:30] | <jgaehring[m]> | hm, yea sure could |
| [14:44:37] | <mstenta[m]> | i'm a big proponent of running npm in docker 😅 |
| [14:44:40] | <jgaehring[m]> | or some other dependency |
| [14:44:46] | <symbioquine[m]> | `npm start` still isn't working for me |
| [14:45:10] | <jgaehring[m]> | might also be something peculiar to the GitHub Action |
| [14:45:26] | <symbioquine[m]> | One thing I see is |
| [14:45:27] | <symbioquine[m]> | ACTION uploaded an image: (40KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/kgPlDzEDCQF... > |
| [14:45:54] | <symbioquine[m]> | Which I think only happens when I run `npm start`, not `npm run build` |
| [14:46:46] | <mstenta[m]> | paul121: I wonder if these two issues should be in the farmOS.org repo? I had to ask myself the same question with the other issues I opened 😅 |
| [14:46:46] | <mstenta[m]> | - https://github.com/farmOS/farmOS-community-blog/issues/4 |
| [14:46:46] | <mstenta[m]> | - https://github.com/farmOS/farmOS-community-blog/issues/5 |
| [14:47:05] | <mstenta[m]> | I almost don't know if we need an issue queue in the blog repo at all... |
| [14:47:17] | <mstenta[m]> | although I did open this one there: https://github.com/farmOS/farmOS-community-blog/issues/3 |
| [14:47:44] | <mstenta[m]> | But that could potentially be moved elsewhere too, or discussed in the forum and just open a PR |
| [14:48:08] | <mstenta[m]> | (in the interest of directing everyone to the forum instead of making "yet another issue queue" an option... thoughts?) |
| [14:48:53] | <jgaehring[m]> | oh, think it's a Netlify issue |
| [14:49:25] | <jgaehring[m]> | not sure if you can see this, but... |
| [14:49:25] | <jgaehring[m]> | https://app.netlify.com/teams/jgaehring/builds/63601443d8c56f0008001f00#... |
| [14:49:43] | <symbioquine[m]> | > <@jgaehring:matrix.org> not sure if you can see this, but... |
| [14:49:43] | <symbioquine[m]> | > https://app.netlify.com/teams/jgaehring/builds/63601443d8c56f0008001f00#... |
| [14:49:44] | <symbioquine[m]> | I can't see that |
| [14:50:24] | <jgaehring[m]> | maybe this link then: |
| [14:50:24] | <jgaehring[m]> | https://app.netlify.com/sites/gracious-brattain-bdd606/deploys/63601443d... |
| [14:50:35] | <jgaehring[m]> | might be a red herring, but I'll try updating it |
| [14:50:47] | <symbioquine[m]> | > <@jgaehring:matrix.org> maybe this link then: |
| [14:50:47] | <symbioquine[m]> | > https://app.netlify.com/sites/gracious-brattain-bdd606/deploys/63601443d... |
| [14:50:47] | <symbioquine[m]> | yep |
| [14:54:40] | <jgaehring[m]> | jgaehring[m]: well, took a while to find the right settings page to do it, but finally did and running the build again to see |
| [14:55:18] | <paul121[m]> | <mstenta[m]> "(in the interest of directing..." <- oh, I suppose yes we don't really need an issue queue for the blog repo. but both of those issues I opened (I believe) would need need some code/github action added to the blog repo itself. I don't think it's a huge deal to keep it? |
| [14:55:30] | <paul121[m]> | <mstenta[m]> "(in the interest of directing..." <- I guess, if you found an issue with a blog post, where would you report? 🤷 |
| [14:55:59] | <jgaehring[m]> | jgaehring[m]: well shoot, that's probably why I didn't update it before: |
| [14:55:59] | <mstenta[m]> | oh ok, thought they only needed farmOS.org changes - fair enough - yea no harm in leaving it open i guess... |
| [14:55:59] | <jgaehring[m]> | https://app.netlify.com/sites/gracious-brattain-bdd606/deploys/636019b7e... |
| [14:55:59] | <paul121[m]> | s/need// |
| [14:56:11] | <jgaehring[m]> | says it worked though, lemme reload it and see |
| [14:56:41] | <jgaehring[m]> | ha! worked! |
| [14:56:41] | <jgaehring[m]> | https://deploy-preview-49--gracious-brattain-bdd606.netlify.app/blog/ |
| [14:57:13] | <mstenta[m]> | 🤩🎉 |
| [14:57:53] | <jgaehring[m]> | hmm, should I be nervous about that incompatible plugin though? don't think I have time today to upgrade Gatsby |
| [14:58:27] | <jgaehring[m]> | probably no biggie either way, we can always revert if a future build fails |
| [14:59:28] | <symbioquine[m]> | Yeah, I've noticed in other projects that Gatsby seems a bit high maintenance from a version upgrade/compatibility perspective... |
| [14:59:30] | <mstenta[m]> | Oh... can we get the "2022" bit in the URL so it's /blog/2022/getting-started? |
| [14:59:39] | <mstenta[m]> | Just noticed that... |
| [14:59:51] | <mstenta[m]> | Is that in the front matter? |
| [14:59:54] | <jgaehring[m]> | haha, and Gatsby 5 comes out tmw: |
| [14:59:55] | <jgaehring[m]> | https://www.gatsbyjs.com/resources/webinars/gatsby-v5 |
| [15:01:46] | <mstenta[m]> | will this do it? https://github.com/farmOS/farmOS-community-blog/pull/6 |
| [15:01:49] | <jgaehring[m]> | ACTION uploaded an image: (323KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/LzkjhcCJSFw... > |
| [15:02:56] | <jgaehring[m]> | mstenta[m]: eh, that might do it, but probably a better way |
| [15:03:46] | <mstenta[m]> | maybe start with that and then figure out another way and back-update any posts? |
| [15:03:57] | <jgaehring[m]> | I also don't think I realized you wanted that to be in the URL, is that for SEO? |
| [15:04:18] | <mstenta[m]> | don't want to add any more work before we launch |
| [15:04:40] | <jgaehring[m]> | I'm a little worried the `/` could mess up parsing somehow |
| [15:04:43] | <mstenta[m]> | maybe not so much SEO as just organization... eg: what if 10 years from now we want another "getting-started" post? |
| [15:05:52] | <mstenta[m]> | the nice thing about the blog is we can let these things flow into the past, and not get bogged down by maintaining/updating them if we don't want... but if all slugs are unique without year then we might start running into conflicts eventually... dunno |
| [15:06:21] | <symbioquine[m]> | jgaehring[m]: My guess is that it will work: https://github.com/jgaehring/farmOS.org/blob/43dfd1fd4d7c038518d59afafeb... |
| [15:07:39] | <symbioquine[m]> | As long as the FrontMatter parsing doesn't care |
| [15:08:05] | <jgaehring[m]> | oh, yea, I guess it should be able to create the route, but b/c we're not using a `config.yml` file it's gotta parse the pathname to build the nav tree, and that's where it might go bonk |
| [15:08:26] | <symbioquine[m]> | ah |
| [15:08:26] | <mstenta[m]> | ah |
| [15:08:31] | <jgaehring[m]> | or maybe not, haven't tested for that |
| [15:08:32] | <mstenta[m]> | jinx symbioquine |
| [15:09:27] | <jgaehring[m]> | kinda intended `slug` to be _just_ a slug, so no promises if you start treating it like a path segment |
| [15:10:31] | <mstenta[m]> | mm yea that makes sense jgaehring - where is the code for "finding" posts? maybe it could just use whatever subdirectories are in the `posts` dir too? |
| [15:10:59] | <mstenta[m]> | it would be nice to not have it in the slug i agree |
| [15:12:20] | <symbioquine[m]> | mstenta[m]: That seems really nice, then it also helps organize them within the repository! |
| [15:13:20] | <jgaehring[m]> | mstenta[m]: yea, this is actually what I intended, and what I thought you wanted to do w/ the subdirectories |
| [15:14:25] | <jgaehring[m]> | here's the parsing logic, it builds a tree that then gets passed to the react component that builds the menu: |
| [15:14:25] | <jgaehring[m]> | https://github.com/jgaehring/farmOS.org/blob/blog/lib/navigation.js |
| [15:17:51] | <jgaehring[m]> | I would probably suggest making changes in that React component, actually, or even better yet, altering the tree for the blog source specifically in `gatsby-node.js` |
| [15:19:03] | <jgaehring[m]> | but really best to add a `config.yml` or just change the directory structure, those are really the two options it was designed for, and the config file should give you all the freedom you want to structure the navigation |
| [15:21:52] | <mstenta[m]> | a `config.yml` in `farmOS-community-blog` you mean? |
| [15:22:23] | <mstenta[m]> | i'm not super familiar with how that works... would it require a line for every blog post? |
| [15:23:41] | <jgaehring[m]> | it works just alike `mkdocs.yml` |
| [15:23:55] | <mstenta[m]> | ah ok |
| [15:24:04] | <jgaehring[m]> | so yea, basically |
| [15:24:14] | <mstenta[m]> | makes sense |
| [15:24:31] | <mstenta[m]> | could get unwieldy |
| [15:24:43] | <mstenta[m]> | but maybe as a simple first step? |
| [15:25:09] | <mstenta[m]> | kinda defeats the purpose of having `slug` i guess |
| [15:25:17] | <jgaehring[m]> | ya know what, I take all that back |
| [15:25:29] | <jgaehring[m]> | (sorry, been too long since I was working on all this) |
| [15:25:51] | <jgaehring[m]> | I didn't really think we'd want to put EVERY blog post in the menu |
| [15:26:14] | <jgaehring[m]> | so it's not creating a nav tree anyways |
| [15:26:24] | <jgaehring[m]> | (so extra `/`'s won't be an issue) |
| [15:26:38] | <symbioquine[m]> | It would be nice to have a tag cloud (or something similar) also at some point |
| [15:26:41] | <mstenta[m]> | oooh! |
| [15:26:41] | <mstenta[m]> | gotcha! |
| [15:26:46] | <jgaehring[m]> | my going idea was, just list them in reverse chronological order for nwo |
| [15:26:46] | <jgaehring[m]> | now |
| [15:26:52] | <mstenta[m]> | ooooh tag clouds! haven't seen one of those in a while 😄 |
| [15:26:54] | <symbioquine[m]> | Doesn't make sense until we've got a few more posts of course |
| [15:27:06] | <jgaehring[m]> | and once there's enough content for that to become a problem, figure out something else then |
| [15:28:48] | <symbioquine[m]> | 🚲️🏠️🤓 |
| [15:29:38] | <mstenta[m]> | shall we try https://github.com/farmOS/farmOS-community-blog/pull/6 then? |
| [15:29:39] | <jgaehring[m]> | ACTION uploaded an image: (28KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/NuPxbUsvczV... > |
| [15:36:23] | <FarmerEd[m]> | Well done lads 👍 |
| [15:36:27] | <FarmerEd[m]> | Oíche Shamhna Shona Daoibh |
| [15:38:04] | <mstenta[m]> | jgaehring: should I just go ahead and merge that PR? or do we want to test it first? |
| [15:38:11] | <mstenta[m]> | (can always revert if it breaks something) |
| [15:38:44] | <jgaehring[m]> | mstenta[m]: which? |
| [15:38:51] | <mstenta[m]> | https://github.com/farmOS/farmOS-community-blog/pull/6 |
| [15:39:16] | <symbioquine[m]> | Seems low risk to me |
| [15:39:18] | <jgaehring[m]> | I don't see why not |
| [15:39:22] | <mstenta[m]> | done! |
| [15:39:37] | <jgaehring[m]> | ok, I'll rebuild the preview |
| [15:40:11] | <mstenta[m]> | paul121: off topic, but i have a few minutes to kill so i'm glancing at open farmOS PRs... I see this one is still a draft? https://github.com/farmOS/farmOS/pull/589 |
| [15:40:46] | <jgaehring[m]> | but until farmOS.org/#49 is merged nothing will appear on the main website |
| [15:40:57] | <mstenta[m]> | are we ready to merge? |
| [15:41:17] | <mstenta[m]> | paul121: oh nm i see... it's waiting for 2.0.9 release of farmOS-map |
| [15:42:01] | <paul121[m]> | I was going to ask, shall we release 2.0.9 ? Also, when do we start releasing 2.1.0? |
| [15:42:11] | <paul121[m]> | s/0/x/ |
| [15:42:48] | <mstenta[m]> | sure! 2.0.9 is a go! (IMO) |
| [15:42:50] | <symbioquine[m]> | paul121[m]: On the next breaking change? |
| [15:43:03] | <mstenta[m]> | I think technically 3.x would be for breaking changes |
| [15:43:11] | <mstenta[m]> | 2.1.x would be for new features |
| [15:43:14] | <mstenta[m]> | semantically speaking :-) |
| [15:43:27] | <mstenta[m]> | but we haven't really been following that |
| [15:43:51] | <jgaehring[m]> | still working! |
| [15:43:51] | <jgaehring[m]> | https://deploy-preview-49--gracious-brattain-bdd606.netlify.app/blog/202... |
| [15:43:56] | <symbioquine[m]> | Well you can have changes that are technically breaking, but just align with the expected behaviour of the existing features right? |
| [15:44:54] | <paul121[m]> | Maybe a distinction between behavior/UI changes and API changes? |
| [15:46:36] | <mstenta[m]> | > MINOR version when you add functionality in a backwards compatible manner |
| [15:46:37] | <mstenta[m]> | https://semver.org/ |
| [15:46:39] | <paul121[m]> | 2.0 -> 2.1 could have a UI change, but 2.0 -> 2.1 should not have a breaking API change? |
| [15:46:52] | <mstenta[m]> | > MAJOR version when you make incompatible API changes |
| [15:47:50] | <symbioquine[m]> | Yeah that. And the philosophical question of whether changes (like bug fixes) are backwards incompatible if they change the behaviour without changing the interface and bring the behaviour in line with the expected behavior. |
| [15:48:16] | <mstenta[m]> | Yea some of it is open to interpretation - devils in the details 😄 |
| [15:48:27] | <symbioquine[m]> | In theory someone can argue that it's still a breaking change if they depended on the broken behaviour, but from an interface/API perspective it's not a breaking change in that the code will still build/run. |
| [15:48:27] | <mstenta[m]> | But 2.1 should not be breaking anything, is my understanding |
| [15:50:33] | <mstenta[m]> | Big question on my mind is... should we move to farmOS 3.x w/ Drupal 10... 🫣 |
| [15:50:40] | <symbioquine[m]> | For example I would argue that we wouldn't need a new major version for farm_map_google if we made the change to restrict the minimum zoom level when the google layers are showing - even though in theory someone might depend on the current (broken) behavior at those zoom levels. |
| [15:51:03] | <symbioquine[m]> | But a new minor version would probably be a good idea |
| [15:51:20] | <mstenta[m]> | paul121 made the point that we may end up skipping v2 stable 🤣 |
| [15:52:11] | <symbioquine[m]> | What do you mean? |
| [15:52:20] | <mstenta[m]> | symbioquine: yea... i suppose it's all about the "public APIs" (whatever that means in each project)... and whether or not those change |
| [15:52:46] | <symbioquine[m]> | agreed |
| [15:53:29] | <mstenta[m]> | Well... the D10 upgrade will introduce some new requirements upstream that may be considered "breaking" enough that we should warn folks with 3.x... dunno yet. eg: it will require PostgreSQL 13... and it will be upgrading Symfony... so it could mean modules aren't compatible and need minor tweaks |
| [15:53:53] | <mstenta[m]> | PostgreSQL 13 w/ the `pg_trgm` module, specifically |
| [15:53:58] | <symbioquine[m]> | Wow, I guess that makes sense |
| [15:54:41] | <mstenta[m]> | It also might be nice to just break loose and go farmOS 4.x, 5.x, 6.x, etc without waiting 10 years in between each haha |
| [15:54:42] | <symbioquine[m]> | Seems like lots of projects accelerate their versioning changes as they mature |
| [15:54:42] | <mstenta[m]> | Like OpenLayers did |
| [15:54:47] | <mstenta[m]> | Yea exactly |
| [15:55:04] | <mstenta[m]> | I don't see us making the jump to D10 for a bit... so we'll still be on 2.x for a while I imagine |
| [15:55:08] | <mstenta[m]> | Just thinking ahead |
| [15:55:31] | <symbioquine[m]> | Firefox, QGIS, FreeCAD, etc |
| [15:55:32] | <mstenta[m]> | yea |
| [15:55:48] | <symbioquine[m]> | (Firefox is maybe a bit of a special case) |
| [15:55:57] | <symbioquine[m]> | Browser wars being what they are |
| [15:56:31] | <mstenta[m]> | jgaehring: I didn't look closely, but I approved the PR :-) |
| [15:56:54] | <mstenta[m]> | I have to run for now... time to take the kids out for some early trick or treating :-) |
| [15:57:18] | <paul121[m]> | may they have a bountiful harvest :-)_ |
| [15:57:22] | <paul121[m]> | * may they have a bountiful harvest :-) |
| [15:58:26] | <jgaehring[m]> | mstenta[m]: oh great, thanks, I was just adding a comment, but I'll merge right after, then it'll be live and I'll need to step away myself, but huzzah!!! |
| [15:58:36] | <evered[m]> | ACTION uploaded an image: (38KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/OJqExUMlITw... > |
| [15:59:17] | <evered[m]> | I switched to Chrome a couple three years ago, from Mozilla Firefox. :D |
| [15:59:33] | <evered[m]> | This stat is from Wikipedia after a quick Goo-gle search. |
| [16:08:52] | <jgaehring[m]> | https://farmos.org/blog/2022/getting-started |
| [16:08:53] | <jgaehring[m]> | HUZZAH!!!!! |
| [16:09:03] | <jgaehring[m]> | 🎉🎉🎉 |
| [16:09:38] | <paul121[m]> | awesome :-) |
| [16:10:58] | <mstenta[m]> | Huzzah! |
| [16:11:26] | <mstenta[m]> | I'll try to remember to tweet it later :-) |
