# RSS RSS is a Web content syndication format and a dialect of XML. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why the author is using slash pages on Snook.ca DevFeed: [Why the author is using slash pages on Snook.ca]() Original publisher: [Read original article]() Published: 2026-08-07T00:00:00Z Content type: opinion Language: en Sources: [Jonathan Snook]() Topics: [RSS]() Tags: [blog-post](), [rss]() ### AI overview The author introduces the RSS Club on Snook.ca and explains the purpose of slash pages such as /now and /where. The post describes them as a way to share current activities and relevant site information without requiring extensive background, and notes the addition of a privacy policy. ### Source excerpt Hey, it's the inaugural post for the RSS Club on Snook.ca! I was working away on my site, adding content that I thought might be relevant to some, like an AI statement and a privacy policy. Most people probably don't care but for those that do, it's there and it shows that I care about those things, too. I never really had a name for these types of one-off pages but I came across slash pages and with this redesign, I've been considering what felt relevant to include or not include on my own site. Why Now? Some of the items like /now seem like they should be actual blog posts. Like this one. This is what I'm thinking about now. My next blog post will be about what I'm thinking about then, which will be now. Want to know what I'm up to right now? I'm writing now. But when you read this, I'll no longer be writing this. I'll be doing something else. Maybe I'm sleeping, or making coffee, or out walking somewhere, or sitting on the toilet. Why Not? I realize I'm being silly. Sometimes it's nice to catch up with what somebody is up to. It's answering the question, "hey what're you up to these days?" It's surfacing information without requiring people to understand the entire lore about what led you to this moment in time. For example, I subscribe to a couple newsletters that are like a /where page. They update people on their travels while also giving a life update around why they might be on a particular trip, or why they might be at home. Maybe my friends would like to hit up my /where page to see where I might be given all my travels. (I don't have a /where page.) Slash away For now, I have my slash pages plus a couple undocumented ones like my old /speaking page that remains more like a historic artifact found just under the surface. Today, I added my privacy policy. I think that'll be it for now. Have something to say? Tell me about it. ## Taming my intimidating RSS reader queue DevFeed: [Taming my intimidating RSS reader queue]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2026-06-18T07:22:00Z Content type: opinion Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Miniflux](), [RSS]() Tags: [analysis](), [habits](), [miniflux](), [queue](), [reading](), [rss]() ### AI overview The author explains how changes to Miniflux improved their RSS reading experience. They found that perception of an overwhelming unread queue, rather than individual feeds alone, was the main problem, and reduced the pressure by hiding high-volume or low-signal feeds from the global unread list. ### Source excerpt How I regained control of my reading habits ## Sliding Doors: ten years of RSS-Parser DevFeed: [Sliding Doors: ten years of RSS-Parser]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Posts on Marco Gomiero]() Topics: [RSS Feed](), [RSS](), [Mobile](), [Kotlin](), [Coroutines](), [Java](), [Android](), [iOS](), [macOS]() Tags: [android](), [coroutines](), [ios](), [java](), [kotlin](), [macos](), [mobile](), [rss](), [xml]() ### AI overview The author reflects on ten years of RSS-Parser, a library that began as part of an RSS-reading app and was later published for other developers. The article describes how the project contributed to the author's learning and career, including its move from Java to Kotlin and Coroutines, and its continued use in developing a new RSS app. ### Source excerpt Today marks ten years since the first commit of RSS-Parser. TEN YEARS. I want to use this opportunity to reflect on the journey of this library, the sliding doors moments along the way, and the chain of events that made RSS-Parser an important part of my career. The bare bones of the library started earlier, though; it was 2015 when I wrote my first app that I've published to the Play Store. This app was for reading the articles of the tech blog that I was collaborating with (for a while I was reviewing apps, phones, consumer tech - that's when I fell in love with mobile). The blog was built (of course) with the good old WordPress, and at the time I discovered that you can have the published articles formatted in XML - yes, I discovered the existence of RSS. ## A New Resource and Blogroll Page for Performance-Oriented Web Development DevFeed: [A New Resource and Blogroll Page for Performance-Oriented Web Development]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-07-16T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [Web Development](), [Front end](), [CSS](), [HTML](), [SVG](), [Astro](), [RSS]() Tags: [astro](), [css](), [frontend](), [html](), [links](), [performance](), [resources](), [rss](), [svg](), [web-development](), [webdev]() ### AI overview The author announces a new links and resources page for people interested in performance- and platform-oriented web development. It combines recommended resources, background reading, and a blogroll, with an OPML export and more than 250 pointers. The author also comments on creative CSS, HTML, and SVG work, and on the use of 11ty, Astro, and RSS/Atom styling. ### Source excerpt Frances has urged me for years to collect resources for folks getting into performance and platform-oriented web development. The effort has always seemed daunting, but the lack of such a list came up again at work, prompting me to take on the side-quest amidst a different performance yak-shave. If that sounds like procrastination, well, you might very well think that. I couldn't possibly comment. The result is a new links and resources page page which you can find over in the navigation rail. It's part list-of-things-I-keep-sending-people, part background reading, and part blogroll. The blogroll section also prompted me to create an OPML export , which you can download or send directly to your feed reader of choice. The page now contains more than 250 pointers to people and work that I view as important to a culture that is intentional about building a web worth wanting. Hopefully maintenance won't be onerous from here on in. The process of tracking down links to blogs and feeds is a slog, no matter how good the tooling. Very often, this involved heading to people's sites and reading the view-source:// FOMO Having done this dozens of times on the sites of brilliant and talented web developers in a short period of time, a few things stood out. First -- and I cannot emphasise this enough -- holy cow. The things creative folks can do today with CSS, HTML, and SVG in good browsers is astonishing. If you want to be inspired about what's possible without dragging bloated legacy frameworks along, the work of Ana Tudor, Jhey, Julia Miocene, Bramus, Adam, and so many others can't help but raise your spirits. The CodePen community, in particular, is incredible, and I could (and have) spend hours just clicking through and dissecting clever uses of the platform from the site's "best of" links. Second, 11ty and Astro have won the hearts of frontend's best minds. It's not universal, but the overwhelming bulk of personal pages by the most talented frontenders are now built with SS ## New microblog with TILs DevFeed: [New microblog with TILs]() Original publisher: [Read original article]() Author: Julia Evans Published: 2024-11-09T09:24:29Z Content type: opinion Language: en Sources: [Julia Evans]() Topics: [RSS](), [Website](), [Bluesky](), [Mastodon](), [X (Twitter)](), [SQLite](), [Go Language]() Tags: [blog-post](), [go](), [rss](), [social-media](), [sqlite]() ### AI overview The author describes creating a TIL section on their website for saving short notes about useful tools and facts that do not warrant full blog posts. The section uses custom styling, a Rake task for creating posts, and a separate RSS feed, serving as a searchable public alternative to bookmarks while allowing other social-media posts to remain ephemeral. ### Source excerpt I added a new section to this site a couple weeks ago called TIL ("today I learned"). the goal: save interesting tools & facts I posted on social media One kind of thing I like to post on Mastodon/Bluesky is "hey, here's a cool thing", like the great SQLite repl litecli, or the fact that cross compiling in Go Just Works and it's amazing, or cryptographic right answers, or this great diff tool. Usually I don't want to write a whole blog post about those things because I really don't have much more to say than "hey this is useful!" It started to bother me that I didn't have anywhere to put those things: for example recently I wanted to use diffdiff and I just could not remember what it was called. the solution: make a new section of this blog So I quickly made a new folder called /til/, added some custom styling (I wanted to style the posts to look a little bit like a tweet), made a little Rake task to help me create new posts quickly (rake new_til), and set up a separate RSS Feed for it. I think this new section of the blog might be more for myself than anything, now when I forget the link to Cryptographic Right Answers I can hopefully look it up on the TIL page. (you might think "julia, why not use bookmarks??" but I have been failing to use bookmarks for my whole life and I don't see that changing ever, putting things in public is for whatever reason much easier for me) So far it's been working, often I can actually just make a quick post in 2 minutes which was the goal. inspired by Simon Willison's TIL blog My page is inspired by Simon Willison's great TIL blog, though my TIL posts are a lot shorter. I don't necessarily want everything to be archived This came about because I spent a lot of time on Twitter, so I've been thinking about what I want to do about all of my tweets. I keep reading the advice to "POSSE" ("post on your own site, syndicate elsewhere"), and while I find the idea appealing in principle, for me part of the appeal of social media is that it's a ## Docusaurus 3.5 DevFeed: [Docusaurus 3.5]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-08-09T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [modern web development](), [Atom Feed](), [RSS](), [XML]() Tags: [atom](), [blog-post](), [features](), [release](), [rss]() ### AI overview Docusaurus 3.5 is a release focused on new blog features, including social links for blog authors, dedicated global author pages, styled RSS and Atom feeds, yearly sidebar grouping, and options that enforce consistent blog author and truncation practices. ### Source excerpt We are happy to announce Docusaurus 3.5. ## Syndication feed now available DevFeed: [Syndication feed now available]() Original publisher: [Read original article]() Author: Eaton Published: 2023-01-28T17:38:46Z Content type: release Language: en Sources: [Eaton Works Feed]() Topics: [Atom Feed](), [Atom](), [RSS]() Tags: [announce](), [rss](), [syndication]() ### AI overview The site now provides an Atom syndication feed. New posts will be added automatically when published, and the feed is intended to work with compatible readers. ### Source excerpt An Atom feed is now available for the site. ## RSS and XSL Content-Type Requirement DevFeed: [RSS and XSL Content-Type Requirement]() Original publisher: [Read original article]() Author: Erik Runyon Published: 2021-05-19T00:00:00Z Content type: tutorial Language: en Sources: [Erik Runyon]() Topics: [RSS Feed](), [RSS](), [Atom](), [XML](), [Rails](), [User Experience]() Tags: [experience](), [news](), [rails](), [rss](), [user-experience](), [web-development](), [xml]() ### AI overview This article explains that Atom and RSS feeds intended to display with XSLT should be served with the Content-Type text/xml; charset=utf-8 rather than their feed-specific application types. The author reports that changing the response header in a Rails application enabled the formatting and styles. ### Source excerpt We've provided Atom/RSS feeds for News and Events in our custom CMS at Notre Dame for well over a decade. However, if a visitor ended up on the url they were greeted with an unhelpful screen of XML. I decided to remedy this by appying some XSLT and styles to improve the user experience. However, even after reviewing several tutorials, I couldn't get it to work. I was sure I had the templates and markup configured correctly. I even tested outside of the system using very basic test files. I finally started to question whether the Application-Type was correct. One tutorial mentioned making sure you served the correct type, but didn't go into detail as to what the type should be. Since the very beginning, we would serve our Atom/RSS feeds with application/atom+xml; charset=utf-8 and application/rss+xml; charset=utf-8 respectively. What I discovered is that the Application-Type instead should be text/xml; charset=utf-8. Once that was set in my test files everything started to work. Going back the Rails application and setting Application-Type in the "response.headers" and bingo, glorious formatting and styles. I don't expect many users to end up seeing the results of this change. But for those that do, they'll have an explanation about what a feed is as well as links to more resources. So much better than a screen of XML. ## An Open Letter to Bob Frankston DevFeed: [An Open Letter to Bob Frankston]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-07T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [RSS Feed](), [RSS]() Tags: [blogging](), [rss]() ### AI overview An open letter urges Bob Frankston to configure his blogging tool to publish full-content RSS feeds instead of summaries. The author argues that requiring readers to click through from aggregators can cause them to miss the full post and notes that full-content feeds are no harder to produce. ### Source excerpt (Photo Credit - Lisa Meece; Thank You) Hi Bob, I strongly doubt you remember but I met you years ago as part of the Boston Blogging group that Dave Winer used to organize. About the same time I also met Dan Bricklin. I wanted to make a suggestion to you. I've been subscribed to you in my aggregator for a long time but due to the design of aggregators, it isn't clear if a post in the aggregator is full content or summary. Here's all I saw of your current (wonderful) CES post: CES is a time to see new products and services. Alas, my expectations might be too high. And here is how this appears in an aggregator: I thought this was just a lament but I happened to click through and lo and below, a wonderful bit of writing. So my suggestion to you is to change your blogging tool to output the full content of each post you write. I'm pretty certain you wrote your own blogging tool and, thus, I know this is possible; you obviously have the skills (and if that isn't the greatest understatement I've made blogging, I don't know what is). My suspicion is that for yourself it is more important that you get your ideas out into the universe than that you drive people to your site. This is the single best reason for a full content feed. Every time you have to rely on someone clicking thru from their aggregator to your site, there is a solid chance (1 in 2; 1 in 3; 1 in 5; 1 in 10 ???) that they just won't). Often times they don't ever know that there is more content out there; I certainly didn't and I've been in the RSS world now for almost 20 years and I have pretty solid credentials in the RSS world - I was the creator of the Feedster RSS and Blog search engine. Note: My own blog and my recipes are all done with full content feeds so I'm not askign you to do anything that I'm not doing. Also full content feeds aren't really any harder than a summary feed - just put out the full content. Feel free to use my feed as an example. Even better - use Dave's. Btw I loved this point: "I mo ## Goodbye, Feedburner DevFeed: [Goodbye, Feedburner]() Original publisher: [Read original article]() Author: Adam Published: 2019-12-03T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [RSS Feed](), [RSS](), [Google](), [proxy]() Tags: [google](), [proxy](), [rss](), [update]() ### AI overview The article announces the end of Feedburner and asks readers who access the blog through Feedburner RSS to update their subscription method. It also explains that the author cannot provide support or management for Feedburner-based RSS proxying. ### Source excerpt The time has come. ## Clip sharing with Overcast DevFeed: [Clip sharing with Overcast]() Original publisher: [Read original article]() Author: Marco Arment Published: 2019-04-27T16:41:33Z Content type: release Language: en Sources: [Marco.org]() Topics: [podcasting](), [App](), [RSS]() Tags: [apple](), [audio](), [feature](), [rss](), [version](), [video]() ### AI overview Overcast 2019.4 adds audio and video clip sharing of up to one minute from any public podcast. Users can create portrait, landscape, or square video clips, optionally include Overcast and Apple Podcasts badges, and see links to other podcast apps and RSS feeds on public sharing pages. ### Source excerpt Sharing podcasts has never been easy, but I've always tried to lead the way with Overcast, with publicly shareable episode links and optional recommendations from your Twitter friends since version 1.0 in 2014. Podcast sharing has been limited to audio and links, but today's social networks are more reliant on images and video, especially Instagram. Podcasts need video clips to be shared more easily today. I've seen some video clips from tools specific to certain podcast networks or hosts, but they were never available to everyone, or for every show. So people mostly just haven't shared podcast clips, understandably, because it has been too hard. Not anymore. ▶ ↩ This remark on Unco by Stephen Hackett inspired me to finally solve this problem in a way that worked easily, for all podcasts, for both podcasters and listeners to use. With today's 2019.4 update1, you can now share audio or video clips, up to a minute each, from any public podcast. Simply tap the share button in the upper-right corner. You can generate an audio clip, or portrait, landscape, or square video, using your current Overcast theme setting. In order to help spread podcasts further, I didn't want to be heavy-handed in the Overcast branding -- not everyone wants to advertise for one specific podcast app when promoting their shows. So the "Shared with Overcast" badge is optional, and if you'd like, you can also add an Apple Podcasts badge. Finally, I wanted to extend the same app-agnosticism to Overcast's share links. While this design still needs a lot of modernization, I've done a small refresh: Now, for non-logged-in visitors, Overcast's public sharing pages display badges for other podcast apps and the RSS feed for any podcast listed in Apple Podcasts. It's important for me to promote other apps like this, and to make it easy even for other people's customers to benefit from Overcast's sharing features, because there are much bigger threats than letting other open-ecosystem podcast apps get a f ## How we use StackOverflow to support our developers DevFeed: [How we use StackOverflow to support our developers]() Original publisher: [Read original article]() Author: Tristan Sokol Published: 2017-12-19T21:17:48Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Stack Overflow](), [Support](), [RSS](), [RSS Feed](), [data](), [Framework](), [Mobile]() Tags: [analytics](), [apis](), [community](), [developers](), [documentation](), [email](), [metrics](), [mobile](), [rss](), [support](), [tools]() ### AI overview Square describes how its developer-support team uses Stack Overflow, tagging guidance, email notifications, RSS feeds, chat, the mobile app, and analytics to answer questions about Square's APIs and measure response times. ### Source excerpt These are some of the tools and techniques we use to answer your questions about Square's APIs; they might help you support your community, too! ## How to easily handle RSS Feeds on Android with RSS Parser DevFeed: [How to easily handle RSS Feeds on Android with RSS Parser]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2017-08-16T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [RSS Feed](), [RSS](), [Android](), [Android Library](), [Parser](), [Library](), [App](), [GitHub](), [Gradle]() Tags: [android](), [app](), [article](), [bug](), [code](), [display](), [download](), [github](), [gradle](), [how-to](), [library](), [rss]() ### AI overview A tutorial for using the RSS-Parser Android library to download one or more RSS feeds and extract article metadata such as titles, descriptions, content, images, links, and publication dates. It also outlines the parser execution and error-handling callbacks. ### Source excerpt Two month ago I have talked about YoutubeParser, an Android Library that I developed. Today I want to talk about RSS-Parser, another library that I wrote. This library allows you to easily download an (or multiple) RSS Feed in order to display it in your application. For every article it is possible to download the following information: Title Author Description Content Main Image Link Publication Date Here you can find an example of feed. ## Some non-traditional marketing tips DevFeed: [Some non-traditional marketing tips]() Original publisher: [Read original article]() Author: Map Published: 2014-03-31T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [email](), [RSS](), [Messaging](), [Users](), [Website]() Tags: [email](), [marketing](), [messaging](), [rss](), [tips](), [users](), [web]() ### AI overview This opinion article presents non-traditional marketing ideas for software businesses: offer email subscriptions when RSS is less effective, include small calls to action in transactional emails, and retarget existing users to promote unused features. ### Source excerpt Marketing is generally unexciting to a ton of engineers, until it brings eyeballs which bring feedback and dollars. Marketing doesn't have to always be cheesy campaigns or ads, it can often just be surfacing the things your customers actually do want to care about. My favorite type of marketing is when a service sells me on something at the exact time I want it. Here's a few short tips on some non-traditional marketing that won't seem sleezy but still can work quite well. Email subscriptions to your blog RSS is pretty dead, google went and killed it with google reader. Sure there's some decent replacements if you're really tied to it. In particular newsblur by @samuelclay is a great reader. But now days content emerges on twitter, fb, and ranking services, then later is discovered via search. Both of these work pretty well, but twitter is ephemeral for so many. Email still converts incredibly well, if people are abandoning rss but still care about your content give them the ability for it to be put right in front of their face via email. Market in transactional emails Have emails that include receipts? Account confirmations? General notices? No not a monthly newsletter! Transactional emails are obviously valuable to your users. Why not include a small call out to your latest announcement? Have a central hook that your emails can check from and simply include a small call to action within there. Credit to @stevenbristol on strong business podcast for this one Retarget to your existing users In a similar vein of notifying your existing customers in transactional emails about news, you should be doing this all over the web. Retargeting is great to convert people once you've already got them on a landing page, but its also incredibly useful to get existing users to use a specific feature. If you track if they've never used a feature retargeting is a great way to make them aware of it, and once they've used it just count it as a conversion. My favorite retargeting provid ## Automated Google Reader Backups DevFeed: [Automated Google Reader Backups]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-02-01T20:30:00Z Content type: article Language: en Sources: [Keith Smiley]() Topics: [Google](), [Ruby](), [RSS](), [Script](), [RSS Feed](), [Server](), [Authentication]() Tags: [automated](), [download](), [google](), [networking](), [python](), [rss](), [ruby](), [run](), [script](), [server]() ### AI overview This article describes automating Google Reader subscription backups. The author rewrites a Python script in Ruby and schedules it as a cron job on a server to authenticate with Google and download a current OPML subscription export. ### Source excerpt I spend a lot of time in my RSS Reeder (see what I did there?). I still find Google Reader to be the best and easiest way to manage my subscriptions, although I've been wanting to switch to Fever for a while. One thing I wanted to do when I launched my new site (the one you're reading) was to have a downloadable up to date export of my Google Reader OPML file (which of course I never did). I looked around for good ways to automate this and I found a simple Python script to do it with (sorry I couldn't find it again for this post). I decided to rewrite it in Ruby and set it up on my server as an automated cron job. To run the script I came up with use something like: ruby path/to/googleReaderOPML.rb username@gmail.com SekretPassword To add it to your crontab (to run every Sunday at 1:01am) use something like: 1 1 * * 7 ruby path/to/googleReaderOPML.rb username@gmail.com SekretPassword #!/usr/bin/env ruby # # => This script will authorize your Google credentials and download your Google Reader subscriptions # => Usage: ./googleReaderOPML.rb GOOGLEUSERNAME PASSWORD # # The required networking shenanigans require 'uri' require 'net/http' require 'open-uri' require 'rubygems' # This requires the 'colorize' gem. Install with '[sudo] gem install colorize' require 'colorize' # The base Google URLs for callback, authentication, and subscription export $GOOGLE_URL = "http://www.google.com" $LOGIN_URL = "https://www.google.com/accounts/ClientLogin" $READER_URL = "http://www.google.com/reader/subscriptions/export" # The user agent string, for some reason this is required, feel free to change it $SOURCE = "keith.so" # The default output filename, it is automatically overwritten if one already exists $FILE_NAME = "googlereadersubscriptions.opml" # Make sure there is the correct number of arguments if ARGV.count != 2 # Print the instruction puts "Usage: ./#{ File.basename(__FILE__) } USERNAME PASSWORD".red exit end # Build the request URL uri = URI.parse($LOGIN_URL) # Setup the Pa ## Tom Coates - Native to a Web of Data DevFeed: [Tom Coates - Native to a Web of Data]() Original publisher: [Read original article]() Author: Graham King Published: 2006-03-11T18:45:43Z Content type: article Language: en Sources: [Graham King]() Topics: [Web](), [data](), [API](), [interface](), [XML](), [RSS](), [Web platform](), [Ajax]() Tags: [ajax](), [api](), [data](), [futureofwebapps](), [html](), [interfaces](), [network](), [platform](), [rss](), [society](), [software](), [web]() ### AI overview This article summarizes notes from Tom Coates' Future Of Web Apps presentation about moving from linked web pages toward a web of data connected by APIs. It discusses designing around addressable, reusable data objects; providing HTML, API, and XML interfaces; using RSS for list pages; and preserving stable, predictable URLs while supporting manipulation interfaces. ### Source excerpt Navigating the future: Web 2.0 insights from Tom Coates. ## Joshua Schacter - del.icio.us - Things we've learned DevFeed: [Joshua Schacter - del.icio.us - Things we've learned]() Original publisher: [Read original article]() Author: Graham King Published: 2006-02-18T13:05:24Z Content type: article Language: en Sources: [Graham King]() Topics: [web applications](), [Web Development](), [API](), [Monitoring](), [Databases](), [Latency](), [RSS](), [browser]() Tags: [apache](), [api](), [browser](), [cache](), [database](), [developer](), [futureofwebapps](), [latency](), [mod-rewrite](), [monitoring](), [software](), [web-apps]() ### AI overview Notes from Joshua Schachter's 2006 talk about lessons from building del.icio.us, including solving a real problem, monitoring and optimizing applications, designing usable APIs and URLs, supporting RSS, and responding to unexpected user behavior. ### Source excerpt "Valuable insights from del.icio.us founder: Building web apps that users love."