As someone else noted, this is about small, frequently changing files, so you could remove old versions from the history to save space, and use LFS going forward.
I was hoping to hear their thoughts on how Copilot and Cursor compare to Aider, but this is the whole Aider section:
Aider Chat is an exciting CLI alternative:
- Mature and open-source
- Command-line based
- Requires a deeper mental model but offers powerful capabilities
- Perfect for those who prefer terminal-based workflows
I built (but never released) a project for this: an end-to-end encrypted "slow" chat app, where you'd send long-form rich-text letters to friends and they'd take a configurable amount of time to deliver, backed either just by client business logic or optionally with timelock encryption (this one [1], not this one [2]).
I've been meaning to clean it up and open source it.
There is an app called Slowly [0] that kind of does that, you send open letters and people can respond to you. They take time to arrive, the longer you physically are from each other, the longer they take.
I've found it very cool, got a few responses to my open letter and responded to some letters. People were cool and writing long form stuff is great. Unfortunately I struggle to have a long term relationship through this, I feel too shallow. But the experience has been great.
One of the GL.iNet travel routers [1] would probably work for you. They run OpenWRT (or a thin veneer around it), so you can SSH in and install packages and whatnot. They explicitly advertise Wireguard-based VPN support.
I don't have one of their travel routers, but I have a Flint 2.
Oh yeah definitely don't try this unless you have fiber and your ISP isn't too twitchy.
My suggestion is mainly for static site hosting since the Pi only needs to update the cloudflare cache when you make changes, and it should be able to handle a small db and few background services if you need them.
> How do you tell Pinggy is closer to ngrok than Tailscale?
Taking a quick look at the article, it seems like you route traffic through Pinggy, whereas Tailscale is mostly (minus the TURN stuff) peer to peer with some NAT-busting
The main difference is that Pinggy works via a public IP, whereas Tailscale is a private network overlay. Pinggy falls into the bucket of solutions like ngrok, zrok, Tailscale 'Funnel', Cloudflare Tunnel etc.
reply