标签：#RSS

A guide to formatting an RSS 2.0 feed so DEV.to imports your articles, images, and tags with zero formatting errors. 1. Quick Checklist: What to Do [ ] Wrap full article HTML inside <content:encoded><![CDATA[...]]></content:encoded> . [ ] Convert all image src , srcset , and link href attributes to absolute URLs ( https://domain.com/... ). [ ] Sanitize tags ( <category> ): alphanumeric only ( a-z0-9 ), max 20 chars, max 4 tags per post. [ ] Provide a unique <guid isPermaLink="true"> to prevent duplicate imports. [ ] Provide cover images via <enclosure> and as the first <img> inside <content:encoded> . [ ] In DEV Settings, keep "Mark RSS source as canonical" checked and "Replace self-referential links" unchecked. 2. RSS Field Reference <item> Fields Field Requirement What It Does on DEV.to <title> Required Article headline. Escape XML special characters. <link> Required Canonical link back to original post. <guid> Required Unique ID. Prevents re-importing duplicates on sync. <content:encoded> Required Full HTML body wrapped in <![CDATA[...]]> . Converted to Markdown by DEV. <description> Fallback Excerpt/summary. Used as body only if <content:encoded> is missing. <pubDate> Recommended UTC date ( Wed, 19 Aug 2026 10:00:00 GMT ). Sets publication/draft date. <category> Optional (Max 4) Becomes post tags. Must be alphanumeric and $\le$ 20 chars. <enclosure> Optional Sets the post's cover/hero image ( type="image/webp" or image/png ). <author> Optional email@domain.com (Author Name) 3. Strict Formatting Rules Rule 1: Tags ( <category> ) DEV.to rejects or corrupts tags that don't match [a-zA-Z0-9] : Remove special chars: next.js $\rightarrow$ nextjs , web-dev $\rightarrow$ webdev , c# $\rightarrow$ csharp . Truncate: Maximum 20 characters per tag. Limit: Maximum 4 tags per post. Rule 2: Images & Links (Must Be Absolute) DEV.to cannot resolve relative paths like /images/hero.png . ❌ <img src="/images/hero.png"> ✅ <img src="https://yourdomain.com/images/hero.png"> ❌ <a href

Feedly says a bug is behind the performance issues that have made its web app nearly "unusable" for some users, while complaints about its mobile apps and customer support are adding to frustrations.

If you subscribe to more newsletters than you read, which tool fixes it depends entirely on which problem you actually have. Most roundups skip that step and just rank apps. Disclosure up front: we make one of the eight tools below. It's the last entry, it's new, and it has no track record — its section says so plainly. The other seven are real options and for most people one of them is the better pick. Every price and behaviour here was checked against the vendor's own site on 2 August 2026 . Where a vendor doesn't publish a price, this says that instead of guessing. The two problems people both call "too many newsletters" They aren't the same problem, and the tools split cleanly along the seam. Clutter. Newsletters are burying your real email. You'd read them, you just don't want them sitting next to your bank and your on-call alerts. The fix is routing: move them somewhere else. Volume. Twenty-five arrive a week and you have time for three. Moving them changes nothing — now you have twenty-five unread items in a nicer app. The fix is either condensing the pile or deciding what's in it. Almost every tool below solves exactly one of these. Buying a clutter tool for a volume problem is the standard way to end up paying a subscription and still having the same unread count. The plumbing, since you're the one wiring it up Four mechanics show up across all eight: Dedicated intake addresses. Readwise Reader, Meco, Readless and Digest each hand you an address on their domain (Meco's look like you@mecoinbox.com ). You subscribe with it and their infrastructure receives the mail — the cleanest integration point available: no OAuth scope on your mailbox, no IMAP polling, no shared credentials. Mailbox connection. Meco will alternatively connect Gmail or Outlook and pull your existing subscriptions across, setting the selected ones to skip your inbox (reversible at any time, per Meco's FAQ). Much faster than re-subscribing to 25 newsletters by hand. The cost is a read scope

HyperTexting's new app aims to make the open web feel more like social media by turning websites, blogs, newsletters, and podcasts into a scrollable feed, while also making it easier to post to your own website.

Here is an uncomfortable one: you do not own your reading list. You rent it. Every "follow" button you have pressed in the last decade put your reading relationship inside a company's database, where it can be ranked, throttled, or ended the day the business model changes. You did not sign anything. You just stopped owning it. It was not always like this. Feeds were the quiet machinery that kept the web interoperable. RSS and Atom meant a site, a reader, and a robot could all agree on the same stream without asking anyone's permission. You published once, and anything could read it: whatever app, whatever order, no algorithm in the middle. Then it eroded. Plenty of sites ship no feed at all now, and "follow us" quietly became "create an account on someone else's platform." The reason is not mysterious. Platforms had every incentive to close the loop, because a feed lets you leave, and an account does not. So the industry swapped "here is my stream, read it however you like" for "log in to see updates," and a generation of sites simply stopped publishing feeds, because the platform was where the audience was. That is the trade you made without noticing. The open format that asked nothing of you got replaced by a login that asks for everything. Your reading list used to live in your reader and survive a company changing its mind, its ranking, or its whole business. Now it lives in their database and survives exactly as long as they allow. Getting it back is not nostalgia. It is infrastructure for independence: tooling that treats feeds as a first-class citizen, aggregates the sources you actually choose, and keeps that stream under your control instead of a platform's. The full case for why this is worth fixing, and what feed-first tooling looks like, is here: https://mederic.me/blog/open-web-feeds So, honestly: how many of the people and sites you follow could you still read tomorrow if the platform in the middle disappeared tonight?