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...

Using React in Foundation for Sites

This post was the precursor to the Foundation-React Template . React and Foundation are two different web UI frameworks addressing different needs. They evolve differently. Both of them are powerful on their own accord. Fusing them together may create superpower. We will walk through the process of adding React into Foundation. We will start by installing both Foundation and React through command line interface (CLI). Then we will create a simple Todo web app. Along the way we will highlight the development process. But before all that, let us summarize React and Foundation. The details can be found at their respective websites. Both of them are well documented. React is a run-time UI rendering engine. It renders dynamic UI elements in its own fast virtual DOM, and only update necessary changes to the slow browser DOM. This behaves like a  double buffering DOM which makes any UI update feels fast. React wraps a UI rendering script in a component. A React component can ...

Debugging PHP using Apache Error Log

PHP runs on the server side and behaves like a function that return a value against the given arguments. A remote client may call this function and expect a specified return value and nothing else. So how do we debug this function ? It must not return debugging messages since the client is never designed to handle them. We must never burden any client to handle debugging messages. If we run PHP through Apache server then we can use the error log to keep our debugging messages. It may not be the best way to do it. But we only want to talk about this approach now. Error Logs The Apache error log files generally can be found in the following directory: var/log/apache2 We issue the following command from within the directory to read the latest error messages: # tail error.log The tail command reads the last few lines from the error.log file and prints them on the terminal. If we need to read a specific number of lines from the end of the file then we can specify the -n opti...