Published a small intro #video about Asfaload completely produced with #foss: Marp markdown slides, #obs studio recording, #kdenlive editing, #peertube serving. I have embedded it in the homepage at www.asfaload.com

When I introduce someone to Asfaload's solution, I noticed the discussion often follows the same script. That led me to write it down in a post. Take look if you want to understand what Asfaload does and how: www.asfaload.com/blog/asfaloa... #buildinpublic #security #softwaresupplychain

First marketing material for asfaload! "Self-made"(using an LLM). Not a perfect design, but sufficient for now! #buildinpublic

Deployed client howtos at www.asfaload.com/doc/client-c... . Now with demos recorded with github.com/charmbracele... Here's an example for generating a new keypair: #security #buildinpublic #supplychain

One more #breach that @asfaload.bsky.social prevents: www.neowin.net/news/if-you-... Our #opensource #multisig solution is auditable and can be #selfhosted. Check info at asfaload.com Available very soon! #security #softwaresupplychain #jdownloader @neowindy.bsky.social #buildinpublic

Deployed backend for the first time,and ran an e2e test script on it successfully.It registered a #github project,registered a release' assets, collected signatures from devs,and made a download of the asset, checking signatures.Happy with the progress! #buildinpublic #security #softwaresupplychain

A #git #performance #book . Working on @asfaload.bsky.social which stores its data in a git repo to make it auditable, that book looks like a great resource!

I read @filippo.abyssdomain.expert 's post about quantum comp's timeline[1]. Raising questions for @asfaload.bsky.social, a multisig file auth solution, using ed25519 sigs, allowing ssh keys use. But no quantum resistance! So:pqc resist 4 later or convenience now?🤔 1: words.filippo.io/crqc-timeline/

Asfaload can now use your ed25519 ssh keys to sign artifacts! No additional key to manage for Asfaload.

I will probably use the #linux kernel's policy on #ai coding #agents in my projects like @asfaload.bsky.social . In short, add a "Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]" tag to the commits. Humans commit and take responsabilities, but agent use is traced.

I'm having a good experience with getaurora.dev/en/ and #immutable #linux #distribution using #kde , based on universal-blue.org. Integrates distrobox, tailscale, automatic and atomic updates. Only small quirk encountered until now is copy paste between terminals for different containers

A question for #security experts: I'm using #rustlang 's pkcs5 crate that only proposes cbc mode for scrypt(eg this function: scrypt_aes256cbc). Having read GCM is much better than CBC, should I look for an alternative? This is a new project without back compat required. #crypto #cryptography #help

Not sure it is the right order: our documentation is deployed before our backend is even online :-D www.asfaload.com/doc/ The fastest way to deploy the doc was using rust-lang.github.io/mdBook/ , incidentally a #rustlang project like us. #buildinpublic #mdbook #security #softwaresupplychain

Seeing the Axios #compromise on #npm, and as Asfaload enables the detection of unauthorised publications in case of an account hijack,I feel there must be serious opportunities for the project.Take a look at www.asfaload.com and let me know if you have suggestions! #security #supplychain #opensource

Finally, an administration mandates #odf: linuxiac.com/germany-mand... Mandating odf was a suggestion I shared in my eu consultation answer a couple weeks ago. Not sure it is the case, but all tenders should also mandate open formats. Let's hope other in #eu follow. #foss #opensource

Asfaload project,aiming to provide an auditable multisig file downloads auth,passed 1000 commits: github.com/asfaload/asf... In this LLMs age,it might become an even less interesting metric,but if only for me,it reflects the time and energy I put in the project #buildinpublic #opensource #rustlang

Just after posting about tuicr.dev, I discovered during a review that an agent removed a bunch of tests rather than adapt them. #codereview is not optional with #ai #agents...

I find tuicr.dev really useful to #review #ai generated #code ( #rustlang in my case). I've added it to my container config to run agents if anyone is interested: github.com/asfaload/age...

When you #buildinpublic, you also make mistakes in public. No one should not feel bad about it when it happens. I'll share my most recent mistake, anyone willing to follow? Today I realised that in my test pipeline most tests ran twice, leading to loooooong test runs. I discovered it by chance 😬

As my use of #ai has increased gradually (asfaload.com/blog/ai_use/), I have more #code #review work on my plate. I have just installed tuicr (tuicr.dev) in the #docker image I use for development (github.com/asfaload/age...) , and it looks very helpful to ease review of code generated by an #agent

You have to start somewhere: happy with the 10 ⭐ the project got on GitHub: github.com/asfaload/asf... #buildinpublic #foss #opensource #rustlang

I just watched this talk about #rustlang #appsec and my to-do list just got some new high priority items! Interesting talk, especially for the pointers to recommended tools. m.youtube.com/watch?v=5qyu...

You know that feeling as a #developer when you see something in your #software doesn't work as you expected, but you then realise it was you that was wrong and your #code was doing exactly what's needed? #development #devs #tests

