Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

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.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
really_bz's profile
Boris
Boris
Boris
@really_bz

Tweets

Boris

@really_bz

Used to be bz_moz

Joined May 2011

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    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

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    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

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    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

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. David‏ @david_bokan 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @really_bz @bz_moz and

      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 replies 0 retweets 2 likes
    2. David‏ @david_bokan 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @bz_moz and

      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.

      2 replies 0 retweets 3 likes
    3. David‏ @david_bokan 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @bz_moz and

      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.

      2 replies 0 retweets 3 likes
    4. David‏ @david_bokan 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @bz_moz and

      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.

      2 replies 0 retweets 2 likes
    5. David‏ @david_bokan 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @bz_moz and

      4. Fragmentation isn't well suited for dis-contiguous passages. E.g. Selecting two paragraphs separated by an image.

      1 reply 0 retweets 1 like
    6. Boris‏ @really_bz 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @BrendanEich and

      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"...

      1 reply 0 retweets 0 likes
    7. David‏ @david_bokan 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @really_bz @bz_moz and

      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)

      2 replies 0 retweets 0 likes
    8. Boris‏ @really_bz 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @BrendanEich and

      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.

      1 reply 0 retweets 2 likes
    9. Boris‏ @really_bz 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @really_bz @david_bokan and

      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"?

      1 reply 1 retweet 4 likes
    10. David‏ @david_bokan 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @really_bz @bz_moz and

      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?

      2 replies 0 retweets 1 like
      Boris‏ @really_bz 18 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @david_bokan @BrendanEich and

      I don't think there's any misunderstanding going on. It's just not clear to me why we need to support multiple match terms for the use cases this is trying to address.

      7:08 AM - 18 Dec 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. David‏ @david_bokan 19 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @really_bz @bz_moz and

          You said "highlight all instances of a thing" which is not the case, we highlight only the the first instance. Multiple terms allows highlights where a single range-based term would highlight unwanted content (e.g. ad between two paragraphs) because of how the DOM is arranged.

          2 replies 0 retweets 0 likes
        3. Boris‏ @really_bz 19 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @david_bokan @BrendanEich and

          Ah, that was not clear to me from the documents I was reading: it sounded like all the things that matched were highlighted but only the first scrolled to. But I might have misread things, of course!

          1 reply 0 retweets 0 likes
        4. 2 more replies

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info