jjjensen90

The odd thing is that in most countries the age of consent is below (sometimes significantly below) 18. So we’ve got strange mixed signals.

Commonly electrical systems and/or the battery itself in ICEs cause unattended fires.

I think your response is emotionally-charged and mixes feelings with data and anecdotes, which is unhelpful in a complex discussion of a sensitive topic, so I hesitate to engage further, but…

I’ve reviewed much of the existing data on minor-attracted persons (which is scant). The problem is that the samples are heavily biased towards including individuals who are caught or self-admit for care, which is not a very good representative sample. As a few of the studies and articles you posted mention, there was little study done until very recently. You also make the leap without supporting data that this system would catch those most likely to offend. Generally I would say the data is insufficient to conclude in any direction other than dumber people get caught doing crimes at a higher rate than smarter people.

Lastly, I have some serious doubts about your expertise in mental health and the study thereof from your use of “mentally retarded” and “retardedness”. You should know for future discussions that the clinical terminology has shifted to “intellectually disability”.

This is not true and a harmful generalization. There are dumb people of every type. There are probably smart people you respect that engage in CSAM and are minor-attracted. This kind of privacy invasion will only net a tiny section of that population, as most know that lack of caution is life or death.

I've commented on it before, but I have to say again, the Timescale Helm charts are by far the best way I've ever seen a database run in Kubernetes, and actually from an operations, backup, and scaling perspective they are the best database management experience I've had period. Huge fan, always enjoy talking with Feike, and keep up the great work Timescale team.

I brought timescale (a postgres extension that brings time series to postgres) to my current IoT job, and it has been the biggest engineering win of my career. The tooling, community, extensions, and quality of postgres + very high performance inserts + reads has reduced costs for the business dramatically versus the previous cassandra + sql server setup. We have tens of billions of events in multiple timescale hypertables, with many thousands of inserts per second running on r5.xl nodes in k8s (4 vcpu, 30gb ram) and they don't break a sweat.

So yeah, it's "good enough".

I brought Timescale to my current job, and I have to plug their Helm charts. They have made deployment, backup, scaling, and config so easy on k8s for Timescale. Probably the best postgres chart that exists, period. Great work TSDB team.

Yes, there was a midterm held in 1918.

If you're referring to the WFH situation staying with us forever, it definitely will not. Things may change somewhat, but in discussing WFH with a variety of execs who employee tens of thousands of engineers collectively, there is a very strong majority of engineers who would come back to the office tomorrow if able.

Again referring to Go's imperfect but interesting handling of this problem, the style in Go would be:

  data, err := open("/var/foo")
  if err != nil....

In fact, the compiler will make you deal with both values after assignment unless you explicitly ignore one of the return values.

Though I don't think it's perfect, languages like Go that treat errors as simply another type and you check as a return value do get closer to treating errors and success symmetrically versus an exception throwing and typing system like some other languages.

It's incredible the quality you can get in that price range. I bought a PRS SE Custom 24 for $700 and it is like a museum piece compared to what $500-700 would have bought when I was starting out 20 years ago. Absolutely awesome.

I realize you've made a weak straw man argument here, but there are important distinctions that need to be made in discussions about platform/user base moderation. While there are classes of people protected from discrimination by civil rights laws, what is not protected is discrimination or refusal of service for customers based on what they do rather than who they are. Banning someone for cheating, harassment, circumventing moderation, etc is not comparable for banning users of a certain race, and even attempting to equivocate them is a weak argument.

I run multi terabyte, billions of rows HA postgres in kubernetes using a helm chart and Patroni (baked into the chart), which uses the native k8s API for automatic failover and pgbackrest for seamlessly provisioning new replicas. It's a single helm chart and is by far the easiest DBA I've ever done in many years.