Chronotope’s avatarChronotope’s Twitter Archive—№ 87,780

      1. Huh. Is there no meta field for "This is a subscription site and here is how you pay for it"? What if I want to build a news parsing robot that can pay for entry?
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 2 Favorites Mood -2 🙁
    1. …in reply to @Chronotope
      *skims documentation*
      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
  1. …in reply to @Chronotope
    In fact, is there any platform that would allow a client to pay programmatically? If I did make a bot that payed for access to the news, is there even a methodology by which it could? Why not?
    On twitter.com Twitter logo Chronotope’s avatar Mood 0
    1. …in reply to @Chronotope
      Also, wouldn't a meta field by which a robot could tell this is a subscription site be a good trust indicator, or at least tell spiders why your content is inaccessible?
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets Mood +4 🙂
      1. …in reply to @Chronotope
        I mean... lol what if we had a standard by which we could paywall spiders in the 90s? Could you imagine if we started off putting news on the internet for free, but blocking it from Google unless Google paid for access? That's a fun alternate history to meditate on.
        Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets ❤️ 2 Favorites Mood +7 🙂
        1. …in reply to @Chronotope
          Or alternative: if there is a meta value for 'here's the subscription page, pay me', you could negotiate a protocol by which aggregaters automatically promote your paywall instead of negotiating per-platform methods as we do now.
          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
          1. …in reply to @Chronotope
            Imagine the following aggregation-display flow: Retrieve Partial Article, Paywall endpoint -> Prompt user to pay through whatever methodology the platform prefers. -> Payment passed from platform to outlet -> API Query returns the rest of the article immediately.
            Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -1 🙁
            1. …in reply to @Chronotope
              Platform agnostic paywalling... why is this not a thing?
              Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
              1. …in reply to @Chronotope
                Looks like this idea has come up, but not been fleshed out by the w3c. What committee is working on this and how can I get on it? kshay/961253314196328448
                Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood +2 🙂
                1. …in reply to @Chronotope
                  I don't know if I'd have made it a 4xx code though? I want to provide some additional data. Or a partial story. I know that's possible on a 400 code, but it isn't the expectation.
                  oh my god twitter doesn’t include alt text from images in their API
                  Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +1 🙂
                  1. …in reply to @Chronotope
                    There *is* a schema(dot)org markup for paywalled content, but it doesn't provide a property for where resolving a paywall can be done. developers.google.com/search/docs/data-types/paywalled-content
                    OpenGraph image for developers.google.com/search/docs/data-types/paywalled-content
                    Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 2 Favorites Mood +2 🙂
                    1. …in reply to @Chronotope
                      But seriously: I want to build a robot aggregation tool that respects paywalled content and--at the very least--promotes the paywalls of the sites it presents.
                      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +3 🙂

Search tweets' text