Internal status email: Twitter at 3 months old. 160 Users & 100 Tweets per day
anarchogeek.com
anarchogeek.com
This is a problem for me doing thingist (http://thingist.com)... the people who have found and signed up for it seem to have really liked it, but I'm having trouble figuring out how to get more of those people.
(And I am an admittedly horrible marketing person)
Also side note: The bottom pagination links do not work for me. I can click next page and get next page but if I select a number be it 2, 3, or 75 I get an empty page?
Thingist is kindof like status updates, but with more context (and more available space [You can include a description of why you're posting it). Instead of a big bucket called "status", you separate things into different lists.
For instance, I have a list called "Good Bars in Phoenix" (http://thingist.com/t/list/65/)
or a list called "Adventures in Nerdery", which is mostly projects I'm working on (http://thingist.com/t/list/139/)
There are some global lists like "songs I like" (which get added to people by default when they register) (http://thingist.com/t/global/38/)
The example for a use case I always use is finding music that you've posted into the internet. I've been posing songs I like into facebook for 5 years, but as far as I know there isn't a simple way of pulling them back out.
Thingist [tries to] solve that.
But it's more than just status, at least it's a new approach to it. Somebody joined a few days ago, and started posting "things on the menu at a nerd themed restaurant". This resulted in neat sort-of back and forth between us: ( http://thingist.com/t/global/2944/)
(also: fixed the pagination buttons, oops)
I made this video: http://www.youtube.com/watch?v=i1rOJJWyU2s
but it was wayyyy too long.
You need to be showing people what it's about, the instant they visit your site.
I saw your page, thought "hmm, not quite sure what this is" and left. I'm not going to stick around to read an about page.
Then if they signup they can save their list. This makes it easy for users to jump right it in, and may bring in a lot of traffic from facebook. Of course, some users may not want to share each thing they like on facebook, so you'd probably want a normal "love this" button as well for logged in users.
I really like the idea of [optionally] importing facebook likes... Hmm
(As a sidenote: can I just point out that facebook's API is freaking awesome?)
No you may not. Facebooks API is horrible. I was just implementing the like buttons on my site and realized that they have to be iframes (even the FBXML or whatever its called creates iframes). This turns out a bit ridiculous on pages such as yours (if you put them on the feed page) and mine where you Twitter on the other hand allows you to just gives you a URL which points users to a link to share the page.
facebook: click your custom widget -> facebook prompt -> perform action
twitter: click your custom widget -> twitter prompt -> perform action
(Or just do like I do, and change the size of the iframe to 450x20)
It seems a little bit like you're trying to create a more structured version of what people are already doing on Twitter with many of the trending hashtags. (e.g. today's #failedmcdonaldsproducts[1] or #100factsaboutme[2]) Rather than fight the momentum Twitter already has there, perhaps you could take advantage of the Twitter API to automatically pull these trending topics in as Thingist Lists. When a new list is auto-created from a trending topic, you can automatically tweet out a link to the Thingist list with the same hashtag, which will get you exposure among people following that term.
The hard part then is making sure Thingist provides a more compelling experience than Twitter for browsing these sets of things. I'm not sure if you're there yet, but there is definitely an opportunity to do something better than search-by-hashtag. If you do pull this off, you'll have plenty of fresh content to keep new users engaged until they start creating lists right on Thingist.
(According to http://blog.twitter.com/2011/03/numbers.html)
cache:<target URL here>
http://www.google.com/search?q=cache:%s
Then give it the keyword 'cache'.
From now on, from the URL bar, you can just type cache <whatever> and it will go straight to a search for the cache of that.
Obvious was supposed to be a company which hacked out many ideas, a kind of incubator. The problem was one of the first batches of ideas turned in to a major run away success.
Apache-specific advice: if you're on a small VPS or other box with not much RAM, and didn't tweak the distribution defaults for MaxClients and friends in its configuration, a HN-size load will OOM you rapidly, especially with mod_php. The defaults for prefork MPM are nuts in the major distros (as in, assuming 4 GB of RAM or more for mod_php).
Since you're going up and down, I assume this is the case. I suggest dropping MaxClients to 5 for now and letting us wait a bit.
I dropped down the number of preforked apache processes, we'll see if that helps. It's also where i run some rails experiments, so we'll see. Load's back up to 7...
I had no idea hacker news got a lot of traffic.
This is a great story that put a bunch of hot air in our balloon tonight as we realized we're actually not too far off this track.
We have no expectation of being another Twitter by any possible stretch of the imagination, but finding out that at this early stage we're tracking with a reasonable expectation is a great point of validation.