Discover New Programming Memes with RSS

Direct answer

Send an unauthenticated GET request to https://devme.me/rss.xml. Parse the RSS 2.0 channel, process up to 50 items, and use each item’s <link> or permalink <guid> as the canonical DevMeme destination.

Capability and version

RSS 2.0 — public feed

Supported surface

The supported endpoint is exactly /rss.xml. It returns XML with the RSS, Media RSS, and content:encoded namespaces. There is no RSS page parameter, topic filter, account feed, or token exchange.

Authentication

No authentication is required. A feed reader or agent can fetch the public URL without cookies. Do not attach an account session to routine polling.

Prerequisites

• An HTTP client that can parse XML.
• Support for the RSS 2.0 channel and item structure.
• A cache that can retain the last valid response across a temporary 503.

Steps

1. Send GET https://devme.me/rss.xml with an RSS or XML accept header.
2. Require a successful RSS content type before parsing.
3. Read channel metadata, then process each <item> in returned order.
4. Deduplicate with the permalink <guid> or canonical <link>.
5. Retain the last valid feed and respect its cache policy before polling again.

Copyable example

curl --fail --silent --show-error \
  --header 'Accept: application/rss+xml' \
  https://devme.me/rss.xml

On success, require status 200 and content-type: application/rss+xml; charset=utf-8 before parsing.

URL and response contract

Each <item> can contain:

• a title;
• a canonical meme <link>;
• a permalink <guid>;
• a short description using the title and indexed category or tag labels;
• content:encoded with image and text HTML;
• media:content for the image;
• an optional <pubDate> only when DevMeme has an authoritative publishedAt.

The feed does not emit an <enclosure> record. Clients that need an image should read media:content or the HTML inside content:encoded.

An item link leads to a canonical page such as Ancient Debugging Wisdom from Confucius.

Expected result

The client receives a valid RSS 2.0 document with channel metadata and up to 50 items. Each item provides a stable DevMeme page link or GUID, while image-aware clients can use media:content or content:encoded.

Ordering and freshness

The server asks for 50 items with idx:desc. That is descending catalog-index order, not a promise of strict publication chronology. <lastBuildDate> reports when the XML was generated; it is not a publication date for every item.

Do not infer freshness from a missing <pubDate>, and do not substitute a historical Telegram or source-post timestamp.

Limits, caching, retries, and errors

A successful response uses:

Cache-Control: public, max-age=900, stale-while-revalidate=3600

Treat the feed as fresh for 15 minutes. A cache may serve a stored response for up to one hour while it revalidates.

If the underlying meme index is unavailable, DevMeme returns status 503 with the plain-text body rss_unavailable. Keep the last valid cached response, wait, and retry with bounded exponential backoff. Never turn that error body into an empty successful feed.

• The feed is a fixed 50-item window with no pagination.
• It is not a keyword-search endpoint; use the browser search workflow for a query.
• Item order can change as the catalog changes.
• A missing pubDate is intentional when no authoritative publication date exists.
• Feed generation depends on the DevMeme search index and fails explicitly when that dependency is unavailable.

Attribution rules

Retain the item title and canonical link or GUID when you quote, summarize, or surface the result. If you reuse or embed media, review the source and rights information on the linked meme page; RSS availability does not grant ownership or reuse rights.