Law enforcement shouldn't have to rely on the banks to disclose anything to them unless they come with a court order and ask specific questions.
The laws are put a strain on day-to-day business for everyone and it's tiring.
114 karma · joined September 16, 2009
Law enforcement shouldn't have to rely on the banks to disclose anything to them unless they come with a court order and ask specific questions.
The laws are put a strain on day-to-day business for everyone and it's tiring.
By getting another team to take over, it's almost as if we were getting one/two other co-founders to come on board. My co-founder and I will take an advisory role and that's why it's fair that the new team gets a majority stake in the company. We would retain 10-15% of common stock each.
I'm hoping we can find a team to take over. My co-founder and I will certainly be there to help with all the technical stuff and the business model.
I will probably write a more thorough post about it later on, but right now we're trying to focus on finding a team to take over and save taketake.
Redis is used for our messaging queue (resque), sessions and caching. MongoDB is used to store our user data. Redis could be used to store our user data as well but we feel that MongoDB is a lot easier to work with because of its query language.
MongoDB fits better to store our user data and Redis fits better for our messaging queue, sessions and caching. We have yet completed migrating from MySQL to MongoDB which is why I've listed both in my post.
Once you found them, ask them if they would part take into grapev.in mavens. Tell them you are looking for feedback from heavy grooveshark users and in return they will be the only ones with early access to some grapev.in features.
Create them a special account, give them a place where they can connect to each other. Make them super fans by iterating and get to market fit with them.
They will evangelize your product for you - sounds like a good starting point.
The idea spun from our internet marketing efforts at the time. Lots of people are searching for reviews online and there's so much spam content out there... we set to find a solution. It's only about a year later that we started to work full-time on the idea. It was the first time for us to work on a project like this and made all sorts of mistakes along the way. But we're finally done and releasing it!
Feel free to email me at matt at taketake, perhaps we can help each other in the space! Cheers!
Then when we're about to put the site live and had to remove the placeholders... it felt strange looking. So we came up with this idea!
For the lack of content part we will be launching city by city and will be showing wants and haves from people living around your area. We are also working on our taste engine to show you things that we think you are interested in.
We've built a database of things, we've got about 50,000 things so far. Those were manually reviewed and curated by our team. So there will be some content on there that we will suggest you check out upon joining.
I want to be able to track time without relying on the user to submit it manually. I want a tool that submits automatically with me controlling the idle time and if I want screenshots or not.
After a while when you develop a trust relationship with your remote workers you don't necessarily want to take screenshots all the time and/or for all projects. Screenshots are not always necessary and can, if used all the time, wear down morale.
If you work with a new remote workers on a quick project, sure why not. But when these remote workers becomes part of your company and are working 40+ hours a week for several months, it's overkill.
Also for sensitive projects - I don't necessarily want screenshots published on a 3rd party site and/or be submitted over an unencrypted connection.
* Delete/Edit button for projects created; * SSL option (on/off in account settings); * Mac/Linux client; * Option to turn off the screen capture per project or per user.