Hi, Jigs, You're probably best off running your regex search and doing any replacing within your own application, before you send the tweets off to Twitter -- once the tweet's been tweeted, there's no way to modify it.
You could probably follow your users, search for suspicious tweets, delete them (provided your users have authenticated your app), and possibly re-send censored copies -- in general, this sounds like a pretty annoying feature, deleting tweets and re-sending near-duplicates (especially for the people following your users), but if you've got a very paranoid user base, they may think an obnoxious tweet-delete-retweet cycle is worth it to protect their data? Good luck, -Alex On Wed, May 18, 2011 at 12:08 AM, jigneshbh <jigs.bh...@gmail.com> wrote: > Hello, > > I need one help regarding encryption or masking certain keywords when > a user accidently keys in sensitive information e.g. SSN (XXX-yy-ZZZZ) > to anyone (as opposed to DM) which gets displayed on the time line > > e.g. i tweet as per > @jigsb my SSN # is XXX-yy-ZZZZ. > When it gets displayed on the time line, it should look like - > @jigsb my SSN # is ***-**-**** > > I guess, the detection of pattern should not be an issue (using > RegEx), but does Twitter website gives you an interface to detect such > pattern and take actions accordingly > > Appreciate your help in this regard > > ~Jigs > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Alex Feinberg CTO, Trak.ly http://trak.ly/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk