<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: markmnl</title><link>https://news.ycombinator.com/user?id=markmnl</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 03 Jul 2026 07:51:00 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=markmnl" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by markmnl in "Ask HN: What are you working on? (May 2026)"]]></title><description><![CDATA[
<p>You're absolutely right to pick up on that, I did study the landscape and Matrix is closest.. biggest difference is fmsg is just messages - group like chats evolve naturally in the threads - but to get a message someone has to send you one. Group messaging platforms like Matrix, Rocket.Chat etc have concept of rooms/forums/channels i.e. groups, then have HTTP APIs to manage membership and sync messages.. fmsg just messages someone has to send you<p>Also fmsg being its own protocol can do novel things like to auto challenge during sending back to sender - can't do that with HTTP</p>
]]></description><pubDate>Mon, 11 May 2026 09:31:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=48092842</link><dc:creator>markmnl</dc:creator><comments>https://news.ycombinator.com/item?id=48092842</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48092842</guid></item><item><title><![CDATA[New comment by markmnl in "Ask HN: What are you working on? (May 2026)"]]></title><description><![CDATA[
<p>Shiping a real product, esp. a game, from scratch is an awesome achievement, congrats. (My first shipped product was Square Heroes also on Steam).<p>I feel like perfecting something can be trap, sure keep it alive, but maybe think about the next thing to work on too?</p>
]]></description><pubDate>Mon, 11 May 2026 05:33:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48091352</link><dc:creator>markmnl</dc:creator><comments>https://news.ycombinator.com/item?id=48091352</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48091352</guid></item><item><title><![CDATA[New comment by markmnl in "Ask HN: What are you working on? (May 2026)"]]></title><description><![CDATA[
<p>Working on fmsg - open protocol for instant messaging, distributed by domain like email..<p>Its a message definition and protocol, addresses look like @user@domain, anyone can run a host, and threaded messages are linked by cryptographic parent hashes..<p>The idea is to take the best from email: open protocol, domain ownership, interoperability (unsolicited mail is a feature not a bug), and the best from closed instant messaging rebuilt: efficient binary messages, conversational threads, sender verification, message integrity etc. built-in. Originally envisaged for human-to-human messaging but partculalrly interesting time right now with human-to-agent and agent-to-agent messaging...<p>The OSS stack is up and running: Go host, Dockerised full setup, CLI, Web API, and a spec nearing v1.0. Did Show HN post week ago: <a href="https://markmnl.github.io/fmsg/show-hn.html" rel="nofollow">https://markmnl.github.io/fmsg/show-hn.html</a><p>Seeking feedback, criticism, validation :) protocol bikeshedding, and especially interest from founding-engineer types who want to help build an open messaging ecosystem rather than another closed app..</p>
]]></description><pubDate>Mon, 11 May 2026 05:29:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48091339</link><dc:creator>markmnl</dc:creator><comments>https://news.ycombinator.com/item?id=48091339</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48091339</guid></item><item><title><![CDATA[Show HN: fmsg – An open distributed messaging protocol]]></title><description><![CDATA[
<p>fmsg is a message definition and protocol intended as an alternative to email and IM apps. Like email it's distributed – anyone can host a server for their domain. Unlike email, messages are binary, verifiable by all peers, and linked into a DAG using cryptographic hashes. Sender verification and message integrity are built into the protocol, so you get what email needs SPF/DKIM/DMARC for out of the box.<p>The host implementation (fmsgd) is written in Go. There's a Docker compose setup to get a full stack running in minutes: <a href="https://github.com/markmnl/fmsg-docker" rel="nofollow">https://github.com/markmnl/fmsg-docker</a><p>The spec is nearing v1.0: <a href="https://github.com/markmnl/fmsg" rel="nofollow">https://github.com/markmnl/fmsg</a> — would love feedback. Send me a fmsg at @markmnl@fmsg.io</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47834580">https://news.ycombinator.com/item?id=47834580</a></p>
<p>Points: 5</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 20 Apr 2026 14:06:34 +0000</pubDate><link>https://markmnl.github.io/fmsg/show-hn.html</link><dc:creator>markmnl</dc:creator><comments>https://news.ycombinator.com/item?id=47834580</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47834580</guid></item><item><title><![CDATA[Why Exceptions should be Exceptional]]></title><description><![CDATA[
<p>Article URL: <a href="http://www.mattwarren.org/2016/12/20/Why-Exceptions-should-be-Exceptional/">http://www.mattwarren.org/2016/12/20/Why-Exceptions-should-be-Exceptional/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=13235401">https://news.ycombinator.com/item?id=13235401</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 22 Dec 2016 06:48:32 +0000</pubDate><link>http://www.mattwarren.org/2016/12/20/Why-Exceptions-should-be-Exceptional/</link><dc:creator>markmnl</dc:creator><comments>https://news.ycombinator.com/item?id=13235401</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=13235401</guid></item></channel></rss>