COLLECTED BY
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: ArchiveBot: The Archive Team Crowdsourced Crawler
To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.
There is a dashboard running for the archivebot process at http://www.archivebot.com.
ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

ljharb on master
[eslint config] [base] [patch] … [eslint config] [patch] extend … Merge pull request #1996 from r… (compare)
ljharb on master
[editorial] [react] fix typo [eslint config] [*] [deps] upda… (compare)
const da = await(
await fetch("http://newsapi.org/v2/top-headlines?sources=techcrunch&apiKey=")
).json();
// console.log(da);
const val1=da.articles[0].title;
const val2=da.articles[1].title;
const val3=da.articles[2].title;
const val4=da.articles[3].title;
const val5=da.articles[4].title;const des1=da.articles[0].description;
const des2=da.articles[1].description;
const des3=da.articles[2].description;
const des4=da.articles[3].description;
const des5=da.articles[4].description;
const titles = data.map(x => x.title); const descriptions = data.map(x => x.description), etc
eslint-config-airbnb with babel-preset-airbnb on a create-react-app but I keep getting this following error: Parsing error: Unexpected token =eslint. I've set up my .babelrc file to have "presets": ["airbnb"] and most of the answers I found kept suggesting to add "parser": "babel-eslint" to my .eslintrc.json file. The thing is I'm not using babel-eslint. What would be the equivalent solution for the airbnb babel preset? Thanks!
For some odd reason, create-react-app gives me the following error with eslint 7 😕
The react-scripts package provided by Create React App requires a dependency:
"eslint": "^6.6.0"and asks me to
const getR = async()=>(
await fetch("http://newsapi.org/v2/top-headlines?sources=techcrunch&apiKey=077fe507985744818b3f405349c79601")
).json();
(async ()=>{
const articles=(await getR()).articles;
articles.map(({title,description},index)=>{
(
value+index = title
description+index = description
)
}).join('')
})();
opentok.createSession(function (err, session) {
if (err) return console.log(err);
const token = session.generateToken({
role: 'moderator',
expireTime: (new Date().getTime() / 1000) + (1 * 24 * 60 * 60), // in one day
data: 'name=ajay',
initialLayoutClassList: ['focus']
});
return { sessionId: session.sessionId,token:token}});
can any one tell me how to get these value in a variable ?
Can anyone please explain this part of the airbnb style guide to me?
https://github.com/airbnb/javascript#arrays--mapping
It says:
4.6 Use Array.from instead of spread ... for mapping over iterables, because it avoids creating an intermediate array.
// bad
const baz = [...foo].map(bar);
// good
const baz = Array.from(foo, bar);But I don't understand why you wouldn't instead do:
const baz = foo.map(bar);
foo.map(bar) is fine. If it's a non-array iterable, then use Array.from to prevent converting to an array just to use map
11.2 Don’t use generators for now.
Why? They don’t transpile well to ES5.
React portion of the guide to be updated further? Given the way it refers to function components as stateless and only recommending them if you don't have state or refs, I feel like it hasn't been updated to reflect the introduction of hooksHi there
I have an async function which I would like to convert to an Observable stream (using rxjs operators). The await calls must execute in the order they appear in the function.
async authenticateUser(profile: Profile): Promise<any> {
let authCookie: any;
try {
authCookie = await getCookie();
} catch (error) {
console.error(error);
}
if (!authCookie || authCookie?.length < 1) {
cancelAuthenticationCookieGet();
throw {message: "login failed", status: -2};
}
await saveProfileAsync(profile);
await storeCurrentAuthCookieAsync(authCookie);
storeSessionStorage();
await setPartitionSessionCookie(profile.url, authCookie);
}Is there a clean way to accomplish the above?