
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Hi, I have a PWA application that I have developed internally for my company. I recently upgraded it to .NET 6 by creating a new project and moving everything over.
When I went to deploy this last week, everything went wrong. I was getting integrity errors everywhere, and some of the users I had testing for me also had the same issues. The app was able to update its service worker assets when you reloaded with a clear cache, but doing a reload right after would bring the version back to the old one, and eventually just broke the application. I had to revert back to the .NET Core 3.1 version temporarily.
The way I have my PWA setup, it should show an "Update Now" button when I do publish a new version. Normally it's instant, and has worked really well on .NET Core 3.1, but for some reason, it did not show up that time.
I haven't tried since, but what I did was run a PowerShell script to check the hashes found in the service-worker-assets.js file with the calculated hashes, and everything matched for all the files in that failed deployment. I also looked at the blazor.boot.json and the hashes seemed to match there as well.
I can't really tell what happened. I heard that one way to fix this was to delete the obj and bin folders before publishing, but I haven't tried that yet. I don't want to publish until I know for sure what went wrong that day.
And just for more information, here's my deployment process:
And just FYI, I use the default web.config that comes with the publish step. I haven't messed around with configuring it.
Any ideas how I can better assess what went wrong here? I believe the browser was holding onto old cache somehow?
Here's the service.worker.published.js file:
The text was updated successfully, but these errors were encountered: