Everything in this article is terrifying and, somehow, what scared me the most was how much Internet is actually the world for so many people born not that later than myself. It is incredible how fast this change happened.
Also, I know my role as a professional is doing nothing but making that a bigger issue.
As a side note: bullying (cyber or not) is not the same in all countries. In my hometown, when I was growing up and we were not that penetrated by american culture yet, nothing like this would happen. The worst thing possible was a light fist fight.
I don't agree that twitter popularity lies on how easy it is to publish on it but in the fact that it establishes a reading contract. I know exactly how much time reading a single tweet will take me so I can read them in many circumstances.
That's why I think apps like TwitLonger make no sense.
The point is not to remove a functionality but to further constrain a contract (and enforce it).
The problem is that you are trying to enforce it on top of an existing platform with a use case for which it doesn't really make sense.
If you really don't want to receive long emails from strangers you can always add a filter in your mail setup that deletes any email over 500 chars long from people not in your address book with an autoreply that says "I don't read anything over 500 chars long".
IndexTank right now supports preffix search, stemming and a basic implementation of a Did You Mean feature. Regarding languages, it supports tokenization for every western language, and not long ago, we added support for CJK too.
It is not exactly built ON Lucene. It reuses very specific constructs. The main one is the structure that holds the comprised index. And that is only used for the long term index. The realtime part of the index has been written for IndexTank exclusively.
It is not like that. Check our FAQ out: https://indextank.com/documentation/faq2. We're talking to several interested parties who would like to take over the service.
Thanks for doing the right thing, we've really enjoyed the service. I'll look forward to the source release -- maybe we'll bring search back in house. Again -- congrats! :)
Michael, I'm Ignacio, from IndexTank, we exchanged some emails. Come to our website's live chat so we can think of a workaround for any problems you're experiencing with our whims :)
Tweaking relevance is not super-easy with Solr. We designed IndexTank to have a very simple way to play with ranking. You can modify your formulas in your dashboard or through the API and see the results order change in real time.
I really love what you got here. I'd be happy to help you try out IndexTank and make it better. It would really take the Solr configuration burden off of you.
well I considered using IndexTank earlier on, especially because I didn't know yet how to deploy Solr. The relevance is mostly done already, I just needed to learn to use formulas :)
One thing that put me off is your cap in queries per day. The smallest paid plan (50k items in index) is capped at 1,000 queries per day.
Isn't that an issue for most sites ? Do people usually cache your results ?
The 1k cap for the 50k doc plan is old, we will be upping that significantly. What would be a number of queries per day that would make you comfortable?
As a side note: bullying (cyber or not) is not the same in all countries. In my hometown, when I was growing up and we were not that penetrated by american culture yet, nothing like this would happen. The worst thing possible was a light fist fight.