I think this would technically be possible, but less practical once it's supported natively in the browser.

Web Monetization supports multimedia content monetization as well (you place the `link` in your `audio` or `video`). Don't forget that you are in control. If you're a slow reader, adjust the site's amount, so when you spend a long time on a page they don't get excessive payments.

Here's the docs for this: https://webmonetization.org/developers/link-element-webpage/.... You can monetize `audio`, `video`, and `picture` as well.

For the sake of completeness, you can also monetize your Atom, RSS, and JSON feeds: https://webmonetization.org/developers/rss-atom-jsonfeed/.

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.

Here's the docs for how and when continuous payments are being sent: https://webmonetization.org/developers/link-element-webpage/....

[Author here] Hah, our tech writers make me replace this word every single time with "using" in our company blog posts. But this is my blog, my rules ;-)

Your tech writers are correct. Almost never see this word used properly.

[Author here] Safari is not supported. See https://developer.chrome.com/docs/ai/prompt-api#hardware-req... for the requirements.

[Author here] The quote from the repair guy was 270€ for the motor replacement. The new machine was €450. We ended up paying the repair guy €59 for coming, detecting the error, and telling us to let it go. We had the same repair guy exchange the carbon brushes earlier in the year. We really did not want a new machine, but, hey…

[Author here] The AI feature is their implementation on the server. I was just trying to see if the same could be implemented client-side as a good use case for the, as you say, experimental, Prompt API. (It's in origin trial, so you can use it already on production sites.) Downloading a model for just this use case is obviously stretching it. You'd use it if it's there, but not download it on purpose just for this convenience.

New podcast: Learn about some early WebAssembly history from one of the co-creators of Wasm, Alon Zakai! Follow along how Alon explains how we came from Native Client to asm.js and then finally to WebAssembly, and explore some interesting historical and present day sidetracks on the way.

Congrats on doing the podcast! Definitely looking forward to it.

I wanted to complain about the audio, but the YouTube comments on the topic made it clear what the problem was. This means that audio is going to be better in the future.

I sure hope it will :-)

This case study explores how Kiwix, a non-profit organization, uses Progressive Web App technology and the File System Access API to enable users to download and store large Internet archives for offline use. Learn about the technical implementation of the code dealing with the Origin Private File System (OPFS), a new browser feature within the Kiwix PWA that enhances file management, providing improved access to archives without permission prompts. The article discusses challenges and highlights potential future developments in this new file system.

This article was inspired by a Twitter thread: https://twitter.com/tomayac/status/1673173047791034368. It’s apparently not widely known that this works so well—and it’s a nice progressive enhancement that you can add without changes to existing full screen code. Use this trick for any full screen web game, web app, or streamed-to-web environment.