Open GoogleCodeExporter opened 9 years ago
please use the following tweet example containing yfrog image relative to
problem
description:
@ytoad3 wer der derptider wer der ber ber ber Location:
http://tinyurl.com/y4c04ac6c
http://yfrog.com/7b48424376j
Original comment by disot...@gmail.com
on 2 Jun 2010 at 11:09
please use the following tweet example containing yfrog image relative to
problem
description:
@ytoad3 wer der derptider wer der ber ber ber Location:
http://tinyurl.com/y4c04ac6c
http://yfrog.com/7b48424376j
Original comment by disot...@gmail.com
on 2 Jun 2010 at 11:09
That about the different locations then I think it is a correct behavior. When
the user upload the image the app
set current geo location and it is not related with location value in the tweet
text. When the user insert location
to the tweet text the app insert current location value and it value not
changed during the time. If the user has
changed self location then the new location value send to the yfrog but
location in tweet text should not be
changed. If the user want to change location value in the tweet text he need to
remove old value and set new
value by location button pressing.
Original comment by s.shkrabak@gmail.com
on 3 Jun 2010 at 10:33
I believe the case described in the comment above is not the case here. The
following
image has been taken and submitted to tweeter via iPhone within few minutes
from my
house. http://yfrog.com/7b48424376j
Location in the image details on yFrog landing page is correct. However the
following
link in the tweet shows wrong location http://tinyurl.com/y4c04ac6c
Here is entire tweet:
@ytoad3 wer der derptider wer der ber ber ber Location:
http://tinyurl.com/y4c04ac6c
http://yfrog.com/7b48424376j 12:00 AM Jun 1st via yfrog for iphone in
reply to
ytoad3
Original comment by disot...@gmail.com
on 4 Jun 2010 at 6:23
Looks good to close. Verified fixed. Locations are close.
http://yfrog.com/4b99178227j Location: http://tinyurl.com/y4c0f2994
Original comment by disot...@gmail.com
on 9 Jun 2010 at 7:46
Original issue reported on code.google.com by
disot...@gmail.com
on 1 Jun 2010 at 6:57