Thanks for your replies--short of reconvening the standards boards--any suggestions? I tried deleting my wordpress cache.
On Tuesday, July 9, 2013 12:16:26 PM UTC-4, Julien wrote: > > Sorry Bob, you're right. It's more a could than a should :) > My point was that there are many things that can break in the whole > process which would prevent the deletion > from being reflected. > > Thanks, > > On Tue, Jul 9, 2013 at 5:49 PM, Bob Wyman <[email protected] <javascript:>> > wrote: > > > > > > > > On Tue, Jul 9, 2013 at 11:26 AM, Julien Genestoux > > <[email protected] <javascript:>> wrote: > >> > >> I'm afraid this is going to be something that needs to be addressed > >> with Flipboard and Feedly. > >> > >> In theory, Atom has "thumbstones" for deleted content, and in theory, > >> these should be propagated by > >> the hubs, and in theory the publishers should delete the corresponding > >> entries. > > > > It is important to recognize that the receiver of an Atom Tombstone is > under > > no obligation to do anything. One's publication of data on the Internet > must > > never be seen as obligating another to act in the absence of some prior > > agreement to do so. Thus, it is not correct to say that a receiver of a > > tombstone "should delete the corresponding entries." RFC 6721 wisely > and > > explicitly states: > >> > >> Publishers of feeds containing at:deleted-entry elements should note > that > >> the at:deleted-entry element is advisory in nature only, and it may be > >> ignored by Atom Processors. The presence of an at:deleted-entry element > does > >> not guarantee that the atom:entry to which it is referring will no > longer be > >> available. For example, if an entry was published to a feed document > that > >> was published and processed yesterday by an aggregator application, and > then > >> is subsequently deleted today with a corresponding at:deleted-entry > element > >> added to the feed as a signal that the entry was deleted, there is no > >> guarantee that the aggregator application will pay any attention to the > >> at:deleted-entry element during subsequent processing operations. > > > > > >> > >> Now, as you've guessed, somewhere in that theory, something broke and > >> the only way to get the content > >> deleted is to reach out to both Feedly and Flipboard. > >> > >> Thanks, > >> > >> > >> > >> > >> On Tue, Jul 9, 2013 at 3:50 PM, Robert Kennedy > >> <[email protected]<javascript:>> > > >> wrote: > >> > We are using pubsubhubbub on wordpress. We deleted some text blogs, > but > >> > they > >> > are still showing up in our feeds to Flipboard and Feedly. Any > >> > suggestions > >> > on how to fix? > >> > > >> > -- > >> > > >> > --- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "Pubsubhubbub" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send > >> > an > >> > email to [email protected] <javascript:>. > >> > For more options, visit https://groups.google.com/groups/opt_out. > >> > > >> > > >> > >> -- > >> > >> --- > >> You received this message because you are subscribed to the Google > Groups > >> "Pubsubhubbub" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected] <javascript:>. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "Pubsubhubbub" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- --- You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
