psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Show HN: Collections, a fast multiple-account Google Docs client for Mac
41–50 of 101 posts
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#42psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Hi thomas-st, thanks a lot for bring this up. we just fixed the issue and changed credentials on the server as well. All transmission also happen securely through HTTPS and contents are only stored on Google's server, not ours.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#43Kind of confused by this heroku error message I received? Are you storing my gmail credentials on heroku? When I tried again I have a google /looking/ login screen? http://cl.ly/1p0M0o2t0H1E3Z1h3i0n
I think they are mimicking the Google Login page and just saving your username/password. Seems damn fishy to me.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#44This is awesome. Are there any plans to port this to other platforms?
Thanks! There certainly are, but not for a little while. Which would you prefer we support first?
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#45psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Hi thomas-st, thanks a lot for bring this up. we just fixed the issue and changed credentials on the server as well. All transmission also happen securely through HTTPS and contents are only stored on Google's server, not ours.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#46I suggest you not use this app right now. It is currently throwing up debug pages that include information that allows someone to connect to Postgres and dump the database containing information about your documents.
App developers -- please update your Heroku settings and/or turn this off immediately. You are exposing confidential company information to the wild.
Thanks.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#47I know that this isn't really related to the application, but anyway... Please, don't let the browser scale the images for you. I don't like opening a site, and seeing something like this ( http://sadpanda.us/images/1078451-DUYING8.png ). Beside that, this client seems something really awesome, especially the ability to easily edit docs from different accounts.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#48Kind of confused by this heroku error message I received? Are you storing my gmail credentials on heroku? When I tried again I have a google /looking/ login screen? http://cl.ly/1p0M0o2t0H1E3Z1h3i0n
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#49Super nice, but I worry about the slower webkit in webview. If it is much slower, you would get a better experience in the browser, despite the nice UI additions in this app.
Why would an embedded web view be slower than Safari on a Mac? Mac OS doesn't have the restrictions on generated code that iOS does.
Re: Show HN: Collections, a fast multiple-account Google Docs client for Mac
#50psql -h ec2-107-22-171-68.compute-1.amazonaws.com -p 5732 -U u1npugarlguimh -d ddbs2kvmqeieon Since DEBUG=True, finding the password is left as a trivial exercise for the reader. I wouldn't trust the service until they fix the issue.
Hi thomas-st, thanks a lot for bring this up. we just fixed the issue and changed credentials on the server as well. All transmission also happen securely through HTTPS and contents are only stored on Google's server, not ours.
I'm not sure how to validate that this is still timely, though... oh, I created a table:
public | hacker_news_1342216769 | table | ruwdncbzdkulsh
With the current timestamp. So, if you changed anything, it hasn't actually taken effect in the part that matters -- the exposed database.