capture 1 of IBM eyes story:

note that the story was 20d 6h ago

Now capture 2 of the story at 20d 8h ...

prior to the first screen clip I had already 'discarded' the story via "X" .. but it just won't stay dead.... I have many other stories in the same boat...

So what is the meaning of the words 'from the content log"  (I've currently got the Ticker setting at show most as I am in a 'training session, but I would think that having discarded, then read and discarded, would prohibit it from showing up a third time regardless of setting on the Ticker?)

Popped up yet again at 20d 10h.....

Popped up yet again showing 20d 10h still

and yet again just now so they are about 20 minutes apart... this one shows 20d 11h

ok yet again just one minute later!

finally... nothing more on Ticker. ("waiting for content").. will let it run to see if story comes back...

ITS BACK!!! along with all its other brethern....seem to be all things from the "Content Log" -- so the problem becomes one of where do i kill this ?  Off to look for it in sources... or ???

It's stalking ya

You need a restraining order

Hmm... content log shows up twice in my sources... so this might not just be any old stalking... it could be a conspiracy stalk...

Off to see if I can kill one entry in the apml file...

Now i don't think I want to kill one off... they are different:

<Source key="http://newton.typepad.com/content/atom.xml" value="0.00" name="Content Log" type="" updated="2007-05-01T17:51:27Z" from="Particls">

Well they both end up resolving to the same space... so i will try deleting the newton.typepad .com entry...

I cut off a head ... and two appear:

one shows 20d 5h ago; the other 20d 12h ago....

they crossed the ticker within about a minute of each other...AFTER I cut out three entries in total from my APML file leaving only one reference i could find to "content Log" in the apml file

