Loading Profile...
RFC: SMS tagging / extending the interface
As an extension to http://getsatisfaction.com/treasuremy... , I would like to post this request for comments with some thoughts on making TMT rock even more than it does now.
I realize that TMT is primarily a SMS storage solution, but I find myself liking the TextStream more and more, mostly because it allows for live- AND life blogging from any spot I am, thanks to my phone.
At times, I experience things that I would love to share with the readers of my blog and TMT puts me in a position to do so, however, I still have to prefix my SMS to provide some geographic context.
My proposal is as follows:
Provide users with (at least) four prefixes to show where they are right now. The prefixes are only used for geographic positioning and I would suggest using the @ character for that.
Example:
@c = in car, either as driver or passenger
@h = at home
@p = in public, on some road etc, as a pedestrian / biker, during an event
@t = at train, train station, (railed) public transport
Users should also be able to extend this interface with a max. of 5 more prefixes.
The same overall style should be utilized for the way that folders are extended with the difference that the amount of folder-tags is not limited (if at all possible) and that there are no standard tags right from the start. (You could introduce one standard folder "live blogging" and assign prefix " #1 " to it though, to expose users to this function).
As an example, say I a want to send a message to my TextStream and want to tag it for folder "live bloggin" and the content of the message relates to something I have experienced on a train, I would use:
---
@t #1 just saw Paul on the train, texting away like crazy. No wonder the TMT servers are overloaded.
---
Both prefixes have to be suffixed by a space in order to make it recognizable for the system. Error handling should be up to the user, so if someone has set up a folder with " #1 " as the prefix, the message should still be placed in the correct folder, but the user should be able to move the message in the system.
Furthermore, if a message is received like this:
---
<space>@p #1 Just saw Katie in a pub, discussing TreasureMyVoice, sounded interesting
---
the system will simply ignore it, so the <space> character should be a way to "defuse" the triggering system.
Now, discuss!</space></space>
I realize that TMT is primarily a SMS storage solution, but I find myself liking the TextStream more and more, mostly because it allows for live- AND life blogging from any spot I am, thanks to my phone.
At times, I experience things that I would love to share with the readers of my blog and TMT puts me in a position to do so, however, I still have to prefix my SMS to provide some geographic context.
My proposal is as follows:
Provide users with (at least) four prefixes to show where they are right now. The prefixes are only used for geographic positioning and I would suggest using the @ character for that.
Example:
@c = in car, either as driver or passenger
@h = at home
@p = in public, on some road etc, as a pedestrian / biker, during an event
@t = at train, train station, (railed) public transport
Users should also be able to extend this interface with a max. of 5 more prefixes.
The same overall style should be utilized for the way that folders are extended with the difference that the amount of folder-tags is not limited (if at all possible) and that there are no standard tags right from the start. (You could introduce one standard folder "live blogging" and assign prefix " #1 " to it though, to expose users to this function).
As an example, say I a want to send a message to my TextStream and want to tag it for folder "live bloggin" and the content of the message relates to something I have experienced on a train, I would use:
---
@t #1 just saw Paul on the train, texting away like crazy. No wonder the TMT servers are overloaded.
---
Both prefixes have to be suffixed by a space in order to make it recognizable for the system. Error handling should be up to the user, so if someone has set up a folder with " #1 " as the prefix, the message should still be placed in the correct folder, but the user should be able to move the message in the system.
Furthermore, if a message is received like this:
---
<space>@p #1 Just saw Katie in a pub, discussing TreasureMyVoice, sounded interesting
---
the system will simply ignore it, so the <space> character should be a way to "defuse" the triggering system.
Now, discuss!</space></space>
I’m hopeful
Follow this discussion to get notifications on your dashboard.
Create a customer community for your own organization
Plans starting at $19/month
-
-
Inappropriate?i would be interested in this... though more tagging in general than location specific stuff.
eg prefixing it @a dropis in on /a/rss.xml
prefixing @b drops it on /b/rss.xml
not prefixing it puts it on /rss.xml
it makes sense really.
I’m hopeful
-
Inappropriate?Has this been given any more (official) thought?
I’m looking forward to hearing TMT's official position on this
