Kyle Davis

https://fosstodon.org/@linux_mclinuxface

Ceaseless tinkerer.  I do open source stuff for #Valkey at AWS. Ex-#bottlerocket. Ex-#OpenSearch. Ex-#Redis.  Spare time pursuits: #3dprinting, #OpenSCAD, #gardening.  Interested in building a greener future with technology. he/him

Located in Edmonton, AB #yeg

Searchable on tootfinder

Opinions:: My own, not my employers.
Bird site account: @stockholmux
GitHub: https://github.com/stockholmux
Website: https://kylejdavis.com

Public Key

npub1tuk6cgtux45qe089wja2ptnqjde6x4h0rhs6ktks4ys2hwwm8llsep9wu4

NIP-05 Address

[email protected]

Profile Code

nprofile1qqs97tdvy97r26qvhnjhfw4q4esfxuar2mh3mcdt9mg2jg9th8dnllcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsr0e4mt

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1tuk6cgtux45qe089wja2ptnqjde6x4h0rhs6ktks4ys2hwwm8llsep9wu4

Show more details

Last Notes

2024-08-13 11:28:57

What isn’t coffee good for?
https://hackaday.com/2024/08/12/hydrogen-generation-with-seawater-aluminum-and-coffee/

2024-08-05 19:22:08

- reply

dude. That’s not how you’re supposed to brush.

2024-07-29 12:09:26

- reply

love CRDTs. Excited to try this out.

2024-07-19 10:12:41

Now I want a coffee table like this.
(Via Radio Shack Memories on FB)
https://cdn.fosstodon.org/media_attachments/files/112/812/144/565/739/785/original/80ac451687b5bec0.jpeg

2024-07-03 11:07:38

- reply

weeee!
Finally start playing around with $t?

2024-06-22 20:04:06

- reply

former Holy Roman Empire would be very broad.

2024-06-20 14:38:42

Woohoo! My launch day, early-bird Sovol #SV08 finally shipped.
I'm going on a very long trip next week so it's very possible I won't even get to assemble it until August or September though.
#3dPrinting
https://cdn.fosstodon.org/media_attachments/files/112/648/971/656/855/136/original/6868881e84f02db9.png

2024-06-15 20:31:45

- reply

one of my first “I ran into obscene money” purchases would be the Instax TLR.
https://mint-camera.com/en/shop/cameras/instantflex-tl70-plus/

2024-06-15 19:06:30

- reply

there are so many implications of a major city being on ‘rv rules’
I’m flying through YYC on an important trip transatlantic at the end of the month.
I started thinking about how a giant aircraft gets turned around with these water restrictions.
Water is so fundamental.

2024-06-15 18:57:46

- reply

definitely a life anti-trophy.

2024-06-15 18:54:06

- reply

and yet Stampede must go on.

2024-06-14 02:56:56

- reply

I agree. Breaking changes frequently are bad.
Very clear distinction between breaking, feature, and bug fix releases is useful. You only really get that in a post-1.0.0 SemVer
Pre-1.0.0 often obscures that: it becomes unclear if a release fixes a bug or adds a feature you don’t care about (or worse, a breaking change, but it thats often non-Rust projects).

2024-06-13 19:01:35

- reply

So, you wrote "avoid ballooning number of post-1.0 major releases."
Why does that matter?

2024-06-13 16:51:29

- reply

I'd argue that Cargo doesn't use really use SemVer. If you say use use a spec but you start heaping rules on top is that really adhering to the spec?
Seeing a problem with post-1.0.0 releases is actually part of the issue here. It's weird sentimentality on major versions.

2024-06-13 16:30:48

- reply

I am not trolling but ZeroVer is definitely troll-ish (in the best way).
I really hate the 1.0.0 bar in Rust. I get the interaction with the type system, but also maybe there is a misunderstanding or clash with SemVer along the line.
Perhaps the biggest failure in this whole thing is trying to break the emotion of 1.0.0 and major version releases.
Pre-1.0.0, break all you want (even people in production). Communicating that break via major version? Bad.

2024-06-12 14:54:07

- reply

clearly anti-Alberta bias.
(Half joking)

2024-06-11 23:32:19

- reply

I hear ya but he loathes clothes, especially in the summer.
He’s just a tricky, all legs shape.

2024-06-11 23:01:48