In the Asfaload codebase, there was a pattern that kept appearing: using #rust enum to wrap trait implementations. It offers great flexibility, clean #code, all with full #typesafety and no dynamic dispatch. I haven't seen it described often, let's change that! www.asfaload.com/blog/rust-tr...

Happy of the #progress of the project. Those commit and PR numbers are not something to pay much attention too, but it confirms the #project is much alive and progresses continuously.

If you're a #developer, here is some #music you should know about: marcus.bointon.com/music/ Or did you already know songs about #pairprogramming #tailwind #laravel #fediverse #php #webhooks and other dev-themes?

For my #rustlang project's I was looking at possibly switching to nextest, but it doesn't seem to support "a common setup running once and used by all tests in the binary", which I will probably want to implement to shorten my #tests runs....

🎉 First time I could go through the whole chain: - register multisig from a github project - activate it by signing it - register a release - sign it - download a release artifact and authenticate it github.com/asfaload/asf... #buildinpublic #progress #rust

I contributed to the #eu consultation regarding #foss #opensource #freesoftware . Did you? You can still do it until 3 Feb (tomorrow!). interoperable-europe.ec.europa.eu/collection/o...

After the thrills of talking about the project with fellow #fosdem visitors, I'm back at the programming desk. Signals regarding @asfaload.bsky.social were positive, keeping me motivated to #buildinpublic this #opensource #multisig solution!

Some #fun at #fosdem

No asfaload talk at #fosdem this year, but I prepared the design of an A4 flyer, see blog post asfaload.com/blog/fosdem2... And image here: asfaload.com/blog/fosdem2... #buildinpublic #promo #flyer #foss

Events though I now put it clearly in my AGENTS.md file, my #ai #agent fails using the constants used in the project and continues to hardcode values. Every review adds a commit titled 'no hardcoded values' [1] ! What more can I do?.... #llms #opencode #glm #rust 1: github.com/asfaload/asf...

My use of llms for programming has evolved so drastically that I thought it was interesting enough write a blog post about it: asfaload.com/blog/ai_use/ #ai #llms #programming

Without knowing, seems I've doing some spec driven devel for @asfaload.bsky.social lately. I maintain the spec github.com/asfaload/spec in parallel of the code at github.com/asfaload/asf... . This helped #ai use both in code generation and review. Just discovered via martinfowler.com/articles/exp...

Always good to see some switching to #foss solutions: www.heise.de/en/news/Aust... #libreoffice

#github now publishes the sha256 of every project's new github releases assets. To ease the validation process I made a small downloader tool in #rust validating the sha256 after download: github.com/asfaload/asf...

Just merged a refactoring ensuring the code works on a hash value, and not any bytes value, by wrapping said value in a #rust enum (similar #fsharp DU). Fearless refactorings are so enjoyable, don't want to imagine doing it without assistance of the typesystem! github.com/asfaload/asf...

soweli-p/FsiX: A better REPL for F# with project/solution support and hot reloading. #fsharp github.com/soweli-p/FsiX

I like to visit freshstuff.net to #discover new #software projects. Disclaimer: I primarily built it for me and for that purpose 😁 But would be great if others use it regularly too.

#rust encourages immutability, but to a new rustacean coming from #fsharp mutability is very present. Today's example: PathBuf. I had the expectation that push would return a new updated value, but it mutates in place, so my code "let p2=p.push(ext)" was incorrect. Took me some time to realise

I will share asfaload.com updates and progress at @asfaload.bsky.social with tag #buildinpublic . Take a look if it's the kind of stuff you're interested in! Tech used is #fsharp and #rust

Starting with #rust coming from #fsharp, I wanted to try and keep my functional habits of immutability, being ready to take a performance hit if reasonable. It seems that in some scenarios, there wouldn't even be a perf hit: ecency.com/rust-lang/@j... That's encouraging!

It’s also a great reminder to all #fsharp devs that wanted “official” LSP/VSCode-extension from MSFT… Ionide and FsAutoComplete may not be perfect, but at least I won’t fuck around with licenses.

F# opportunity: www.reddit.com/r/fsharp/com... #fsharp

There's a #fsharp post on #hn currently: news.ycombinator.com/item?id=4354... I shared my own adoption of fsharp in this comment: news.ycombinator.com/item?id=4354...

#typescript DU types require an explicit discriminating field type T1 = {type:"one"}; type T2 = {type:"two"}; type U = |T1 | T2; So you have to write field 'type' explicitly. But then you can still compile `var v : U = {} as T1;`. There are reasons, but it still feels weird coming from #fsharp

A couple of weeks after someone suggested #fsharp is dying, and we get the most blogpost- and release-packed 'fsharp weekly' from @sergeytihon.com in a long time: sergeytihon.com/2025/03/01/f... But still no f# foundation activity in sight. The language is far from dead,but the fssf might well be

Am I the only #fsharp dev polling @sergeytihon.com 's website several times during the weekend before the new fsharp weekly edition actually gets published?