Thomas Steiner (@tomayac@toot.cafe) (@tomayac)

Earth, also @tomayac@toot.cafe

The below is an off-site archive of all tweets posted by @tomayac ever

July 4th, 2020

@firt @webkit Or, to be precise, WebKit inherits coarse location sharing from the operating system. Question is, as @firt notes, what they will do with it.

via Echofon in reply to tomayac

@firt Note that coarse location sharing isn’t a new idea at all (but, to be fair, now for the first time implemented by the @webkit team). See Figure 3 of my paper: research.google/pubs/pub48156/. Wonder how they deal with the issues mentioned in the paper. Ge

via Echofon in reply to tomayac

In-depth thread by @firt on precise or coarse location sharing 📍 in iOS 14 and what of this (if anything, no spoilers) is Web-exposed (in Safari, WKWebView, and home screen apps). Love the constructive call-to-action at the end: twitter.com/firt/status/12…

via Echofon

@firefox @webkit 🦊 @firefox users can now give the extension a try: addons.mozilla.org/en-US/firefox/…. It’s still marked as Beta and I added the experimental flag on the @mozilla Add-on Store since the Text Fragment polyfill (for navigation) is still in develo

via Echofon in reply to tomayac

@LeonieWatson @IRCCloud I don’t think that’s currently possible according to docs.microsoft.com/en-us/microsof…; it’s also not mentioned in one of the Explainers (github.com/MicrosoftEdge/…). But, drum roll 🥁, we have a Project Fugu 🐡 bug open for this featbugs.chromium.org/p/chromium/iss…

via Echofon in reply to LeonieWatson

@slightlylate @dfabu @gregwhitworth My understanding of their mission statement is that custom elements, too, should agree on a common (exposed!) structure and behavior, so the underlying implementation can be swapped, and the code touching those elements

via Echofon in reply to slightlylate