zeeg

It appears there don’t seem to be efficient indices on the table. Definitely a slip up on our part.

Here’s a quick fix:

create index disqus_dupecheck on wp_commentmeta (meta_key, meta_value(11));

We will be moving away from the comment meta I guess since it’s inefficient for querying against values in WordPress.

What’s the problem? May also want to cross-post this to our official forums for a more timely reply ??

The id generation is fixed now in 0.99.8.3 — In the next release I’ll tweak the id to not use a decimal.

This is simply an error due to you using PHP4.

While considering this, I’m also wondering if I could set the post ID to 0 in the comments table, and have a secondary table which overlaps with this so that I can point event->comment.

This should be fixed in 0.98h/0.99.

So no problems then?

Sounds like you didn’t read the requirements.

PHP5 and MySQL5 are both required.

Fixed int he latest version.

Size shouldn’t matter, can you throw me a link to an example?

Are you specifying them as a full URL?

0.95c fixes this (but I’d go with 0.96)

lifestream_event (it might be _events) is the main table, but its a bit more complicated than to simply remove an event.

Can I ask that you cross-post this over to our official support forums, so that it can receive more visibility.

Off hand, I can’t see any reason why it would be duplicating posts for any plugin other than stumbleupon (I believe stumbleupon messed up their feeds).

If you have SSH access on your host, you could try doing php -r "echo file_get_contents('https://twitter.com/statuses/user_timeline/captainnapalm.rss?page=1&count=20');"

Turns out it was just a typo in the code for the lifestream_update() function call.