COLLECTED BY

Organization: Archive Team

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.

Collection: Archive Team: URLs

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20220616212637/https://github.com/Matvey-Kuk

Matvey-Kuk Follow

Matvey Kukuy Matvey-Kuk

Follow

Ex-Amixr CEO (acquired by Grafana Labs), head of Grafana OnCall

42 followers · 9 following

Grafana
Tel Aviv, Israel
@Mkukkk

Achievements

BetaSend feedback

Achievements

BetaSend feedback

Organizations

Block or Report

Block or report Matvey-Kuk

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned

grafana/oncall Public

Developer-friendly incident response with brilliant Slack integration

Python 1.2k 28

668 contributions in the last year

Learn how we count contributions

Less More

NEW! View your contributions in 3D, VR and IRL!

Contribution activity

June 2022

Created 83 commits in 1 repository

grafana/oncall 83 commits

Opened 8 pull requests in 1 repository

grafana/oncall 8 merged

Dev to main Jun 14
Using image: grafana/oncall Jun 14
Polishing telegram Jun 13
hobby-docker-compose Jun 9
Texts update on the plugin configuration page Jun 8
New Logo! Jun 8
Small polishing, links for OSS config page Jun 6
OSS Docs refresh Jun 6

Reviewed 13 pull requests in 1 repository

grafana/oncall 13 pull requests

Add missing slack settings to live settings mapping Jun 15
Fix Telegram message template for AlertManager Jun 15
Specify net.core.somaxconn for engine in docker-compose.yml Jun 15
Add PagerDuty migrator Jun 14
makeReq Jun 14
bug fixes Jun 14
Remove https:// prefix from BASE_URL docker env var Jun 13
Add publishing workflows for next (unreleased) and released documentation Jun 13
Plugin configuration polish Jun 10
Only execute release process on tags that match version pattern Jun 9
Remove demo token related code/logic Jun 9
Grafana cloud notifications Jun 8
Oncall docs IA refactor Jun 8

Created an issue in grafana/oncall that received 4 comments

"Tiny" deployment version for those who want a small deployment footprint?

A few HN commenters raised a topic of a large deployment footprint: https://news.ycombinator.com/item?id=31740902 We deliver OnCall with redis + ra…

4 comments

Opened 6 other issues in 1 repository

grafana/oncall 5 open 1 closed

Add templates for "ciao" Jun 14
Add templates for "uptime-kuma" Jun 14
Add "uptime" native integration templates Jun 14
Add raw alert content view Jun 14
Make explicit which template is rendered where Jun 14
Make Slack acknowledgement reminder team-specific Jun 14

Started 1 discussion in 1 repository

grafana/oncall

Join our community call! 🤗 June 22, 14:00 UTC [Developer setup tour, meet the team, Q&A] Jun 6

16 contributions in private repositories Jun 1 – Jun 15