afiori

> Why would the US and Israel resort to X?

> That’s how you end up with wide scale civilian deaths.

Has Israel ever shown restraint wrt civilian deaths?

Then they would drop the connection with esni

Agree, but a significant point missed in the article is that of data vulnerability. with E2EE the company db is useless to an external attacker.

For some companies (eg facebook, google, tiktok) i would be mostly worried about the company itself being untrustworthy. For others I would be mostly worried about the company being vulnerable.

because most implementations are not going to be like that.

Also a password could be the passkey, the passkey protocol is basically a way to send to a server an authenticated public key. The client could deterministically convert passwords to key-pairs and authenticate with those

Imo the need to register an app with an oauth provider is a plus

not really in-topic but constant-time crypto primitives are considered hard for any compiled language with a lot of optimizations

I am pretty sure that the issue is that they either admit to being so l stuck as a vassal beholden to Google, or they pretend to be enterprising and forward looking with many promising projects

Without a lot of discipline it is very easy to end up with a css with lots of unclear and hard to guess effects. Eg consider the case of <A type=1><B><A type=2></A></B></A> where A and B are complex templates. Any selector with the " " operator on A risk expanding to the inner A even if it was intended only for the outer. Similarly a :has selector might catch a descendant of the wrong element.

@scope fixes a lot of this, but it is a complex problem. With tailwind you mostly have to worry about inheritance

Even ignoring all non renewable consumption in growing the corn to be turned into ethanol it is still going towards an incredibly polluting infrastructure.

While each solar panel is a small step towards more and better electrification

I enjoyed the pragmatic historical definition of OOP given in https://www.youtube.com/watch?v=wo84LFzx5nI where essential it can be seen as subtype polymorphism

The premise of the article is the desire to avoid accidental collisions, especially from newly installed system binaries.

In such cases you might get errors like sl being both a version control system and the steam locomotive

Probably prefix notation would work better, but I suspect that there would be a stronger effect from predictable and reasonable declinations/suffixes/prefixes at a grammatical level.

IIRC the methane is produced at launch site with considerable pollution

Sure but if it was a good idea we could do it on earth too and datacenters could stop gurgling a city worth of water

This should depend on the frequency of the switching, if it is every few seconds it should behave sorta the same

Neither it means that McDonald's should aspire to be a chef

The paradox is about the set of all sets that do not contain themselves, or a theorem that such a set does not exist.

In the context of the paradox you need to call it a set, otherwise it would not be a paradox

Vibes are a perfectly solid ground to refuse to engage with something.

Things like this combined with the countless ways to hide "feature flags" in a giant codebase makes me feel that anything less than "the entire app was verified + there is literally no way to dynamically load code from remote (so even no in app browser) + we checked 5 years of old versions and plan to do this for the next 5 years of update" is particularly meaningful.

Still very important but my issue has never been with zucks inability to produce solid software, rather in its intentions and so them being good engineers just makes them better at hiding bad stuff.

The thing that make the formula click to me is that it is written as a thriller.

By the last 10% of the book/serie he has created a problem you are 100% sure is insurmountable but by the last 5% you realise how small hints through the story could be composed to create a solution.

in the eu i think this is significantly less common

then you are not using any vpn service marketed or provided in the UK[0]. if you were to sell access to your VPS to others then you would have to do age verifications on them maybe.

[0] maybe it is still illegal, IDK, bu likely due to other laws (eg a generic "it is illegal to use workaround for X")

then you are not using any vpn service marketed or provided in the UK. if you were to sell access to your VPS to others then you would have to do age verifications on them maybe.

maybe it is still illegal, IDK, bu likely due to other laws (eg a generic "it is illegal to use workaround for X")

i don't think so, it is not provided as a service. if you provide vpn service people can connect to from their router then you need to do age verification before giving them a key/password to connect to the server

The email sent from your own separate server will fail basic dmarc/SPF/dkim validation the email sent by their own servers likely will appear legitimate

In my native language the literal translation of possibly has a distinct preferably meaning but I feel that in English it does not.

It might be a victim of polite/ironic/sarcastic influences to language that turns innocuous words into contronyms

It is a free non-copyleft licence, it is the expected result that derivatives are not similarly free

My superficial understanding is that arm does not prevent from sharing implementation details of your own design but most chips also license a starting implementation that has such limitations. So the end result is often more restricted than the ISA licence some would require

48/56 bits numbers would be useful in many circumstances