Mark, great to see you here! Now I trust the platform is in the right
hands. :)
Cheers,
Alexy
On Dec 1, 10:49 pm, John Kalucki jkalu...@gmail.com wrote:
Perhaps someone from Platform could weigh in on this?
In [vulgar] Russian, I'd say it seems Platform retracted its tongue
into a [bodily cavity]. :) Platform, hey! :)
Cheers,
Alexy
We are taking a look... hope to have an update soon
On Thu, Dec 3, 2009 at 8:21 PM, braver delivera...@gmail.com wrote:
On Dec 1, 10:49 pm, John Kalucki jkalu...@gmail.com wrote:
Perhaps someone from Platform could weigh in on this?
In [vulgar] Russian, I'd say it seems Platform retracted its
Gardenhose apparently returns illegal Unicode, as confirmed by
PostgreSQL and Perl's Encode, a very trusted, high-mileage code. We
surely can trap illegal Unicode errors but need to know whether you're
aware of it, the rationale, and plan of action, if any. -- Alexy
On Nov 21, 5:10 pm, braver
In this case, this isn't the Streaming API. That encoding is almost
certainly what was presented to Twitter, probably exactly as encoded
by the client. In this case, I'd complain to:
http://mobileways.de/products/gravity/gravity/
If you request the Tweet via the REST API, you'll see the same
John -- thanks for clarification! Certainly it's the data in
Twitter's database as a whole, not just the Streaming API. One
question is whether you should accept illegal Unicode? Probably it's
a safer thing to do to avoid scaring the clients, but maybe you'd want
to apply some filter before
Perhaps someone from Platform could weigh in on this?
-John
On Dec 1, 7:41 pm, braver delivera...@gmail.com wrote:
John -- thanks for clarification! Certainly it's the data in
Twitter's database as a whole, not just the Streaming API. One
question is whether you should accept illegal
