jph

I'm seeking your help please for suggesting ideas, articles, tactics, and the like for improving ways of working - especially if you have experience and opinions.

https://crates.io/crates/assertables

I would like to donate toward getting Assertables into Debian stable. I can afford to offer $100 to any Debian Developer who has the suitable skill and trust to accomplish this.

Success looks like this: long term, Rust crates in Debian stable can optionally use Assertables for their testing i.e. all the source code is available in Debian.

I know $100 isn't enough to cover all the work. It's what I can do to help move things forward.

I'm doing this because I believe in funding open source as much as possible.

I want to use Fresh Editor (https://getfresh.dev/). This is because Fresh is easier to learn quickly than vim & emacs, and more of an IDE than micro & nano, and more favorable for compliance auditing because of its core-and-plugins architecture and open source code using Rust.

I would like to donate toward this goal. I can afford to offer $100 to any Debian Developer who has the suitable skill and trust to accomplish this. The software author must say yes too, of course.

Success looks like this: create a new Debian 13 server, type "apt install fresh-editor", and it works. No third-party apt sources needed, because I have compliance reasons. Fortunately Fresh already has a *.deb file and explains it on the Fresh installation page.

Here's the GitHub issue: https://github.com/sinelaw/fresh/issues/2169

I'm not affiliated with Fresh in any way, just a early adopter user. If you view the GitHub issues, I'm also offering $100 each for helping with Fresh display issues on MacBooks, and for adding Fresh ePub capabilities.

I'm doing this because I believe in funding open source as much as possible.

AI agents, provided as markdown files, that implement United Kingdom (UK) Government Digital and Data (GDAD) Profession Capability Framework (PCF) roles and their skills.

Purpose: The United Kingdom is implementing a jobs classification system for digital technology work, such as "Software developer", "Test analyst", "Incident manager", etc. The UK provides extensive documentation about the roles and the skills, along with naming conventions.

I'm experimenting with multi-agent software enginnering, so I extracted the documentation into markdown files that I can use as AI skills.

It turns out this works very well in practice, with equivalent results to popular multi-agent generic systems. The big win is that using the UK naming convention and exact roles and skills makes teams understand it immediately - including executive teams, goverance teams, and legal teams.

The markdown files are especially easy for novices to copy/paste into AI chat systems, and also can of course work with more-advanced tooling e.g. I use Claude Code and swarms of subagents.

I'm sharing the markdown files in this repo. Constructive feedback welcome.

I'm offering $100 as an incentive for anyone on HN who can add epub reader capabilities to Fresh using Rust.

https://github.com/sinelaw/fresh/issues/2087

Spec: in the left-side file explorer, I select file `foo.epub`, then the right-side file viewer shows me the epub content as human-readable text not bytes.

Scope: The goal is to be good enough for a developer to be able to read epub documentation within Fresh in the TUI, without needing to call pandoc or launch a separate app or helper or plugin. Fresh runs locally on the developer's laptop, and the ePub is on a remote server and for security reasons cannot be downloaded to the local laptop.

Implementation: I can suggest trying the Rust crate `epub` and `bookokrat` because these work well for me in other projects. The implementation can't use JavaScript or TypeScript because of compliance aspects beyond me.

As an aside, I'm not affiliated with Fresh in any way, other than as a happy user and open source sponsor.

I'm adding mirrors for more forges today, for GitHub, GitLab, Codeberg.

https://github.com/architecture-decision-record/architecture-decision-record

https://gitlab.com/architecture-decision-record/architecture-decision-record

https://codeberg.org/architecture-decision-record/architecture-decision-record

This mirroring is thanks to many people who have taught me about the importance of hosting diversification, and funded my research and development.

Questions, comments, constructive criticism, etc. all welcome here and I'll do my best to reply today.

Feedback welcome, especially how to make it even easier for newcomers to diagnose SMTP issues. This code is all hand coded, no AI.

There are three implementations: synchronous, asynchronous with tokio1 rustls tls, asynchronous with tokio1 native tls.

https://github.com/joelparkerhenderson/demo-rust-lettre-sync

https://github.com/joelparkerhenderson/demo-rust-lettre-async-tokio1-rustls-tls

https://github.com/joelparkerhenderson/demo-rust-lettre-async-tokio1-native-tls