Show HN: Fatnest, easy collaborative tweeting(fatnest.com)
fatnest.com
Show HN: Fatnest, easy collaborative tweeting
http://fatnest.com
8 comments
Is this about birds?
Hi, I made this in my free time because there wasn't really anything that let me delegate tweeting access without all the other junk to people. I envisioned it as something quick and handy for accepting submissions, etc.
I built the similar http://TweetFavor.com, which Twitter promptly shut down once people started using it, post-mortem/rant here: http://restrictionisexpression.com/post/26144987502/im-done-...
Hopefully you don't suffer the same fate, but Twitter's API policies just aren't friendly for fun little projects like these :/
Hopefully you don't suffer the same fate, but Twitter's API policies just aren't friendly for fun little projects like these :/
It's rough. I hope there are open competitors that gain traction and are worth relocating to in the future. But for now I still like the platform over forced bidirectional communication platforms like Facebook. At the very least it's for fun, while it lasts.
Checkout http://app.net if you haven't. FatNest/TweetFavor would likely be useful in that context, I hope it gains traction!
At any rate, developers, developers, developers! :) I love our people :)
At any rate, developers, developers, developers! :) I love our people :)
cool idea!
could be useful for companies (like the one I work at) for employees to tweet via the company official account which is handled by marketing. (If you don't already), you may want a review panel for outgoing tweets, for which (I think) you can charge.
could be useful for companies (like the one I work at) for employees to tweet via the company official account which is handled by marketing. (If you don't already), you may want a review panel for outgoing tweets, for which (I think) you can charge.
Neatly executed ! & a nice idea! Few suggestions:
1. Actions seem to lead user across several pages ; IMO, they could be done in a single page (for example, managing an already-added-twitter-account).
2. When I invite someone, you seem to auto-create an ID for their email id. Am not sure if (a) this might end up creating a lot of unused/spam Fatnest accounts, (b) the user (who is invited by email) may not really like it, because he/she might or might not 'actually want' to sign up.
1. Actions seem to lead user across several pages ; IMO, they could be done in a single page (for example, managing an already-added-twitter-account).
2. When I invite someone, you seem to auto-create an ID for their email id. Am not sure if (a) this might end up creating a lot of unused/spam Fatnest accounts, (b) the user (who is invited by email) may not really like it, because he/she might or might not 'actually want' to sign up.
Good ideas. I'm thinking a mailto/registration link that'll automatically link the user to the delegated twitter account would probably remove the abuse vector. Thanks for the suggestions!