News for hackers. Stuff that matters.

fmvilas

fmvilas on Hacker News

Re:Show HN: Commune, one feed for newsletters on Beehiiv, Kit, Ghost, ... on Tuesday November 10, 2026 @06:57AM (#50439069)
For context: I'm Fran Mendez, I created the AsyncAPI standard. I launched Commune earlier this year because I wanted to have a community layer on top of my newsletter hosted on Kit. As with AsyncAPI, I knew I wasn't alone and figured it could be of interest for other people too. People started asking for the sending part so I built that as well. Fun fact, one of my newsletter issues talked about why I'm not building yet another email service. Lol, life! Also, as a developer myself, I want tools to integrate with each other. Commune is no exception so I made sure it has its own API, MCP, and developer portal: https://usecommune.dev. If you're running a newsletter, I'd love for you to try it. It's all free unless you send emails with Commune.

Show HN: Commune, one feed for newsletters on Beehiiv, Kit, Ghost, and more

Posted by fmvilas on Tuesday November 10, 2026 @06:55AM
from the show-hn dept.

https://usecommune.com

Commune is a newsletter platform with a shared feed. Newsletters listed there come from many providers: Beehiiv, Kit, Ghost, Buttondown, Substack, MailCheap, Mailchimp, and even blogs via RSS. For every article, a discussion is created automatically. The homepage is the product. You only need an account to interact with authors and other readers.

( Read More... | 1 comment | on HN )
Re:Railway Security Disclosure on Thursday October 22, 2026 @04:25AM (#50192708)
> As such, we strongly recommend that you immediately roll all environment variables, including any API keys, stored in Railway, as well as any private registry credentials, and review logs for those services for unusual activity.

> All deployments are paused

Can you explain us how can we rotate secrets without going down too?

Re:Mistake Oddysey on Tuesday July 20, 2021 @05:52AM (#27891778)
Tales from a Git, Github, Markdown, and VS Code beginner.
Re:AsyncAPI – OpenAPI-like specification for event-driven architectures on Monday March 30, 2020 @04:01PM (#22731718)
It's been around for 3 years already hehe! And yes, crafting my own format was how it all started. Happy to hear more about your project!
Re:AsyncAPI – OpenAPI-like specification for event-driven architectures on Monday March 30, 2020 @01:58PM (#22730416)
You're right. My fault here. It should actually be possible to define a gRPC streaming API (never tried). The only missing thing for me is the protobuf compatibility though.
Re:AsyncAPI – OpenAPI-like specification for event-driven architectures on Monday March 30, 2020 @01:54PM (#22730363)
Waleed is awesome. I wonder why he didn't call it asyncapi-waleedator though :P
Re:AsyncAPI – OpenAPI-like specification for event-driven architectures on Monday March 30, 2020 @01:33PM (#22730116)
If you mean protobuf, here's a link to the discussion on why it wasn't included in v2.0.0. That said, we'll explore adding non-JSON formats (like XSD and protobuf) to the specicification this year.
Re:Release to NPM and Docker Hub with GitHub Actions and Conventional ... on Friday March 20, 2020 @10:16AM (#22637649)
This is awesome! It's a pity that Github Actions don't work well with PRs coming from forks. We could do many more things.