API question: inconsistent usage of /p and /plan

[Max Ogden]

I am noticing inconsistent usage of the base 36 encoded /p route and
the base 10 encoded /plan route

for instance:

if you search in the 'What are you planning to do' field for an event
(e.g. 'open data day') and click on the resulting event, it takes you
here:

http://plancast.com/plan/145604

but if you navigate to that same event from the plancast.com/home
page, it takes you here:

http://plancast.com/p/34ck

for more context see https://github.com/maxogden/calagator/commit/6210e680474507f8e910412cf329edb24becc23f

this is annoying because I want to ask users for plancast plan ids,
but I have no way of knowing if they are going to enter the base36 or
the base10 representation

thanks,
max

[Mark Hendrickson]

Hi Max,

Sorry about this -- that's a known inconsistency that will be corrected in our next code push, slated for Friday evening.

Basically, when we designed the search autocomplete, we cut some corners and used the base 10 when we should have gone with base 36. 

Please let us know if there's anything else with which we can help, and we'd love to hear about your project.

Best,

Mark

--
Mark Hendrickson
My plans: http://plancast.com/mark
My info: http://ursusrex.com | http://about.me/mark
My tweets: http://twitter.com/mhendric