In case anyone cares, I now have a basic implementation of RSS cloud working in Snarfer. It's still a work in progress, but I've at least proved to myself that...
Dave, I would really like to support a real-time RSS mechanism. Unfortunately, I can't figure out how to make rssCloud work in many real world scenarios. Here...
... I'm guessing you didn't read my message in which I said I had just got RSS cloud working on a deskop client from behind a NAT - no router configuration ...
Can you elaborate on how you enabled NAT traversal? Firewalls are not only a technical problem, they are also an adoption problem. Most all large corporations...
Dave, The RSS Advisory Board is the only place to go for RSS help. James runs tests to determine the usability of various RSS elements and knows more about the...
... Then who _does_ own the spec? You? Can you try and fix the gaping holes in the spec then? The spec has several gaping holes, and nobody outside of the...
... Mr. Winer doesn’t *want* anyone to try and fix them. Atom was not created because everyone wanted the glory of being spec authors of yet another...
... I'm using UPnP (Universal Plug and Play) - more specifically, the Internet Gateway Device protocol. On Windows, it's just a couple of lines of code. You...
UPnP is not supported by many routers and is specifically disabled in Windows by default because of malware issues. This solution would only work, if a geek...
... The Windows firewall can be controlled programmatically as well, so in theory that part is still feasible without geek intervention too. As for UPnP...
1. I'm pretty sure that Harvard University [1] owns the RSS 2.0 spec. 2. The Roadmap specifies terms under which you can modify the spec. It makes no mention...
... The RSSCloud Interface has been a part of the specification since 1999. You're proposing to make changes to it, rather than doing new work in a namespace. ...
Direct quote from Dave, "I will join as a member, if you want me to, to help give it legitimacy." http://tech.groups.yahoo.com/group/rss-public/message/1374 ...
Hi folks-- Didn't get any response before, so just wanted to try one more time: Is anyone at RssBoard interested in providing an XML namespace for RSS 2.0, for...
Randy Charles Morin and I have been working on draft documentation for an RSS namespace. Here's a link to it: http://www.rssboard.org/rss-namespace As the docs...
Hey, that's really great! (Turns out there were many good responses to my earlier post that I missed because my subscription notifications to this list are not...
I'm working on parsing some RSS 2.0 content, and I've found that several popular RSS 2.0 documents have multiple links embedded in one <link> tag separated by...
Nate, Believe it or not, that's just one big weird-ass looking singular link, not multiple links. There's nothing in RSS about having multiple links in the...
Hello, everybody. Here are some comments on the draft rss-namespace document posted at http://www.rssboard.org/rss-namespace 1.) The Introduction says: "This...
With the current interest in rssCloud and PubSubHubbub (PuSH), I've been thinking about all the bandwidth that's consumed by the RSS elements that describe the...
I posted this idea on my blog [1], and Antone Roundy had a better idea than ttl -- putting the date and time the feed details were last updated in the element,...
In theory this info is already coming with the feed as part of the HTTP headers. Use the data that's already present. But since that data is often ignored (and...
... I would think you'd still need to send the full feed by default for backwards compatibility with clients that don't understand your new minimal format. And...
... My thinking was that because the namespace was centered on RSS, it would be better to use its date-time format. If it was expanded to support Atom, I would...
... By "this info" you mean the date-time of last update, correct? I can see why it would be better to make a HEAD request to the feed details feed to...
... It’s not just ease of parsing, it’s also 2- vs 4-digit years (are you using RFC 822 or RFC 2822 format?), and the presence of redundant information...