There are also rate limits on Google side for incoming mails. By just forwarding four domains to my Gmail I used to hit them quite often. Then 2 years ogo, I stopped forwarding and switched to the now discontinued Gmail fetching domain mails over POP...

I'm wondering, now almost three years in after the Forgejo/Gitea fork, which side of the fork ended up better. Both still seem very active with thousands of commits each.

I run a Gitea server (since long before the fork, constantly updated) that handles issues, pull requests, signed commits, CI/CD, actions, and even serves my containers and packages. It's been amazing.

Of course Forgejo can do the same. For those who’ve followed both projects closely — which fork would you say has come out ahead? Codeberg being Forgejo's SaaS offering likely gives them more resources, but I also wonder if that means their priorities lean more toward SaaS than self-hosting.

I use LLMs (like claude-code and codex-cli) the same way accountants use calculators. Without one, you waste all your focus on adding numbers; with one, you just enter values and check if the result makes sense. Programming feels the same—without LLMs, I’m stuck on both big problems (architecture, performance) and small ones (variable names). With LLMs, I type what I want and get code back. I still think about whether it works long-term, but I don’t need to handle every little algorithm detail myself.

Of course there are going to be discussions what is real programming (like I'm sure there were discussions what is "real" accounting with the onset of a calculator)

The moment we stop treating LLMs like people and see them as big calculators, it all clicks.

Browser password managers with passkeys are more convenient for me, but a pass vault can still be useful for recovery codes and API keys.

I used pass for a while but couldn’t see what threat model it actually solves:

If you let GPG agent cache your key, any script (e.g. an npm post-install) can just run `pass ls` or `pass my/secrets` and dump all your credentials. At that point it’s basically just full-disk encryption with extra steps—might as well keep everything in ~/passwords.txt.

If you don’t cache the key, you’re forced to type your long GPG password every single time you need a secret.

I tried a YubiKey for on-demand unlocking, but the integration is clunky and plugging it in constantly is a pain if you need passwords multiple times per hour.

I eventually switched to Bitwarden.

It’s great on esp32 with MicroPython. Even has support for server sent events (SSE). Paired with htmx, SSE gives some fun intetactive web experience for iot devices - instant GPIO status indicators etc. Loved tinkering with it. The source code is very readable too.