bgentry

European honeybees, which are used in most of the world, have no such defense mechanism and would indeed be helplessly slaughtered by these hornets.

I’d definitely advocate watching some YouTube footage about these creatures, they’re fascinating.

This topic inevitably comes up on every HN 1Password thread.

My workaround for this is to go out of my way to make sure the iOS app is closed before I resume playback on my desktop.

AirPlay 2 has been out for years.

The lack of criminal prosecutions is more of an indication that District Attorneys aren't doing their job (or that the reality of their job is that they are disincentivized from prosecuting criminal cops).

If you believe the experts that are well-versed in this area, this is not how it works in practice. The Wikipedia article covers a lot of the controversy around this doctrine: https://en.wikipedia.org/wiki/Qualified_immunity#Objections_...

Here is an example of a man in Grand Rapids, Michigan, who was brutally assaulted by undercover officers because they believed he was somebody else. Take a look at how difficult it has been for him to get any recourse for a blatantly obvious abuse of power (6 years and counting): https://twitter.com/AaronParseghian/status/12701818156644966...

An officer that chokes a nonviolent person to death for 9 minutes straight, or an officer that kicks an unthreatening protester in the face, or that fires rounds at people peacefully standing in their own home's doorway, or one that knowingly attacks journalists, should be first and foremost be prosecuted and put in jail, and also be subject to civil suits for their actions.

Unfortunately there is a significant structural disincentive for DAs, prosecutors, and Attorneys General to pursue such cases except in the most egregious high-profile incidents so justice is rarely served. Eliminating qualified immunity allows individuals some recourse to sue the perpetrators in these incidents, but it is no replacement for prosecuting and putting them in jail.

Its text is quite straightforward, essentially saying that judicial officers are liable for the violation of a person's rights.

However the concept of "Qualified Immunity" is a Supreme Court invention which began to be applied in the late 1960s, and which today effectively shields police from any meaningful (civil) liability as originally defined by the law. It's hard to square the modern interpretation and its effects with the clear language in the statute, yet here we are needing to pass a law that effectively says "yes this law actually means what it says".

https://theappeal.org/qualified-immunity-explained/

IANAL.

I tried it again right after, and the reminder said "call FRIEND_NAME".

I don't think there was any previous conversational context or anything like that. Hard to fathom how that could happen.

Sometimes you can ask a question and watch it be perfectly transcribed in real time, but then receive a nonsensical answer from it. Ask the exact same question immediately after on the same device, transcribed exactly the same way, and get the correct answer.

Where does such unpredictability come from? How can Siri transcribe the words correctly but fail to deliver the right answer?

Its key findings:

-Zoom documentation claims that the app uses “AES-256” encryption for meetings where possible. However, we find that in each Zoom meeting, a single AES-128 key is used in ECB mode by all participants to encrypt and decrypt audio and video. The use of ECB mode is not recommended because patterns present in the plaintext are preserved during encryption.

-The AES-128 keys, which we verified are sufficient to decrypt Zoom packets intercepted in Internet traffic, appear to be generated by Zoom servers, and in some cases, are delivered to participants in a Zoom meeting through servers in China, even when all meeting participants, and the Zoom subscriber’s company, are outside of China.

-Zoom, a Silicon Valley-based company, appears to own three companies in China through which at least 700 employees are paid to develop Zoom’s software. This arrangement is ostensibly an effort at labor arbitrage: Zoom can avoid paying US wages while selling to US customers, thus increasing their profit margin. However, this arrangement may make Zoom responsive to pressure from Chinese authorities.

Sign in with Apple works natively on iOS, macOS, tvOS, and watchOS. And it works in any browser, which means you can deploy it on your website and in versions of your apps running on other platforms.

So it at least sounds like it can be used anywhere with a web login flow. Although the docs say this must be accomplished using their JS library, as opposed to a standard OAuth2 flow of some kind: https://developer.apple.com/documentation/sign_in_with_apple

Dupe of https://news.ycombinator.com/item?id=22735746

Distru is a software platform for the cannabis supply chain. Our product helps cannabis companies manage production, sales, invoicing, and shipments, automating compliance with complicated state regulations that require real-time inventory tracking gram-by-gram. We are growing rapidly with over $700M in transactions per year passing through our platform, and we're uniquely positioned to define trade in the growing cannabis industry.