( I note that although i had set the desirability to 'Strongly Dislike' for both entries in the rate your sources box before the delete, when I first started up the one entry remaining there had been reset to "indifferent"

A recheck now shows two entries both set to indifferent... back to check apml file again... I must have saved it... I must have saved it... 

OK I'm sure I have it down to one instance in my apml file... and only one instance showing on the ticker as far as I can see... but I read it, I x it, I mark the entire source as having been read....

AND I STILL CAN'T KILL THE Beast....

off to listen to my Eagles Hotel California track.... 

(ummmmmm Hotel california)

And she said 'We are all just prisoners here, of our own device'
And in the master's chambers,
They gathered for the feast
They stab it with their steely knives,
But they just can't kill the beast

I so wanna listen to it right now.... but I don't have it

This is the url of the page.... http://newton.typepad.com/content/2007/04/ibms_many_eyes.html

this is the feed I subscribed to.... http://feeds.feedburner.com/ContentLog

this is the rdf section of the page:

   <  <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
             xmlns:dc="http://purl.org/dc/elements/1.1/">
    <rdf:Description
        rdf:about="http://newton.typepad.com/content/2007/04/ibms_many_eyes.html"
        trackback:ping="http://www.typepad.com/t/trackback/18018466"
        dc:title="IBM's Many Eyes"
        dc:identifier="http://newton.typepad.com/content/2007/04/ibms_many_eyes.html"
        dc:description="I found this reference to IBM's Many Eyes. Many Eyes some of the concepts of Wisdom of Crowds and Web 2.0 visualization, this site encourages anyone to create graphs, data visualizations and tag clouds by uploading their data sets. You..."
        dc:creator="John Newton"
        dc:date="2007-04-26T13:43:25+01:00" />
    </rdf:RDF> 

And  at 21d 17h the damn thing is still coming up.... He hasn't posted anything new since May 4th so perhaps I'll just have to give up and rip the entry out of my APML file?

I have another site giving the same sort of result....so I would really like a better solution than that!

I'm sorry, I just had to laugh at this Bric

At least someone is listening

Sorry, what?

(hehehehe couldn't help myself)

To tell you how sad my existence has been for the last week...

The chuckle you just gave me was the biggest laugh I've had ...

hehehe We're even then!

With Release 0.9.1930.0 stories from this source still repeat... and repeat... and repeat...

I've signed up to it with RSS readers (one standalone; the other Google) and both of these only pick up the stories once... I've run the RSS through W3's feed validator and there are some problems with it... but I can't see any that would cause the problem I've been seeing...

So for now I'll forget that I got several very good items from this feed and use the nice new feature of  version 0.9.1930.0 to  "remove this source" from my attention data files....

Bri can u tell me what the feed is again?

http://feeds.feedburner.com/ContentLog

I've sent it in the past to support.... and have got standard form reply back but nothing else... up to their eyes in the latest release i would guess   .... lots of great stuff in it!

Thanks Bri - Yeah been very hectic last few weeks

Even "Remove this Source" doesn't kill the beast.

There is something very strange going on there Bri - what is the source name as it appears on the ticker?

Source name in Ticker = "content Log" -

Please note : my entry on 16 May @ 05:39 (above) shows I actually ended up with two entrys in the APML file -- both turned out to generate the Same content - but with very different time stamps (about 7 hours apart - see the screen capture at 16 May 06:09 where I captured two entrys as they crossed the ticker about a minute apart).

Then I killed duplicate entry in my apml file thinking this might be what caused the problem -- but it had no apparent effect on the remaining entry still coming up.

A recheck just this afternoon shows both entries are back in my APML file... so I'll try killing first one (again) then If I still have the problem I'll manually kill the other...Perhaps some synchronization goes on between the OPML, APML and cache that I have not been clearing properly in trying to manually edit the APML file?

This is the "Owner" record I'm removing before retesting:

<Source key="http://newton.typepad.com/content/atom.xml" value="0.00" name="Content Log" type="applcation/rss+xml" updated="2007-05-17T01:19:06Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334">
            <Author key="John Newton" value="0.00" updated="2007-05-17T01:19:06Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
            <Author key="" value="0.00" updated="2007-05-17T01:19:10Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
          </Source>

<note it is formatted correctly in apml file

This is the other entry that I am leaving in that turns out to point to a copy of the same content:

<Source key="http://feeds.feedburner.com/ContentLog" value="0.00" name="Content Log" type="applcation/rss+xml" updated="2007-05-15T07:49:40Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334">
            <Author key="John Newton" value="0.00" updated="2007-05-15T07:49:40Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
            <Author key="" value="0.00" updated="2007-05-15T07:49:42Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
          </Source>

ON rerunning Particls for several minutes (enough to bring the item into view) it appears that the APML entry I had deleted has been recreated:

<Source key="http://newton.typepad.com/content/atom.xml" value="0.00" name="Content Log" type="applcation/rss+xml" updated="2007-05-23T06:15:03Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334">
            <Author key="John Newton" value="0.00" updated="2007-05-23T06:15:03Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
            <Author key="" value="0.00" updated="2007-05-23T06:15:05Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334" />
          </Source>

this is compared to time stamp on the enty shown above (the one I deleted from the APML file) of  updated="2007-05-17T01:19:10Z"

So I have deleted both references that had the name="Content Log" --

He's Back (see IBM"s Many eyes at centre of Ticker !!!) 

Two new entries have been created for me in my APML file just by starting up Particls and watching the Ticker go by:

<Source key="http://newton.typepad.com/content/atom.xml" value="0.00" name="Content Log" type="applcation/rss+xml" updated="2007-05-23T06:28:21Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334">

and the second one

<Source key="http://feeds.feedburner.com/ContentLog" value="0.00" name="Content Log" type="applcation/rss+xml" updated="2007-05-23T06:29:04Z" from="Particls" particls-device="30280F3C2C0533B79565267C7B3B9FB31394E334">

Oh dear.... I'm sure this isn't funny for you guys, Bric and Particls crew, but I'm finding it hilarious that Bric, you are being stalked by a news item called 'IBM's Many Eyes' no less

hehehe 

Note that they show as having been created a half minute apart...

@ dekrazzee1: This is a sign that I might as well sign up for iStalkr I guess...

This is what makes Beta so much fun (to be sure not so much for the Particls guys) but If I can find the tough to believe stuff I will... seems to be a special gene I was born with....

Anyways Chris... I have about exhausted things that I can think of.... off to fortify my mind with a shot of Scotch... I'll try again after than to see if it brings any great ideas out...

hahahaha Bric - yeah, might as well join iStalkr.... that way you get to do the stalking at least....

Bri - removing it from the APML file will not remove the source - only its ranking

To remove the source itself you need to remove it from the OPML File

And I dont think your pain is amusing - unlike Dek she is just mean hehe

Re:

But this is what I thought I did by two different methods:

1) using the "remove this source" by right click from the item on the ticker

2) using the delete source  from within the "manage my feeds" function

At any rate manually deleting the record from the OPML file and the two records from the APML file seems to have had the desired effect....

So now off to add the offending feed again to see if it causes the same effect... 

Current status:

