Skip to main content

Extending Tweet to a Larger Audience

You tweet but when people reply they are replying to you, not your tweet. There is no such thing as commenting a tweet. Your tweet must be replied in real time before you tweet another subject. Otherwise a reply may be mistaken for a different tweet. Unfortunately when you tweet not all of your followers are listening, and not many people will be searching for your tweet. Thus, your tweet audience is limited. It is the nature of Twitter that your tweets will be left behind after some time.

On the other hand, your listening followers may want to respond to your tweet but choose to keep quiet instead. One of the reason is that they don't want to be associated with your tweet personally. Or, they just don't want to make you feel bad with their responses. Thus, you don't get good interactive audience.

Let extend your tweet with blindtalk. What is a blindtalk? Check the website. A blindtalk is a short message posted anonymously. Anyone can respond to a blindtalk also anonymously. You don't have to register to use the service, you just blindtalk straight away. Once you blindtalk, click on the status link to go to the blindtalk status page. There is a tweet link that will bring you a page where you can copy a prepared tweet for your blindtalk. Copy and tweet it.

Now your tweet will have a link to your blindtalk. Your followers now will have a chance to respond to your tweet anonymously. And your blindtalk will also be published in the website where more people will have a chance to respond to your blindtalk which is also your tweet.

Blindtalk will also be left behind after some time. But responses to a blindtalk will resurrect it from time to time. The responses themselves may also be responded which will create a structure of responses. All related responses will resurrect the original blindtalk. It is something that Twitter doesn't provide.

Your tweet is now extended to a larger audience with blindtalk.

Comments

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr...

Everything has a Signature

Every data has a signature  which can be derived mathematically. All data of any size can be digested into fixed-size signatures. The signatures can be used to identify the data. Unique data has unique signature. Cryptographic hashing is a mathematical technique to hash or digest a data to reveal its signature. Digesting the same data always produce the same signature. Any minor change on the data will produce significantly different signature. A changed data is a different data. Data signature, hashing or digesting makes it possible for the data to be represented by its signature into a subsequent signing by combining it with one or more data signatures to produce a new signature representing a larger data set. Eventually, all data can be digested in chunks to produce a single signature. A signature can be verified by hashing the same data again which will produce the same signature. This introduces data signing-verification concept. In a communication between two parties, ...

Separation of Front-end and Back-end Concerns

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts....