I so totally have. And while I was at it, I've started to add new features.
Namely, in the XML outputter, when posting an tag, the XML outputter would not spit out who actually posted the topic, a crying shame when trying to archive communities such as ours (this despite that the HTML outputter would).
[Pause.]
Well now it does. Oh, and now it spits out links to the original article on LJ itself. As such, I can now directly link back to the actual RP conversations.
Oh, and the numbering system for entries, you know, how random it seems? (Like this entry, being "76484.html"?) Apparently LJ decided that it would be decidedly bad if they just numbered things {1, 2, 3, 4, ...} because people would wonder where missing entries were. And so, in their infinite wisdom, they obfuscated it.
Totally so. It really just took rewriting the download function so that I could actually log what the server was sending me in response. Once I realised what I actually had, then everything just sort of fell together.
Comments 8
Reply
Namely, in the XML outputter, when posting an tag, the XML outputter would not spit out who actually posted the topic, a crying shame when trying to archive communities such as ours (this despite that the HTML outputter would).
[Pause.]
Well now it does. Oh, and now it spits out links to the original article on LJ itself. As such, I can now directly link back to the actual RP conversations.
Oh, and the numbering system for entries, you know, how random it seems? (Like this entry, being "76484.html"?) Apparently LJ decided that it would be decidedly bad if they just numbered things {1, 2, 3, 4, ...} because people would wonder where missing entries were. And so, in their infinite wisdom, they obfuscated it.
PublicPostID = (PrivatePostID * 256) + Random(Between 0 and 255 inclusive)
Where PrivatePostID = 1, 2, 3, 4, ... And Random can be pulled from the server through the export phase.
Reply
Reply
Yeah, I'm all good.
Reply
(The comment has been removed)
Reply
Reply
Reply
Reply
Leave a comment