simpleupdateprotocol - Project Hosting on Google Code

Earlier this year Oct 08, 2009 faq (Frequently asked questions about SUP) Wiki page commented on by michael.chelen - Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Oct 08, 2009 faq (Frequently asked questions about SUP) Wiki page commented on by michael.chelen - Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Laconica has Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Laconica has Oct 08, 2009 faq (Frequently asked questions about SUP) Wiki page commented on by michael.chelen - Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Laconica has Laconica been renamed Status.net and the PHP code is now located at: * http://github.com/zh/statusnet/blob/master/actions/sup.php * http://github.com/zh/statusnet/blob/master/actions/userrss.php Laconica has Jul 31, 2009 testpage (One-sentence summary of this page.) Wiki page commented on by santoshsingh1984 - mmmmm mmmmm Jul 29, 2009 testpage (One-sentence summary of this page.) Wiki page commented on by tony.hartmann - opopop opopop Jul 12, 2009 r33 (Fixed the typo caught in the review of r32 by adewale at htt...) committed by dclinton - Fixed the typo caught in the review of r32 by adewale at http://code.google.com/p/simpleupdateprotocol/source/detail?r=32 Fixed the typo caught in the review of r32 by adewale at http://code.google.com/p/simpleupdateprotocol/source/detail?r=32 Jul 11, 2009 r32 (Updated the Security Considerations section per Adewale Oshi...) committed by dclinton - Updated the Security Considerations section per Adewale Oshineye's suggestions at http://friendfeed.com/simple-update-protocol/c3372901/it-is-possible-given-sufficient-resources-or Updated the Security Considerations section per Adewale Oshineye's suggestions at http://friendfeed.com/simple-update-protocol/c3372901/it-is-possible-given-sufficient-resources-or May 12, 2009 issue 1 (mysite.com should be example.com in Python source) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com May 01, 2009 issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com May 01, 2009 issue 2 (Not clear how to implement SUP with RSS 1.0) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com May 01, 2009 issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyumumut@hotmail.com May 01, 2009 issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com May 01, 2009 issue 2 (Not clear how to implement SUP with RSS 1.0) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com May 01, 2009 issue 1 (mysite.com should be example.com in Python source) commented on by medyumu...@hotmail.com - medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com medyum, sihir, cin, şeytan, MEDYUMU, şifa, hoca, muska büyü, sara nöbeti, medyum ankara medyum, medyum, büyü, muska, nazar, cin, cinler, cinler a http://www.medyumumut.com Jan 24, 2009 r31 (Revised as follows: * The term 'Updates Document' in place...) committed by dclinton - Revised as follows: * The term 'Updates Document' in place of 'SUP Feed' * The term 'Resource Token' in place of 'SUP ID' * The term 'Update Token' in place of 'Update ID' * The HTTP 'Link' header is used instead of the 'X-SUP-ID' * The rel value 'updates' is used instead of 'http://api.friendfeed.com/2008/03#sup' * Updated introductory text Revised as follows: * The term 'Updates Document' in place of 'SUP Feed' * The term 'Resource Token' in place of 'SUP ID' * The term 'Update Token' in place of 'Update ID' * The HTTP 'Link' header is used instead of the 'X-SUP-ID' * The rel value 'updates' is used instead of 'http://api.friendfeed.com/2008/03#sup' * Updated introductory text Jan 10, 2009 r30 (Update the IPR mode from full3978 to trust200811.) committed by dclinton - Update the IPR mode from full3978 to trust200811. Update the IPR mode from full3978 to trust200811. Jan 10, 2009 r29 (Updgrade the idnits tool from http://tools.ietf.org/tools/id...) committed by dclinton - Updgrade the idnits tool from http://tools.ietf.org/tools/idnits/ to enable the trust200811 IPR boilerplate. Updgrade the idnits tool from http://tools.ietf.org/tools/idnits/ to enable the trust200811 IPR boilerplate. Jan 10, 2009 r28 (Set the SVN mime-type of all .xslt documents to text/xml) committed by dclinton - Set the SVN mime-type of all .xslt documents to text/xml Set the SVN mime-type of all .xslt documents to text/xml Jan 10, 2009 r27 (Upgrade the xml2rfc tool to the bleeding-edge development ve...) committed by dclinton - Upgrade the xml2rfc tool to the bleeding-edge development version from http://xml.resource.org/experimental.html to enable the "trust200811" ipr mode Upgrade the xml2rfc tool to the bleeding-edge development version from http://xml.resource.org/experimental.html to enable the "trust200811" ipr mode Jan 10, 2009 r26 (Moved rfc processing instructions inside the <rfc/> element) committed by dclinton - Moved rfc processing instructions inside the <rfc/> element Moved rfc processing instructions inside the <rfc/> element Jan 10, 2009 r25 (Use the rfc processing macros rather than the writing out th...) committed by dclinton - Use the rfc processing macros rather than the writing out the xml system entity directly when referencing RFC bibxml files. Use the rfc processing macros rather than the writing out the xml system entity directly when referencing RFC bibxml files. Jan 10, 2009 r24 (Use the external bibxml description of the Nottingham HTTP L...) committed by dclinton - Use the external bibxml description of the Nottingham HTTP Link header I-D, rather than hardcode the bibliographical reference inline. Use the external bibxml description of the Nottingham HTTP Link header I-D, rather than hardcode the bibliographical reference inline. Jan 06, 2009 r23 (Added a note about creating a mailing list for spec review.) committed by dclinton - Added a note about creating a mailing list for spec review. Added a note about creating a mailing list for spec review. Jan 06, 2009 r22 (Fixed document name to -current. Will knowingly fail the id...) committed by dclinton - Fixed document name to -current. Will knowingly fail the idnits tests until it is updated. Fixed document name to -current. Will knowingly fail the idnits tests until it is updated. Jan 06, 2009 r21 (Fixed typo (missing word).) committed by dclinton - Fixed typo (missing word). Fixed typo (missing word). Jan 06, 2009 r20 (Set appropriate mime types via svn properties.) committed by dclinton - Set appropriate mime types via svn properties. Set appropriate mime types via svn properties. Jan 06, 2009 r19 (Replaced -00 versions with a -current version prior to the f...) committed by dclinton - Replaced -00 versions with a -current version prior to the first submission to tools.ietf Replaced -00 versions with a -current version prior to the first submission to tools.ietf Jan 06, 2009 r18 (Fixed production rules of update_id and sup_id to allow '-' ...) committed by dclinton - Fixed production rules of update_id and sup_id to allow '-' instead of '_' Fixed production rules of update_id and sup_id to allow '-' instead of '_' Jan 06, 2009 r17 (The updates field is required, not optional.) committed by dclinton - The updates field is required, not optional. The updates field is required, not optional. Jan 06, 2009 r16 (Rebuild .txt and .html files from trunk.) committed by dclinton - Rebuild .txt and .html files from trunk. Rebuild .txt and .html files from trunk. Jan 06, 2009 r15 (Fixed typo swapping href for type) committed by dclinton - Fixed typo swapping href for type Fixed typo swapping href for type Jan 06, 2009 r14 (Set appropriate mime types via svn properties.) committed by dclinton - Set appropriate mime types via svn properties. Set appropriate mime types via svn properties. Jan 06, 2009 r13 (Initial commit of a IETF I-D for the Simple Update Protocol) committed by dclinton - Initial commit of a IETF I-D for the Simple Update Protocol Initial commit of a IETF I-D for the Simple Update Protocol Older Dec 17, 2008 r12 (update) committed by paul.buchheit - update update Dec 16, 2008 faq (Frequently asked questions about SUP) Wiki page edited by paul.buchheit Dec 16, 2008 faq (Frequently asked questions about SUP) Wiki page edited by paul.buchheit Dec 16, 2008 faq (Frequently asked questions about SUP) Wiki page edited by paul.buchheit Dec 16, 2008 faq (Frequently asked questions about SUP) Wiki page edited by paul.buchheit Dec 16, 2008 r7 (add sup validator) committed by paul.buchheit - add sup validator add sup validator Dec 16, 2008 faq (One-sentence summary of this page.) Wiki page added by paul.buchheit Dec 16, 2008 testpage (One-sentence summary of this page.) Wiki page added by paul.buchheit Dec 06, 2008 issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) commented on by cadenhead - Oops -- power grab! Make that the former chairman of the board. Oops -- power grab! Make that the former chairman of the board. Dec 06, 2008 issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) reported by cadenhead - What steps will reproduce the problem? 1. Create an RSS feed that has a LINK tag identifying a SUP provider, like http://workbench.cadenhead.org/files/rss-sup-example.xml. 2. Try to validate this feed in the Feed Validator: http://feedvalidator.org/ What is the expected output? What do you see instead? It fails with a "channel contains more than one link" error, since neither RSS format permits multiple link elements. A solution that would work for both Atom and RSS is to identify a SUP provider with a namespace element, like this: <rss xmlns:sup="http://friendfeed.com/api/sup/"> <channel> <sup:provider href="http://friendfeed.com/api/sup.json#53924729" type="application/json" /> I'm the chairman of the RSS Advisory Board. To discuss this issue, you can contact us at rssboard.org or on the mailing list RSS-Public at http://groups.yahoo.com/group/rss-public What steps will reproduce the problem? 1. Create an RSS feed that has a LINK tag identifying a SUP provider, like http://workbench.cadenhead.org/files/rss-sup-example.xml. 2. Try to validate this feed in the Feed Validator: http://feedvalidator.org/ What is the expected output? What do you see instead? It fails with a "channel contains more than one link" error, since neither RSS format permits multiple link elements. A solution that would work for both Atom and RSS is to identify a SUP provider with a namespace element, like this: <rss xmlns:sup="http://friendfeed.com/api/sup/"> <channel> <sup:provider href="http://friendfeed.com/api/sup.json#53924729" type="application/json" /> I'm the chairman of the RSS Advisory Board. To discuss this issue, you can contact us at rssboard.org or on the mailing list RSS-Public at http://groups.yahoo.com/group/rss-public Nov 29, 2008 r4 (switch to simplejson to be consistent with the validator) committed by paul.buchheit - switch to simplejson to be consistent with the validator switch to simplejson to be consistent with the validator Oct 21, 2008 issue 2 (Not clear how to implement SUP with RSS 1.0) reported by evan.prodromou - It might be nice to have a namespace for RSS 1.0, too. We use RSS 1.0 as the primary RSS feed for Identi.ca. We have Atom and RSS 2.0 feeds, too, but it'd be nice to have a way to add it for 1.0, too (and have that working inside FF). It might be nice to have a namespace for RSS 1.0, too. We use RSS 1.0 as the primary RSS feed for Identi.ca. We have Atom and RSS 2.0 feeds, too, but it'd be nice to have a way to add it for 1.0, too (and have that working inside FF). Aug 27, 2008 issue 1 (mysite.com should be example.com in Python source) commented on by philipp.lenssen - Or perhaps "mysite.example.com", I dunno, I guess mysite gets the point across! Or perhaps "mysite.example.com", I dunno, I guess mysite gets the point across! Aug 27, 2008 issue 1 (mysite.com should be example.com in Python source) reported by philipp.lenssen - really not important, though it got me confused for a second as I figured mysite.com is some kind of service connected to this really not important, though it got me confused for a second as I figured mysite.com is some kind of service connected to this Aug 27, 2008 r3 (sup intro) committed by paul.buchheit - sup intro sup intro Aug 27, 2008 r2 (sup intro) committed by paul.buchheit - sup intro sup intro Aug 27, 2008 Project simpleupdateprotocol created by btaylor - Simple Update Protocol (SUP) - a feed update protocol Simple Update Protocol (SUP) - a feed update protocol

