31–40 of 41 posts
How did you associate this data? I signed up as +quickly@gmail.com .. never used that address before.
Please disclose what dataset you used to associate my account with the name you greeted me with.
Also, what are you thinking for pricing?
When the software is ready for people to try out, this will make a great Show HN. Good luck with the work!
HEY. I signed up with a gmail address that uses an alias for my from:. You sent me a "hi welcome thanks for signing up" email that included a different alias I've used online before. How did you associate this data? I signed up as +quickly@gmail.com .. never used that address before. Please disclose what dataset you used to associate my account with the name you greeted me with.
PS: I just checked. You have also provided your name. :-)
Looks interesting...I noticed the task creation examples in the video all started with "Can you please...". How good is the parser at picking up implied requests. For example, where I work, requests more likely look something like "We should look at improving the caching layer" or "prod is hanging". Also, what are you thinking for pricing?
I hope by the time we release, we will be fairly good to cover most of the use cases.
Looks interesting, but we took "Show HN" out of the title since Show HNs are for things that you've made that other people can play with. So a video isn't a Show HN unless, of course, the video itself is the product. When the software is ready for people to try out, this will make a great Show HN. Good luck with the work!
Looks interesting, but we took "Show HN" out of the title since Show HNs are for things that you've made that other people can play with. So a video isn't a Show HN unless, of course, the video itself is the product. When the software is ready for people to try out, this will make a great Show HN. Good luck with the work!
Thanks dang. Sorry we have not been very active on posting to HN, just a consumer of information. It seems we got that part of the title wrong.
Earlier quoted context omitted.
You're expecting people to take your word for it. Even if you're telling the truth, when your security is compromised, so are all your users' email, because you have full access to it. Bottom line: Yet another "web 2.x", proprietary, "beta," SaaS, subscription, third-party, unrestricted-privacy-compromising tool without a business model that might be around for a few years before being bought and ruined or going bank…
> Seriously, it could be done [...] in a bit of Perl or Python [...] A few hours [...] People said the same thing when dropbox was announced, look where we are now: very few people do it locally, and dropbox has won.
How is that relevant to the issue of giving a third-party access to ALL OF YOUR EMAIL for the sake of convenience? How does that justify doing so rather than developing a client-side, FOSS solution?
Earlier quoted context omitted.
> Seriously, it could be done [...] in a bit of Perl or Python [...] A few hours [...] People said the same thing when dropbox was announced, look where we are now: very few people do it locally, and dropbox has won.
Dropbox has won? Won what? Was there an International File Sync and Sharing Software Competition? How is that relevant to the issue of giving a third-party access to ALL OF YOUR EMAIL for the sake of convenience? How does that justify doing so rather than developing a client-side, FOSS solution?