I'll answer you the same way somebody answered me. Nope. In order to fix the quoting you'll have to become a level 5 HTML programmer and fix every individual quote yourself.

I don't think there's a such thing as a "level 5 HTML programmer" I just thought it sounded fun.

*boogies*
Ah ah ah ah level five, level five, level fiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiive...
>> ^rottenseed:

I'll answer you the same way somebody answered me. Nope. In order to fix the quoting you'll have to become a level 5 HTML programmer and fix every individual quote yourself.
I don't think there's a such thing as a "level 5 HTML programmer" I just thought it sounded fun.

You would have to make a regular expression that captures the ugly code and converts it to pretty code instead. Otherwise you would have to make a pretty deep change in the way the comments are saved, such that the links are generated on the fly and saved differently, so when you quote you insert something else than the "raw" html code, but instead something like [quote http://talks.videosift.com/talk/Can-the-quote-option-be-fixed?loadcomm=1#comment-1258926] or [quote=1258926] then it would generate it when posted.

Essentially, it's a bit of a hassle.

Comment hidden because you are ignoring dag. (show it anyway)

It's not an easy fix - or we would have done it. There are other options, like turning quoting off or making it much simpler - that we could think about.

The vast majority of quoting issues appear to be relating to the at sign for copying in members... couldn't you at least strip that in the quoting process (didn't sifty used to do this?) or else quote escape it (ampersand hash 64 semicolon - @ - @) so that sifty doesn't try to re-process the already processed link?>> ^dag:

It's not an easy fix - or we would have done it. There are other options, like turning quoting off or making it much simpler - that we could think about.

Sometimes quoting works, sometimes it doesn't...sort of like me.
Who am I to make your job harder?
Keep up the good work, soldier.
>> ^dag:

It's not an easy fix - or we would have done it. There are other options, like turning quoting off or making it much simpler - that we could think about.

I pissed @lucky760 off quite a bit when I made this comment. I was under the impression, as many others probably are, that quoting was still broken because nobody gave a shit to fix it.

After I apologized; and credit to lucky for accepting it and switching back to friendly mode so quickly; we began discussing the problem(s) a bit. He made it clear that while he had heard lots of whining (my words, not his), he hadn't seen anything in the way of examples. I was able to provide him with some (one of them actually popped up right there in our discussion when I quoted him) and I think 4 or 5 quoting bugs have been fixed since I made that original comment.

I reported another one just a day or two ago that seems way more convoluted than the others. It might not actually be worth fixing because I bet it doesn't even come up more than 2-3x a year.

So now I stand here like Donald Trump telling my story about being a huge asshole and getting something done because of it.

But kudos to lucky for his recent bug-squashing kung fu.

The short, best answer to many of the issues in VideoSift is: we need a new Sift Operating System (or SOS for short).

The current system on which VideoSift exists is extremely huge and complex and there are just so many complications with the way many things were added on that make some things very difficult (or not worth the effort) to fix or improve upon.

When meatspace issues permit, we'll build a new, much better system from scratch and all our current issues will be gone (and replaced with different ones).