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.
This issue has been moved from a ticket on Developer Community.
Blazor Documentation lacks examples on the scenarios where some settings are used.
It would be really helpful in many places to use real life usage of the settings to give context and make the settings more discoverable through search engines.
This is just one of the many places in where it's difficult to know when to apply this setting Disable integrity checking for non-PWA apps
There is the text"
There may be cases where the web server can't be relied upon to return consistent responses, and you have no choice but to disable integrity checks. To disable integrity checks, add the following to a property group in the Blazor WebAssembly project's .csproj file:"There may be cases where the web server can't be relied upon to return consistent responses" doesn't explain examples of the cases in where that will happen. So basically, we can't know when to apply this setting. It would be good to give a couple of real scenarios to give context. The Blazor team work with low level details of the Browser and framework that the developers may not know.
This is just an example, but it applies to everywhere. A lot of times the settings don't explain the scenarios in where they can be applied, only what it does. This makes difficult to know how if it's required for us or not. Also, it creates additional work for the Blazor team, because it forces us to create new issues, we we don't have a way to understand when to apply certain settings or what they do exactly.
I submitted a Fix for the documentation but I got this answer:
This content came over directly from the PU ("product unit") who maintain the Blazor framework. I think they don't intend to provide a specific list, but you can ask them. Open an issue on their repo asking them the question ...
https://github.com/dotnet/aspnetcore/issues
Provide a link to the section where it's discussed ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-6.0#disable-integrity-checking-for-non-pwa-apps
Please add ...
cc: @guardrex dotnet/AspNetCore.Docs#25032
... to the bottom of your opening comment so that I follow along. I might re-open this for doc work depending on what they say.
Original Comments
Feedback Bot on 2/15/2022, 10:28 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: