from the looks of it, his CTs are mis-reporting/double counting. A very common problem with tesla installs. My solar roof had the same issue initially, and electricians really thought it was generating more then the rating of the inverters, until I fixed it (software controlled). With 3 inverters he can't have more than ~23kw AC (assuming each is 7.8kw, which is the largest inverters tesla had at the time). My solar roof is a bit smaller (~21kw), in a similar region, but the daily peaks are slightly less than half of what he was showing.
>My solar roof had the same issue initially, and electricians really thought it was generating more then the rating of the inverters, until I fixed it (software controlled).
What was the software fix? Was there some config that wasn't set correctly?
yeah exactly, had to go into "installer mode" and configure the CT that's on a secondary powerwall, so it wouldn't count that value as part of the generation (forget the exact cryptically named option). Otherwise it considered energy pushed towards that powerwall as "additional energy in the system", and since the grid ct didn't show it was coming from there, it was assuming that the generation must be coming from solar. Or so it seemed.
interestingly, when the psuedo 'irc' connection is created, the user's ip address looks to be intended to be the source address..but because someone forgot that there's an akamai proxy in the middle (and didn't adjust for X-Forwarded-For or whatever), the ip you actually get is the akamai ip (its also in the source)
<script>
var USER_IP = '23.62.236.92';
Was curious since the ip appeared real, but wasn't mine.
It's not unheard of for the fbi to operate (and pay for) the infrastructure to facilitate and even promote piracy. See "operation bandwidth" where they essentially did just that for 2+ years. Granted that effort was targeted somewhat higher up the food chain then your average home user trying to download a copy of the latest overhyped blockbuster.
Sooner or later I'm going to need to know the name of the company (unless they want to hire me sight unseen). What stops me from circumventing them then?
I think this is a ridiculous fear, and I've often told recruiters 'no thanks', because of this practice. I don't know you, you don't know me. If you don't want to trust me w/ the details which can directly impact both our lives (my potential future employer, your potential commission), why would I trust you with the details that impact just my life (my future career)?
To set up the interview, the recruiter sends your contact details to the company. Once that happens, as far as that company is concerned, the recruiter owns you.
So ~650M daily active users..4PB of data warehouse created each day, that means ~7MB of new data on each active user per day. Given that its data warehouse, I'm going to guess its not images, seems like a lot to me. I guess it shouldn't surprise anyone that every interaction on and off the site, is heavily tracked.
A lot of that data is duplicated to allow for efficient querying or transformation. It often is too slow to process the data as it comes in, so an initial process will write the data in a raw form, and some other process might select a subset of the data to process, and then submit it in an "annotated" form (filling in, say, the AS number of the client IP). Another process will run later in a batched fashion and perhaps annotate the full set of information and summarize it into a bunch of easily-queried tables.
A lot of that data is also not tied to individuals either - for example the access logs for the CDN (which, being on a different domain by design, does not share cookies so is not attached to an account) even reasonably heavily sampled is probably tens of gigabytes a day, and is rolled up into efficient forms for queries in various ways. A lot of it isn't even about requests coming through the web site/API - it may just be internal inter-service request information, or inter-datacenter flow analysis, or per-machine service metrics ("Oh, look, process A on machines B through E went from 2GB resident to 24GB in 30 seconds a few seconds before the problem manifested").
(Not that it makes too much of a difference at this scale, but it is closer to 860M daily actives.)
Yup, EC2 instances should be issuing a gratuitous arp on startup. I've seen the same thing on subnets with a lot of DHCP churn due to constantly rebooting embedded devices.
