Spoonfed now gives you a clearer way to see that difference and decide what to do about it.

See a feed's publishing rhythm

Each feed's settings include a 30-day activity graph. The bars show how many articles arrived on each day, making it easy to spot the difference between a steady feed, a bursty one, and a feed that rarely publishes.

The feed list also shows an articles-per-day score, so you can get a quick sense of a feed's volume without opening its settings. The graph gives you the detail when you need to make a decision.

Set a sensible discard window

Auto-discard removes old, unread articles from the reading pool after a period you choose. It is useful for fast-moving feeds where yesterday's news shouldn't remain in the queue indefinitely.

The activity graph marks your current discard cutoff, so you can see how the setting relates to the feed's recent publishing history instead of guessing. Change the threshold and you can immediately reason about what will still be waiting for you.

Bookmarked articles are kept, even when auto-discard runs. The setting is for managing the queue, not for deleting the things you decided were worth saving.

Different rules for different feeds

A global threshold is a good starting point, but feeds deserve different treatment. Set a short window for a high-volume news feed, leave a slow personal blog around for longer, or disable auto-discard for a publication you never want to miss.

Per-feed overrides let you do that without changing the default for everything else. The graph's cutoff marker makes each choice visible in the context of that feed's actual behavior.

Less queue maintenance

The point is not to make you manage your feeds more often. It is to make the queue take care of itself. Once you have a feel for how a feed publishes, choose the rule that fits and let Spoonfed quietly clear out what is no longer useful.

Your feeds can be as varied as the things you read. They do not all need to compete for the same amount of attention.

The latest profile updates add both.

Add a name and a little context

Your profile can now have an optional display name and description. Use the name people know you by, then add a sentence about what you read or why you share it. Descriptions support Markdown, so you can keep the introduction as plain or as expressive as you like.

The profile URL remains a system-generated ID rather than being tied to your display name. You can change how your profile is presented without having to change every link to it.

Choose how things are published

You can share bookmarks, quotes, or both. For each type, you can choose between automatic publishing and manual publishing:

• Automatic publishing adds new bookmarks or quotes to your profile as you save them.
• Manual publishing keeps them private until you explicitly choose to share them.

This gives you a useful default without taking away the ability to keep a particular item to yourself. Your profile is private until you enable it, and only the content covered by your settings is visible.

Reset the link when you need to

If a profile URL has been shared more widely than you intended, you can reset it from Settings. The old URL stops working for both the profile page and its RSS feed, and a new one is generated.

Resetting the URL is permanent, so it is designed as an intentional privacy control rather than something to do casually. Anyone you still want to follow your reading will need the new link.

Still RSS, still optional

There are no follower counts, likes, or notifications. People can read your profile on the web or subscribe to its RSS feed, without needing a Spoonfed account.

Public sharing remains opt-in and one-way. The new controls just make it easier to decide what that sharing looks like.

Spoonfed now lets you save those passages directly from the reader.

Save a quote while you read

Select any passage in an article and the quote action appears beside it. Save the selection as-is, or add a note before saving it. The passage is kept with its surrounding article, so you can always see where it came from and return to the full piece later.

Quotes preserve the formatting of the selected text, including things like emphasis, links, and code. You don't need to copy and paste anything into another notes app, and you don't have to interrupt your reading to make sense of it later.

Add the thought that goes with it

A quote on its own can lose its meaning. A short note makes it more useful: why you saved it, what it reminded you of, or what you want to follow up on.

Notes are optional. If the words are enough, save the quote without one. If you know you'll want the context later, add it while the idea is still fresh.

Everything in the Library

Saved quotes and bookmarked articles now live together in the Library, ordered by when you saved them. Quotes show the passage and any note you added; bookmarks keep the article title and source close at hand.

Each quote also links back to the complete article. A saved passage can be the end of a thought, or the reason to start reading the rest.

The Library is not another inbox to clear. It is a small, personal collection of the things that were worth keeping.

You'd save a quote, then remember you also bookmarked an article from that day, and have to switch tabs to find it. The separation made sense in theory, bookmarks are articles, quotes are passages, but in practice it just meant more clicking to find the thing you were looking for.

So I merged them.

The Library

There's now a single Library view that shows bookmarks and quotes together, ordered chronologically. Newest first. No tabs, no filters unless you need them.

Each bookmark shows the article title and where it came from. Each quote shows the highlighted passage, the optional note you added, and a link back to the original article if you want to re-read it. They sit next to each other in the same list, the way memories actually work, not sorted by type, but by when they happened.

A few other things

