Re: RSS to compete with social networks
Seth Russell <[email protected]> Mon, 10 Feb 2014 13:50:29 -0800
| Newsgroups | gmane.network.syndication.rss.support |
|---|---|
| Message-ID | <CACfYUR7H_UMRPe07WdEYEjh+iaNrsX=39MwoA6YHgGvOQYHOOA@mail.gmail.com> |
--001a11c1223a77713f04f2145694 Content-Type: text/plain; charset=ISO-8859-1 seems to me that you could have just one feed and avoid the separate secret transactions ... which wold be very cumbersome ... by just encrypting those items in the feed that are private to a specific group. A person could read the secret items if they were given the key in a separate channel. Great idea, incidentally. I hope it happens. seth the #toothlessfoodie <https://plus.google.com/s/%23toothlessfoodie> Facebook: facebook.com/russell.seth Blog: fastblogit.com/seth/ Talking products: www.speaktomecatalog.com On Tue, Jun 25, 2013 at 11:42 PM, Roxics <[email protected]> wrote: > > > What we are missing in RSS is the ability to send content privately. For > instance if I want to mark a blog entry to only be viewable to certain > people I really can't do that while also syndicating it. Someone would have > to come to my website, login and view it. This puts RSS at at a > disadvantage compared to social networks that have privacy walls in place > where members can view restricted content from other members on their > friends list. > > It would be nice if RSS supported some kind of protocol for doing this. So > that I can mark a blog entry as readable to only certain email addresses. > Then people can put their email address in their RSS reader and if the > entry comes through with their email address on the include list, it will > show them the restricted content. > > I'm not entirely sure how this would work. The reader would have to ping > back the source the original feed came from and request a hidden feed that > contained the information that was left out of the public feed. Which means > the software that publishes would have to generate special hidden feeds for > each email address on the include list for that entry. > > Ultimately the end user experience should feel similar to circles on > google+. A person can submit their email address to your self hosted weblog > and you can then manage all those people by putting them into groups. > Whenever you add a blog entry or image or video or audio clip you can mark > that content to be viewable to only certain groups if you don't want it > public. > > Similarly it would be nice if RSS featured some kind of profile feed. > Where instead of entering email addresses (like mentioned above) someone > could just sumbit their profile URL and the the reader would parse the RSS > profile feed from it. It would send basic information like username, first > and last name, profile photo, website URLs, description, interests, gender, > relationship status, who I want to meet, etc. This information doesn't > necessarily get saved to the website it's submitted it, but instead it gets > pulled up every time that person appears on that website. > > The idea is that a social network could be created using personal websites > without a central repository. A person submits their profile URL from their > personal website to other personal websites. They are then added as a > contact that can be grouped and view restricted content coming form that > site in their chosen feed reader. > > > --001a11c1223a77713f04f2145694 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <head> <style type="text/css"> <!-- /* start of attachment style */ .ygrp-photo-title{ clear: both; font-size: smaller; height: 15px; overflow: hidden; text-align: center; width: 75px; } div.ygrp-photo{ background-position: center; background-repeat: no-repeat; background-color: white; border: 1px solid black; height: 62px; width: 62px; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited { text-decoration: none; } div.attach-table div.attach-row { clear: both; } div.attach-table div.attach-row div { float: left; /* margin: 2px;*/ } p { clear: both; padding: 15px 0 3px 0; overflow: hidden; } div.ygrp-file { width: 30px; valign: middle; } div.attach-table div.attach-row div div a { text-decoration: none; } div.attach-table div.attach-row div div span { font-weight: normal; } div.ygrp-file-title { font-weight: bold; } /* end of attachment style */ --> </style> </head> <html> <head> <style type="text/css"> <!-- #ygrp-mkp { border: 1px solid #d8d8d8; font-family: Arial; margin: 10px 0; padding: 0 10px; } #ygrp-mkp hr { border: 1px solid #d8d8d8; } #ygrp-mkp #hd { color: #628c2a; font-size: 85%; font-weight: 700; line-height: 122%; margin: 10px 0; } #ygrp-mkp #ads { margin-bottom: 10px; } #ygrp-mkp .ad { padding: 0 0; } #ygrp-mkp .ad p { margin: 0; } #ygrp-mkp .ad a { color: #0000ff; text-decoration: none; } --> </style> </head> <body> <!-- |**|begin egp html banner|**| --> <br><br> <!-- |**|end egp html banner|**| --> <div dir="ltr"><div>seems to me that you could have just one feed and avoid the separate secret transactions ... which wold be very cumbersome ... by just encrypting those items in the feed that are private to a specific group. A person could read the secret items if they were given the key in a separate channel. <br> <br></div>Great idea, incidentally. I hope it happens.<br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">seth <br><br>the <a href="https://plus.google.com/s/%23toothlessfoodie" target="_blank">#toothlessfoodie</a><br> Facebook: <a href="http://facebook.com/russell.seth" target="_blank">facebook.com/russell.seth</a><br>Blog: <a href="http://fastblogit.com/seth/" target="_blank">fastblogit.com/seth/</a><br>Talking products: <a href="http://www.speaktomecatalog.com" target="_blank">www.speaktomecatalog.com</a><br> </div></div> <br><br><div class="gmail_quote">On Tue, Jun 25, 2013 at 11:42 PM, Roxics <span dir="ltr"><<a href="mailto:[email protected]" target="_blank">[email protected]</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <u></u> <div style> <span> </span> <div> <div> <div> <p>What we are missing in RSS is the ability to send content privately. For instance if I want to mark a blog entry to only be viewable to certain people I really can't do that while also syndicating it. Someone would have to come to my website, login and view it. This puts RSS at at a disadvantage compared to social networks that have privacy walls in place where members can view restricted content from other members on their friends list. <br> <br> It would be nice if RSS supported some kind of protocol for doing this. So that I can mark a blog entry as readable to only certain email addresses. Then people can put their email address in their RSS reader and if the entry comes through with their email address on the include list, it will show them the restricted content. <br> <br> I'm not entirely sure how this would work. The reader would have to ping back the source the original feed came from and request a hidden feed that contained the information that was left out of the public feed. Which means the software that publishes would have to generate special hidden feeds for each email address on the include list for that entry. <br> <br> Ultimately the end user experience should feel similar to circles on google+. A person can submit their email address to your self hosted weblog and you can then manage all those people by putting them into groups. Whenever you add a blog entry or image or video or audio clip you can mark that content to be viewable to only certain groups if you don't want it public. <br> <br> Similarly it would be nice if RSS featured some kind of profile feed. Where instead of entering email addresses (like mentioned above) someone could just sumbit their profile URL and the the reader would parse the RSS profile feed from it. It would send basic information like username, first and last name, profile photo, website URLs, description, interests, gender, relationship status, who I want to meet, etc. This information doesn't necessarily get saved to the website it's submitted it, but instead it gets pulled up every time that person appears on that website. <br> <br> The idea is that a social network could be created using personal websites without a central repository. A person submits their profile URL from their personal website to other personal websites. They are then added as a contact that can be grouped and view restricted content coming form that site in their chosen feed reader. <br> <br> </p> </div> <div style="color:#fff;min-height:0"></div> </div> </blockquote></div><br></div> <!-- |**|begin egp html banner|**| --> <br> <br> <!-- |**|end egp html banner|**| --> <div width="1" style="color: white; clear: both;"/>__._,_.___</div> <!-- Start Recommendations --> <!-- End Recommendations --> <!-- |**|begin egp html banner|**| --> <img src="http://geo.yahoo.com/serv?s=97476590/grpId=17061272/grpspId=1706030390/msgId=2014/stime=1392069071" width="1" height="1"> <br> <!-- |**|end egp html banner|**| --> <!-- |**|begin egp html banner|**| --> <br> <div style="font-family: verdana; font-size: 77%; border-top: 1px solid #666; padding: 5px 0;" > Your email settings: Individual Email|Traditional <br> <a href="http://groups.yahoo.com/group/rss-public/join;_ylc=X3oDMTJndm1oNzA5BF9TAzk3NDc2NTkwBGdycElkAzE3MDYxMjcyBGdycHNwSWQDMTcwNjAzMDM5MARzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMzkyMDY5MDcx">Change settings via the Web</a> (Yahoo! ID required) <br> Change settings via email: <a href="mailto:[email protected]?subject=Email Delivery: Digest">Switch delivery to Daily Digest</a> | <a href = "mailto:[email protected]?subject=Change Delivery Format: Fully Featured">Switch to Fully Featured</a> <br> <a href="http://groups.yahoo.com/group/rss-public;_ylc=X3oDMTJlcWUzMXVvBF9TAzk3NDc2NTkwBGdycElkAzE3MDYxMjcyBGdycHNwSWQDMTcwNjAzMDM5MARzZWMDZnRyBHNsawNocGYEc3RpbWUDMTM5MjA2OTA3MQ--"> Visit Your Group </a> | <a href="http://info.yahoo.com/legal/us/yahoo/utos/terms/"> Yahoo! Groups Terms of Use </a> | <a href="mailto:[email protected]?subject=Unsubscribe"> Unsubscribe </a> <br> </div> <br> <!-- |**|end egp html banner|**| --> <div style="color: white; clear: both;"/>__,_._,___</div> </body> </html> --001a11c1223a77713f04f2145694--