this post was submitted on 22 May 2025
858 points (99.3% liked)
Technology
70283 readers
3627 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've actually been thinking about this a lot. "Save Webpage" is useless nowadays because everything is loaded externally through scripts. What if it saved a timeline of requests and responses somehow and could play it back? This might require recording the entire JS state though... and so much more with browser APIs. Saving just the requests+responses as a cache would fail if the scripting was non-deterministic. Maybe it would make sense to literally save a "recording" of the HTML and CSS changes, playing back only the results of any network requests or JS?
This would be a whole new pipeline to make interactivity work. Emulating a server with cached responses would allow to reuse the JS part of websites and is easier to do. I have no doubt that some pages wouldn't work and there would be a shitton of security considerations I can't imagine.