<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: jolaflow</title><link>https://news.ycombinator.com/user?id=jolaflow</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 20:27:52 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jolaflow" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jolaflow in "Ghostty is leaving GitHub"]]></title><description><![CDATA[
<p>Check out Epiq <a href="https://github.com/ljtn/epiq" rel="nofollow">https://github.com/ljtn/epiq</a><p>It was born out of frustration and does just that. It is about to go v1 within days.</p>
]]></description><pubDate>Wed, 29 Apr 2026 16:44:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=47950920</link><dc:creator>jolaflow</dc:creator><comments>https://news.ycombinator.com/item?id=47950920</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47950920</guid></item><item><title><![CDATA[New comment by jolaflow in "Ghostty is leaving GitHub"]]></title><description><![CDATA[
<p>> I think the docs should describe this in detail.<p>Thanks for the feedback. I will add a section about that in the readme!<p>[EDIT] - readme updated with section about event sourcing strategy</p>
]]></description><pubDate>Wed, 29 Apr 2026 15:05:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47949471</link><dc:creator>jolaflow</dc:creator><comments>https://news.ycombinator.com/item?id=47949471</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47949471</guid></item><item><title><![CDATA[New comment by jolaflow in "Ghostty is leaving GitHub"]]></title><description><![CDATA[
<p>Hey! Creator of Epiq here. Epiq is platform agnostic mening that it is doing its own thing and does not connect to github issues. Epiq maintains its own board definition as an immutable (append only) event log, which is synchronized using git.<p>An integration layer with github issues or other platforms is definitely not unthinkable.<p>V1 is about to be released in the coming days.</p>
]]></description><pubDate>Wed, 29 Apr 2026 14:24:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47948908</link><dc:creator>jolaflow</dc:creator><comments>https://news.ycombinator.com/item?id=47948908</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47948908</guid></item><item><title><![CDATA[New comment by jolaflow in "Epiq: Distributed Git-backed CLI native issue tracker TUI"]]></title><description><![CDATA[
<p>Epiq developer here.<p>Epiq is a CLI/TUI issue tracker that lives entirely inside your repo - no accounts, no SaaS, no context switching. Issues and kanban boards are stored as an event log on a dedicated Git branch, so everything is versioned, time-travelable, and syncs with regular git push/pull.<p>Built as a response to the frustrating hurdles with the current tooling. It has Vim-style keyboard navigation, works offline, supports multiple user collab via Git, and includes an MCP server so agents like Claude can read/write issues directly.<p>V1 is just a few days away.<p>Let me know if you have any questions.</p>
]]></description><pubDate>Wed, 29 Apr 2026 14:15:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=47948791</link><dc:creator>jolaflow</dc:creator><comments>https://news.ycombinator.com/item?id=47948791</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47948791</guid></item></channel></rss>