this post was submitted on 28 May 2026
351 points (98.6% liked)

Technology

84988 readers
4534 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Wildmimic@anarchist.nexus 7 points 20 hours ago* (last edited 20 hours ago)

I don't think so - from how i understand it, everything where you upload a file to a server to edit it there wouldn't work at all.

The flow looks like this:
You select a file for upload - the browser creates a file in OPFS storage representing the original file - any change you make serverside are replicated to the copy in OPFS storage - when you save the file, you don't actually have to download it, but the file gets moved from OPFS to wherever you save the file. This prevents long downloads and a lot of warnings (if you would download the file in the classic way, the OS would flag it with the Mark of the Web even tho it is your own file, triggering smartscreen on Windows) and the file in OPFS storage is encrypted because of HTTPS.

it's explained in detail here: https://web.dev/articles/origin-private-file-system