martin@rootjazz wrote:Anyway, I can post more than 50 :-\
Not from a queue you can't, which is what I said
As for TJ reporting the errors, if TJ stated what the errors were than the users could sort it out themselves for most errors, if for example it was too many uploads, then that is easily resolved
Do you have any idea on what is involved? I can assure you, when you typically think of something as "simple" or "easy" that it probably isn't. The issue here was tumblr change their error reporting schema, and unkindly didn't inform me...
the problems are that TJ doesn't tell you what the error is or what the error means, for example what does "couldn't pull urlframe" mean
I think that is one of the better error messages. TumJaz couldn't pull an iframe. I knew exactly what it was and got it fixed within the hour of it being reported.
if this was translated into layman terms in an error module or error code help list, then the users could sort it themselves, creating less work for you here.
Basically the logs are for me, not you. They give you a basic idea of what is going on, but are not intended to be "layman" readable. They are to allow me locate specific pieces of code when things go wrong. Thus short, cryptic and direct. Otherwise I need to write a book for each process, explaining what is happening. And you know my thoughts on documentation
====================================================================================================================
I'm trying to say that YOU wouldn't have to spend so much time looking through logs, it was suggestion to try and HELP YOU spend less time on trivial but urgent things and more time on important things, it's a principle of time management, you do code, I'll do management, thank you.
I think you're over complicating the error reporting module "write a book for each process" is complete nonsense, a sentence would do, you're too sensitive to allow people to suggest changes to your baby, but as you have shown you don't know how tumblr works but have written a bot for it, before you reply just remember who the customer is here.
