callahad

61 ms·

601.
by callahad 10y ago
Update: Looks like the <kbd> tag dates to the first draft of HTML 2.0 in 1993, where it was defined as "in an instruction manual, Text typed by a user." ( https://tools.ietf.org/html/draft-ietf-iiir-html-
602.
by callahad 10y ago
My reading of it is that: 1. <kbd>___</kbd> means "literal user input" 2. <kbd><kbd>___</kbd></kbd> means "this specific, atomic keypress" 3. <kbd><kbd><s
603.
by callahad 10y ago
I believe your kbd example is incorrect. You suggest > To save, press <kbd>Ctrl + S</kbd>. But the spec (both W3C and WHATWG) suggests that individual keys should be nested inside an outer <kbd> tag: "When t
604.
by callahad 10y ago
Isso ( https://posativ.org/isso/ ) is a possible alternative that only requires Python and SQLite.
605.
by callahad 10y ago
Most current WebAssembly compilation paths produce asm.js as an intermediate artifact. In the near term, backwards compatibility should be relatively simple: save both and load the asm.js code as a fallback.
606.
by callahad 10y ago
Well, you can run it and it does things, which effectively puts the question of "real" or "satire" into our hands. At this point, it is what we make of it.
607.
by callahad 10y ago
Speaking solely as a skeptical third-party: > What is the process to be added? 1. Sign a Contributor License Agreement granting relevant copyright and patent licenses to Google so they can redistribute your contributions to AMP. You al
608.
by callahad 10y ago
> AMP is not a ranking factor That language is misleading: only AMP articles are eligible for "Top Stories" placement, which means non-AMP results are completely excluded from the most prominent ranking on SERPs. AMP may not
609.
by callahad 10y ago
That's how it should work, but now how it actually works. From https://github.com/ampproject/amphtml/issues/534#issuecommen... : > "AMP is an evergreen JavaScript library. We will not allow u
610.
by callahad 10y ago
Google, and solely Google, control what tags are allowed on AMP pages, and thus what advertising and analytics companies are allowed to compete on AMP sites. AMP also requires that every page depends on external JavaScript sourced from Goog
611.
by callahad 10y ago
AMP is not a standard. It is a Google product with developer documentation, but that documentation does not make it a standard any moreso that Twitter having an API makes it a standard. AMP allows your websites to rank better / more
612.
by callahad 10y ago
There's a recording of this keynote at https://www.youtube.com/watch?v=3dDGkLHOldw There's also a more in-the-weeds braindump of where Persona went wrong at https://github.com/portier/portier.
613.
by callahad 10y ago
Barring unforeseen complications, U2F support should land in stable Firefox this year. The tree of bugs to follow is rooted at https://bugzilla.mozilla.org/show_bug.cgi?id=1065729
614.
by callahad 10y ago
That sounds like a bug worth addressing.
615.
by callahad 10y ago
It's possible that the FIDO Alliance, with enough support from large enterprises, will be able to compel browsers into implementing something native. Otherwise, it feels like anything in this space will need to bootstrap itself by, fir
616.
by callahad 10y ago
We're trying to bring Mozilla itself out from behind the shadow of Firefox, almost the inverse of when RIM renamed themselves Blackberry.
617.
by callahad 10y ago
I believe this project was funded by the Mozilla Corporation (MoCo), which is a separate, wholly owned subsidiary of the non-profit Mozilla Foundation (MoFo). You can read more about MoFo at https://www.mozilla.org/en-US&#x2
618.
by callahad 10y ago
Predominantly, though it is based on your locale. Some folks (including en-US) get Yahoo, others Baidu, Yandex, or Google.
619.
by callahad 10y ago
Respectfully, I'd rather not wade into that on HN. It's in the past, and there's a great deal of nuance that would be hard to convey here. I'm confident that Mozilla is in a good place today.
620.
by callahad 10y ago
> Why isn't "Let's Encrypt" a Mozilla project? ...because it already was? The whole thing started as a collaboration between Mozilla and the EFF. Its success allowed Josh to spin it out into an independent organizatio
621.
by callahad 10y ago
The formal announcement is now live at https://blog.mozilla.org/opendesign/arrival/
622.
by callahad 10y ago
The video leaked ahead of the formal announcement (which is coming in the next hour or so).
623.
by callahad 10y ago
Thank you for keeping the Persona dream alive. It turns out that being open source wasn't sufficient for Persona to be able to be continued by a third party: we accidentally baked in some intractable centralization, and the code was to
624.
by callahad 10y ago
1. In hindsight, I firmly believe that Persona's emphasis on browser integration was a red herring, and directly resulted in an architecture that was intractably centralized. 2. We committed massively to Firefox OS relative to our si
625.
by callahad 10y ago
I found this article from the Fastmail folks to be rather enlightening, and being Fastmail, you know it's meticulously correct: https://blog.fastmail.com/2016/12/24/spf-dkim-dmarc/
626.
by callahad 10y ago
It's true that the Web can't do everything yet, but bringing in gpgpu is moving the goalposts. For media, ORBX.js was able to hit 1080p60 with 12bpp on smartphones three years ago, using a codec hand-written in portable JavaScript
627.
by callahad 10y ago
The next release of Firefox (in two weeks) has native support for FLAC, and in the near future (by the end of March) I'm optimistic that WebAssembly will allow for efficient third party implementations of codecs. We'll get there..
628.
by callahad 10y ago
Servo! ( https://servo.org/ ) You get to watch as a browser incrementally adds support for the web from scratch, something that hadn't previously happened this century. I'm also rather bullish on Firefox, hence my s
629.
by callahad 10y ago
While literally true, Rust's benefits make it easier to write safe, parallel code, which often directly translate into greater speed and efficiency.
630.
by callahad 10y ago
Core APIs for common functions (intercept these network requests, inject these stylesheets, etc.) are being standardized so you don't have to reinvent the wheel on every damn browser. Browsers can also freely implement additional, non-

More ›