Happy to see that there is corporate sponsorship for this. Gives me some hope that this will allow MDN to outlast any eventuality that might befall Mozilla.
That's pennies to Google/Microsoft. For Coil.com on the other hand...
For the unaware, Coil is a subscription service that you pay a certain amount to, and that amount gets spread through websites you visit that have a WebMonetization tag in the <head> element:
<meta name="monetization" content="crypto-address-here">
1. Start a one month subscription and browse your websites. The add-on changes colour depending on whether the current site is monetized or not.
2. Try to find them here: https://coil.com/explore. If you click on "blogs", there's a search bar that you can use.
There's also a Twitter bot that tracks how many websites have it (https://twitter.com/WebMotized). Currently at 1400, with about a dozen of sites added weekly.
1. would show coil is getting quite a bit of money.
2. would show importance of MDN.
The extension helps us bootstrap the ecosystem but a native integration is far superior. Check out Puma browser for an example of the integrated experience for mobile.
Credit to Ali Spivak who kicked this all off and helped us realise what a crucial role good platform documentation plays and how important it is to fund good knowledgeable writers.
<meta name="monetization" content="bitcoin:my-bitcoin-address">
Doesn't work that way though. I have to sign up with somebody like coil.com and put an address they give me on my websites. This is just worse. Much much worse than it needs to be.
You don't have to sign up with Coil to earn. There are other wallets that are on the Interledger network such as Uphold and Gatehub that can give you a payment pointer to put into your site's HTML. If you want your earnings to be converted to BTC that's possible I think.
However, there's no reason for me to have an account anywhere in order to receive bitcoin. All I need is a bitcoin address.
I don't want to sign up with Coil, Interledger, Uphold, Gatehub, or any other random third party, in order to receive bitcoin. And there is zero reason why I would have to.
So that you can make payments to someone else regardless of whether they want to use Bitcoin or not.
I believe Interledger is the right level of abstraction for this, in the same way that you wouldn't want your email server to have to know or code against the lower protocols, e.g. Ethernet or WiFi, but only IP, TCP and SMTP. This way your email server can EHLO any email server, regardless of the network topology or underlying protocols.
Interledger does the same for payments.
I see no evidence that Interledger can be used for receiving money without having to set up accounts or run software. Plenty of evidence to the contrary.
As I said before, to receive bitcoin from one of these systems, there is nothing I should need to do other than advertise my bitcoin address. Anything more than that, and the system sucks.
Correct.
What you want requires support in the user agent (web browser) though.
The end result is very cheap and quick funds transfers to any node on the network. This lightning network infrastructure would make micropayments feasible.
Granted, there are still problems to solve. But this is the dream.
And AFAIK OOXML isn't currently evolving as much as this Open Web.
> Well, it can render and interact with Gmail quite well. It’s pretty much perfect on a few sites we’ve targeted as focuses during development, but it struggles with many others.