tomayac

The Google Drive terms of service are here: https://www.google.com/drive/terms-of-service/. None of the files are publicly accessable, nor shared with other persons than myself. IANAL.

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

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

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

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.

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.

[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 ;-)

[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.

I sure hope it will :-)

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.

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.

Hello, Tom from Chrome’s DevRel team here with a special focus on Project Fugu APIs! Happy to answer questions Hacker News may have.

The Chrome DevRel team (that I’m part of) have collected many WebUSB apps in our showcase: https://developer.chrome.com/blog/fugu-showcase/?api=webusb.

More background on this extension at https://developer.chrome.com/blog/how-fugu-is-my-browser-and....

Please see https://developer.chrome.com/blog/capabilities/#how-will-we-... for the actual process. Nothing happens behind closed doors; other vendors can chime in at any time, and are actually very much encouraged to do so.

Yeah, sorry. There’s a lot of side threads to read and potentially respond to.

0711 love! Viele Grüße!

The Origin Private File System is coming to all browsers, Chrome, Safari, and Firefox. It's a universally agreed-on Web standard: https://fs.spec.whatwg.org/.

Mozilla opposes the picker methods of the File System Access API. They are fully behind the Origin Private File System part, and actually have the SQLite demo from the article running in Firefox Nightly.

An interesting side note about this project is that in the SQLite team’s experiments the technology outperformed Web SQL in many cases.

Right, there's now a dedicated method: `HTMLInputElement.showPicker()`.

And getting the default permission period right for this feature once unflagged is something we're very actively discussing. Watch our publications web.dev and developer.chrome.com for updates on this.

Just noting that the browser support matrix is right here: https://web.dev/patterns/advanced-apps/contacts/#:~:text=con...

It's an Eleventy widget powered by MDN's browser-compat-data: https://github.com/mdn/browser-compat-data.

The advantage of using the `showSaveFilePicker()` method is that you can get a `FileSystemFileHandle`, with which you can then implement a true "edit, save, edit, save,…" flow; always saving over the current file, instead of downloading copies on each "save".

This article focuses on the shifted focus of the Project Fugu team from implementing new capabilities to refining and improving the existing ones.

Project Fugu DevRel here (https://twitter.com/tomayac)! The way to approach this is with progressive enhancement wherever possible. See https://web.dev/svgcode/ for an example where I try to make this concrete. Well noting that if your app depends on hardware APIs like WebHID, this approach obviously won’t work. What you can always do, though, is let other browser vendors know how and why you want them to support Fugu APIs.