Comments for TextMarks Blog

Comment on BronxRhymes Interactive Hip Hop History powered by TextMarks by Cherrie Sakuma

Cherrie Sakuma — Tue, 02 Mar 2010 19:41:45 +0000

Great to see the love being spread on here! Hip-hop for life!

Comment on New keyword separators: * and – and , by tribui

tribui — Wed, 03 Feb 2010 18:01:54 +0000

This is great.

I would have preferred # to be included too. Then you can have

myclassifiedsad#1234

The colon : and pipe | would also be great too.

Or how about nothing, a wildcard keyword. As long as it does not encroach on any existing keywords and is not the prefix of any standard dictionary words, it can be a premium wildcard keyword like:

zq <– wildcard keyword
zq123
zq1
zqinfo

etc.

tribui

Comment on New: Auto-post your alerts to Twitter by dkamins

dkamins — Mon, 05 Oct 2009 18:28:53 +0000

@Tim,
That currently isn’t supported, but we might let you do it in the future. Thanks for the feedback!

Comment on New: Auto-post your alerts to Twitter by Tim Hayes

Tim Hayes — Fri, 02 Oct 2009 22:31:32 +0000

I love this feature, but I would like to be able to update both twitter and my website widget at the same time. As I see it now, an alert goes to twitter, and an update goes to the web widget. How can I do both with one entry?

Comment on WordPress Plugin – Let readers subscribe to get posts by SMS by Hosting

Hosting — Tue, 04 Aug 2009 22:02:16 +0000

thank you very good

Comment on Custom Welcome Messages (New) by Ronald

Ronald — Mon, 08 Jun 2009 23:22:07 +0000

i really hope textmarks would be available to more networks and outside US.. we’d love them in philippines.. it’ll be great to integrate it with one of my websites

Comment on New V2 API Alpha Release by TextMarks Blog » Blog Archive » “Subscribe to TextMark” => “Join TextMark”

Sat, 16 May 2009 00:01:53 +0000

[...] The old commands and terminology are still valid, but you may see some of these new terms in system messages, on our site, and in our new V2 API. [...]

Comment on New V2 API Alpha Release by dkamins

dkamins — Wed, 22 Apr 2009 18:23:31 +0000

@John S.,
In which API methods specifically are you interested in seeing this extra info?
Also, can you say in what context would you not know what the request was for and would need this info?

Comment on New V2 API Alpha Release by John S.

John S. — Wed, 22 Apr 2009 06:06:30 +0000

It would be nice if an API method like invite_to_group() would echo back the number/user sent with the request so I can tell what the request was for. When I submit a new number, I just get OK. When I submit a number with a pending request, the number is returned back, but only in the error message.

Comment on New V2 API Alpha Release by dkamins

dkamins — Sat, 28 Mar 2009 04:48:17 +0000

@Jared,

The new V2 API does not yet have client libraries publicly available. You may still interface with the API using standard HTTP requests, but you will have to write your own client code for now.

We will likely release PHP and Python client libraries first.

Meanwhile be sure to try the “TEST” box on each API method documentation page. You can make direct API calls from your browser and inspect the results. This is a good way to familiarize yourself with the new API.