4/
Curious, have you tried pass / passwordstore?
What’s your experience?
www.passwordstore.org

3/
Also great for other machine secrets. I used to manage these in Bitwarden, but opening a UI for small tasks felt tedious, and their CLI never really clicked.

Nice to have as an additional option. I think I’ll mostly rely on it for now

2/
Works amazingly with direnv. I can declare in my .envrc which passwords a project needs, and pass loads them dynamically. Very smooth.

1/
I’ve been trying out pass / passwordstore for a few days. Had to revamp my GPG settings first, but it was worth it.

The concept is simple but powerful: track all your passwords in a repo, encrypted before check-in. Version-controlled passwords feel surprisingly good.

4/
For 1 machine: Docker Compose.
For simple multi node setups: Swarm Mode.
For complex, dynamic scaling: Kubernetes

Check out docker swarm mode here:
docs.docker.com/engine/swarm/

3/
Just tried Docker Swarm Mode. Much easier. Feels stable. Compose integration makes the workflow smooth

2/
Kubernetes is powerful, but heavy. Learning curve is steep, managing resources gets complicated fast, debugging is painful.

I used Docker Swarm back when it is now called "legacy". Compose compatibility was nice, but it felt unstable and volume support was lacking

1/
I have tried many container orchestration solutions. Running directly via CLI is only fine for experiments. For real deployments you need something declarative like a compose file, otherwise nothing is versionable and you are just hoping it keeps working

5/
For now I am still running MinIO. But once RustFS is ready for production, I will likely switch.

It deserves more visibility. If you are curious about alternatives to MinIO, give RustFS a try and share your experience.

4/
I tested it locally. Even though it is not production ready, I was impressed.
Options are easier to manage, monitoring is built-in, and Prometheus/Grafana ship out of the box. And most importantly user management is simple again.

3/
I found RustFS.
github.com/rustfs/rustfs

It looked solid from the start. Benchmarks suggested it could even outperform MinIO. And with full S3 compliance, things that failed with MinIO suddenly just worked.

2/
But a recent MinIO update took away a lot of convenience.
No user management in the UI. No access key handling. No simple metrics.

That is when I went looking for alternatives.

1/
RustFS is not rust::fs.
It is an open source, S3 compatible object storage system written in Rust.

I used MinIO for a long time. About a year ago I needed on-prem storage and S3 was the best fit.

Axiom — Logging, re-invented. Cloud-native architecture meets built-in tracing and routing. Experience log management without compromise.

Been using Pino on and off. Tried others like Winston, never quite clicked. Pino logs JSON by default, which makes sending data to services like Axiom (axiom.co) or Loki+Grafana easy.
Official site: getpino.io

What logger do you use?

I often use Jina.ai Reader to prep web pages for LLMs. Works great.

But sometimes I need a local, private option.

Just found defuddle. Strips clutter from pages, outputs clean text + metadata. Perfect for feeding into an LLM without sending URLs to a 3rd party.

2/
This time I took the time to read the docs properly—super clean abstraction.
Trainer class, built-in logging, multi-GPU, checkpointing, mixed precision—makes a lot of things smoother.

Starting a small side project with it. Curious how it’ll go! #PyTorchLightning #DeepLearning

1/
For years, I mostly stuck with raw PyTorch—flexible and fully in control.
I’d heard of Lightning but never gave it a real try… until a teammate suggested it last year.
Didn’t quite work with our stack back then.

Revisited it last weekend. #PyTorch #ML

This New AI is 100x Faster at Reasoning Than ChatGPT The tiny Hierarchical Reasoning Model mimics the brain's structure to solve complex tasks in a single pass — no internet-scale pretraining.

Always watching for transformer alternatives.

They might look like the future of AI right now, but nothing says that will last forever.

Meet HRM. 27M parameters. Beats much larger models in some reasoning benchmarks. Uses a planner + executor instead of the transformer stack.

Small & Smart

But what really impressed me is their lifetime storage offer. One-time payment, WebDAV, VPN, and more
internxt.com/lifetime

Some time ago I compared S3 providers. Interxnt replied, “You forgot Interxnt.”

They were right, and I’ve since looked into it

Their S3-compatible storage looks solid and pricing is competitive, or rather the best of the options I am aware of
internxt.com/de/cloud-obj...

Placeholder pics, sub kilobyte placeholder images Placeholder pics is the lightest way to include placeholder images in your designs

Just came across placeholder.pics, great for quickly adding placeholder images to early frontend mockups.

Unlike picsum.photos, this one makes it clear these are just placeholders rather then feature images.

Example: placeholder.pics/svg/300x500

Better Auth 1.3 | Better Auth SSO with SAML, Multi Team Support, Additional Fields for Organization, Performance and more.

Better Auth 1.3 just dropped
www.better-auth.com/blog/1-3

Lots of great additions, but the new Stripe plugin really stood out to me

It handles users, subscriptions, payments, even webhooks. Takes so much complexity off your plate
www.better-auth.com/docs/plugins...

Switched from poetry to uv for a few hobby projects.
Poetry was fine, but slow.
uv is fast. Like, actually fast. Even with big deps like torch.

Give it a try: buff.ly/CAbMS1B

Frontend is not my domain, but icon/component libraries make rough frontends so much faster.

I’ve often used heroicons.com, super clean, copy-paste ready.

Just found freesets.dev
It aggregates tons of free resources, with licenses listed. Looks great.

Sure, here’s a tweet-sized version:

Been testing out Biome, a Prettier + ESLint replacement in one. No plugin chaos, no config juggling. Just one fast, stable tool. Written in Rust. Feels great so far. Might be switching for good. Try it?

3/
A common, flexible routing component baked into Vite?
That would be a game-changer for framework builders and devs closer to the metal.
Anyone sharing that opinion?

2/
Most frameworks go with either file-based or code-based routing.
I’ve used both, and honestly—file-based just feels more intuitive. SvelteKit, Next.js, you name it. #frontend

1/
Routing is one of the key places where meta frameworks built on Vite keep borrowing from each other.
At #ViteConf, there was even talk of Vite offering a built-in router. That idea stuck with me. #webdev

Just built a mini project with LynxJS.
Super fast setup, great performance out of the box.

But native things like camera & sharing?
Still very involved to set up.

Promising framework though. Excited to see where it goes.

lynxjs.org

Node now runs #TypeScript natively.

Bun and Deno had this from the start, and it was a key reason I switched to #Bun.

Still, this is a big deal for Node and for TypeScript being treated as a first-class citizen.

Curious what you think