Private digest history now keeps past issues searchable
This Bookmarks API deploy fixes a real gap in the private editorial reading digest: past issues no longer need to disappear into delivery history.
For opted-in beta accounts, past daily digests can now be stored in a digest archive and retrieved later through digest history. Archived entries also keep the original bookmark tags from each saved source. That matters because an old digest is much more useful when it still carries the same context you already gave those bookmarks.
If you use tags to group saved reading, this change makes older digest issues easier to search and revisit later instead of acting like one-time emails.
What changed
This release adds three connected improvements to the private editorial reading digest:
- Past daily digests can now be archived instead of only existing at delivery time.
- Digest history retrieval now includes archived issues.
- Archived digest entries preserve original bookmark tags from the underlying bookmarks.
The result is simple: a digest issue from earlier in the week can still be useful when you come back to it later.
Why the tags matter
A digest is only half the job. The real job is finding a source again when you remember the topic but not the title.
Before this change, a past digest issue could be useful in the moment, but older issues had less staying power. Now archived digest entries keep the tags that were already attached to each bookmark. If you saved an article with tags for a topic or project, that tag context stays with the archived digest entry too.
That gives old digest content a better path back into your normal Bookmarks workflow:
- revisit a previous digest issue
- recognize the saved source you want
- use the original bookmark tags as retrieval context
This release does not claim a new tag UI or a redesigned archive screen. The shipped change is narrower and more useful than that: archived digest data now keeps the tag information that already existed on the bookmark.
Better history for a beta workflow
This update is aimed at people already using the private digest beta, plus anyone helping validate it.
The rollout has not widened. The private digest beta remains limited to opted-in accounts. That limit matters here because this deploy improves a specific beta workflow rather than announcing a broad product launch.
If you are in that beta, the change is practical. A daily digest is no longer just something that arrives once. It can now become part of a retrievable history.
Storage and retrieval got tighter
Under the hood, this release also improves how archive data is persisted.
The digest system now has dedicated persistence support for archive metadata. That is the part that makes stored history more reliable instead of treating archive behavior as an afterthought. The release also expanded PostgreSQL coverage for digest history and archived digest retrieval.
That testing detail matters for users because this feature depends on correct storage and retrieval. An archive is only useful if past issues come back consistently, and if preserved tags survive the round trip.
A concrete example
Say you saved several sources during the week and tagged them by topic. One of those sources appears in your daily digest.
With this release, that digest issue can be archived, and the archived entry keeps the original bookmark tags from the saved source. Later, when you want to revisit that issue, the archived digest still has the same tag context that made the bookmark findable in the first place.
That is the through line of this deploy: keep old digest content connected to the saved bookmarks it came from, instead of flattening it into a one-time delivery artifact.
What did not change
A few boundaries are worth stating clearly:
- This is a Bookmarks API deploy focused on digest history and archive retrieval.
- The private editorial reading digest is still beta-only for opted-in accounts.
- This release does not establish a new public rollout on iOS, the Chrome extension, or every Bookmarks surface.
- It also does not resend accepted historical digest mail.
Those constraints are part of the feature, not footnotes. This was a focused patch release with one job: make past digest issues easier to find again.
Why this release matters
CodeSplash Bookmarks is at its best when saved sources stay useful after the first read. That usually comes down to two things: keeping enough context on the item, and making it possible to come back later.
This release improves both for the digest workflow.
Archived issues now have a place to live. Archived entries keep the original bookmark tags. Digest history becomes something you can return to, not just something that happened once.
If you want to follow CodeSplash Bookmarks updates, product links are here: https://codesplash.ai/downloads
Try the release in the private digest beta, or reply with feedback on how digest history should work for you.
Feature screenshots
CodeSplash Bookmarks: reading queue, tags and collections: feature reading queue on iPad · View original full-resolution image
CodeSplash Bookmarks: reading queue, tags and collections: feature tags and notes on iPad · View original full-resolution image
CodeSplash Bookmarks: reading queue, tags and collections: feature tags and notes on iPhone · View original full-resolution image