Trying the same experiment on the iPad. #

i want to sign off this specific problem. here's the experiment that has to work…

1. post this
2. see it immediately show up in the timeline 
3. reload the page
4. still see it in the timeline
5. edit the post (this is me editing the post)
6. publish
7. see the update in the timeline
8. reload the page, still see the update

we're making sure the update appears not only in the browser i'm editing in, but also in the feedland database running behind the scenes.

result of experiment. it worked! omg i can't believe it. thank you thank you. 😉

I think we have all bets covered now. 

When I post this to Daveverse it will show up immediately in the timeline. 

And for good luck we also send a message to FeedLand to check it, so even if it doesn't get an rssCloud ping due to misconfiguration of the server, it will still show up if I reload the page, and on any other system that doesn't happen to be the authors. 

Glad I investigated this now, would hate to have to work on it later, knowing how I had to insert calls into very sensitive parts of the system. Small pieces loosely joined require some time to burn in before inflicting it on innocent users. 😀

Let's make an edit happen.

I think perhaps the Daveverse server is not doing the rssCloud notifications for subscribers, because: 

• when i publish something new to daveverse, feedland doesn't immediately check the feed, as it would if it were getting a rssCloud ping.
• the rssCloud mechanism appears to be working properly for wordpress.com-hosted sites, and for Scripting News and other sites that support rssCloud.
• i find that if i cause the check to happen in WordLand (something it can do because it can talk directly to the feedland server) i get the notification via websocket and the update happens in the timeline.
• note that daveverse.org is hosted on my own server, with help from Scott Hanson.
• since this is being posted on daveverse.org it serves as a test case for me to confirm some of the things i said here. 😉

Good morning Daveverse! 

I learned something new today. Sometimes my keyboard stops working. Or one key stops working. I try turning it on and off. Usually fixes the problem. But today the Return key stopped working. I figured okay this keyboard is burned out, so I got one of my other supposedly burned out keyboards and swapped it in. Return key still doesn't work. Oh.

Then I tried quitting Chrome and relaunching it. And boom it works. 

Keep remembering sometimes it's a software error and sometimes it isn't your software that's misbehaving, probably.