Quote:
Originally Posted by Greenie
That's a lie. I refuse to believe that the programmers could not include the paysite's & affiliates code into the new system.
Hell, here's the solution: if my new "unique" account number is 1234567, then have a database that has ALL my old codes in it. Each time it sees one, like 581222 for Amateur facials, replace it with 1234567.
Problem solved.
|
From a programmer: problem solved in about 2 days worth of coding, testing, and a few dry conversion runs.
One way or the other you still need a userid, and a siteid that is being linked to. This means that the hash algorithm is reversible, or you have the hash stored as a key with userid/siteid stored alongside of it.
So... you're basically using the same values internally, just that on the outside it looks different.
I utterly fail to see how redirecting the old codes to the new ones becomes impossible -- you already know how the hash is generated, so go ahead and do it.
So far, all I've seen compares to:
"We're releasing a new shiny system, unfortunately our architects and programmers are fucking idiots who can't figure out how to get the old links redirecting to the new links, but we're going to go ahead with it anyway because well, it's new and shiny".
Good luck with that.