1. manually deleted  opml and apml entires.... this of course "killed the beast" no more stalking  by IBM many eyese story
2. went back to the blog page and  used the "track this page with particls " button -- selected RSS1.0 feed.... success the stories displayed and did  not come back to ticker when  killed with "x"  on feed
3. used the  "delete this source" (right mouse click) from manage feeds box to get rid of RSS 1.0 feed successfully
4. went back to blog page... selected Atom feed... success
5. did the same procedure to bring up RSS 2.0 feed by itself.... success

Current thoughts (next steps to try and replicate the problem) I will:

1.  delete rss 2.0 feed
2. go back to blog and select all three feeds (in case this is what I inadvertantly did at the very beginning of this escapade)
3. If no results there I will look for the "second source" that had appeared in my APML that pointed to the same stories and add it again....

I think that the problem should not happen agan with the new build Bri - because in the old build the browser button allowed duplicates to creep in.

But we have patched that bug in the latest version

The Saga Continues..... fresh scents ... go onto victory tracking hounds....

So step 2 above (select all three feeds and see if that results in symptom) produced negative results...

Step 3 though.... oh sweet success????  I think  perhaps I'm being stalked by many eyes Again!

It turns out that the " subscribe"  button on the blog site gives a URL: http://feeds.feedburner.com/ContentLog that is different from what the "track this page with particls" returns (<Source key="http://newton.typepad.com/content/atom.xml" value="0.00" name="Content Log" type="" updated="2007-05-01T17:51:27Z" from="Particls">)

At least I got a feed across the ticker.... so now to shut Particls down and restart it ... and see if the offending story comes up again!

ITS OFFICIAL I'M BEING STALKED BY MANY EYES (again) !!!!

YES YES YES ... its something to do with the feedburner feed...... don't know why yet (if its by itself or in combination with the atom feed that is causing the problem.... But this is it...

 Unfortunately my day job interrups and I most go pretend to earn a living...  so I probably won't be able to run the necessary steps to confirm if it is the duplication of items of if the problem occurs just with the feedburner solo until the wee hours of the morning or tomorrow....    but I got it... he says mumbling like a madman to himself....

ok a couple minutes more on it:

1. "remove this source" (right click on  feed) doesn't
2. delete feed (using the manage feeds box) seems to but

• the ticker still shows the feed in question .....  so something in the feedburner application messes up the ticker feed so it doesn't respond correctly to attempts to control feed sources
  
• I'll need to check to see if any other items I have like this also resolve to feedburner issues (rather than sites updating their content ever so slightly so the feed looks new)

Chris - I'm not mean! I recognise good humour

And if I can like be stalked by Many Eyes think how much I must enjoy being poked fun of for it!  You tell him dek

ps . of the 11 stories I got from this feed (all of which exhibited this problem)I did pick "Many Eyes" to focus on.... I thought it was quite ironic.... but Dekrazee1 was the only one interested enough to post ... or perhaps the only one with a truly bent sense of humour like mine - so it jumped out at her too!

Chris: re

This Thing I Know to be True:

subscribing to http://feeds.feedburner.com/ContentLog  may result in stories that won't be killed... they keep coming back again, and again and again.... like the  beast in Hotel California you can stab it with your steely knives but you just can't kill the beast if you have another source that delivers the same content and has the same "name" in your apml output.

and these things I don't   (yet !)

• if the remove source works for this feed by itself ; or
  
•  if this removal problem is only when the feed is duplicated in some manner
• if this problem goes beyond this particular source or is a potential problem for all feedburner sources

More work to come.... but a cautionary note:

for now would appear to be if you have a choice between feeds (RSS1; RSS2; Atom; Feedburner) for use by Particls only choose the Feedburner as a last resort.... at least this one feed doesn't play nicely with Particls! (and while built in checks by Particls are meant to catch if you try to add the same feed using the "track with" button, inserting the url of a feedburner site directly through "subscription helper" might result in a duplicate that causes grief in causing the never ending story and is impossible to kill directly). 

See.... dek has taste

Stalked by Many Eyes.....

Ok... so I've got another problem feed to work with....

I don't seem to see the same artifacts if I accidently get both rss1 and rss2 duplicate feeds.... only when one or more of the 'duplicates' is a feedburner source.

@Bri - Thanks for all the feedback! I loaded both those feeds up myself, and managed to reproduce the problem. Hopefully the next update should make them go away.

Glad I could help !

Yes thanks for the excellent diagnosis Bri - it's been a very hard problem to narrow down - hopefully we have finally nailed it!