Hi Zealous Co,
Over the weekend, we rolled out a change to fix issues with escaped fragments. I now see the appropriate gallery cards when I tweet http://www.zealous.co/#!project;id=5701808034938880 and http://www.zealous.co/#!project;id=6327994469580800. Please let me know if you are experiencing any further issues.
I think my case is not usual as other people but can I give a question? I’m just wondering that whether the Twitterbot is considering hash on url (not hashbang, hash!). My case is http://blincle.com/#!/#detail-53d091366803fae3a9529e90 and I need them to be like http://blincle.com/?escaped_fragment=/%23detail-53d091366803fae3a9529e90 or just escaped_fragment instead of _escaped_fragment (my server detects both), but I’m not sure if the # coming after #! is well converted to %23. The twitter card validator shows http://blincle.com/#!/#detail-53d091366803fae3a9529e90 is “server error”, while http://blincle.com/#!/%23detail-53d091366803fae3a9529e90 just works fine (of course, for the latter one, my server receives /?escaped_fragment=/%23detail- blah blah).
#
#!
%23
/?escaped_fragment=/%23detail-
hmm. Two underscores surrounding some word somehow got stripped. escaped_fragment
escaped_fragment
