Live data from Hacker News

What happened with the Web Monetization API?

chriscoyier.net

11–20 of 271 posts

Re: What happened with the Web Monetization API?

#11

> It needs to be built into the browsers and web standards such that it’s incredibly smooth and fast. I wanna send $1 to a website, it happens instantly and anonymously, and the developer can do things around this. Like unlock features! For instance, stop showing ads, offer more complete downloads, unlock tutorial courses, etc. Make it easier and faster than using a credit card. Are there any promising avenues toward…

GNU Taler

Re: What happened with the Web Monetization API?

#12
post #9

> It needs to be built into the browsers and web standards such that it’s incredibly smooth and fast. I wanna send $1 to a website, it happens instantly and anonymously, and the developer can do things around this. Like unlock features! For instance, stop showing ads, offer more complete downloads, unlock tutorial courses, etc. Make it easier and faster than using a credit card. Are there any promising avenues toward…

> Are there any promising avenues towards microtransactions that gets around small card transactions getting a hefty fee One option is to have regulations about card fees, which is the case in the EU (0.2% for debit, 0.3% for credit). Another is to use an alternative payment method, like India's UPI or Eurozone's SEPA which are free and instantaneous.

The UX around card and SEPA payments sucks, though. I hear UPI is nicer.

Re: What happened with the Web Monetization API?

#13

The problems with monetization and micropayments are not technical and no easy-to-use API is going to help with adoption. Dealing with money is a real pain due to fraud, security, and legal compliance and those problems don't go away when the amounts are small.

I mean I’m sure that’s what the processors want people to believe. But even if those problems are difficult, they aren’t insurmountable: I’m sure that libraries would be developed over time that would allow for these things to happen, securely and without error, much as the SSL libraries have developed over the decades.

Re: What happened with the Web Monetization API?

#14

> It needs to be built into the browsers and web standards such that it’s incredibly smooth and fast. I wanna send $1 to a website, it happens instantly and anonymously, and the developer can do things around this. Like unlock features! For instance, stop showing ads, offer more complete downloads, unlock tutorial courses, etc. Make it easier and faster than using a credit card. Are there any promising avenues toward…

Frankly, this is probably just going to manifest as a digital currency. Add 10$ to your wallet. At the end of the month that's distributed or something

Re: What happened with the Web Monetization API?

#15
post #7

> It needs to be built into the browsers and web standards such that it’s incredibly smooth and fast. I wanna send $1 to a website, it happens instantly and anonymously, and the developer can do things around this. Like unlock features! For instance, stop showing ads, offer more complete downloads, unlock tutorial courses, etc. Make it easier and faster than using a credit card. Are there any promising avenues toward…

> Are there any promising avenues towards microtransactions that gets around small card transactions getting a hefty fee This is anathema here in the US but the rest of the world typically does not use credit cards as the default payment method.

But they (we) do use debit cards as one tho.

Re: What happened with the Web Monetization API?

#16

> It needs to be built into the browsers and web standards such that it’s incredibly smooth and fast. I wanna send $1 to a website, it happens instantly and anonymously, and the developer can do things around this. Like unlock features! For instance, stop showing ads, offer more complete downloads, unlock tutorial courses, etc. Make it easier and faster than using a credit card. Are there any promising avenues toward…

[deleted]

Re: What happened with the Web Monetization API?

#17
post #10

The problems with monetization and micropayments are not technical and no easy-to-use API is going to help with adoption. Dealing with money is a real pain due to fraud, security, and legal compliance and those problems don't go away when the amounts are small.

Even those are solvable problems, the real issue is social. There's a reason Flattr failed and Patreon has been a huge success. People would rather personally support a handful of creators at $5/month than put the equivalent money in a tip jar at a bunch of faceless websites.

Before coil failed, making this something that happened in the background seemed promising.

Re: What happened with the Web Monetization API?

#18

I remember Brave introducing BAT tokens that you could earn for seeing ads and then donate to other websites and content creators. How did that experiment end up? Was it just a crypto hype thing?

The concept is a deliberate scam. Brave removes the legitimate ads from the website owners, and puts their own ads on top. Then presents that as somehow helping website owners.

Re: What happened with the Web Monetization API?

#19
The solution to this is a centralized model, where users top up their account with money. Then they get a button in their browser where they can click to pay for features in the current open tab or donate if the page is free.

The top up could even be a recurring payment if the user wants.

Re: What happened with the Web Monetization API?

#20
I was ruminating around this topic the other day and came to conclusion it is probably terribly missed opportunity for certain advertising company. Now it sounds super scary privacy-wise, smells monopol-y and overall may not happen anymore (I think), but consider:

In situation when "all" users are being in fact "logged into" their service anyway, then features such as - pay to hide ads on this particular web (basically "overpay the advertiser"), - pay to keep ads and support the author of this particular web, - pay for extra features but remain anonymous for web's author, - provide data about yourself that the company gathered about yourself to the web's author, then it sounds like quite low-hanging fruit.

Web authors would gain "auth" for free, integration would allow some "serverless" features for otherwise basic webs and so on. My initial idea was (probably akin to Brave(?)): - pay advertiser one centralized "ransom" to disable X ad impressions, so they can be distributed to websites authors as I go, just the same way as if I was exposed to a real ad.

For favourite websites I could either top that by also allowing ads again, or paying them more, obviously with certain share ending up as a fee for that mediator.

I guess there was/is some blatant obstacle that prevented this (perhaps advertisers would all bail out when the could be legally "overpaid" by users?) or it in fact had been implemented somehow in the past (distant enough I missed it completely), but it was a fun thought exercise anyway.

Post reply on HN