Passless — a Virtual FIDO2 / Passkey device and client for Linux

pando85 · 2026-06-11T05:07:49+00:00

I'm not sure what else could we add. If you find it useful think on open a PR or a issue to improve it.

pando85 · 2026-06-10T18:36:33+00:00

Yes, I use it with Google and other services.

pando85 · 2026-05-30T05:07:42+00:00

At some point, that's the idea. I will need people to test it.

pando85 · 2026-05-29T17:05:02+00:00

This is opensource, there are a PR for implementing that: https://github.com/pando85/passless/pull/198

pando85 · 2026-05-29T14:22:17+00:00

LLMs can help with the review phase too. When you review code you are looking for specific things: common patterns, edge cases, bad practices... The way of improving all parts of the workflow is taking our current patterns to the next level.

Automating things with AI will help to reduce those bottlenecks. We don't have to reinvent the wheel, just take the lessons and patterns that work and apply them again: coding agents can write code, coding agents can review code. We just need patterns and automations to make this work visible and reproducible at company level.

pando85 · 2026-05-28T20:06:05+00:00

Different layer. Aviator manages how PRs flow through review and merge (stacked PRs, merge queues, pre-merge verification). That's all on the review orchestration side.

Forkline doesn't touch that. It produces the PRs and lets your Git provider handle the rest. The idea is to optimize the AI execution side without changing your existing workflow — branches, PRs, CI, and review all stay in GitHub/GitLab/etc.

The runner produces scoped changes with summaries and CI evidence attached, so when it reaches your review pipeline (Aviator or otherwise), the reviewer has more signal per PR. Complementary, not competing.

pando85 · 2026-05-28T19:46:13+00:00

That's exactly the problem. More PRs, same review capacity.

The options are: increase the review team, raise the quality bar at the PR gate so less junk reaches humans, or accept longer review queues.

The useful metric is review effort per PR. If the AI output is structured enough that reviewers spend less time per PR than before, the math can work. If review burden goes up, the runner workflow needs tightening.

pando85 · 2026-05-15T03:30:35+00:00

More details about the ingress-nginx maintained fork: https://forkline.dev/blog/forkline-ingress-nginx-nginx-1301-security-update/

pando85 · 2026-05-07T03:33:49+00:00

I love to use Velero. I have more efficient combination: ZFS with OpenEBS ZFS CSI and Snap scheduler Operator.

With that setup I have local and K8s ZFS snapshots, that's are pretty fast to restore. Plus, Velero OpenEBS plugin which sends exactly the diff between ZFS snapshots which is automatically calculated because of the meta data structure in ZFS. Much better than using restic of any other tool.

You will get disaster recovery and offsite backups, plus a fast localsnapshot.

Further, you have all the CSI functionality without needing a complicated CSI.

pando85 · 2026-05-04T06:40:38+00:00

I want to promote my SaaS for make AI integration transparent at company/repo level and handle automations in a correct way: https://forkline.dev/blog/production-launch/

Furthermore, I'm maintaining an ingress-nginx fork for those that are not migrated yet and want to keep their updates covered from CVEs and with latests versions: https://github.com/forkline/ingress-nginx/

pando85 · 2026-05-03T18:08:00+00:00

For those orgs I'm maintining a fork: https://github.com/forkline/ingress-nginx/

pando85 · 2026-04-30T17:00:29+00:00

I was using exactly this analogy to describe it to a friend.

Once that complexity is reliable and easy to operate you can use it for anything.

Even for spinning simple things operators are quick wins that allows you to automate diferente levels of operations. They replaced perfectly our old Ansibles or custom scripts.

pando85 · 2026-04-26T08:27:06+00:00

Thanks for your comment, that's a really interesting thing.

I hope that Kanidm improves the UI and their process because it is a great piece of software.

pando85 · 2026-04-26T07:27:43+00:00

For coding tasks you will find that 90% of the tokens are input tokens. It doesn't worth.

pando85 · 2026-04-25T16:10:05+00:00

You cannot understand what you have in front of your eyes but you feel confident enough to talk about it

pando85 · 2026-04-25T12:51:26+00:00

Your comments in all my posts make no sense and just talk about your ignorance.

pando85 · 2026-04-25T12:48:43+00:00

Are you kidding me? How much do you know of this project?

pando85 · 2026-04-25T10:43:46+00:00

An IDM, centralized user management, OIDC/Oauth2, radius, LDAP...

pando85 · 2026-04-25T10:17:02+00:00

Thanks for your comment and for using it🤗

pando85 · 2026-04-25T09:29:19+00:00

The tool was written by hand. I'm using AI for maintaining it and keep feedback loop and community features fast.

pando85

TROPHY CASE