This is from a couple of years ago: Mr. Button and a little surgery and we tried an alternate to the cone of shame.
It didn’t work but he looked very handsome.
#DogsOfMastodon
https://cdn.fosstodon.org/media_attachments/files/112/599/992/515/069/523/original/af85f2ec2f061833.jpeg

2024-06-11 22:57:23

- reply

It reminds me of this great session from #TXLF about the oldest peripheral with a driver in Linux. I think it was from 1909?
https://2024.texaslinuxfest.org/talks/the-oldest-linux-peripheral/

2024-06-11 20:54:49

- reply

we had both a daisy wheel (military surplus beast) and a dot matrix.
I’m willing to bet that daisy wheel would easily work on a Linux machine today. The dot matrix less likely.

2024-06-11 20:51:04

- reply

that must have been slick for the day.

2024-06-11 20:49:53

- reply

it wasn’t all good back in the day. I recall some DOS programs just not working with particular printers. So, buy software from a store, bring it home, tough luck.
(But yes, an #oshw printer would be keen. Thermal seems very do-able. Ink and laser… much more complicated.)

2024-06-11 20:46:20

- reply

I don’t recall ever using the copy function.

2024-06-11 20:41:16

- reply

This wasn't some sort of proprietary thing, IIRC, you just plugged it between your printer and the parallel port and it just worked. We used it on our #PCjr and later our 286 machine.
Reading the description in the catalogue it was even more interesting than I thought. It was programmable and had an OS. In the late 80s!
2/2

2024-06-11 20:41:04

Of all the #retrocomputing stuff I see online, there was one device from my childhood that I've yet to see discussed.
The Radio Shack PTC-64 Print Controller.
It was a miracle. Back in the day, you had to wait for your computer feed your printer data, preventing it from doing anything else.
With the print controller (we called it a 'print spooler') you just sent jobs off to print and your computer rapidly would return to do other stuff.
1/2
https://www.trs-80.com/wordpress/models/printers/
https://cdn.fosstodon.org/media_attachments/files/112/599/429/369/201/912/original/b9117aebdeef7868.png

2024-06-11 18:39:06

- reply

definitely should include Valkey!

2024-06-09 20:25:22

- reply

I prefer opt in telemetry (I’m required to select no telemetry anyway).
Also it can’t choke in an air gapped environment if i accidentally have telemetry on.

2024-06-05 13:24:13

A Q&A with @npub1sh3…6stv about #Valkey
https://www.odbms.org/2024/06/on-the-open-source-valkey-project-qa-with-madelyn-olson/

2024-06-05 06:08:59

- reply

I dunno. That’s one thing I want dumb.

2024-06-04 23:53:41

- reply

exactly.

2024-06-04 18:35:03

Being the only Canadian on a team that is full of people who are from/live-in the US is interesting.
When someone doesn't understand a term or reference I say, they automatically assume it's a 'Canadian-thing'.
Very freeing, actually.

2024-06-04 14:32:00

- reply

it’s such a hassle at that point just throw a new 9v in it.

2024-06-04 14:29:34

- reply

mine are also hard wired and they still chirp!

2024-06-04 14:16:46

- reply

they are very inconsiderate.
But yeah, I know it a life safety devices but the time of chirping is always so consistently in the middle of the night.

2024-06-04 14:06:54

Why must smoke alarms always decide to start low-battery chirping at 4am?
I would definitely pay extra for one with a small back up battery and a real time clock that would only low-battery chirp between 9am and 9pm.

2024-06-04 06:05:22

- reply

“(foreign language)” on the subtitles makes lose control of my bowels in anger.

2024-06-04 01:11:34

- reply

according to @npub1wf9…8mkg, this is very likely the case, assuming nothing goes awry with Fedora 41.

2024-06-03 21:19:14

- reply

(Big credit to @npub17k6…r3xx on this!)

2024-06-03 21:18:06

And following up from Alpine...Fresh out of the FESCo meeting:
#Valkey replaces Redis in #Fedora 41.

2024-06-03 20:29:12

- reply

ah, good to know. Still, the problem remains is that they are distributing a bunch of step files w/o a license and calling it open source.

2024-06-03 17:36:58

#Alpine has replaced Redis with #Valkey in 3.2.0
https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.20.0#Redis

2024-06-03 15:43:41

- reply

and it was a single file, no license file.
You _could_ distribute open source via Google Drive, but you’d still need the license file. It would be very weird, but you could.

2024-06-03 14:19:26

- reply

what keeps them in the hole? Friction? Glue? Heat setting?

2024-06-03 14:08:27

- reply

(I should add that both are based on Voron, but at least Sovol is upholding their obligations.)

2024-06-03 14:07:20

:sigh:
In the #3dPrinting world, #OpenSource is so misunderstood.
There was a video comparing the Sovol #SV08 (GPL3) to a Troodon kit. The creator concluded that one place the SV08 definitively had a leg up was that it was open source.
About a week later the same creator posted a google drive link with the STEP file for the Troodon saying "Look, Troodon is open source."
Open up the STEP file in FreeCAD and the license metadata: "All rights reserved."
https://cdn.fosstodon.org/media_attachments/files/112/552/596/393/654/690/original/bf4b59a1151565ed.png

2024-06-03 00:31:53

- reply

yeah, I hate that stuff. Big problem on printables; sometimes they even win contests.
However, It does look like many have successfully printed this though. There are some commenters grumbling about the STL being weird but the step file being fine.

2024-06-03 00:17:04

- reply

that’ll do it.
It’s amazing how many people put broken models on sites like printables.
Good luck - if you still have problem you may have to manually fix them the mesh.

2024-06-02 23:25:07

- reply

what does the preview path look like? I kind of suspect a non-manifold model.

2024-06-02 20:33:22

- reply

ah! I was talking about a networking switch. Signaling between the boards via IP, not power. Power could still come from PoE but it would need still need power regulators, mosefts, etc.
You would definitely need that board and something else. I think you could likely come up with a single board useful in different contexts though, depending software and how you populate it.

2024-06-02 20:22:49

- reply

yep.
The insurance man not paying to rebuild your house should be a more common point of discussion in DIY circles.

2024-06-02 20:06:09

- reply

IIRC, real time patches make Linux a different beast on any fronts.
And I’m highly suspicious of Python in anything RT given stuff like GC and GIL. So, yeah, compiled.

2024-06-02 20:02:32

- reply

I don’t think anyone is debating that you’d need some sort of power transistor to manage the required current. All the MCU is responsible for is switching transistor.

2024-06-02 18:48:42

- reply

I have a feeling people use cable chains sometime because they _look_ cool (sadly)

2024-06-02 18:47:22

- reply

Humm, maybe.
I recall the original marketing material touted heat up speed as an advantage. Seems like now they pulled back on that (probably due to reliability, as you mention).
Regardless, I think there is a lot that could be done on the bed with a dedicated MCU.

2024-06-02 18:26:58

- reply

Honestly question: Would you _need_ a cable chain if you had a single cable?

2024-06-02 18:16:26

- reply

take a look at the Prusa XL’s heated bed setup. It’s got its own ARM MCU.
IMHO something like this is the future. The idea of switch AC to heat up the whole thing seems wasteful and silly. Most of the time you only need to heat a fraction of the bed.
(Image from Reddit)
https://cdn.fosstodon.org/media_attachments/files/112/547/906/742/196/069/original/570b16c8f6b01aed.jpeg

2024-06-02 18:09:13

I find stories like this fascinating in context of the electricty discourse going on in #Alberta.
The Western Interconnection is “our” grid, which includes California (we’re not electrical an island like Texas, despite what some would like you to think).
We talk a lot about “energy” but are we missing the point, to the detriment of our own future?
If we’re not careful, our investments will end up being obsoleted by what’s going on in the wider context.
https://cleantechnica.com/2024/06/02/solar-passes-100-of-power-demand-in-california/

2024-06-02 17:51:31

- reply

that’s a big sheep.

2024-06-02 17:50:18

- reply

sure. Probably not suitable for bog standard connectors/cables. There are options for ruggedized RJ45/cat-6 cables.
OTOH, Same would be said for USB-C though, right?

2024-06-02 17:24:36

- reply

ironically, I'd feel much better about doing real time control in 1989 than today.
There is just a lot going on in a modern Linux on a (semi) modern chip, there is just so much going on. Paring that down is tough and uncomfortable has tradeoffs. Far easier to farm it out to an MCU for rt stuff.
Putting them together would allow non-RT critical stuff on Linux (sensors, etc.) and keep the motor control RT. All in one package.

2024-06-02 16:55:08

- reply

I have several issues with Raspberry Pi, both as a company and their products.
Mutual pin control is really interesting. Linux isn’t realtime, so time sensitive control still needs an MCU which you can’t do with a zero, so you have to add another board.
It also opens up potential for elimination of an entire layer of protocol between the two devices.
Finally, I’m going to assume that the RISC-V board is much more power efficient than a zero + an MCU.

2024-06-02 16:46:42

- reply

multiple MCUs common today already in the form of tool head boards 🤷
In my experience, a lot of the annoying complexity of self building and sourcing is around crimping and speciality wiring.
And people are squeamish (or prohibited in some regions) in making power connections.
I constantly think: Make it simpler, reduce the BOM.

2024-06-02 16:25:12

- reply

there are a bunch of standards but looks like 71 watts is the highest one.
Probably not enough for a heated bed, but motors and hot ends are within the range.

2024-06-02 16:13:41

- reply

Imagine this:
- Rig PoE
- Each component gets its own board (extruder, axis motors, screen, fans, etc.)
- Connect everything with RJ45 to a small switch
2/2

2024-06-02 16:13:32

I am intrigued by this board.
Dual RISC-V cores, one running Arduino and the other running Linux + on-board ethernet. The kicker: they can jointly control the GPIO pins. Oh, and it's $8.
It's likely not powerful enough to run #Klipper in a #3dPrinting application today, BUT this would be extremely interesting to run something Klipper-like without the split brain of MCU and Linux.
https://youtu.be/SeExddxWdNs
1/2

2024-06-02 16:01:29

- reply

huh. Yeah, the quantity of 1 thing is a big problem, even knowing what I know. I can totally understand that setup, not material or production time is what costs here.
Anyway, maybe I was just poking around at the wrong places. Next time I need something I'm going to see what I can get done locally instead of being shipped from god knows where.

2024-06-02 03:15:00

- reply

oh yeah, there are adds about this at our airport (which is a little weird).
Ironically, they’d probably not touch anything I would need though. Too small potatoes vs giant contracts like yours coming in.

2024-06-01 22:07:11

- reply

well, I can only outside the know-how about machining, as we live in different counties (about 3000km apart).
I’d still need to get it done by someone.

2024-06-01 22:00:57

- reply

I have a brother that teaches machining, so I’d just outsource it. 😉

2024-06-01 17:04:06

I see a lot of #3dPrinting content overlap with machining and metal working.
The making and designing aspect of that is mildly interesting to me, but I know I'll likely never have a CNC/metal lathe/wielder. It just wouldn't fit into my space nor would I have the time to learn the craft.
All of this content is just kind of a miss for me. Am I alone in this?

2024-05-30 21:48:06

I've been reviewing the #Valkey docs before publishing them. They were inherited from that other project and the neglect is pretty wild.
Here is my favourite so far.
A linked example that has been public for 14+ years with a note that it's been broken since 2010 (because of Chrome _6_).
😳
https://github.com/valkey-io/valkey-doc/issues/128

2024-05-29 18:59:44

- reply

lol. More general than that!

2024-05-29 17:55:13

Linking to autogen IDs from Markdown headers is a link rot disaster. Don't do it.
E.g. `# My heading` changed to `# My awesome heading` on foo.md also changes the ID, so someone linking to `foo.md#my-heading` is screwed.

2024-05-03 16:28:18

- reply

yeah, I did cut and come again. I would usually just add a bit more nutrients. The quality/taste does go down quickly though.

2024-05-03 15:31:58

- reply

surprised how clean the roots look. Good job! Algae in my setup was hard to control with _anythjng_ not fully blacked out.
I suspect that you’ll have a lot of nutrients left over when the lettuce is harvested. Not a big deal, but you could probably go smaller. I found about 2 liters was just sufficient for most loose leaf lettuce.

2024-05-03 15:17:12

- reply

how’s it look in the reservoir? Are the roots out pacing the nutrients? Any algae?

2024-04-29 23:04:14

I sat in on FESCo meeting today regarding [@jonathanspw](https://fosstodon.org/@jonathanspw)’s proposal on #Valkey
While the particular decision was deferred for a couple of weeks, it was fascinating to see how decision are made in #Fedora.

2024-04-15 04:00:58

- reply

I agree with the last two panels, but the first two are only true if it’s not a hybrid 😉

2024-03-11 17:37:14

Working on some new presentation abstracts.
One topic I'm particularly interested in is versioning and how to evaluate a project with healthy versioning vs projects that have versioning that will make your life hell.
So, this talk would go over projects where they intentionally stay below 1.0.0 for 10+ years, have breaking or license changes in minor or patch versions. and un-versioned documentation. Stuff like that.
What term fits best?