Seeing the brand new Inbox experience of standing beside all other UI/UX I've designed and built for #radicleVsCode makes me feel all fuzzy inside.

That one little single grove, keep an eye on that... My full in-browser @radicle.dev "Grove" node is a first-class gossip citizen of the real network: it dials a production seed through the relay, holds the session, announces itself and its inventory, subscribes, and receives the network's gossip.

Perhaps the best Radicle Inbox experience to date has been achieved internally. 👀

🚢 v0.7 is relesed! The dream is here. You no longer need httpd to use #radicleVscode. Load the full history of heartwood's patches in around 1s. Also superbuffed diffs and rad clone experience. Enjoy! marketplace.visualstudio.com/items?itemNa...

AI is great at any task you’re a beginner in and awful at any task you’re an expert in.

Where the work happens on @radicle.dev over the past year: issues and patches per repo. Heartwood leads, but community projects like strom, Brawler and KB-Dashboard sit right alongside the official ones. Native, in-repo collaboration in action.

Looked at my logs and noticed I've spent _390h_ in June building Radicle tech. That's.. 13h/day without any day off. The reality is that I did take a couple days off, meaning I worked only ~5-8h like a bum. Which also means that I've worked multiple 21h days. No breaks usually.

What if I told you, that soon you'll be able to finally use #RadicleVsCode with no httpd, as God intended? 🥹

Collaboration on @radicle.dev is accelerating. Distinct people active each quarter has more than doubled over the past year, now 223 and rising. 811 have taken part all-time. Decentralized code, very much alive.

Watching youtube without each thumbnail shouting at you begging for your attention is such an improved and, dare I say, healthier experience. Won't ever go back to not using dearrow.ajay.app again.

Two years of the Radicle network growing: 9,000 repos, 120+ GiB, and climbing.

A Radicle seed that seeds everything mirrors the whole public network. Mine (radicle.at) hit ~9,200 repos and ~119 GB before I did anything about it. So I wrote `radicle-seed-prune` to trim it safely. 🧵

ℹ️radicle.at just got buffed 💪 - multiple, load-balanced httpd instances - shared, on-disk response cache - per-IP rate-limiting - disk-pressure-adaptive automated storage pruning 👉 radicle.zulipchat.com#narrow/chann...

“If we cannot stop the machine from devouring everything, then you, then I, must become truly human. More human than before.” - Johnathan Pageau

Big news, but can't talk about it. Yet. 👀 ⚪🎩

Diving deep into @radicle.dev heartwood and that's all nuts in there. Working with all of that is insane in my eyes. How tf this thing was built from scratch given the required accumulated understanding of so many things is beyond me. Respect to the forerunners and the current runners.

My first app ever. 2016. The rush!

I wanted to make quick edits _possible_. Then I tried making them just a tad smoother. Then I went too far and reimplemented VS Code in the browser. 😅

git commit -m "feat: create and edit @radicle.dev repos in the browser"

The best way to start a coding session. Change my mind. youtu.be/JgTuVcNDKuk?...

Just 24h ago, I released the latest @radicle.dev VS Code version. Since yesterday the lifetime total downloads increased by 30% day-to-day on the Open VSX registry. In a day. I have no words. Thank you. 🙏

So uh.. the new version broke the markdown rendering, so uh.. the one thing it actually is helpful with, showing a patch title, descr, comments is now broken in prod. And it breaks only in prod build, which is how it went past me. How? Classic UMD/CJS/ESM fiasco. Fixing...

"It's about damn time." Feels unreal, but I've actually released a new Radicle VS Code version. 👉 radicle.zulipchat.com#narrow/chann...

This is the most obscure shit I've seen in some time... Just look at this silly fix.

we are so back #radicleVscode

✅ Few things beat an all-green CI that took blood, sweat and plenty of Greek cursing. #σουγαμήσω

I just can't get this out of my head 👀

Don't do the mistake I did and go out trying to wrestle with this... Just `npm install -D @maninak/eslint-config` for a powerful linting suite that allows you to keep working on developing your app and keep your your AI agents on a leash too. 👉 github.com/maninak/esli...

I dream of a future where @radicle.dev public seed nodes are unnecessary and exist only for convenience. Only indexing and providing services on network metadata, hosting no actual contents (unless non-public) akin to a BitTorrent tracker with a bit of Gnutella spice on top.

1/ I've cooked up a thing. 👨‍🍳 It's called *@maninak/eslint-config*, and is an opinionated, batteries-included, linting and formating suite that just works™. Supports JS/TS, Node, Vue, React, Svelte, TailwindCss, Markdown, JSON/YAML/TOML, ... github.com/maninak/esli...

Always has been...

For all who asked over the years, I've finally found a great service to receive support on: liberapay.com/maninak Please only sponsor what you can spare. I hope to offset the hosting and domain costs of radicle.at, serving the Radicle community for over 2 years.

After spending a week wading through ESLint rules, I swear that name was `ts/no-insufferable-types` for a quick second

Today #radicleVscode reached 1K downloads on the alternative OpenVSX registry, already surpassing the those from the official Microsoft Marketplace. Something to be said here about @radicle.dev and independent IDE users. Also demand for software sadly not maintained for over a year.

The only real goal is enjoying the practice. "Goals" of the austere administrative kind are a distraction from being alive in the moment and fulfilling your destiny's calling. Unless that approach is a joyful game in itself (it can be). So take that side-quest. It's the "main" one, really.

I've found that as I try to doc functions in succinct wording, albeit annoyingly tedious and notably time-consuming, will often expose either some unhanded edge case, a suboptimal signature or that it just does too much. Good code is easier to doc. If hard usually a smell pointing to refactor.

This is the most refreshingly exciting tech news (of any kind) I've come across since years. The stated principles I would sign in a heartbeat. Who knows what will come out of it or where this will lead. One thing's for sure, it takes balls to set out for this and I'm loving the audacity of it.