We make private RSS feeds truly private.

    Or at least try. )
    Recently, I presented a script to the public that allows you to export feeds along with sub-entries from Livejournal.com.
    And immediately the voices of reason were heard:
    payalnik : What a bad method to open sub-locks for the whole internet. We are waiting for the first scandals.
    anton : But you understand that by doing so, you run the risk of opening the sub-locks of all your friends in public and after a month find them in the search?

    The whole day I went and tried to remember: somewhere I already saw it. Someone has already talked about this. And remembered!
    And then finding the source was not difficult:
    http://php.vanhecke.info/2008/01/20/republish-a-feed-or-other-data-protected-by-http-basic-authentication
    As for personalized RSS feeds, most services do not protect content with the requirement to enter a username / password, but provide the user with an open but random URL for the feed.
    For web-based RSS aggregators, such as Bloglines or Google Reader, there is a non-zero chance that other users will stumble on the private content of your feeds.
    That is why Bloglines introduced the directive.
    If the ee feed contains, Bloglines will not display its content in an open search.
    However, the author did not find any mention that Google Reader supports this directive. True, the experiments showed that from a different account it was not possible to find the contents of the tape with the installed directive, although the tape exists and has been added for a month.

    Specification Link: www.bloglines.com/about/specs/fac-1.0

    Also popular now: