|
Metapost: Current Comments |
Disqus is trying really, really hard to sync the Disqus comments with the Blogger feed that the Current Comments widget gobbles. Google is making this difficult because Google hates you. (Yes, you.) So Current Comments will be buggy until Google decides you're alright after all. Sorry about that.
13 comments:
This is an automatic message from DISQUS.
You can view current comments directly via the new link at the top of the widget. This is an interim fix.
"You may view current comments directly here."
What did I ever do to Google? (Other than call them evil for fucking up Blogger, I mean.)
And now the Current Comments are randomly loading stuff from 2 years ago. Stellar.
And now the Current Comments are randomly loading stuff from 2 years ago. Stellar.
Plus, when I decided to click one of them for a bit of memory lane, I found that many of the comments were shown twice, with timestamps five hours apart. Makes reading the thread a bit tricky. (No idea if it's related.)
> "Google is making this difficult because Google hates you"
Don't worry, by now it's entirely mutual.
It looks like when I was digging around in the Disqus panel to force the sync over and over and over again (Google slams it stopped after about 40 comments), I accidentally told it to import OLD Blogger comments INTO Disqus. (The buttons are on the same page.)
I'm concerned that means that pre-Disqus threads will now have double comments FOREVER. I sincerely hope not.
Ok, so, a few points:
1 Google should remove the "Don't" from their unofficial motto because if they just left it at, "Be evil," it would be honest, and there is no rule (I've checked) that says that evil can't be honest. In fact, I think the most compelling evil often is honest evil.
2 If no appropriate solution can be found then, after November (for I assume National Novel Writing Month to put the entire world on hold since the "National" is anachronistic and it's really been international for a while now) one possible solution would be to give someone/[multiple someones] you trust the access necessary to delete the duplicated comments and have them do the slow painstaking work of removing them by hand.
Even when they are not in simple xxyyzz order there are relatively straight forward ways of locating duplicates, it's just long, tedious, and not the type of work you want to do when you could be writing about Twilight (Did you know there are six different ways Bella as clumsy to the point of disability reinforces patriarchal culture? Other than the fact that the number six was chosen at random, it's true.) Hence the idea of it being someone you trust rather than you.
3 Hopefully a better way can be found.
4 What the fuck Google?
1) That does appear to be a problem. The problem has been solved before (http://pyhacker.com/archive2011/convert-comments-exported-disqus-wxr/), but that was in conjunction with a full site move. I don't know how deeply Disqus integrates with blogs (neither blogging nor using Disqus myself), but the closest equivalent here would be:
a) Download the comment export
b) Filter the comments and write them back as the importable format
c) Create a new Disqus "site" with empty comment history
d) Import the new comments there
e) Re-associate the comments here with the new site.
I don't know if that (especially c and e) is possible with Disqus, and it might break many other things in the process.
The other option is to use the Disqus API to make the changes online, using one of the language bindings. That, however, would carry the downside that you'd have to run (yourself) code given to you by someone else or alternately provide your API keys to someone else, and those keys double as authentication tokens.
2) I'm not worried about duplicate verification, since the "human" approach is good enough -- if two comments in the same thread have the same content (ideally posted by the same user), then they must be duplicates.
Google is making this difficult because Google hates you. (Yes, you.)
I have actually begun to suspect this. Livejournal also hates me.
Can Disqus comments be backed up/restored to some externally-manipulable file, preferably XML-based? It should be simple enough to export comments, find some invariant between duplicates (probably a hash of contents), remove the duplicates, and re-import. Maybe 100 lines of Python, but were I to do it I'd have to learn how to do the XML manipulation in the first place.
That said, it's all contingent on Disqus playing nice with export/import.
I'm concerned that means that pre-Disqus threads will now have double comments FOREVER. I sincerely hope not.
Would it be possible, physically possible I mean, not necessarily within the bounds of what is manageable for you personally, to manually delete the duplicated comments from disqus?
My dearie military service to get labels
is authority since he was absolved of Cabal in sexual congress to the Bali dud onrush
and released from clink Utmost twelvemonth.
This HF RFID Labels is those kinds of measures would never
receive a audience.
Here is my web page: pixocool.com
Post a Comment