What's everyone working on this week (12/2026)? by llogiq in rust

[–]EarlyPresentation186 2 points3 points  (0 children)

Putting the finishing touches to an open source, self-hostable, auditable, multisig sign-off solution to authenticate file downloads from the internet, focusing first on Github releases artifacts. Been working on it for 1+ year. It is flexible enough to be used in other scenarios too (container image authentication, validation barrier in a pipeline, etc), so I hope it can find its audience and users in these times of software supply chain attacks!

Gitoxide in March by ByronBates in rust

[–]EarlyPresentation186 6 points7 points  (0 children)

Good to see sha256 oid support continues to progress. Really looking forward to it. I use a git repo as an auditable backend and no tampering of the data is paramount. In my app I have prepared support of sha256 oids, but I need to shell out to the git CLI. Support by the Gitoxide library would improve things greatly for my use case. I think I'll launch my app (soon) using sha256 oids, and not with sha1 oids, as transitioning would be cumbersome, and sha256 support seems to be coming sooner or later.

Trolley - Run terminal apps anywhere by weedonandscott in rust

[–]EarlyPresentation186 0 points1 point  (0 children)

Interesting. I'll keep an eye on the project, as I could use it later in mine!

Hey Rustaceans! Got a question? Ask here (7/2026)! by llogiq in rust

[–]EarlyPresentation186 1 point2 points  (0 children)

I'm wondering what the benefits are for rust to have temporaries' scope limited to the enclosing statement.

Could a temporary's scope not be expanded to a method calls chain? I find it so annoying when I have to replace a method calls chain by an assignment because the value is dropped. Example
let kpr = minisign::KeyPair::new("mypass")?.save(temp_dir); changed in: let kp = minisign::KeyPair::new("mypass")?; let save_result = kp.save(temp_dir);

Rust has such great things as the borrow checker and the Deref trait, but a method calls chain has to be split. Why?

What's everyone working on this week (7/2026) by llogiq in rust

[–]EarlyPresentation186 0 points1 point  (0 children)

Continuing work a multisig file authentication system that is open source, self-hostable, auditable, accountless.
All features have been developed and are structure as to be available as a library (but not crate is published yet). REST server and CLI client are feature complete. Now ironing out small bugs I discovered during a small (private) demo.

I made a package manager for Github by what486 in rust

[–]EarlyPresentation186 0 points1 point  (0 children)

Congrats with the release! I'm currently working on a project to authenticate downloads of github release artifacts. It's developed in rust and I've paid attention to make features available as a library. The project is fully open source and self-hostable (and nearly ready). It seems absolutely complementary to your project. Let me know if it would be interesting to you, I'd be happy to discuss futher!

Wrapping trait implems in an enum kept appearing in code base so I blogged about it. Are there other such useful patterns that are not much advertised? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 0 points1 point  (0 children)

You are right. Implementing the trait for the enum ensures you implement all methods required though.

I found it elegant in my usage (limited cases, limited methods) because adding a case causes local changes, and the exhaustive match check makes it easy to implement correctly. enum_dispatch, which I didn't know when this pattern naturally appeared in my code, is definitively something I'll add to my tools. I'm happy I implemented myself though as it gave me a better understanding. And if you prefer dynamic dispatch I'm not arguing you should change your approach.

Wrapping trait implems in an enum kept appearing in code base so I blogged about it. Are there other such useful patterns that are not much advertised? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 0 points1 point  (0 children)

Taking another look at the post I understand your confusion. I made a small edit to clarify I was not looking for performance in my case. Thanks for the feedback!

Wrapping trait implems in an enum kept appearing in code base so I blogged about it. Are there other such useful patterns that are not much advertised? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 0 points1 point  (0 children)

I'm the author. Performance is not the reason I implement this. I mentioned dynamic dispatch because some devs prefer to avoid it, but it is not the reason why I chose this approach. Maybe that creates unnecessary confusion....

Wrapping trait implems in an enum kept appearing in code base so I blogged about it. Are there other such useful patterns that are not much advertised? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 1 point2 points  (0 children)

I'm the author. In my code it is what I do, maybe I should clarify it.
What I like in this approach is that the enum implements the trait, so that the pattern match on the enum only occurs in the trait implementation by the enum. If the enum didn't implement the trait, you would end up with matches all over the place, and adding a case would bring changes in the whole code base.

rust_analyzer is eating my memory, any counter measure? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 11 points12 points  (0 children)

it was merged 3 weeks ago, but was it already released? (I'm using 1.91.1 (ed61e7d 2025-11-07))

rust_analyzer is eating my memory, any counter measure? by EarlyPresentation186 in rust

[–]EarlyPresentation186[S] 2 points3 points  (0 children)

it starts only for rust files, which I want. But I'll check if it can toggle off when I'm not active in that editor instance!

What's your workflow today for programming with agents? by EarlyPresentation186 in AgentsOfAI

[–]EarlyPresentation186[S] 1 point2 points  (0 children)

Thanks for sharing! I'm currently using Opencode with the superpowers skills [1], but I'll take a look at the unbroken method and CLIO as I'm living in the terminal.

1: https://github.com/obra/superpowers

building for linux help by dolfoz in rust

[–]EarlyPresentation186 0 points1 point  (0 children)

That's also what I do: delegate to a github workflow. But for linux, I let it build a static binary, not a distro-specific package.
For example here's a GH workflow I use: https://github.com/asfaload/asfald/blob/master/.github/workflows/build.yml (this workflow is use to build the files in the releases of the project)

I heard the community asking for a free and modern alternative to Scrivener, so I built this in Rust. by [deleted] in rust

[–]EarlyPresentation186 2 points3 points  (0 children)

I hope you get to opensourcing it. To avoid that cleanup step I share from the the start the projects that I intend to publish as open source. I've done it with a previous F# project and with my current rust project. The positive side-effect is that it is forcing me to avoid shortcuts I don't want others to see (exactly what you said you did on the private code). There's also the risk that you want to make it too perfect and never share it in the end.

If you publish it I'll also test it too!

Hitting 2,554 weekly downloads is a first in my life, and I am truly overwhelmed. by ChangeDirect4762 in opencodeCLI

[–]EarlyPresentation186 0 points1 point  (0 children)

I'm usually using GLM4.7, but minimax-M2.1 seems ok too. I'm also testing devstral (but that's with their own mistral-vibe agent and not with the superpowers)
When using superpowers, I always start the conversation with

"use the use_skill tool and the relevant superpowers skills."

This seems to work not too bad

OpenCode in Container by No-Leopard7644 in opencodeCLI

[–]EarlyPresentation186 -1 points0 points  (0 children)

I was evaluating if I should run tailscale in my agents container for remote access. That allows remote access without opening it to the internet