> On 17 Jan 2021, at 11:24, Mark Nottingham <mnot@mnot.net> wrote: > > Hey Henry, > >> On 17 Jan 2021, at 6:52 am, Henry Story <henry.story@bblfish.net> wrote: >> >> Another response is to make it easy for them to deploy micropayments, so that >> users coming from search engines can easily pay per article read, and then >> subscribe if they find themselves reading articles from that paper very often. >> >> I regularly land on newspapers via search engines, twitter, blogs, … and these ask me for >> a monthly or yearly subscription which I don’t really want. I can’t possibly subscribe to >> all newspapers I come across, for lack of time. But I would be happy to pay a >> small amount per article read if it were a one click affair and secure. > > That reminds me; a few years back I was in a meeting with some executives from a Very Large Publishing Company (one who everyone would instantly recognise). > > After the meeting, two of the execs took me aside and started asking some very detailed questions about micropayments and whether a standardisation effort could be started for them. It turns out that they were convinced that advertising-funded sites were a medium-term dead end, and they were looking for other options. > > I wonder if they feel the same way today; besides the pending legislation, the "cookiepocalyse" is causing a lot of navel gazing in the adtech industry, and publishers are waking up to the notion that they're getting ripped off, and might be able to do it better on their own, or at least based upon their own knowledge of users, rather than an ecosystem where there are hundreds of middlemen. > > Personally, I'm very interested in a privacy-preserving micropayments/microsubscriptions system -- not only for HTML content, but also RSS/Atom... There is the https://webmonetization.org project that I think is designed for web payments in the browser. Thinking of RSS feeds, implies that one has a blog/podcast reader that gives a unified view across all content. That requires a unified way of tying resources to payment before they are viewed. The 402 HTTP error code could be useful for that. Henry > > Cheers, > > > -- > Mark Nottingham https://www.mnot.net/ > Henry Story https://co-operating.systems WhatsApp, Signal, Tel: +33 6 38 32 69 84 Twitter: @bblfish
Received on Sunday, 17 January 2021 11:09:38 UTC