Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
brettcvz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
151.
▲
User testing at startups
(blog.filepicker.io)
28 points
by
brettcvz
14y ago
|
6 comments
152.
▲
Filepicker.io Has Stolen My Heart
(soconnor.com)
10 points
by
brettcvz
14y ago
|
0 comments
153.
▲
by
brettcvz
14y ago
Totally unrelated to the article, but you should CNAME your tumblr blog so that HN et al. show flutterapp.com
154.
▲
by
brettcvz
14y ago
We've been talking with the Close.io folks directly, but you may have experienced some slowness this weekend due to increased load. We're rolling out a new architecture soon that should address the issue for the next order of magnitude. Reg
155.
▲
When Apps Meet Cloud Storage: Tectonic Shift Ahead
(wired.com)
24 points
by
brettcvz
14y ago
|
6 comments
156.
▲
by
brettcvz
14y ago
I hate to be so self-promoting, but http://jsfiddle.net/GTYX5/2/ should do everything you're asking for
157.
▲
by
brettcvz
14y ago
Our concern is that if we return the direct S3 url, people less experienced will assume that the S3 url should work by default, when it will 403. So we return Filepicker.io urls which alias to your S3 bucket
158.
▲
by
brettcvz
14y ago
Alternatively, use Filepicker.io. filepicker.store(myFile, {location: "S3"}, function(FPFile){console.log("File stored in S3 at "+FPFile.key+" and available at "+FPFile.url);});
159.
▲
A Paradigm Shift in Cloud Storage
(blog.filepicker.io)
16 points
by
brettcvz
14y ago
|
3 comments
160.
▲
by
brettcvz
14y ago
Got it! Good call, thanks
161.
▲
by
brettcvz
14y ago
While I agree it can be a huge time suck, the way to deal with many of these things is to find the right people to outsource to (particularly for HR, corporate contracts, etc) rather than ignore entirely
162.
▲
by
brettcvz
14y ago
In general, it's referring to the fact that you should be very careful with what you write down. For example, if you send an email to a potential employee that the 10,000 shares you are offering them are worth $10,000, you've effectively va
163.
▲
by
brettcvz
14y ago
Makes sense, will add an note on the paypal comment in github
164.
▲
by
brettcvz
14y ago
Great! Happy to take a look at a pull request if you have one
165.
▲
by
brettcvz
14y ago
Love the enthusiasm! To us, anything that helps makes products work more seamlessly together online is a win for the web and the world we want to see. It also seems like Dropbox is encouraging a different use case, in that the links they pr
166.
▲
by
brettcvz
14y ago
Yup, it's great to see that Dropbox shares our vision of helping connect online storage to online applications, so the spirit is the right one. Our goal is for users to be able to connect directly to their online content, and we're working
167.
▲
Startup Events
(blog.filepicker.io)
25 points
by
brettcvz
14y ago
|
5 comments
168.
▲
by
brettcvz
14y ago
There's always a balance between giving an overview for people who have never done this sort of thing before and writing to the aficionados with the battle scars of having done this a few times. Happy to share more detailed notes here, but
169.
▲
by
brettcvz
14y ago
Yup, didn't want to get into the weeds with the specifics, but we use the same procedure as AWS, where we use the shared secret to recreate the signature provided and then match the two (as well as verifying the method performed is allowed
170.
▲
by
brettcvz
14y ago
In general that's true, but specifically referring to public-key encryption only the holder of the private key will be able to create an encrypted message, so it serves as authentication
171.
▲
by
brettcvz
14y ago
I like the breakdown between the three. The first two make sense from an API standpoint, hence why we have policies that can specify the range of what a bad actor has access to. We do auditing on our side to keep tabs on anything that seems
172.
▲
by
brettcvz
14y ago
Being able to create arbitrary files without asking the user gets into some nasty security issues, so we went with "export" instead. Once the user selects where they want to save the file to, you can then perform .read's and .write's on it
173.
▲
by
brettcvz
14y ago
Oops! Sorry, bytes
174.
▲
by
brettcvz
14y ago
Took a bit longer to handle the edge cases, but we now have the max file size stopgap implemented. On your developer portal you can set the maximum size that you'll allow to be uploaded. We're still moving forward with the more fully-featur
175.
▲
by
brettcvz
14y ago
We take this stuff seriously. Great, shoot me an email at brett at filepicker.io and we can walk through how to get you set up on the new security scheme
176.
▲
by
brettcvz
14y ago
Also, given the feedback, we're implementing a way to set the max file size on your developer portal. Fix should go out in the next 10-15 minutes
177.
▲
by
brettcvz
14y ago
On it! We have a new security release coming out next week that allows the use of server-side secrets to lock down both uploads and reads. We've already contacted the author and are happy to work with anyone who is concerned and get them ea
178.
▲
by
brettcvz
14y ago
We're using the ability to talk over CMIS added in Sharepoint 2010
179.
▲
by
brettcvz
14y ago
That's actually a clever idea, and opens up the door to connecting to servers directly over ssh
180.
▲
by
brettcvz
14y ago
Given that it uses Filepicker.io, probably makes sense for us to take a look. The idea of turning files into URLs is one that we really like
More ›