I was surprised how well Gemini could deal with signals.

I used it on a (overly) complex DAG with signals tracking internal node state and dependencies between nodes. It tracked down a few very subtle edge cases where the signal graph was getting too complex.

Oh nice! I had come across docs.gitea.com/next/usage/p..., must have completely missed it in the prod docs

I'll have to give this a shot, I much prefer hosting my own forge 🔥

Is GitHub's package repo still the best solution here?

I've toyed with a self-hosted option like @gitea.com, looks like their package repo is still in dev preview

Even better is when you realize the surprise was an infinite loop of `npm run lint` failures being fixed with `as any` types that further break linting 🙃

Every timeline needs more cowbell

My first thought is a "contacts" type table and a markdown editor plugin for auto-complete

Syndication hooks could replace the handle placeholder with web/Mastodon/Bluesky specific links as needed

I do think this is a gap in the POSSE approach, it gets complicated URLs aren't the source of truth