@_lopopolo@ewhauser@tombombadeel Okay, to confirm: you're suggesting that skills that only the user invokes is an empowerment issue and should be migrated to some other mechanism. I was struggling to wrap my head around the concept but that mindset is a huge unlock for me.
@_lopopolo@tombombadeel What's your recommendation to enforce the skill count constraint? Is this just a manual discipline thing for you? My concern is that skills are configured at the repo level and mechanically enabling/disabling skills based on session intent sounds exhausting
@kristoferlund It's great work and I desperately need it. At what level of development do you think you will consider it "good enough" to release an alpha of sorts?
@Flsun_official We really need a comment from you on open sourcing your forks of software in use on your hardware. A closed source implementation of Klipper and associated software is antithetical to the 3D printing ecosystem as well as a US copyright law violation.
.@Flsun_official By not open sourcing your forks of Klipper, KlipperScreen, Mainsail, and Moonraker currently in use on your S1 3D printer, you are in breach of their GPL licenses and therefore in violation of copyright law in the United States.
@UncleJessy4Real@YGK3D@HexiBase
Check out the @SnowflakeDB driver for SQLTools in @code, they've released version 0.5.0 w/ additional object visibility that I wrote.
It's my first foray into extensions and public contributions. I'm working on intellisense and context menu utilities next!
#devtools#extensions