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: The Github Hitrub

This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201213130229/https://github.com/howdyai/botkit/issues/1841

howdyai / botkit

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove the revokable proxy behavior inherited from Bot Framework #1841

Closed

benbrown opened this issue Oct 28, 2019 · 10 comments

Assignees

Labels

stale

Contributor

benbrown commented Oct 28, 2019

Is your feature request related to a problem? Please describe.
The current behavior of turning the "turn context" into a revokable proxy that stops working is hard to deal with and difficult to explain. We should (optionally) remove it from the Botkit adapters.

Describe the solution you'd like
By deriving a new class from BotAdapter, then changing all Botkit adapters to derive from that.

When used with Botkit the proxy behavior should be disabled by default.
Otherwise it should be on by default (this is the expected behavior when used with Bot Framework)

benbrown self-assigned this

benbrown mentioned this issue

"TypeError: Cannot perform 'get' on a proxy that has been revoked" on using setInterval to let bot reply repeatedly #1856

Closed

movi1224 commented Nov 13, 2019

Can you please see my comment on #1856 , I met some issues on that :(

Contributor Author

benbrown commented Nov 13, 2019

I think you misunderstand what this ticket is about.

This would be a change to the code inside the Botkit adapters to use a different base class - not a change to your bot code.

stale bot commented Jan 12, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label

benbrown removed the stale label

stale bot commented Mar 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label

Contributor Author

benbrown commented Mar 13, 2020

Not stale.

stale bot removed the stale label

stale bot commented May 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label

Contributor Author

benbrown commented May 13, 2020

not stale

stale bot removed the stale label

stale bot commented Jul 12, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label

stale bot closed this

Contributor Author

benbrown commented Jul 20, 2020

still not stale! changes underway in bot framework SDK to allow this.

benbrown reopened this

stale bot removed the stale label

stale bot commented Sep 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label

stale bot closed this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

You can’t perform that action at this time.