I cannot boost this enough.
Anyone making the arguments Apple made in this case needs to be tarred, feathered, beaten, and fired. Out of a cannon. Into the sun.
"In what appears to be a computer glitch the Home Office thought he was a one-year-old child."
Is there also a kibitab? And does that mean to have 1024 tabs or one with mraw.org open?
@liw 0.018, but i risk hitting 0.050 on any given workday, which is demonstrably too many.
I'm currently at 0.015 kilotabs in this browser.
You still can weigh in on the license approval, btw. The license is not approved until the Board officially reviews it. That's scheduled for our next board meeting, happening this Friday, Feb. 14.
The Cryptographic Autonomy License is one step closer to being approved by the OSI board, having been approved by the review committee. http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2020-February/004660.html
I think this is a big mistake, though I blame myself partly for not weighing in previously. I will be spending time over today and tomorrow writing why I think this is "a big mistake with good intentions but potentially disastrous results"
The @OpenSourceOrg License Committee has made a recommendation to approve the Cryptographic Autonomy License, Beta 4 https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2020-February/004660.html
In an international organisation, I find it a best practice to express timestamps using explicit day of week, unambiguous date (either YYYY-MM-DD or writing out the name of the month), and times in both UTC and local time, with the two time zones expressed explicitly, and possibly both using a common name and a time zone offset from UTC.
For example, right now it is Monday, 10 February 2020, and the time is 16:20 UTC or18:20 EET (UTC+2).
It's a bit repetitive, but that helps notice mistakes.
Fingerprint casts used to circumvent Aadhaar https://mastodon.social/@jairajp/103634535531015741
Fingerprints are weak security; with modern 3d printing are trivial to fake. (That also has some, but different, implications for evidence considerations too; most notably, fingerprints can be planted.)
The "server-side rendering" trend is great (aka: serve a web page), but when the goal is progressive enhancement it's easy to mistake the technicalities for an end result.
Serving HTML and doing something in JS is not "progressive" nor "enhancing" if the HTML is unusable by itself, with visible-yet-nonfunctional UI elements, requiring seconds of interaction-blocking JS execution before it is scrollable and clickable.
Blog post by @adactio