19:04 <LyreCalliope[m]> The keybase organ shutdown has begun. We're still good for now, but this feels like the official countdown is beginning.

19:05 <ocdtrekkie> I heard Zoom dropped 15% of their staff, it doesn't surprise me supporting Keybase stuff is on the chopping block.

19:17 <LyreCalliope[m]> Wow. These layoffs really do feel like collusion. Gotta rebalance the labor market to keep developers wages in check. Pass down the side side effects to everyone else.

19:18 <ocdtrekkie> Probably, though FWIW, all these tech companies feel like they were paying people multiples of what the rest of us get anyways. I know real estate in tech hubs is obscene, but when someone posts online they won't consider a developer job for less than a quarter million dollars a year, it blows me away.

19:19 <ocdtrekkie> It'd just be nice if the CEOs salaries took some of the hit too. Which of course they don't.

19:20 <ocdtrekkie> Worst case re:Keybase, if it stops working, people just see a PGP key for the author instead of the author info. They can still go to the source link to contact the author. But I suspect even if we switch to Keyoxide, we may want a little database somewhere servers can query the legacy Keybase profile info for older apps. We only have a couple dozen profiles that need to be cached, and I think the app index is already caching that data.

19:30 <TimMc> LyreCalliope[m]: Wow, I haven't thought about Keybase in a while...

22:18 <isd> fr33domlover: I just realized there was a gitlab.com mirror this whole time that I'd totally forgotten about: https://gitlab.com/isd/haskell-capnp :P

22:19 <isd> More mirrors is better though I guess.

22:19 <isd> I think I set that up to use gitlab CI at some point

22:20 <ocdtrekkie> haskell-capnp is now like the most decentralized git repo I've ever heard of, you can work on it with whatever flavor of code forge you want now. :P

22:20 <ocdtrekkie> mirror all the things

22:21 <isd> I'm willing to bet the linux kernel holds that title.

22:22 <ocdtrekkie> I don't know, are they willing to accept patches through three different software stacks? Or do they have one approved method?

22:28 <isd> Different subsystems use totally different places, and then stuff gets merged by local maintainers up the tree until it lands in Linus's repo. there's a file MAINTAINERS in the repo that tells you where to submit issues/patches based on what part of the code you're working on.

22:29 <isd> They mostly still use git-format-patch/git-am rather than using the PR/MR workflow

22:29 <isd> i.e. "email a patch to this mailing list"

22:31 <isd> The file is literally over 22K lines long

22:33 <ocdtrekkie> I think we've put too much thought into my "woo, it's mirrored on three different code forge platforms" comment at this point though. :P

22:33 <isd> Also the other day I started fussing with https://gitlab.com/isd/guile-capnp

22:33 <isd> Agreed :P

22:33 <ocdtrekkie> Very neat! Hopefully someday I can garden cabbages from inside a Sandstorm app.