303 karma · joined December 2, 2012
Everything about it sucks, cost, anual page limit license, I can only run it as root for some reason, but the OCR quality is superb.
here's the scripts I use if it's useful: https://github.com/cove/scanbd
DDR memory is laid out in an array of rows and columns, which are assigned in large blocks to various applications and operating system resources. To protect the integrity and security of the entire system, each large chunk of memory is contained in a "sandbox" that can be accessed only by a given app or OS process. Bit flipping works when a hacker-developed app or process accesses two carefully selected rows of memory hundreds of thousands of times in a tiny fraction of a second. By hammering the two "aggressor" memory regions, the exploit can reverse one or more bits in a third "victim" location. In other words, selected zeros in the victim region will turn into ones or vice versa.
For example, have expert templates for Subaru cars, that integrates dash.by and jiffy lube, my insurance, waze, the manufacture etc. then just apply common things I'd want in a single click.
* Such as schedule an oil change on my calendar on the weekend when I'd normally get my oil changed.
* Does my manufacture have any serious issues I should know about?
* Check how many miles I'm driving, and see if my insurance policy could be updated to reduce my rate.
* Suggest a gas station that's on my routes that are more cost effective than the one I'm using.
* Remember where I parked my car in case I forget.
* If I park in a 2hr zone, use pay by phone to pay the parking automatically for me.
* If I'm going to the Symphony, schedule a Lux to meet me out front.
Here's what it looked like for me last May: https://www.dropbox.com/s/9rkor22hn3q6z5t/IMG_2183.jpg?dl=0
The argument of doing what's best for everyone is just not something that resonates in their politics, much in the same way that's it's not a mainstream value in the USA either. Rather it's about "what's in it for me". Those are not the values of the majority in continental Europe thankfully, asking the question of what's best for everyone resonates stronger.
On a side note, GCE has a similar feature with Stackdriver: https://cloud.google.com/error-reporting/docs/viewing
Does a 50cal really seem like a sport rifle? The inventor goes on towards the end of this video to suggest it's useful for personal self-defence?
https://www.youtube.com/watch?v=1n3usocws0E&t=0m42s
Here's an example of a guy who has 1.5M subscribers explaining how he'd protect himself answering the door in the middle of the night with a completely impractical close range weapon.
- instance needs to be force stopped, that doesn't always work in the AWS console, you have to open a support case
- scaling things up: s3 buckets that get sudden amounts of traffic need to be manually partitioned, ELBs as well
- they have more logs on the backend you can't see: ELB logs aren't complete for example, they have more detailed logs only support has access to
- RDS failovers: determining if a RDS failover was due to a maintenance period or a hardware problem
- SNS/SQS errors: 5xx from SNS/SQS due to backend issues you have no control over
- Accidently used the official CentOS AMI? Oops, that AMI is "locked" and doesn't let you mount the image on another instance to get your data, you have to use support to get them to remove market codes
- New instance types don't alway boot correctly, this happened with i2s, they'd just fail to boot sometimes
- Accidently use CloudFormation to deploy your stacks? Lots of support tickets to fix all the backend problems with that, but at least Terraform solves that now :)
Unless there's a specific feature that you need in GCP, AWS is a safer bet from scalability, stability, support and cost.
GCE has an edge on performance, per minute billing, custom machine types, and some datacenters in areas AWS doesn't cover, however they're learning how to be a public cloud, so you will run into beta level bugs, scalability issues, support issues (they also limit how many people can open a ticket in your org), and stability problems. If you do go GCP, make sure you have a rep and a high level support contract, otherwise it's going to be hard when you run into issues.
* CF gets deadlocked if resources are changed outside of it, and there's no way to prevent people from doing that either
* No concept of a rolling update to a fleet or any warning it's going to cause an outage with out having to dig through fine print in the docs on every single change, just terminates all the EC2 instances in an ASG/ELB in some cases
* If you have a template, remember any change you make to that template has to be applied to every single stack you have, otherwise you'll either damage something or deadlock the stack when updating it later, it can't figure out what's deployed on it's own and maintains its own state that can be different from the real state. We had to stop using templates at all and just store a copy of each template in our local git repo.
* If you have more than 100 stacks searching the list of stacks requires clicking a handful of times on the "show more stacks" button before it'll show the one you typed in
* Stupid slow, esp. compared to Terraform
* Doesn't delete Route53 DNS records even after saying it does in the log outout
* Can break ELB configurations, such as sticky sessions and cause outages
* Doesn't actually support deploying all AWS resources, SNS/SQS perms/rules aren't complete for example.