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
This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.
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.
4. Fragmentation isn't well suited for dis-contiguous passages. E.g. Selecting two paragraphs separated by an image.
Is the goal here "selecting" or "pointing at"? A lot of the proposal seems to focus on the "selecting" aspect; when I described it to someone their reaction was "this is just sticking the entire browser find functionality in the URL"...
Sorry, I'm being loose with terminology. It's "pointing at"; we specifically avoid creating selections for security. find-in-page via url is apt, though with more disambiguating power. We've thought about integrating it with the FIP UI but haven't yet (more of a UI issue though)
Again, the use cases I am aware of are more like "link to a thing that doesn't have an anchor provided", not "highlight all the instances of a thing". If there are use cases motivating this, I'd really like to understand what they are.
Or put another way, _why_ are we building find-in-page-via-URL if the problems we want to solve "just" need "indicate a spot on the page via URL"?
Ah, I think the misunderstanding is "match". In :~:text=foo&text=bar, we call both "foo" and "bar" the "match term". Both "foo" and "bar" be indicated but only the first occurrence of each (it differs from FIP in this way). Is there a section I could clear up?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.