We are a lean 20 person engineering-focused team that includes early engineers from Opendoor and Heroku. We are hiring experienced engineers to help take our product to the next level. We love product-minded engineers that can own a feature across the frontend and backend, even if they're stronger at one side of that. Our tech stack is built from the ground up on Elixir/Phoenix, Postgres, React/Redux, and GraphQL.

After bootstrapping ourselves to profitability, we raised our seed round with Felicis Ventures, Village Global, Global Founders Capital, and notable angel investors including Elad Gil, Katie Stanton, and Avichal Garg: https://techcrunch.com/2019/06/03/distru-a-maker-of-supply-c...

Please apply at https://distru.com/careers and mention Hacker News!

- Some iPhones in this generation began randomly shutting down as their batteries aged.

- While looking into this, Apple determined it happened because certain aged batteries could no longer deliver enough current to sustain peak workloads (computers use more current when performing more intensive tasks). This is probably due to Apple underprovisioning the battery capacity in this generation, but that's not something they could fix in existing devices.

- Apple added a mechanism to detect when these random shutdowns occurred on a specific device due to insufficient power from the battery.

- Once the random shutdown had been detected on a specific device, that specific phone would instead throttle its CPU when the system was under heavy load to prevent the random shutdown from occurring.

In short, your phone was not affected unless your battery had already degraded and was experiencing power-related random shutdowns. The changes Apple made to deal with this were an unequivocally user-friendly change to work around a hardware shortcoming and keep peoples' phones working well for longer than they otherwise would have.

The mistakes Apple made were:

- Designing the phone hardware with barely enough battery capacity, such that some moderately old phones might not be able to keep working properly when the batteries decayed.

- Not being transparent with the hardware design flaw above, such as proactively replacing any customer whose device was being affected by this flaw while still under warranty.

- Not going far enough with the software changes to initially add something like the battery health info they later added in response to this PR fiasco.

That's about it, I think?

Distru is a software platform for the cannabis supply chain. Our product helps cannabis companies manage production, sales, invoicing, and shipments, automating compliance with complicated state regulations that require real-time inventory tracking gram-by-gram. We are growing rapidly with over $700M in transactions per year passing through our platform, and we're uniquely positioned to define trade in the growing cannabis industry.

We are a lean 20 person engineering-focused team that includes early engineers from Opendoor and Heroku. We are hiring experienced engineers to help take our product to the next level. We love product-minded engineers that can own a feature across the frontend and backend, even if they're stronger at one side of that. Our tech stack is built from the ground up on Elixir/Phoenix, Postgres, React/Redux, and GraphQL.

After bootstrapping ourselves to profitability, we raised our seed round with Felicis Ventures, Village Global, Global Founders Capital, and notable angel investors including Elad Gil, Katie Stanton, and Avichal Garg: https://techcrunch.com/2019/06/03/distru-a-maker-of-supply-c...

Please apply at https://distru.com/careers and mention Hacker News!

However it hasn’t actually saved $1M, only saved a small amount over the alum that probably would have otherwise saved them from the $1M upgrade :)

While the Water Reclamation Facility in Bozeman found the chemistry worked, the logistics of transporting the liquid brewery waste there are too expensive for now. If regulations get stricter, the plant may consider this approach in the future.

So did they save $1M using this approach, or are they not even using it after all?

If you wanted to discuss GCP's likelihood of sticking around, this top story from earlier this week would have been an appropriate place: https://news.ycombinator.com/item?id=21815260

You only have to involve state in 1 request every 10-15 minutes upon refresh. All other requests can be done without having to check for revocation. This is a pretty nice real-world tradeoff.

You only get this benefit if you’re doing everything in a single Postgres database. By the time you outgrow that setup, you may as well move to a more dedicated job queue or something built on Redis, because you’ve already lost the benefits of having a single system.

I suppose you could maintain the queue in a separate Postgres database, but without sharing ACID with the app I’m not sure What you’d gain vs another system.

* If the entire worker process dies, then it will lose its Postgres connection which is holding an advisory lock on the jobs being worked. This releases those jobs to be worked by another worker. I don't recall how the built-in retry & back-off mechanisms work in this scenario. This advisory lock is indeed held for the entire time the jobs are being worked on, but only from a single supervisor connection (rather than one connection per job).

* If the job thread crashes, the worker supervisor catches this and the job is marked for a retry at a later time.

[1]: https://github.com/que-rb/que/blob/master/lib/que/migrations...