It was in the era when everything walk on the DOM tree, not streams.
Streaming is not supported until later version.
3,605 karma · joined May 3, 2018
Streaming is not supported until later version.
For end-user application, it's a mess. You can't compile once and run everywhere.
LSB (Linux Standard Base) tried to that and failed.
flatpak/Snap/AppImage all tried to that, each have its own set of problems.
Better integration for mainstream, sure. but at the end we have less choice.
No. You need to audit for correctness in additional to safety.
locale != encoding.
Try sort a phone book with tr_TR.UTF-8 vs en_US.UTF-8
not just next token.
This is like: tell it a random sentence in the book, it will give you the next sentence 42% of time.
They know your government id when you subscribe to their service.
CloudFlare, otoh, never have your identity. They only have the metadata
It is trivial to hire someone in Asia to do these kind of fake reviews
Yes, but no.
If you know floor is wet, you cant let people in
If you know insider information, you cant trade.
If you know sb have disabilities, you must provide assistance.
If you give immunity for these, the lawyer will ensure the one in the act never know those information. OTOH, if we hold this to a person, someone can be hold accountable for some systemic communication failure
With so many new, markup words everyday on social media ("enshittifcation" - i am looking at you), autocorrect can be annoying.
Keeping computer commands in notes also prompt me to turn off autocapitalisation
Once they are off, typing in lowercase is just natural
In additional to youtube.com, in many cases, they redirect to many countries specific domain as well (e.g google.co.jp)
Youtube is common enough that they want to login on the same flow
> If you want to use GeoIP, fine — but only for currency, shipping, legal stuff, never for language
Many EU country have more than one official languages.
Most previous colony is bilingual.
This. Many trival changes breaks API. This is not ideal for library developers.
You can argue it is broken already, but this is forcing the breakage onto every api caller, not just some broken caller.
Maybe autofix as we type, or autofix when it save the document / advance to next line.
> With Advanced Data Protection, the number of data categories that use end-to-end encryption rises to 25 and includes your iCloud Backup,...
> iCloud Backup (including device and Messages backup) (3)
> (3) .... Advanced Data Protection: iCloud Backup and everything inside it is end-to-end encrypted, including the Messages in iCloud encryption key.
Type checking in compile time is do-able with templates, even better with constexpr.
The problem is, of course, each library have its own set of rules and they won't interop with each other.
They have been taking similar role before the industrial revolution.
[1] https://www.postgresql.org/docs/current/warm-standby.html [2] https://www.postgresql.org/docs/current/logical-replication....
Just feeling uncomfortable putting more data into DNS. DNS is not encrypted. DNSSEC is easy to bypass (or break way too often that nobody want to enforce it).
-- but these are not w3c's problem.
Unpopular opinion: There are no privacy-preserving way for "fraud mitigation".
Either you accept fraud as cost to run business, or do away the privacy. Most business owner don't want the fraudulent user to come back, ever. If we value the privacy of user, we need to harm some business.
Scanning them are resources intensive. The choice are (1) skip scanning them; (2) treat them as malware; (3) scan them and be DoS'ed.
(deferring the decision to human iss effectively DoS'ing your IT support team)