501–510 of 1001 posts
I got frustrated on how difficult it is to compare many elections using alternative voting methods against each other, so ended up extending a friends project, adding more results, details and statistics.
Just added datasette lite to the approval voting site. it’s pretty cool to query the SQLite db in the browser. https://approval.vote/data
A fiat to crypto payment gateway for businesses and freelancers without a strict KYC. Users can pay using card and merchants can claim instant crypto settlement[1].
WIP: a casino algorithm that outperforms most casino algorithms in terms of user retention over a long period of time with the objective function of maximizing long term profit.
[0]: https://xclip.in [1]: https://obliqpay.com
I recently added pose tracking of the 3d model so I can overlay 3d effects onto the underlying video.
Here's a demo: https://mukba.ng/p?id=29265051-b9c7-400b-b15a-139ca5dfaf7e
A 90-min workshop to introduce development Teams the full potential of AI coding agents.
Over the last few months I’ve been optimizing an AI-first SDLC for real engineering (not vibe code), getting amazing results on small Teams both in terms of delivery output and devex.
Some friends asked me to formally present and help their Teams, and enjoyed every moment of it.
The core features of this tunneling tool are stable. I am working on adding support for TCP as well as UDP traffic through the same tunnel.
The failure mode I keep hitting: once you give an agent tools, it gets ambient authority over all of them. There's no clean way to say "for this task, read-only on the reports table" or "spin up no more than 3 VMs." When the agent spawns sub-agents mid-execution, they inherit full access by default.
IAM doesn't help much. Authority stays tied to the agent's identity even as intent shifts during execution.
I'm exploring a capability-based model instead: authority is explicit, task-scoped, and attenuating. Closest to Macaroons/Biscuit, but adapted for workflows where delegation happens dynamically mid-task.
Early prototype (Rust core, Python SDK, LangChain integration), still thinking it through. Notes here: https://niyikiza.com/posts/capability-delegation/
It sits on top of existing tools like PagerDuty, Jira, Prometheus, Elasticsearch, and Slack, and normalizes them into a shared schema. It doesn’t store operational data, it just brokers requests through pluggable adapters and returns unified structures.
The motivation came from incident response workflows that still require hopping across multiple vendor UIs and APIs with different auth models and query languages. Instead of another “single pane of glass,” this is meant to be a small, transparent glue layer.
On top of the core service, I’m also exposing everything via an MCP server so LLM agents can query incidents, metrics, and logs as typed tools without needing vendor-specific knowledge.
Currently open source, written mostly in Go and TypeScript. Still early, but usable with PagerDuty, Jira, Prometheus, Elasticsearch, Slack, and mock providers. Feedback from SREs and infra folks has been very helpful so far.
150+ tools for financial research in one place.
If you enter a ticker, you'll get a handy launchpad with deep links to top tools.
The problem: most people have 100+ accounts with weak/reused passwords. Changing them manually is tedious, so nobody does it.
The solution: import a CSV from your existing password manager (1Password, LastPass, Bitwarden), select which accounts to update, and the app uses browser automation with Gemini 2.5 Flash to navigate to each site's password change page and update them in parallel. Exports a CSV with the new passwords to import back.
Key technical choices: - browser-use library for AI-driven browser automation (handles dynamic sites better than Selenium) - Local-only architecture: passwords never leave your machine, no cloud sync, everything stays in memory and is cleared after use - Electron + Python: React frontend with a Python agent for browser automation via stdio IPC - OpenRouter for LLM access (Gemini for navigation, Grok for validation)
Security was the most important and the hardest constraint. Passwords can't be logged, can't be sent to the LLM context, and can't persist on disk. Custom fork of browser-use to inject credentials via secure parameters invisible to the AI agent.
Currently at v0.38 with code signing and notarization for macOS. Working on improving success rates - the main challenges are 2FA requirements and anti-bot detection (Cloudflare, reCAPTCHA).
Would love feedback from anyone in the security/password management space.
I have been making a micro-arcade of one button games using a fun little library I found.
It is so fun to just have an idea and implement it in under an hour or two. It is a great creative outlet.
Give them a play if you have a second, they are very rough around the edges but are playable on mobile or browser.