Post

if I were to start working on a Software Release lexicon for us to get @electronjs.org release metadata on protocol, would anyone else be interested in collaborating on it?

29/9/26, 1:49 pm1 repost11 likes

Anuj Ahooja

@quillmatiq.com

I think @graham.systems has been working on this as well!

tierney cyren

@bnb.im

would love to collaborate @graham.systems :)

Graham

@graham.systems

Yes, I’d love to make that happen! If you check out dist.town I have most of the building blocks ready to make it happen, barring the presently LLM-written docs. Send me a DM!

dist.towndist.townSharing a release should be the easy part. One page for new versions, changelogs, and files — whatever your project is, wherever it lives.

tierney cyren

@bnb.im

if anyone has domain recommendations my DMs are open. @nicr.dev and I have a couple ideas already but nothing exactly perfect

Mastro.{js,ts}

@mastrojs.bsky.social

can you leave room for a binary field in the future, where you can attach a zip of the npm package? 😁

tierney cyren

@bnb.im

even if it's not added at the beginning, additions are ~backwards compatible for lexicons. I'd probably take inspiration from how app.bsky.feed.post does embeds and have separate lexicons for the binary: github.com/bluesky-soci...

Mastro.{js,ts}

@mastrojs.bsky.social

yes, it's great that you can add it later. if it's a ref that would prevent downloading it always if you only want the other fields (basically what's in package.json)?

Chris Pardy

@pardy.at

Yes, for other projects

Yeah why not :)

Sounds like a fun side project

tierney cyren

@bnb.im

hell yeah