751 karma · joined February 27, 2010
A one time pad requires a key as long as all the messages you want to encode since each key bit is only used once.
A link from the github page might be helpful!
The trick is to understand the strengths and weaknesses of any given framework and match those with the constraints of your project.
This part of the process seams especially opaque and I've had far more customers than I would have expected have cards declined for no discernible reason.
I wonder if shared merchant accounts are a plus or minus here.
Bots will either hit both or neither and get rejected. Screen readers/toolbars may be an issue, though the names would be hard to think what to autofill with. It has never come up in practice -- the reject message tells people to email us directly
If you have javascript turned off, you'll need to email directly too -- and the site won't work so there probably isn't much lost!
I'm not worried about the email address being in the open, but my original contact page form was getting hundreds (thousands?) of spam submissions a day until I implemented some simple javascript 'traps' to filter out the bots.
I've still not worked out why a bot wants to fill in a contact form with spam anyway, seems like a real waste of time.
Are there products that let you do this pre-retirement as opposed to at retirement? If so they certainly don't seem as popular as the traditional save-to-65-then-buy-one approach.
I'd much sooner have a clean VM to run my tests on than have to think about the ways the previous user might have left things in an insecure state.
What if the record you deleted was subject to some kind of uniqueness constraint. If another user has added a record that has the same data, then flipping the delete flag off again would not violate that constraint.
Sure, it could be handled by checking if the constraint is violated. but you rapidly run into a lot of code to implement that one feature and dealing with thinking of and testing all the edge conditions makes it much easier (& cheaper) to focus on other features.
Tarsnap: easier to set up and use Duplicity: fully open source, and I think the restore speed was significantly faster ... but I've not properly benchmarked it apples-to-apples.
If you are backing up a lot of frequently changing files (eg. database backups) then tarsnap's bandwidth charges (probably caused by the underlying EC2 charges) can swamp the storage cost. Running duplicity against rsync.net avoids this.
As an extra advanced trick: adjust the stride length for incline changes ... though I don't know how you get that information accurately enough!
Would still love to see a non-developer centric site to point customers at so they can understand who/what Stripe is in order to integrate with our site via Stripe Connect.
That is a pretty big hurdle to have to jump through!
You'd have to pry it from my dead hands ... works, is comfortable, has lasted years and comes in a left-handed version!
I'm looking at this as an option vs a small AWS deployment. Seems to offer a lot of the flexibility of virtualization at a much better price/performance point than AWS.
But the 'Generate HTML with Inline Styles' button isn't appearing as a button (and doesn't do anything when clicked on) when running the latest Chrome on Win 8.1
Interestingly newrelic is reporting the site down at the same time it is reporting a normal level of load on it.
I'm running this at home and it works great for adding custom actions to Siri
Though all I know is the headline rates quoted for most common processors where <2% seems very aggressive. Who gets the other 1.95% of that?
I don't see how Braintree and Square are interchangeable for anything other than physical point-of-sales use cases ... which doesn't seem like Braintree's sweet spot
Still, I think it is a cool idea and will give the bookmarklet a try for a while.
So if for a given usage pattern the screen does consume 60+% (which is what I often see) then keeping it off all the time certainly helps ... but also makes the phone a lot less useful!
No longer am I concerned about errant semi-colons or a stupid typo in a method name on an error handling path that a unit test missed.
But other than that: * everything is in source code control, with clones of the repository in a few places * AMIs for the production machines (copied to multiple AWS regions for redundancy) Only taken every couple of months since they are just a pull & build away from being up to date. * Google/Dropbox for email, documents, etc using TrueCrypt for sensitive stuff
I don't really see the need for a full traditional backup process. When I did use one, I never found the time to fully test the restore process frequently so would have to doubt how robust it was anyway!