This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
1SqueakyChu
Yikes! I run the TIOLI challenges on the wiki, and now we have NO EDIT BUTTON at all. Any idea how long it will take before we can once again edit the wiki?
3timspalding
@conceptdawg will be working on this tomorrow. We had to invalidate all login credentials along with the addition of the Captcha; we forgot the Wiki uses the same information, but is on a different server.
4bnielsen
>3 timspalding: Thanks for working on it. I use the Wiki quite a lot, so I miss it :-)
Clearing out the spammers is more important, so I'll live without the wiki editing for now.
“Three cheers for Captain Spa(u)lding!"
Clearing out the spammers is more important, so I'll live without the wiki editing for now.
“Three cheers for Captain Spa(u)lding!"
5ccatalfo
>4 bnielsen: We're working on this, should have it fixed soon.
6ccatalfo
>4 bnielsen: Wiki edits should now be working.
7SqueakyChu
Thanks you so much, Tim and Chris, for getting right on the spammers, notifying us of problems, and fixing them speedily. You guys are great!
8conceptDawg
Tim and Chris...and Chris. :)
We have two developers...both of whom are Chris. It's confusing.
But on the bright side, Tim can blame Chris for everything.
We have two developers...both of whom are Chris. It's confusing.
But on the bright side, Tim can blame Chris for everything.
9conceptDawg
And another thanks to Chris (@ccatalfo) for filling in more on LT while I've been less than 100% while battling sickness for the last day and a half. He's smarter than I am anyway, so it was probably a win/win.
11SqueakyChu
>8 conceptDawg: ...to both Chrises as well as to Tim, thank you!
P.S. I actually thanked the other Chris (you!) on the other thread! :D
P.S. I actually thanked the other Chris (you!) on the other thread! :D
12conceptDawg
>11 SqueakyChu: Good. I just wanted to make sure he got credit too. Some of the newer folks might not realize that we are two separate people.
For those people: Chris Catalfo (@ccatalfo) usually works on the LibraryThing for Libraries side of things but he dabbles over here at LT.com too (he knows more about Add Books than I do, for instance). Chris Holland (@conceptDawg, me) works on pretty much everything at LT, but while I'm a full-stack developer on the LT.com side I'm mostly just UI/UX on the LTFL side, TinyCat, and BookPsychic. While I take care of most of the native App stuff (LTApp, Litsy, LibraryAnywhere, etc.) we are both full-stack on Litsy. It's crazy up in here.
For those people: Chris Catalfo (@ccatalfo) usually works on the LibraryThing for Libraries side of things but he dabbles over here at LT.com too (he knows more about Add Books than I do, for instance). Chris Holland (@conceptDawg, me) works on pretty much everything at LT, but while I'm a full-stack developer on the LT.com side I'm mostly just UI/UX on the LTFL side, TinyCat, and BookPsychic. While I take care of most of the native App stuff (LTApp, Litsy, LibraryAnywhere, etc.) we are both full-stack on Litsy. It's crazy up in here.
15conceptDawg
>13 gilroy: >14 lilithcat: Yeah. It was a really cool (and nice looking, thank you) kind of mini-site/tool but never really got much traction. Too bad really. Maybe we can repackage it and use it again in some other way.
16ianreads
>15 conceptDawg: Talking about tools that never got much traction, http://www.librarything.com/lttl/ is still limping along. IIRC that was whipped up (by you) in an afternoon? Would love for it to get some love again!
17conceptDawg
HAH! Yes. Even I had forgotten about that that one. We could certainly "do better" now if we had the time. I'll make no promises. I learn my lessons.
18conceptDawg
Interesting. I checked on the Timeline feature and it wasn't working correctly. The libs were originally loaded from a project at MIT and that project has long-since been shut down. Luckily they DID provide downloadable libraries of the last version they released. I've downloaded those and updated the code to support the final version they released.
User beware: There are SOOO many things that aren't working correctly in that code. It was written in the dark ages when LT was but a wee child. It was never an officially supported project anyway.
ETA: I think it was written around 2007, based on the dates on a couple of files. I'm amazed that enough of our internal functions still work that are that old.
User beware: There are SOOO many things that aren't working correctly in that code. It was written in the dark ages when LT was but a wee child. It was never an officially supported project anyway.
ETA: I think it was written around 2007, based on the dates on a couple of files. I'm amazed that enough of our internal functions still work that are that old.

