Coming Soon To Hashtagify Beta: Hashtags Trends Comparison

Some great new features are coming to hashtagify.me. Already available in beta are hashtags trends and an analysis of the days of the week and times for the day when each hashtags are more used.

Coming soon to the beta is the ability to compare the trends of different hashtags; If you want to get an example of this feature, you can check out this blog post on Social Media Sun.

prism-hashtags-timeline

15 Million Hashtags, And Counting

hashtagify15millionHashtagify.me has been collecting data about hashtags on Twitter since April 2011, and the use of hashtags has only been going up since then. So, after little more than two years, we’re proud to announce that today we passed the mark of 15 million hashtags classified in our systems, that you can still search and browse almost instantly.

Not just that. In the next weeks we’re going to release on hashtagify.me many new, advanced features, and still for the same convenient price of 0 USD.

Now that we’re talking about it, would you like to know why is hashtagify.me free, and help us keeping it that way? You can do that, read about our approach, and validate it with your feedback. Oh, and you can also gain early access to our new features – you just need to answer a few questions about which features you’d like more. Read more.

Hashtags on Google Plus too!

As pointed out by Chris Messina, the “inventor of Twitter hashtags” (rather, the one who pushed for their adoption on Twitter, which is no little feat), Google just rolled out hashtags autocompleting on Google Plus, thus giving their official support for hashtags there.

This is very good news, because hashtags are a really easy way to tell what your posts are about. And because hashtagify.me could add Google Plus hashtags data too in the future… would you like that?

Hashtagify Pro private beta

Lately I’ve been hard at work on Hashtagify Pro, a new tool that lets you track a specific campaign or subject (not limited to hashtags) on Twitter and analyze which influencers are impacting it and how.

Today is a big day: We are ready to start a private beta!

You can go to pro.hashtagify.me and take a look at the new website, where you can also find a Demo/Tour that shows the kind of analysis you can do with Hashtagify Pro.

If what you see interests you, you can apply for a free beta account using the link in the home page. Beta accounts will be activated as soon as there are free resources on the server.

We’re also very interested in your feedback: Comments, glitches, ideas, suggestions. Hashtagify Pro is still in evolution and your suggestions now can have an important impact.

So, let us know what you think!

PS: Hashtagify Pro works best with a recent browser. IE only works with version 9.

Bootstrapping hashtagify pro: How I doubled my workweek productivity

Creating a startup while working a full time job has its pros and cons. Among the pros, you don’t have to use a lot of your time minding your investors (or looking for them), and you can devote your energies to just make the best possible product. Among the cons, progress is slower and it is very difficult to be productive on workdays, when you already spend 8 hours or more on your day job.

But a week ago I read a comment on HN (edit: thanks to raju in the comments for pointing me to the exact link)┬áthat inspired me to rethink how I’m organizing myself , and with one simple change I doubled my productivity on workdays. How? Instead of working on hashtagify at nights, after getting home from my day job, I’m starting my day two hours earlier, and doing 2 hours of programming in the morning, before going to work.

I’m usually a night person, and have always been very productive at nights, since when I was just a student. But after eight hours of work, it is difficult to have that kind of focus that you need to program, and the two (or two and a half) hours in the morning have been much more productive than the equivalent time in the evening.

After coming home I still do some lighter work, and don’t go to bed without having scheduled a task to do the next morning; this way when I wake up I don’t have to think what to do and I can be immediately productive.

So, the bottom line is that work on hashtagify pro is proceeding very well: now I’m making as much progress during the workweek as I usually make during weekends, while before I only made major progress outside workdays. This means that soon enough I’ll be able to release the first beta. Stay tuned!

Evaluating a Twitter Campaign

If you’re doing a marketing campaign on Twitter, how can you measure its real impact? And, specifically, how can you evaluate the individual contribution of single campaign participants?

This is something that has been asked to us, and we think we’ve found an interesting solution to visually show this information by leveraging the hashtagify technology. So, if you’re interested in this kind of analysis, stay tuned. And, if you have specific suggestions or requests related to this, don’t hesitate to contact me writing to @hashtagify . First come, first served…

Be seeing you!

Working on hashtags/users data… and a little setback

These days I’ve been working on getting the data needed to show the top tweeters/influencers for an hashtag.

For the less used hashtags that’s not easy, but for the more common ones I was already getting some interesting enough data and I was thinking about the possibility to publish a first beta this weekend.

Unfortunately, while working on this new feature, something got corrupted on Redis – the database where we collect our data – and had to go back to an older backup; you might already have noticed that the number of examined tweets displayed on hashtagify fell from over 50 to 43 millions.

Nothing serious, but this means that we’ll need to wait some more time for the first beta. I just hope to be able to publish something before I’ll leave for a 2 weeks vacation to Russia next week… but don’t hold your breath!

While working no this I also learned something interesting about how to execute batch jobs on node.js: I expected some complications from the non sequential nature of node, but I hadn’t forseen the full extent of the surprises! I’ll try to share this to thos interested in this kind of technical details an upcoming post.

Cheers