While I was in there, a couple of small improvements crept in:

• You can now remove a bookmark directly from the Library card without having to go back and re-read the article.
• Quotes link through to the full article, so if a passage made you want to read the rest, one click gets you there.
• The old /bookmarks and /quotes URLs redirect to /library, so nothing is broken if you had anything bookmarked.

The Library is also the foundation for public profiles, when you mark things for sharing, this is where you do it.

How it works

By default, your profile is private. Nothing you read or save is visible to anyone else. If you want to share, you opt in from Settings and pick a display name.

Once you've done that, you get a public page at /u/your-name. You choose what shows up there, bookmarks only, quotes only, or both. Each item you want to share gets individually marked for publication, so your public profile only shows what you explicitly put there.

The profile page is clean and minimal. No follower counts, no engagement metrics, just a list of what you've been reading, in chronological order.

The RSS part

The reason I built this the way I did is that I wanted people to be able to follow each other's reading without needing an account. If someone finds your profile interesting, they can subscribe to your RSS feed in any reader and get updates alongside their regular subscriptions.

That felt like the right model for Spoonfed. Reading is personal, sharing is optional, and when you do share, you do it in an open format that doesn't require the other person to join anything.

What's not there

There are no likes, no comments, no notifications when someone views your page. I kept those out intentionally. Adding social interactions would change the dynamic, you'd start curating for an audience rather than reading for yourself. The public profile is a one-way window, not a social feed.

The daily reading limit is a simple fix for that. Set it to whatever feels right, ten articles, twenty, fifty, and once you've hit it, Spoonfed stops serving new ones for the day. The app shows a done screen and that's it. Come back tomorrow.

Why opt-in?

I didn't make this the default because different people use Spoonfed differently. Some people read in focused short sessions and naturally stop on their own. Some have the kind of mornings where they want to read as much as they like. The limit is there for people who want a hard stop, not everyone.

Setting it to zero disables it entirely, no cap, read as much as you want. The default is zero.

How it interacts with the queue

The limit is about articles read, not time spent. If you read quickly, you'll hit it faster. If you spend twenty minutes on a long piece, you've still only used one slot.

Articles in your Library, bookmarks and quotes, don't count toward the limit. Neither does browsing your archive. The limit is specifically for advancing through new articles in the reading queue.

It resets at midnight in your local timezone, so you start fresh each day.

The latest update adds a publishing activity graph to each feed's settings panel, a small bar chart showing how many articles that feed published each day over the last 30 days. At a glance you can see whether a feed is steady, bursty, or barely posting at all.

Why this matters for auto-discard

The graph was really built to make auto-discard more useful. Auto-discard lets you set an age limit on articles, anything older than N days gets quietly marked as read and cleared out of your queue. It's a way of keeping high-volume feeds from piling up indefinitely.

The problem before was that setting a sensible discard threshold felt like guesswork. Now you can see the actual publishing pattern before you decide. A feed that posts twice a week probably doesn't need aggressive discarding. One that posts fifteen times a day almost certainly does.

The graph also shows a marker for your current discard setting, so you can see how many of the last 30 days' articles would have survived. It makes the setting feel concrete rather than abstract.

Per-feed overrides

You've been able to set a global auto-discard threshold for a while. What's also possible, and worth knowing if you haven't used it, is overriding it per feed. The noisy tech news feed can discard after a week while the slow personal blog you love sits in your queue forever. The activity graph makes it much easier to decide which feeds deserve which treatment.

That's annoying enough that I built a fix for it.

Spoonfed now saves your scroll position as you read. Not just roughly, it stores the exact fraction of the way through the article you were. Come back five minutes later, five hours later, or the next morning, and the page will restore to where you left off.

How it works

As you scroll, the position is quietly saved in the background. There's no button to press, no manual save, it just happens. When you return to the article, the scroll restoration fires before the page renders, so there's no flash of the top of the article before jumping down.

It's one of those features that's invisible when it works and deeply annoying when it doesn't. The goal was to make it feel effortless.

Opting out

If you'd rather always start articles from the top, some people prefer that, there's a toggle in Settings to disable scroll restore. It's on by default.

Color themes

There are five themes: Default (light), Dark, Nord, Catppuccin, and Catppuccin Latte. They apply across the whole app, reader, settings, library, everywhere. Switching is instant with no reload required.

Nord and the Catppuccin variants are for people who use those palettes everywhere and find it jarring when one app breaks the pattern.

Typography

Four font families are available: the default system sans-serif, a serif option for a more editorial feel, monospace, and OpenDyslexic for readers who find it easier. On top of that you can set five font sizes, five line height options, and four letter spacing settings.

