There's a problem on one of my servers that appears to have started sometime yesterday. Haven't found where the problem is exactly yet.
How it manifests -- you post something to Radio2, but it doesn't appear on Twitter immediately.
Update: I've found a problem, but it appears to only relate to my linkblog feed. If you've seen a similar problem in the last couple of days please post a comment here. I saw a comment in Anton's feed that made me think the problem wasn't just with my feed.
The problem was that it was pinging the wrong URL, not the one that I had set up to connect to Twitter. The mystery is why it started behaving this way now? Regardless I "solved" the problem by adding a callback to my account on Shreveport that pings the other URL when I post, and now we're back to immediate synching. If you have a problem like this with your feed please click the Green Button.
The problem is on my r2 instance on your server. I haven't set it up on my server yet... Here's the static archive: http://static.reallysimple.org/users/pensato/linkblog.html
It exposes an email address...
Dave: Sorry I hadn't mentioned it earlier. I've noticed it do this in the past, intermittently. I'm positive that between midnight and when I posted the first comment here, it was simply not going to Twitter at all. Now it is again, so I have re-posted a few that I thought I wanted to go out there.
Do you need more detail? I'm not sure how much more I actually have, because I wasn't paying close attention.
Not sure if this is when you watch the logs, but I did just post something, and it went immediately to Twitter--as it usually does, no lag.
I've noticed an issue with my Radio2 posting to Twitter for a couple of weeks, but realized I was misinterpreting the character count -- I think the count does not include the shortened url -- and so began to write shorter posts. But I think I've also had today's problem, i.e. short posts that don't make it to Twitter. I just haven't looked back over my archive to see if there's a pattern.
I will look over my archives later today and report back.
9/27/12; 11:25:25 AM by AZ added a title to test the new title feature on past comments.
Just let me know if it starts happening again, as soon as it starts happening. Via email. :-)
It would help if you could try to post something when I can watch the logs.
That was the behavior I was seeing. The problem was the realtime notification wasn't working, but it was picking up the update at fifteen minute intervals, which is how often it polls the feeds (as a backup in case realtime stops working).
I know I always say this but maybe some of you haven't heard it -- it's important to report problems when they happen. Rex, before you start working around it, let me know what's going on. You might think it's polite not to do so, but actually it works against the process. Sooner or later the problem is going to have to be addressed. If I hear about it when it happens, I'm more likely to figure out the cause.
Adam, I think the problem is on my cloud server, so it would make sense that you're not seeing it because you're running your own cloud server, right?
I've noticed the problem -- and just tried it -- still happens. At first, I thought it had to do with length of comment, but that's not a factor. My work around has been to copy and paste into Twitter -- which is lame of me, yes...but I wanted to at least have an archive link associated with my link blog.