This is not a "standard." From their documentation[0]:

  Browsers already know how to interpret certain rel
  values because of web standards.

  ...

  The monetization link type, however, isn’t a standard yet.

And nothing about the "Web Monetization" primary intent[1] is appealing as a standard worthy of being adopted:

  Web Monetization gives publishers more revenue options ...

0 - https://webmonetization.org/developers/link-element-webpage/...

1 - https://webmonetization.org/

What happens if you block network for the tab once it's finished loading? Does it delete the page if payments aren't going through anymore?

When Coil did their demos years ago the payment streaming examples were videos and music. A pay per minute kind of deal. Payment streaming for read content does sound abusive especially for slow readers.

It only streams money when the tab is in the foreground and active. But yes, if you are on a monetized tab, get called for lunch, and don't lock your computer (what's wrong with these people , it could be that you stream all your funds to that one tab. I think the extension and the final browser UI once it's natively supported needs a way to let you limit the maximum amount of money, and also show you stats about where your money went so you can more easily adjust each site's amount.

I guess if it would reach the higher level of adoption there would be a very easy way to charge back for the auto- requested stuff.

Also there could be mandatory confirmation required for any amount set.

Want to remove ads? Click and confirm.

For just donating 1c per minute of reading you could have those queued somewhere and still have a chance to explicitly approve it once a month / a week / a day

This makes it obviously a pain in the ass that nobody normal will tolerate; dead on arrival, waste of time