All of these apply directly to the article text in the reader, which is where it matters most.

Live preview

The settings panel shows a live preview of the article text as you change options. You don't have to save to see the effect, adjust the slider, see the text change, decide whether you like it. Saves a lot of back-and-forth.

The combination of theme, font, and size that works for reading a dense technical post is often different from what works for a personal essay. Having the controls close at hand makes it easy to adjust.

They're off by default, if you don't know what vim keybindings are, you probably don't want them showing up unexpectedly. Enable them from Settings > Features.

The shortcuts

The gg shortcut works the way it does in vim, press g twice in quick succession.

Why opt-in

Keyboard shortcuts that fire unexpectedly are one of the most irritating things a web app can do. If you're in a text field or just pressing j while thinking about something else, the last thing you want is for the page to suddenly scroll or advance to the next article.

Keeping them behind a toggle means they only activate for people who've specifically asked for them.

Full-text fetch solves this. When enabled for a feed, Spoonfed fetches the original article page and extracts the main content from it, rather than using whatever the feed provides. You read the full article in the reader without leaving.

How it works

Under the hood it uses go-readability, the same extraction logic that powers Mozilla's reader mode, to pull the main text out of the page and strip away the navigation, ads, and surrounding noise. The result is stored and displayed the same way as any other article.

It's not perfect. Complex page layouts occasionally confuse the extractor, and paywalled content can't be fetched regardless. But for the majority of feeds that truncate their content, it works well.

Per-feed control

Full-text fetch is enabled globally by default, but you can turn it off for individual feeds that already provide complete content, there's no point fetching the page again if the feed already gives you everything. The toggle lives in each feed's settings panel.

For feeds with rich, complete RSS content, you'll probably never need it. For the ones that give you three sentences and a "read more" link, it makes a noticeable difference.

The content filter is a simple way to deal with all of that.

How it works

You add a comma-separated list of words or phrases to the filter in Settings. When Spoonfed fetches new articles, any item whose title, summary, or content contains a match is silently marked as read. It never appears in your queue, it doesn't show a notification, it just quietly disappears.

Matching is case-insensitive and whole-word, filtering "swift" won't block articles containing "swiftly".

Why silent

I deliberately didn't add any "X articles filtered" counter or notification. The point of the filter is that you don't want to think about those topics. Showing you a count of what was blocked would put them back in your attention, which is the opposite of what you wanted.

Filtered articles are marked as read rather than deleted, so they show up in your archive if you ever want to revisit them. The filter is about your reading queue, not permanent removal.

The archive is that somewhere.

What it is

Every article you advance past in the reader gets saved to your archive automatically. There's nothing to configure, nothing to enable. You press Next, the article moves to read, and it's in your archive with the timestamp of when you read it.

The archive shows your full reading history in reverse chronological order, newest first, infinite scroll. You can see today's reading, last week's, months ago.

Re-reading

Clicking any archive entry opens the full article in the same reader view you used the first time. The content is stored, so it works even if the original page has since been updated or removed.

This is useful for the "I'm sure I read something about this once" moments that are otherwise impossible to resolve. You remember approximately when you read it, you scroll back to around that time, and there it is.

What the archive isn't

It's not a to-do list and it's not a search index. There's no full-text search across your reading history, and there's no way to resurface things you've archived back into your reading queue. For saving things you want to keep, bookmarks and quotes, the Library is the right place. The archive is just the record of what you've read, in the order you read it.

Spoonfed tries to make both of those things less annoying.

Auto-discovery

When you paste a URL into the feed input, Spoonfed checks whether it's a feed URL directly. If it's a plain website URL, it fetches the page and looks for <link rel="alternate"> tags, the standard way websites declare their feed addresses. Most blogs and publications include these. If one is found, Spoonfed subscribes to it automatically.

In practice this means you can paste https://example.com just as easily as https://example.com/feed.xml. Either works.

OPML import and export

If you're coming from another RSS reader, export your subscriptions as an OPML file and import it in Spoonfed's Settings. It will subscribe you to all the feeds in the file, skipping any duplicates, and start fetching content in the background.

Export works the same way in reverse, your full subscription list as a standard OPML file, compatible with any other reader. Your feeds are yours; you can take them anywhere.

Why this matters

Lock-in is one of the things that makes people wary of investing in a new tool. If your subscription list is trapped in one app, switching becomes a project. OPML support means it never is. Try Spoonfed, and if you decide it's not for you, export your feeds and leave. Nothing is lost.