ok! it was a fever dream week of rushed readme-driven #Rust development, but finally I have something for you all to test out. :)
the new #SparkleShare CLI codenamed Twinkle:
ok! it was a fever dream week of rushed readme-driven #Rust development, but finally I have something for you all to test out. :)
the new #SparkleShare CLI codenamed Twinkle:
check out the README, clone the repo and `cargo install --path . and you'll be good to go.
there's also a Flatpak built in the CI and you could give it limited folder access but not sure how to do it exactly...
code deps are minimal. even removed serde and now only chrono, notify, and sha2 are left and I can probably remove chrono too. #Rust
also love that "cargo test" is built-in. (first time I've seriously done this in a project :P).
when a test fails I think "yes! that saved me another hour or two of debugging!" and I take a nap.
hey I'm just nice ok?
https://github.com/hbons/Twinkle/blob/main/src/ssh/keys/known_hosts/savannah.rs
Launchpad's docs mention ED25519 keys are available, but a ssh-keyscan only shows RSA.
it makes me think the page is generated. so far the only Git host I've encountered that doesn't have its eggs in a row...
even SourceForge did better...
@hbons you removed Serde!? And it… does stuff? On the web…?
@MostlyBlindGamer well, the internet. piggybacking on Git!
@hbons I'm always astonished when some of our gnome friends tell me that cargo is horrible in their opinion
@zeenix I agree on the build.rs part, but I don’t use that. :)
@hbons yeah, I try to avoid that too but it's not always possible. I think for apps, it's fine. In libraries you hardly ever need it anyways.
@hbons Rust makes testing incredibly smooth for a solo developer. I write a lot of tests for .NET, sure, but that’s because I have a whole internal testing framework I can use.
You can get to that low friction point in any stack, I suppose, but cargo definitely makes it take less effort. That means it makes it more natural to shift left.
@MostlyBlindGamer that's what always kept me from doing it. already choice paralysis picking a testing framework...
@hbons we have a whole domain-oriented framework, so TDD with integration tests is actually worth considering. Just don’t ask how much it cost to get there.
Unit tests in Rust come super naturally. Big integration stuff, less so, at least for me.
@MostlyBlindGamer right, still need to do the integration tests. I think these will just be simple CLI scripts. any recommendations?
@hbons not really… I guess all you need for your asserts is the odd ls or hash, right?
That feels doable in some kind of containerized fashion.
@hbons so... Just a thought: #reticulum supports git now. So used in conjunction with twinkle, we could have a very competent syncing system. I think. Maybe?
@hbons just realized you might not know what reticulum is and it's git integration:
https://markqvist.github.io/Reticulum/manual/git.html#git-main
@cbleslie i’m confused to what this is. :)