sanyaade-g2g-repos / posit-mobile

Automatically exported from code.google.com/p/posit-mobile
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Twitter plugin - sending tweeting seems to be a bit inconsistent #298

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I'm using an emulator with no gps coordinates. This may or may not be a factor 
because of the number of characters in a tweet (140char).

What steps will reproduce the problem?
1.Start basic POSIT
2.Click Add Find
3.Type in 0 to 4 characters in the name field.
4.Press the menu button to 'Twit Find'

What is the expected output? What do you see instead?
The tweet should be successful.

I'm not sure how to describe this issue. It seems sometimes the length of the 
tweet could be a problem? Sometimes when the tweet contains more than 140 char, 
it successfully splits into multiple tweets. But, sometimes only the first half 
gets sent.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by gordonle...@gmail.com on 11 Dec 2011 at 2:30

GoogleCodeExporter commented 9 years ago
Test Case (Find with two fields: name; descriptor):
Tweeting Find 1:
Message1.1: Name = Stan Description =
Message1.2: blahblahblah (where blahblahblah is a string with 100 characters)

Tweeting Find 2:
Message2.1: Name = Gordon Description = 
Message2.2: blahblahblah (where blahblahblah is the same as Find 1)

In this situation, the tweet will fail because Twitter has restrictions on 
identical Message appearing. Actually, in this situation, 1.1,1.2,2.1 will all 
be sent. But 2.2 will not, and the application will display a toast saying the 
message was not sent. 

I have done some more work to minimize the messages in another patch. 

When designing this functionally, I imaged a find plugin providing a customized 
message to be tweeted which would be unique. Perhaps generally speaking, the 
only way to address this is to put the find's uid+time stamp at the beginning 
of each message associated with the find. This might be necessary but also 
might use up a lot of characters.  

Original comment by stan.f...@gmail.com on 12 Dec 2011 at 11:51

GoogleCodeExporter commented 9 years ago
Maybe we should take out some of the information that gets sent. 

Are we using this functionality to tweet all the information in the find? 
(guid, id, revision, status, ..., deleted) This doesn't seem particularly 
useful since if we have internet connection, we can sync to the server. 

Or as a general 'cool' feature to tweet about my find. (Name, description, 
longitude, latitude, picture?, and maybe the current time if we need the tweet 
to be unique)

This doesn't guarantee the length of the tweet, but it would shorten it and be 
more readable.

Original comment by gordonle...@gmail.com on 12 Dec 2011 at 10:05

GoogleCodeExporter commented 9 years ago
Perhaps we can discuss this at today's meeting.   Perhaps something like basic 
find name, abbreviated description and comment might make sense until we have a 
client telling us how they want it to work.

Original comment by ram8...@gmail.com on 13 Dec 2011 at 2:15