IRC logs for #farmOS, 2022-11-11 (GMT)

2022-11-10
2022-11-12
TimeNickMessage
[20:00:41]* symbioquine[m] has quit (Read error: Software caused connection abort)
[20:17:28]* symbioquine[m] has joined #farmos
[20:31:13]<mstenta[m]>https://twitter.com/AaronBobeck/status/1590776331775741963
[22:22:35]<mstenta[m]>paul121 jgaehring symbioquine pcambra 3wc ~ they/them Farmer Ed Ok sooo... I went down a little rabbit hole... 😄🐇
[22:22:58]<mstenta[m]>I set up a Mastadon account: https://fosstodon.org/@farmOS
[22:24:25]<mstenta[m]>And a GitHub repo w/ an action that publishes commit messages to both Mastadon and Twitter: https://github.com/mstenta/farmOS-microblog
[22:24:53]<mstenta[m]>https://fosstodon.org/web/@farmOS/109323003652149870
[22:25:12]<mstenta[m]>https://twitter.com/farmOSorg/status/1590906546271264768
[22:25:26]<mstenta[m]>proof of concept... thoughts?
[22:26:28]<mstenta[m]>one neat thing we could do with this: when a new blog post gets published we could automatically add a commit to this repo
[22:28:06]<mstenta[m]>it also provides a way to grant more folks access to publish tweets/toots, without the need to share twitter/mastodon passwords
[22:29:40]<mstenta[m]>one thing i like about this idea is it creates a record of official announcements
[22:30:15]<mstenta[m]>it won't capture engagement on each platform, of course... (likes, comments, retweets, etc)
[22:30:35]<mstenta[m]>but maybe still nice as an archive
[22:40:01]<mstenta[m]>ooh what if we embed mastodon on the farmOS.org homepage...
[22:40:38]<mstenta[m]>looks like this will generate an iframe: http://www.mastofeed.com/
[22:41:38]<mstenta[m]>so we'd have "microblog" on the homepage, w/ news, updates, and links to full blog posts
[22:42:10]<mstenta[m]>all controlled from another Git repo 😄
[22:43:24]<paul121[m]>Sounds pretty useful!
[22:44:01]<paul121[m]>I made a fosstodon account today too, mastodon.social is closed for signups haha
[22:44:18]<mstenta[m]>oh wow! have they been flooded?
[22:44:44]<paul121[m]>I think so
[22:48:22]<paul121[m]>Release notifications could be automated too?
[22:48:50]<mstenta[m]>Yesss!
[22:48:51]<paul121[m]>At any rate it makes our lives kinda fun, and that's the whole point of this, right? :D
[22:48:58]<mstenta[m]>YES!
[22:49:37]<mstenta[m]>(i needed something fun to hack on)
[22:59:13]<mstenta[m]>https://github.com/farmOS/farmOS.org/pull/60
[22:59:52]<mstenta[m]>just another proof of concept to start the discussion ^
[23:00:37]* calbasi[m] has quit (Read error: Software caused connection abort)
[23:00:53]* calbasi[m] has joined #farmos
[23:07:21]<mstenta[m]>https://deploy-preview-60--gracious-brattain-bdd606.netlify.app/
[23:34:14]* ircwaves[m] has quit (Read error: Software caused connection abort)
[23:36:30]<symbioquine[m]><mstenta[m]> "I set up a Mastadon account..." <- Followed!
[23:49:10]<paul121[m]>Could newsletters be added to the community blog as well? And be archived/tooted with this same infrastructure?
[23:49:55]<paul121[m]>Maybeeee emailed but we could probably do that manually :-)
[23:51:06]* ircwaves[m] has joined #farmos
[00:35:54]<paul121[m]>In the past we talked about using Buttondown which uses markdown and has an API: https://docs.buttondown.email/api-reference/introduction
[06:39:16]<mstenta[m]>Automate all the things!!
[06:40:14]<mstenta[m]>> one neat thing we could do with this: when a new blog post gets published we could automatically add a commit to this repo
[06:40:14]<mstenta[m]>a big question in my mind... for both this ^ and "sending a newsletter" paul121 is: what is the trigger?
[06:40:44]<mstenta[m]>we don't really have an explicit "publish" action
[06:40:58]<mstenta[m]>maybe when a PR is merged?
[06:41:58]<mstenta[m]>and we have a blog category for "Newsletter" perhaps? or... maybe a separate `newsletters/**` directory we could trigger GH actions on?
[06:43:05]<mstenta[m]>another slight oddity with all this: the date of a blog post isn't necessarily when it is published exactly
[06:43:28]<mstenta[m]>so some things to think through... but i love the ideas generally!
[06:45:16]<mstenta[m]>> Release notifications could be automated too?
[06:45:16]<mstenta[m]>I am SO glad you suggested THIS too! I might look into that next... it would remove another manual step from the release procedure! https://farmos.discourse.group/t/2-x-release-procedure/1070
[06:45:56]<mstenta[m]>And it would be a perfect followup to the Docker Hub automation I have ready to merge as well
[06:46:56]<mstenta[m]>Now I'm curious if OpenCollective has an API as well... 🤔 (also for automating release announcements... and maybe newsletters too!)
[06:53:26]<mstenta[m]>I feel like the flow of this is starting to gel in my mind:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/74427d7105...)
[06:54:02]<mstenta[m]>And all of it (I think) could be automated from the farmOS-community-blog and farmOS-microblog repos!
[06:56:40]<mstenta[m]>(... pondering whether or not farmOS-microblog should just be another branch of farmOS-community-blog... just to simplify/unify... but I think there are some good reasons to keep them separate too...)
[06:57:31]<mstenta[m]>Excited to brainstorm more on all this! Wish the next monthly call wasn't a whole month away! 😄
[07:00:27]<mstenta[m]>In either case... jgaehring paul121 symbioquine if y'all like where this is headed, any objection to moving https://github.com/mstenta/farmOS-microblog to the farmOS GH org and making a second commit to announce that we're on Mastodon? 😃
[07:25:56]<mstenta[m]>It does look like OC has an API for updates: https://graphql-docs-v2.opencollective.com/update.doc.html
[07:25:56]<mstenta[m]>GraphQL is very foreign to me though
[08:44:13]<jgaehring[m]><mstenta[m]> "In either case... jgaehring paul..." <- go for it! I wish I had more bandwidth to give to all this stuff right now, but trying best I can to get Field Kit to beta (finally) plus other competing interests, so don't let me be a blocker for any of this, all looks great!
[08:44:33]<mstenta[m]>awesome!!
[08:45:11]<mstenta[m]>ps: i also just made a free buttondown acct: https://buttondown.email/farmOS 😄
[08:46:15]<mstenta[m]>for some reason doing actual programming feels harder with one arm, but this kind of stuff is doable, so i'm just rolling with it!
[09:55:26]<mstenta[m]>https://farmos.discourse.group/t/funding-proposal-buttondown-email-basic...
[10:31:16]<mstenta[m]>> In either case... jgaehring paul121 symbioquine if y'all like where this is headed, any objection to moving https://github.com/mstenta/farmOS-microblog to the farmOS GH org and making a second commit to announce that we're on Mastodon? 😃
[10:31:16]<mstenta[m]>went ahead with this :-)
[10:31:19]<mstenta[m]>https://twitter.com/farmOSorg/status/1591090730507853825 / https://fosstodon.org/web/@farmOS/109325881538051078
[10:32:19]<mstenta[m]>Just had another idea: can we automatically announce monthly / weekly call links with this?
[10:33:14]<symbioquine[m]>mstenta[m]: That's awesome!
[10:33:35]<mstenta[m]>I suppose at the very least I can set up a cron script somewhere to do that haha
[10:34:05]<mstenta[m]>Oh! Maybe on the irc.farmos.org server...
[10:34:27]<mstenta[m]>Since its already on 24x7 and we're paying for it
[10:34:40]<mstenta[m]>Or another GitHub Action perhaps...
[10:35:46]<mstenta[m]>Maybe another action in the same repo would work
[10:36:11]<mstenta[m]>The funny thing about the way this is set up is we need to tweet/toot to commit changes to the repo 😆
[10:36:13]<symbioquine[m]>The tricky bit would be getting it to run at the right time without running super frequently...
[10:36:24]<mstenta[m]>Mmm yeaa
[11:48:05]<threewordchant><mstenta[m]> "And a GitHub repo w/ an action..." <- that's super cool! never seen anything like that, amazing collaborative praxis 👏
[12:24:49]<mstenta[m]>And if you aren't on Mastodon or Twitter you can just subscribe to our GitHub Actions: https://github.com/farmOS/farmOS-microblog/actions 😆
[12:26:49]<symbioquine[m]>Maybe https://github.com/farmOS/farmOS-microblog/commits.atom would be better...
[12:27:18]<mstenta[m]>https://i.kym-cdn.com/entries/icons/original/000/022/900/704.jpg
[12:35:42]<mstenta[m]>> The tricky bit would be getting it to run at the right time without running super frequently...
[12:35:43]<mstenta[m]>Now I want to figure this out...
[12:37:18]<mstenta[m]>Weekly dev calls seems pretty straightfoward: https://cron.help/#0_9_*_*_Thu w/ a message like "The #farmOS weekly dev call is today at 12 pm noon Eastern. All are welcome! https://meet.jit.si/farmos-dev"
[12:37:32]<mstenta[m]>Monthly call is trickier...
[12:37:39]<mstenta[m]>https://askubuntu.com/questions/1361146/crontab-date-definition-for-only...
[12:38:14]<mstenta[m]>But if we ran it every Wed, with a secondary bash conditional... somehow?
[12:38:29]<mstenta[m]>(via GitHub Actions I'm thinking for both)
[12:38:45]<mstenta[m]>https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-g...
[12:46:49]<mstenta[m]>https://antonydandrea.com/running-a-cron-job-every-2nd-wednesday-of-the-...
[12:59:55]<mstenta[m]>Think this'll work? https://github.com/farmOS/farmOS-microblog/pull/1