--- title: Atom feeds description: Every Sifa profile publishes an Atom XML feed of its activity. Subscribe in any feed reader (NetNewsWire, Reeder, Feedly, etc.) to follow someone without an Atmosphere account. --- Every public Sifa profile publishes an Atom feed of its activity. Anyone with a feed reader can subscribe to it. No Sifa account, no [Bluesky](https://bsky.app) account, no [AT Protocol](https://atproto.com) identity required. Open web, open standards, open subscriptions. ## The URL pattern ``` https://sifa.id/p//activity.atom ``` Examples: - `https://sifa.id/p/alice.bsky.social/activity.atom` - `https://sifa.id/p/alice.com/activity.atom` (custom domain handle) You don't have to remember the exact path. Feed readers usually auto-discover the feed from the profile's HTML. Most apps let you paste in the regular profile URL (`https://sifa.id/p/alice.bsky.social`) and they find the feed themselves via the `` tag in the page head. ## How to subscribe In most feed readers ([NetNewsWire](https://netnewswire.com), [Reeder](https://reederapp.com), [Feedly](https://feedly.com), [Inoreader](https://www.inoreader.com), [FreshRSS](https://freshrss.org), [Miniflux](https://miniflux.app), [NewsBlur](https://newsblur.com)) the flow is the same: 1. Copy the Sifa profile URL. 2. In your reader, hit **Add Feed** (or equivalent). 3. Paste the profile URL. If the reader doesn't auto-discover, paste the explicit `/activity.atom` URL instead. ## What ends up in the feed The feed mirrors the rules in [Activity feed](/docs/activity-feed): the **"Made"** entries (articles, reviews, repos, RSVPs, and other things you create), not the **"Did"** entries (likes, follows, reposts). That keeps the feed useful as a way to follow someone's work, not a firehose of every tap they make on the network. ## Refresh interval The feed is cached for **30 minutes** at the edge (`Cache-Control: public, max-age=1800`). A reader polling more often than that hits the cache and doesn't see new entries until it expires. That's what most well-behaved readers default to anyway. Need fresher data than 30 minutes (say, you're building something that reacts to new Sifa activity)? Read directly from the AT Protocol firehose instead of polling the Atom feed. ## Why we publish the Atom feed Three reasons: - **Read access without an account.** Someone reading this docs page may not want a Bluesky or Sifa account just to keep tabs on what you publish. A feed reader is enough. - **Long-time-horizon readers.** Feed readers outlast platforms. People who subscribed to your blog in 2007 may still subscribe in 2026. Atom feeds give your Sifa profile that same durability. - **Bridge to non-Atmosphere apps.** Tools that don't yet understand the AT Protocol (link aggregators, automation services, custom dashboards) can still ingest your activity through plain XML. ## What's not in the feed - Private fields. There are none on Sifa profiles, so this is mostly an academic point. - "Did" activity (likes, reposts, follows). See [Activity feed](/docs/activity-feed) for why. - Real-time updates. The 30-minute cache is by design. Use the firehose for real time. - Cross-account aggregation. The feed is per-profile. There's no "everyone you follow" feed yet.