<feed xmlns='http://www.w3.org/2005/Atom'>
<title>hutch.git/Hutch/Models/Inbox.swift, branch v3.6.0</title>
<subtitle>ios client for sourcehut. swiftui.
</subtitle>
<id>http://git.krz.sh/krz/hutch.git/atom?h=v3.6.0</id>
<link rel='self' href='http://git.krz.sh/krz/hutch.git/atom?h=v3.6.0'/>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/'/>
<updated>2026-07-16T00:31:17+00:00</updated>
<entry>
<title>fix: give inbox threads identity distinct from their grouping key</title>
<updated>2026-07-16T00:31:17+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-07-16T00:31:17+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=eff81f34bb51ecc6e0aa5d831567db2cea0527a9'/>
<id>urn:sha1:eff81f34bb51ecc6e0aa5d831567db2cea0527a9</id>
<content type='text'>
InboxThreadSummary.id returned threadGroupingKey, which is listRID plus the
subject with Re:/Fwd: stripped. Two unrelated threads on one list sharing a
subject therefore shared an id — common on sourcehut, where "[PATCH] test" is
an ordinary subject — which collides under Identifiable in every list that
renders these summaries.

Key id on the root Message-ID, which is unique per thread, and leave
threadGroupingKey subject-based so replies still collapse into one
conversation.

Read state moves to threadGroupingKey at each call site. It was already
keyed on that string via id, so persisted keys are unchanged and marking a
conversation read still covers the whole subject group, matching how
HomeViewModel already builds the key for isUnread.
</content>
</entry>
<entry>
<title>fix: collapse work inbox messages into thread summaries</title>
<updated>2026-04-20T18:15:04+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-04-20T18:15:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=380fb866d090c5f13b2ad3f88f1fe23c4ade4801'/>
<id>urn:sha1:380fb866d090c5f13b2ad3f88f1fe23c4ade4801</id>
<content type='text'>
</content>
</entry>
<entry>
<title>improve home attention flows and cross-linking</title>
<updated>2026-04-12T05:34:54+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-04-12T05:34:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=5f6d545eb3455a9e4da5a3cb4460811e3a48d939'/>
<id>urn:sha1:5f6d545eb3455a9e4da5a3cb4460811e3a48d939</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat: implement support for projects, lists, and pastes</title>
<updated>2026-03-19T20:17:38+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-03-19T20:17:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=6ba4e967d5dfb5d3c7bb97a0f2662f3180595563'/>
<id>urn:sha1:6ba4e967d5dfb5d3c7bb97a0f2662f3180595563</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat: add inbox threads and move builds under more</title>
<updated>2026-03-19T06:53:46+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-03-19T06:53:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=1e3c748119c6e9eec27f02146f17ea0302ff648a'/>
<id>urn:sha1:1e3c748119c6e9eec27f02146f17ea0302ff648a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat: add support for reading inbox messages (emails) and replying in-app</title>
<updated>2026-03-19T06:17:49+00:00</updated>
<author>
<name>Christian Cleberg</name>
<email>hello@cleberg.net</email>
</author>
<published>2026-03-19T06:17:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.krz.sh/krz/hutch.git/commit/?id=441b69afae30ee6b662be38004fd7b5de1e47302'/>
<id>urn:sha1:441b69afae30ee6b662be38004fd7b5de1e47302</id>
<content type='text'>
</content>
</entry>
</feed>
