See https://groups.google.com/a/chromium.org/g/blink-dev/c/zlLSxQ9BA8Y/m/Sy5K41lkAwAJ …:
LGTM1: @yoavweiss (Google)
LGTM2: @chrishtr (Google)
LGTM3: @DanielBratell (Opera)
LGTM4: @slightlylate (Google)pic.twitter.com/pOOIJp1pe1
Chrome Project
& Web Standards TL; Blink API OWNER
Named PWAs w/ @phae; probably making her
DMs open. Tweets my own; press@google.com for official comms.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
See https://groups.google.com/a/chromium.org/g/blink-dev/c/zlLSxQ9BA8Y/m/Sy5K41lkAwAJ …:
LGTM1: @yoavweiss (Google)
LGTM2: @chrishtr (Google)
LGTM3: @DanielBratell (Opera)
LGTM4: @slightlylate (Google)pic.twitter.com/pOOIJp1pe1
Thanks! So next q is non-chromium/Blink browser response. Cc'ing @othermaciej @bz_moz
Official Mozilla response to this will be at https://github.com/mozilla/standards-positions/issues/194 … -- we are still trying to sort out why exactly Google decided to not go with the existing fragmentions work and instead went off to create its own thing, and what that means in terms of what we should do.
assuming you mean: https://indieweb.org/fragmention , the main points: 1. fragmentation doesn't work where the page uses frag-based routing. Users might want to link to such pages and we can't tell a priori if it will work or not. It'd be confusing why some pages don't work.
2. We did lots of trials with Google Search and found simple text strings to be ambiguous in too many cases. I'll see if I can post some of our findings publicly.
3. Privacy. It makes sense to hide the text query string from even the destination page. Without the :~: syntax and fragment stripping, the page would be able infer sensitive information e.g. a user's search terms.
Oh, and on point #2: we started with a simple syntax-less string similar to fragmentation but got feedback from the WebAnnotations community that they'd been down that road and it was too ambiguous. We tried to match WA's https://www.w3.org/TR/annotation-model/#text-quote-selector … where we could.
Yes, it was given in https://news.ycombinator.com/item?id=19169698 … and referenced herehttps://github.com/WICG/ScrollToTextFragment/issues/4#issuecomment-463988339 …
Thank you. Fwiw, putting that sort of thing somewhere in an explainer would be pretty helpful in the future when evaluating standards proposals.
Agree that a fulsome "Considered Alternatives" section is good practice for Explainers. We're gonna do some work to try to improve this in coordination w/ the @w3ctag.
Not just considered alternatives, but also specific links to problems with them, if possible.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.