I think that for this sort of _interactive_ application, there's no avoiding the need to manage scroll/history.
2,244 karma · joined January 26, 2012
dan@tillberg.us
meet.hn/city/40.1672117,-105.101928/Longmont
I think that for this sort of _interactive_ application, there's no avoiding the need to manage scroll/history.
Sure, it may be _possible_ the account is acting "autonomously" -- as directed by some clever human. And having a discussion about the possibility is interesting. But the obvious alternative explanation is that a human was involved in every step of what this account did, with many plausible motives.
Curl-bash without hash-checking from a four-month-old domain with full k8s cluster access? All the identities connected are brand new, including the brand-new HN account that posted this. There are four commits in the repo, and three are back-dated to exactly 1 year ago.
But this "semi-monopolistic trade union" not only inflates their wages (which maybe that's a good thing), but it also harms the lives of the population they purport to serve. Many (most imo) people in the US simply cannot afford the monopoly's prices, and the monopoly has little incentive to innovate. This cartel of doctors actively prevents lower-cost, more efficient alternatives from coming to market.
Presidential pardons do not limit or prevent private civil lawsuits.
I suggest in general using function scoping to drive the lifetime of contexts, etc. This works also for defers and tracing spans in addition to the canonically shadowed `ctx` variable.
There is an old issue in the tracker proposing changes to alleviate this: https://github.com/golang/go/issues/34510. The original author (bcmills) of the errgroup package shared insight into the design choices/tradeoffs he made.
They _are_ smart people. There's more to the differences in perspective than "lib smart, maga stupid".
Have you tested whether you can receive email directed to firstlast@gmail.com? Perhaps theirs is really firstlastt@gmail.com and all their contacts "correct" it.
This is I guess where the analysis gets fuzzy, where honest assessments may vary widely.
My gut instinct is that enriched uranium blown up underground (assuming it was even there) would take at most around a year to recover, by turning the site into an open-pit uranium mine. The product wouldn't need to be re-enriched from scratch, as simpler mechanical filtering could probably isolate much of the already-enriched uranium.
But perhaps it would be much harder.
Is it even possible to "destroy" enriched uranium? It would seem to me that the most one might achieve by blowing it up with bombs is to spread it out a little bit.
> Subaru may collect the following personal information about a consumer:
> Categories of personal information:
> Identifiers: Consumer records, Commercial information, Internet or Other Electronic Network Activity, Audio recordings, Vehicle geolocation, Professional or employee-related information, Inferences, Sensitive personal information
> Categories of sources from which the personal information is collected: Retailers, i.e. authorized Subaru dealerships , Provided by consumer or vehicle, Third parties
> Business or commercial purpose for which Subaru collects or sells personal information: To provide services to the consumer, To market goods and services to consumers, To provide marketing by third parties for third party goods and/or services, To comply with legal obligation
> Categories of third parties with whom the personal information is shared: Business service providers, Contractors, Retailers, Corporate parent and affiliates, Third party providers of goods and/or services, Entities required to comply with the law
> Categories of personal information sold: Identifiers for third party marketing of goods or services., Consumer records for third party marketing of goods or services
> Categories of personal information disclosed for business purpose: Identifiers are disclosed to service providers, contractors, and third parties., Consumer records are disclosed to service providers, contractors, and third parties., Commercial information is disclosed to service providers, contractors, and third parties., Internet or other electronic information is disclosed to service providers, contractors, and third parties., Vehicle geolocation is disclosed to service providers., Inferences are disclosed to service providers and contractors., Sensitive personal information is disclosed to service providers and contractors.
While AWS egress pricing gets a lot of attention, I think that the high cost of inter-AZ traffic is much less defensible. This is transfer on short fat pipes completely owned by Amazon. And at $0.01/GB, that's 2~10X what smaller providers charge for _internet_ egress.
How many bits of actual decision is going on here, as compared to the period of time that decision applies to?
For example, if a person decided once per second whether or not to go for a walk, that could be 1 bit per second. But if that person is constantly transitioning back and forth between walking and not-walking, we could consider their behavior pathological. Instead, for most people, the information density of these decisions is quite low, i.e. the per-second decision bits are very compressible.
Personally, I only decide whether to go for a walk (or not) _at most_ once every few minutes. Even if we add in bits for "where" and "precisely when" and "how long", I think we're still at just a small fraction of 1 bit per second.
Are you able to cite any evidence for this sort of conspiracy, or is this mainly conjecture? My search came up short. While one can certainly imagine it taking place, particularly in smaller groups, I expect there are both federal and likely also state laws that would make such activities illegal. At the very least, it would seem hard to hide at scale.