issue 3 (SUP's link tag is invalid RSS 1.0 and RSS 2.0) reported by cadenhead - What steps will reproduce the problem? 1. Create an RSS feed that has a LINK tag identifying a SUP provider, like http://workbench.cadenhead.org/files/rss-sup-example.xml. 2. Try to validate this feed in the Feed Validator: http://feedvalidator.org/ What is the expected output? What do you see instead? It fails with a "channel contains more than one link" error, since neither RSS format permits multiple link elements. A solution that would work for both Atom and RSS is to identify a SUP provider with a namespace element, like this: <rss xmlns:sup="http://friendfeed.com/api/sup/"> <channel> <sup:provider href="http://friendfeed.com/api/sup.json#53924729" type="application/json" /> I'm the chairman of the RSS Advisory Board. To discuss this issue, you can contact us at rssboard.org or on the mailing list RSS-Public at http://groups.yahoo.com/group/rss-public

What steps will reproduce the problem? 1. Create an RSS feed that has a LINK tag identifying a SUP provider, like http://workbench.cadenhead.org/files/rss-sup-example.xml. 2. Try to validate this feed in the Feed Validator: http://feedvalidator.org/ What is the expected output? What do you see instead? It fails with a "channel contains more than one link" error, since neither RSS format permits multiple link elements. A solution that would work for both Atom and RSS is to identify a SUP provider with a namespace element, like this: <rss xmlns:sup="http://friendfeed.com/api/sup/"> <channel> <sup:provider href="http://friendfeed.com/api/sup.json#53924729" type="application/json" /> I'm the chairman of the RSS Advisory Board. To discuss this issue, you can contact us at rssboard.org or on the mailing list RSS-Public at http://groups.yahoo.com/group/rss-public

Earlier this year

Older