By 2028, not 2008.

My money is on the technology behind a flux capacitor maturing before Helion’s fusion tech.

Thanks - corrected.

There are copy/paste buttons on Gboard, but they're kind of hidden. Press the 4 squares in the top left of the keyboard and select Text Editing. You get arrow keys, a button for toggling select, and cut/copy/paste. In a way it's like switching out of insert mode in vim.

The language is Dutch, the collection of dialects spoken in the Flanders region is Flemish. If you're feeling charitable, you can refer to it as a language variant.

Here is the constitution of Belgium: https://www.senate.be/doc/const_nl.html Articles 2 and 3 define the Flemish (Vlaamse) community and region. Article 4 defines the language areas and specifically mentions Dutch (Nederlands), not Flemish.

See also: the Dutch Language Union (https://en.wikipedia.org/wiki/Dutch_Language_Union) being founded on a treaty between the Netherlands and Belgium.

For a language that's derived from Dutch but now its own proper language, try Afrikaans.

The big difference here is that the bloom filter implementation runs entirely client-side. It saves a roudtrip per search.

You may have Gateron Clears, which are lighter than Gateron Browns. Gateron Browns are basically equivalent to Cherry MX Browns, but Gateron Clears are entirely different from Cherry MX Clears. This has tripped me up more than once.

Regardless of how the court case turns out, I can't see this whole affair ending well for Grsecurity. They need good PR with the exact people that are likely to side against them in this matter.

That's how the Snapchat Spectacles work: one side contains the camera, bluetooth and other electronics, the other side contains the battery.

Here's one to add to your list: https://github.com/lucy/tewi-font

The trick of entering a dummy username and password, which is then modified in the post request sounds a whole lot better than playing clipboard roulette or messing with the DOM.

This sounds pretty cool! What I'm wondering, is how they are intercepting the POST request and at what level?

I have not read yet, but my guess is they are taking all HTTP requests from the page and looking for their dummy username/password and replacing that. Not every login form (though we would like it) is in a form tag w/ an explicit action. Some SPA's will do an AJAX post of JSON w/ the credentials embedded (which is bad practice, but happens).

Actually, the more I think about it, I don't think I want this extension to do that...how does it know how long between when the fake fields are entered and when I press submit? Now I am going to read the paper...

Edit: Yup, the extension intercepts all network traffic even before you click submit. If you, e.g., hash on the client side this password manager will break. If you never click submit, this extension will continue to read all HTTP bytes from the page going back to the server it seems, looking for some strings...not sure the perf implications of this.

Out of curiosity, why is an AJAX post of JSON with credentials embedded bad practice?

Not bad practice from a security perspective per se, just annoying to users that don't want JS, or like the non-password fields to support their browser's features like autocomplete, etc. Granted if it's a SPA, some of that usability shop has sailed. And while any AJAX post is secure normally, many JS implemented login solutions open themselves up to CSRF and other problems.

You can have the form submit to a real address when js is disabled, and disable the form's behavior when js is enabled.

FYI Service workers can intercept and modify requests.

Only for the same origin they were installed on. So a generic solution like this one wouldn't really work as a service worker.

Also it is quite common that extensions ask for to be able to read all traffic. What would be stopping other extensions from being jerks?

Are they using dummy parameters in the request so they can substitute correctly?

> The trick of entering a dummy username and password,...

vim-airline requires you to use a patched font that replaces certain little-used unicode characters with shapes that airline uses to draw its UI. Specifically, those < and > looking dividers in the airline statusline. Although it's totally possible to use airline without this and it will look only slightly less fancy.

They're not little-used unicode characters. They're code points in the Private Use Area, which is an area of Unicode that's explicitly set aside and will never be assigned to "real" characters, specifically so they can be used for custom things. vim-airline's use of the PUA for its custom glyphs is quite appropriate, it's just annoying that it requires a patched font.

Incidentally, the Apple glyph (, or ⌥⇧K on macOS), is actually in the PUA as well (in fact, it's the very last PUA codepoint, U+F8FF). Which is why it may not render correctly in fonts that don't ship on macOS. Anyone reading this on Windows, Linux, or Android probably won't actually see the apple character.

My understanding is that the *lines are using custom glyphs for box drawing characters along with icons in the PUA. All legit use of Unicode.