I’d love feedback on this! github.com/nperez0111/bookhive/pull/229
book.lexicon.community proposal by nperez0111 · Pull Request #229 · nperez0111/bookhive
github.com
Lexicon Community
Book WG momentum: @nickthesick.com submitted a PR on BookHive with proposed lexicons for book editions and standalone reviews — splitting edition data from reviews into distinct namespaces. The path to community.lexicon.* publishing: a Tangled registry PR is next. Join the discussion.
Sep 20, 2026 at 3:29 PM
Please don't use Slack for FOSS projects
This blog post was published on November 1, 2015. It might be out of date, have broken images or links, or simply contain bad ideas and opinions that didn't stand the test of time. Please read generously!
No more tokens! Locking down npm Publish Workflows—zachleat.com
A post by Zach Leatherman (zachleat)
npm Blog Archive: changes to npm’s unpublish policy
npm Blog (Archive); updates from the npm team are now published on the GitHub Blog and the GitHub Changelog
Kindly Closing Pull Requests
Getting your first pull request from an outside contributor on GitHub is an exciting experience. Someone cared enough about the problem you were solving to check it out themselves, change…
GitHub Stacked PRs
Break large changes into small, reviewable, stacked pull requests with first-class GitHub support.
Don’t Like It? Code it Yourself!
Have you ever considered paying for, or sponsoring, a * bug fix * new feature * plugin * small tweak to existing functionality ... for software that you use? I don’t mean waiting for a new release of the software, which will contain a bunch of new features you may or may not care
i couldn’t be more excited Inlay is finally out and open source! i’ve been working on this nonstop for the past few months. it’s a bit in the “mad science” territory but i hope it inspires you too to think about malleable and remixable social user interfaces
Inlay
today was the Inlay release day! discover, remix, create, and compose different ways to view the Atmosphere data on inlay.at
🙋♂️ so ... for reasons: I would love to know people's frustrations with: - the current npmjs.com - admin user flows on npm web ui (and cli, locally) 🙏
Check out this thread and contribute your papers if you'd like to share!
Rafael M Batista
I’ve created a Collection on @semble.so for #IC2S2. It’s open for anyone to throw in a link to their paper. If that’s too much work, you can reply here with a link and I’ll do it for you and send you the “card” Semble is proving to be a great tool for discovering new research @ic2s2.bsky.social
I opened up the repo if you want to peek under the covers. Nothing earth shattering going on here. I will say that Claude made this an afternoon project instead of a week long project. github.com/jbeda/joe-dev-blog
GitHub - jbeda/joe-dev-blog: joe.dev personal blog — Hugo + Cloudflare Pages
github.comOK, I wrote up a whole blog post with some more detailed thoughts on this. Curious if anything here resonates with other folks. Thanks to @iame.li, @dholms.at, and @bnewbold.net for helpful pointers and discussions! pckt.blog/b/bits-of-entropy/all-data-sh…
All data should be permissioned data - Bits of Entropy
pckt.blog
Richard Barnes
@dholms.at - What is the right venue for discussion on this Permissioned Data proposal you wrote up. atp@ietf.org or something else? I think it is wrong in some pretty fundamental ways. Or at least the motivations are poorly articulated.
