https://wiki.archiveteam.org/api.php?action=feedcontributions&user=Kpcyrd&feedformat=atomArchiveteam - User contributions [en]2024-03-29T08:36:37ZUser contributionsMediaWiki 1.37.1https://wiki.archiveteam.org/index.php?title=Chaos_Computer_Club&diff=51611Chaos Computer Club2024-01-29T20:10:47Z<p>Kpcyrd: Hamburg: Add public subdomains, Dresden: Add hedgedoc</p>
<hr />
<div>The [https://www.ccc.de/ Chaos Computer Club] is a large association of hackers in Germany<ref>https://en.wikipedia.org/wiki/Chaos_Computer_Club</ref>. Together with its surrounding groups, which are associated with it but not directly part of it, it is often referred to as “the Chaos community”.<br />
<br />
Those hackers create a lot of value like tutorials, information about how to use old hardware, or talk recordings from events they host. But there’s also lots of activism, culture and art to keep track off.<br />
<br />
This is an attempt to organize all those entities.<br />
<br />
== Chaos Computer Club e.V. (CCC) ==<br />
<br />
Projects related directly to the club, excluding ccc.de subdomains that are offline or meant for internal use.<br />
<br />
* https://www.ccc.de/ - main page<br />
* https://ds.ccc.de/ - member’s magazine (also published as public access ebooks)<br />
* http://ftp.ccc.de/ - public ftp<br />
* https://abmahnbeantworter.ccc.de/ - click-through-guide on what to do when received a legal warning<br />
* https://aliens.ccc.de/ - FAQ for CCC members not organised in a sub-group<br />
* https://hacker-archive.org/ - archive for all things hackers, in cooperation with the [https://wauland.de/en/ Wau Holland Stiftung] - still in early buildup/collection phase<br />
* https://cpu.ccc.de - every CCC group can post here<br />
* https://erfafoo.hamburg.ccc.de/ - alternate (unstyled) version of https://cpu.ccc.de<br />
<br />
=== Swiss CCC (CCC-CH) ===<br />
<br />
* https://ccc-ch.ch/<br />
<br />
=== Chaos Computer Club Veranstaltungsgesellschaft mbH (CCCV) ===<br />
<br />
This is the legal entity running the large CCC events, namely the [https://en.wikipedia.org/wiki/Chaos_Communication_Congress Chaos Communication Congress] and the [https://en.wikipedia.org/wiki/Chaos_Communication_Camp Chaos Communication Camp].<br />
<br />
* https://cccv.de/<br />
<br />
== Events ==<br />
<br />
* https://events.ccc.de/ - central event info blog<br />
* https://calendify.com/@CCC/events/past - a fairly complete overview over past Chaos events<br />
<br />
=== General ===<br />
<br />
==== For any Event ====<br />
<br />
===== Media =====<br />
<br />
* https://media.ccc.de/ - talk ans session recordings from events end up here (VERY LARGE)<br />
* https://streaming.media.ccc.de - live and “re-streams” from events<br />
<br />
===== Chaos Emergency Response Team (CERT) =====<br />
<br />
* cert.ccc.de/<br />
* https://bulletin.cert.ccc.de/<br />
<br />
==== For Congress and Camp ====<br />
<br />
* fahrplan.events.ccc.de - schedule of the current/last congress or camp, usually pointing to another place<br />
* https://halfnarp.events.ccc.de/ - pre-congress/-camp feedback system for schedule optimisation<br />
* https://help.ccc.de/ - general help and contacts for CCC event visitors<br />
* https://content.events.ccc.de/ - usually calls for participation<br />
<br />
=== Aktiv Symposium München ===<br />
<br />
* https://asm16.muc.ccc.de/<br />
* https://asm17.muc.ccc.de/<br />
* https://asm18.muc.ccc.de/<br />
<br />
=== Chaos Communication Congress ===<br />
<br />
* ...<br />
<br />
=== Chaos Communication Camp ===<br />
<br />
==== 2019 ====<br />
<br />
* https://firmware.card10.badge.events.ccc.de/ - docs for event badge<br />
<br />
==== 2023 ====<br />
<br />
* https://events.ccc.de/camp/2023/<br />
* https://flow3r.garden/ - event badge<br />
* https://docs.flow3r.garden/ - event badge docs<br />
<br />
=== Easterhegg (EH) ===<br />
<br />
This event is hosted by another group each time.<br />
<br />
* https://easterhegg.ccc.de/<br />
* https://eh01.easterhegg.eu/ -> https://www.hamburg.ccc.de/eh2001/ - offline<br />
* https://eh02.easterhegg.eu/<br />
* https://eh03.easterhegg.eu/ - offline<br />
* https://eh04.easterhegg.eu/<br />
* https://eh05.easterhegg.eu/<br />
* https://eh06.easterhegg.eu/ -> http://eh.cngw.org/ - offline<br />
* https://eh07.easterhegg.eu/<br />
* http://eh08.easterhegg.eu/<br />
* https://eh09.easterhegg.eu/<br />
* https://eh10.easterhegg.eu/ -> https://eh2010.muc.ccc.de/<br />
* https://eh11.easterhegg.eu/<br />
* https://eh12.easterhegg.ch<br />
* https://eh13.easterhegg.eu/ - offline<br />
* eh14.easterhegg.eu - offline<br />
* https://eh15.easterhegg.eu/ -> https://discord.com/invite/8FcDvAf ???<br />
* https://eh16.easterhegg.eu/<br />
* https://eh17.easterhegg.eu<br />
* https://eh18.easterhegg.eu/<br />
* https://eh19.easterhegg.eu/<br />
* https://eh20.easterhegg.eu/<br />
<br />
=== Datenspuren ===<br />
<br />
* https://datenspuren.de<br />
* https://c3d2.social/@datenspuren<br />
<br />
=== Gulaschprogrammiernacht (GPN) ===<br />
<br />
* https://entropia.de/GPN<br />
* https://twitter.com/entropiagpn<br />
* https://chaos.social/@gpn_info<br />
* https://www.mixcloud.com/LoungeControl/ - Livestreams from sets at party area + kitchen<br />
* https://www.youtube.com/@LoungeControl<br />
* https://chaos.social/@LoungeControl<br />
<br />
=== Intergalaktische Club Mate Party (ICMP) ===<br />
<br />
* https://icmp.camp/ - seems to redirect to the current instance only<br />
* https://w.icmp.camp/ - Wintergalaktische Club Mate Party (WICMP)<br />
<br />
=== Intergalaktische Erfahrungsreise (IGER) ===<br />
<br />
* https://fairydust.reisen/<br />
* https://tickets.fairydust.reisen/ - tickets, keeps info on past events<br />
* https://cfp.fairydust.reisen - call for participation<br />
* https://chaos.social/@erfahrungsreise<br />
* https://twitter.com/erfahrungsreise<br />
* https://md.fairydust.reisen - HedgeDoc public metapad hub<br />
<br />
== Regional Subgroups (“Erfas”) ==<br />
<br />
* https://www.ccc.de/de/club/erfas<br />
<br />
These Erfas are mostly hackerspaces, but not all [[Hackerspaces]] are Erfas.<br />
<br />
=== Aachen ===<br />
<br />
* https://aachen.ccc.de/ - Erfa webpage<br />
* https://archive.aachen.ccc.de - old stuff archive (and links to others)<br />
* https://twitter.com/cccac<br />
* https://chaos.social/@cccac<br />
<br />
=== Bamberg ===<br />
<br />
* https://www.hackerspace-bamberg.de/<br />
* https://chaos.social/@backspace<br />
* https://twitter.com/b4ckspace<br />
* https://vimeo.com/backspace<br />
<br />
=== Basel ===<br />
<br />
* https://ccc-basel.ch/<br />
* https://wiki.ccc-basel.ch<br />
<br />
=== Berlin ===<br />
<br />
* https://berlin.ccc.de/<br />
<br />
==== Club Discordia ====<br />
<br />
* https://twitter.com/clubdiscordia<br />
* https://chaos.social/@clubdiscordia<br />
<br />
=== Bremen ===<br />
<br />
* https://wiki.ccchb.de<br />
<br />
=== Cologne ===<br />
<br />
* https://antivirus.koeln.ccc.de/ - corona related PPE making project<br />
<br />
=== Darmstadt ===<br />
<br />
* https://www.chaos-darmstadt.de/<br />
* https://chaos.social/@cccda<br />
* https://wiki.darmstadt.ccc.de/<br />
<br />
=== Dresden ===<br />
<br />
* https://www.c3d2.de/<br />
* https://wiki.c3d2.de/<br />
* https://ftp.c3d2.de/<br />
* https://hedgedoc.c3d2.de/<br />
<br />
=== Dortmund ===<br />
<br />
* https://www.chaostreff-dortmund.de/<br />
* https://wiki.ctdo.de/<br />
* https://tumblr.tumblr.taetaerae.ctdo.de/<br />
* https://gallery.ctdo.de/<br />
* https://planet.ctdo.de<br />
* https://dortmund.media.ccc.de/ - separate media repository?<br />
<br />
=== Dresden ===<br />
<br />
* https://c3d2.de/<br />
* https://dresden.ccc.de/ - https://c3d2.de/ points there<br />
* http://ftp.c3d2.de/<br />
<br />
=== Düsseldorf ===<br />
<br />
* https://chaosdorf.de/<br />
* https://chaos.social/@chaosdorf<br />
* https://twitter.com/chaosdorf<br />
* https://www.youtube.com/channel/UCdiSBf0peR7DQghwHmgFvgQ<br />
<br />
=== Erlangen ===<br />
<br />
* https://erlangen.ccc.de<br />
* https://www.zam.haus/ - venue<br />
<br />
=== Essen ===<br />
<br />
* https://chaospott.de/ - {{job|6i1ql86adu442bfgclvqm2b6t}}<br />
* https://podcast.chaospott.de/ - {{job|8ort0tlhm2jj25kmvyuyhdvup}}<br />
* https://chaos.social/@chaospott<br />
* https://twitter.com/chaospott<br />
<br />
=== Frankfurt am Main ===<br />
<br />
* https://ccc-ffm.de/<br />
* https://chaos.social/@cccffm<br />
* https://wiki.ccc-ffm.de/<br />
<br />
=== Giessen ===<br />
<br />
* https://giessen.ccc.de<br />
<br />
=== Hamburg ===<br />
<br />
* https://hamburg.ccc.de/<br />
* https://chaos.social/@ccchh<br />
* https://wiki.hamburg.ccc.de/<br />
* https://gitlab.hamburg.ccc.de/<br />
* https://planet.hamburg.ccc.de/<br />
* https://cms.hamburg.ccc.de/ - Chaos macht Schule (school program)<br />
* https://oldwiki.hamburg.ccc.de/<br />
* https://easterhegg2003.hamburg.ccc.de/<br />
* https://easterhegg2005.hamburg.ccc.de/<br />
* https://easterhegg2007.hamburg.ccc.de/<br />
* https://easterhegg2009.hamburg.ccc.de/<br />
* https://easterhegg2011.hamburg.ccc.de/<br />
<br />
=== Hannover ===<br />
<br />
* https://hannover.ccc.de/<br />
<br />
=== Karlsruhe ===<br />
<br />
* https://entropia.de/<br />
<br />
=== Leipzig ===<br />
<br />
* https://dezentrale.space<br />
* https://git.dezentrale.cloud/<br />
* https://wiki.dezentrale.space/<br />
* https://chaos.social/@dezentrale<br />
* https://www.facebook.com/dezentrale.space/<br />
* https://twitter.com/dezentrale_eV<br />
<br />
=== Mannheim ===<br />
<br />
* https://dimension.mannheim.ccc.de/ - matrix chatbot?<br />
<br />
=== Munich ===<br />
<br />
* https://acab.muc.ccc.de/ - LED matrix project<br />
* https://acab2010.muc.ccc.de/ - LED matrix project<br />
* https://api.muc.ccc.de/ - API and small documentation<br />
* https://schule.muc.ccc.de/ - for student program "Chaos macht Schule" (semms kinda borked?)<br />
<br />
=== Ulm ===<br />
<br />
* https://www.frrm.de<br />
* https://archiv.ulm.ccc.de/ - archive, seems offline (403)<br />
* https://twitter.com/freiraum_ulm<br />
* https://www.facebook.com/HackerspaceUlm/<br />
<br />
== Chaostreffs ==<br />
<br />
=== Chaostreff Zentralschweiz ===<br />
<br />
* https://central-chaos.ch/<br />
* https://grindcore.ch/channel/chaostreff<br />
<br />
=== UN-Hack-Bar ===<br />
<br />
See [[Hackerspaces#UN-Hack-Bar]]<br />
<br />
== Personalities ==<br />
<br />
(If they run any projects or websites.) Not necessarily (still) members.<br />
<br />
=== Daniel Domscheit-Berg ===<br />
<br />
* https://twitter.com/verstehbahnhof<br />
<br />
=== Linus Neumann ===<br />
<br />
CCC spokesperson<br />
<br />
* https://linus-neumann.de/<br />
* https://www.youtube.com/@Linuzifer<br />
<br />
=== Markus Richter (monoxyd) ===<br />
<br />
* https://richter.fm/ - personal site and podcast hosting<br />
* https://mastodon.social/@monoxyd<br />
* https://twitter.com/monoxyd<br />
<br />
=== Tim Pritlove ===<br />
<br />
Active in all things podcasts, and does that for a living.<br />
<br />
* https://tim.pritlove.org/ - personal website/podcast<br />
* https://metaebene.me/ - “metaebene personal media”, his podcast outlet<br />
* https://podlove.org/ - wordpress podcast plugin<br />
* https://das-sendezentrum.de/ - podcasting community<br />
<br />
== Network Policy, Politics & Activism ==<br />
<br />
* https://digitalcourage.de/<br />
* https://digitalegesellschaft.de/<br />
<br />
== Podcasts ==<br />
<br />
* https://chaosradio.de/ - podcast of Berlin CCC subgroup, originally also broadcasted via local radio station<br />
* https://www.c-radar.de/ - monthly show on Radio Darmstadt (episodes hosted at [https://cdn.media.ccc.de/ cdn.media.ccc.de])<br />
* https://cre.fm/ - “Chaosradio Express”, long form interviews by Tim Pritlove<br />
* https://hackerfunk.ch/ - from Zurich<br />
* https://www.c3d2.de/radio.html - Pentaradio (Dresden)<br />
* https://www.c3d2.de/podcast.html - Pentacast (Dresden)<br />
* https://www.c3d2.de/pentamusic.html - Pentamusic (Dresden)<br />
<br />
== Loosely CCC-related Projects ==<br />
<br />
=== Judend Hackt ===<br />
<br />
Hacker youth project: “Making the world a better place with code”<br />
<br />
* https://jugendhackt.org/<br />
* https://www.youtube.com/@Jugendhackt<br />
* https://twitter.com/jugendhackt<br />
* https://www.instagram.com/jugendhackt/<br />
* https://www.facebook.com/jugendhackt<br />
* https://chaos.social/@jugendhackt<br />
* https://t.me/jugendhackt_info<br />
<br />
==== Local Labs and Contacts ====<br />
<br />
* https://alpaka.social/@potsdam<br />
* https://twitter.com/_TomNovy_<br />
* https://www.instagram.com/la_terra_trema/<br />
* https://www.instagram.com/anders.nikita/<br />
* https://twitter.com/jugendhacktMA<br />
* https://www.instagram.com/forum_mannheim/<br />
* https://twitter.com/jh_isenbuettel<br />
* https://instagram.com/jh_isenbuettel<br />
* https://alpaka.social/@jh_isenbuettel<br />
* https://www.instagram.com/jugendhackt.heilbronn/<br />
* https://twitter.com/piahanfeld<br />
<br />
=== Others ===<br />
<br />
* https://chaoswelle.de/ - amateur radio enthusiasts<br />
* https://coderdojo.com - teaching kids programming<br />
* https://www.cryptoparty.in - education on privacy, encryption and security<br />
* https://data-run.de/ - alternate reality game about surveillance<br />
* https://blog.ssdev.org/ - lockpicking for a sport club<br />
* https://wiki.ssdev.org<br />
<br />
== Code ==<br />
<br />
Send these to [[Codearchiver]] and [[Software Heritage]].<br />
<br />
* https://chaos.expert/ - from CCC-FFM<br />
* https://github.com/Binary-Kitchen/ - Hackspace in Regensburg, lots of soldering tutorials<br />
* https://github.com/frrm - Ulm hackerspace<br />
* https://gitlab.com/c3e - CCC Essen / foobar e.V. / chaospott chaospott.de<br />
* https://git.chaospott.de - Chaospott<br />
* https://git.flow3r.garden - CCCamp2023 badge repos<br />
* https://git.darmstadt.ccc.de<br />
* https://git.koeln.ccc.de<br />
* https://gitea.club.muc.ccc.de<br />
* https://gitea.muc.ccc.de<br />
* https://github.com/b4ckspace<br />
* https://github.com/c3d2<br />
* https://repos.ctdo.de/<br />
* https://github.com/chaosdorf<br />
* * https://git.dezentrale.cloud/<br />
<br />
== Mailing Lists ==<br />
<br />
=== Public Archive ===<br />
<br />
* https://lists.darmstadt.ccc.de/mailman/listinfo/public<br />
* https://www.hamburg.ccc.de/mailman/listinfo/talk - archive empty though?<br />
* https://lists.hackerspace-bamberg.de/postorius/lists/chaosmachtschule.lists.hackerspace-bamberg.de/<br />
<br />
=== Subscriber-only Archive ===<br />
<br />
* https://lists.aachen.ccc.de/listinfo/chaosschule/<br />
* https://lists.ccc-ffm.de/postorius/lists/public.lists.ccc-ffm.de/<br />
* https://lists.chaospott.de/postorius/lists/discuss.lists.chaospott.de/<br />
* https://lists.chaospott.de/postorius/lists/events.lists.chaospott.de/<br />
* https://lists.chaoswelle.de/listinfo/berlin<br />
* https://lists.metarheinmain.de/mailman/listinfo/tcg<br />
* https://lists.hackerspace-bamberg.de/postorius/lists/public.lists.hackerspace-bamberg.de/<br />
* https://lists.hackerspace-bamberg.de/postorius/lists/analogabend.lists.hackerspace-bamberg.de/<br />
* https://lists.hackerspace-bamberg.de/postorius/lists/franconian.lists.hackerspace-bamberg.de/<br />
* https://lists.chaostreff.ch/postorius/lists/basel.chaostreff.ch/<br />
* https://lists.chaostreff.ch/postorius/lists/swiss-chaos.chaostreff.ch/<br />
* https://lists.chaostreff.ch/postorius/lists/zentralschweiz.chaostreff.ch/<br />
* https://lists.chaostreff-dortmund.de/postorius/lists/discuss.lists.chaostreff-dortmund.de/</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Current_Projects&diff=45759Current Projects2020-11-12T17:23:34Z<p>Kpcyrd: Point #gokinjagokinjago to right irc network</p>
<hr />
<div>__NOTOC__<br />
== Archive Team recruiting ==<br />
* [[Dev|Want to code for Archive Team? Here's a starting point.]]<br />
* Help us: '''[[warrior|☞ Download and run your warrior ☜]]'''.<br><br />
* What's on: [http://tracker.archiveteam.org/ online tracker].<br><br />
<!--Combined project activity graphs [http://zeppelin.xrtc.net/corp.xrtc.net/shilling.corp.xrtc.net/project_items.html here].--><br />
<br />
== Warrior-based projects ==<br />
{{:CurrentWarriorProject}}<br />
* [[GitHub]]: Embraced-uh, I mean, bought by Microsoft. '''IRC Channel {{IRC|gitgud|network=hackint}}'''.<br />
* [[Tencent Weibo]]: Chinese Twitter-clone miniblog shutting down on September 28, 2020. '''IRC Channel {{IRC|twocents|network=hackint}}'''.<br />
<br />
<!-- Urgent projects --><br />
<!-- Long-term projects --><br />
* [[URLTeam]]: URL shorteners were a fucking awful idea. '''IRC Channel {{IRC|urlteam|network=hackint}}'''.<br />
<br />
=== Scripts only ===<br />
* Classic [[Google Sites]]: Making sites inaccessible to the public starting November 1, 2020. '''IRC Channel {{IRC|nearlylostmygoogles|network=hackint}}'''.<br />
<br />
== Manual projects ==<br />
* [[Coronavirus|2019-2020 coronavirus outbreak]]: Documenting and preserving data, events, and impacts of the virus on society. '''IRC Channel {{IRC|coronarchive|network=hackint}}'''<br />
* [[Yahoo! Groups]]: Years of internet threads, soon to go private-only. '''IRC Channel {{IRC|yahoosucks|network=hackint}}'''<br />
* [[ArchiveBot]]: For those with lots of disk space, bandwidth and long-term commitment. '''IRC Channel {{IRC|archivebot|network=hackint}}'''.<br />
* [[WikiTeam]]: Saving wikis dumps (XML). And their external links for the Wayback Machine (WARC) as well as exporting MediaWiki databases. Permanent effort, [https://github.com/WikiTeam/wikiteam/wiki/Tutorial#I_have_no_shell_access_to_server everyone can help] (you choose the size of your downloads). '''IRC Channel {{IRC|wikiteam|network=hackint}}'''.<br />
* [[MP3.com]]: Digging through the WayBack Machine's archives to build a database of all the DAM CDs made available through the site.<br />
<br />
== Upcoming & proposed projects ==<br />
<!-- Websites you would like to have archived. Please create a wikipage about the project with information about the website (shutting down? (when), why should it be archived, etc.). --><br />
<!-- Top priority: could disappear anytime now --><br />
<!-- Shutting down, definite deadline given --><br />
<!-- Shutting down, vague deadline given --><br />
* [[Kinja]]: Deleting all user pages, maybe? '''IRC Channel {{IRC|gokinjagokinjago|network=hackint}}'''.<br />
* [[Twitter]]: Deleting inactive accounts <s>2019-12-11</s> sometime. '''IRC Channel {{IRC|twitterdead}}'''.<br />
<!-- Shutting down, no deadline given --><br />
<!-- Archiving the archives --><br />
<!-- Misc. projects (unmaintained sites, distrust in owners) --><br />
* [[Imgur]]: Image hoster decided that using it for hosting images is not permitted. '''IRC Channel {{IRC|imgone}}'''.<br />
* [[JamiiForums]]: the Tanzanian government would like this gone. '''IRC Channel {{IRC|jammedforums}}'''.<br />
* [[LiveJournal]]: Very old, widely regarded as in decline, and has a lot of important stuff buried in it. '''IRC Channel {{IRC|recordedjournal}}'''.<br />
* [[Ownlog]]: Ownlog is losing popularity and support from its owners. '''IRC Channel {{IRC|pwnlog}}'''.<br />
* [[Reddit]]: Banning communities that generate bad PR for Reddit Inc. '''IRC Channel {{IRC|shreddit|network=hackint}}'''.<br />
* [[The Pirate Bay]]: Recently came back up, grabbing an archive for sanity's sake. '''IRC Channel {{IRC|yarharfiddlededee}}'''.<br />
* [[Valhalla]]: Where to store what even the [[Internet Archive]] doesn't have space for? '''IRC Channel {{IRC|huntinggrounds}}'''.<br />
* [[Giphy]]: Bought by Facebook, to be "integrated" (assimilated) into Instagram https://news.knowyourmeme.com/news/facebook-to-buy-giphy<br />
<br />
== Recently finished projects ==<br />
<!-- put projects here that are still in the tracker but not yet deleted so it won't confuse people --><br />
* [[Clutch]]: Game clips site that lost a clutch-or-kick bet, getting kicked on August 14 2020. '''IRC Channel {{IRC|pearls|network=hackint}}'''.<br />
* [[Bitbucket]]: Kicking the bucket on Mercurial repositories by July 1 2020 to worship Git instead. '''IRC Channel {{IRC|kickthebucket|network=hackint}}'''.<br />
* [[Mixer]]: Video game streaming network shutting down 2020-07-23. '''IRC Channel {{IRC|mixdown|network=hackint}}'''<br />
<br />
== Hiatus / Missed the Mark ==<br />
* [[Angelfire]]: Angelfire is a web hosting service that contains big chunks of early WWW history and has no proper backup. '''IRC Channel {{IRC|angelonfire}}'''.<br />
* [[Audit2014|Audit 2014]]: It's time to verify our shit. '''IRC Channel {{IRC|auditteam}}'''. THIS PROJECT IS ON HIATUS AND WILL BE RETURNED TO AS AUDIT2018.<br />
* [[Flickr]]: <s>[[Yahoo!]]</s> SmugMug decided to kill it after finding Yahoo!'s plans to do so before they were bought by Verizon. '''IRC Channel {{IRC|flickrfckr|network=hackint}}'''.<br />
* [[Freeml]]: Japanese mailing list provider is sending its final email 2019-12-02. '''IRC Channel {{IRC|fml}}'''.<br />
* [[FTP]]: Help us find and download all FTP sites! '''IRC Channel {{IRC|effteepee|network=hackint}}'''.<br />
* [[Google Groups]]: "Gone within a year" ([[User:Jscott|SketchCow]], 2016-06-07).<br />
* [[Google News Archive]]: Let's store all newspapers at Google, WCGW? '''IRC Channel {{IRC|papersplease}}'''.<br />
* [[DevPort]]: This [http://developerportfolio.com/ portfolio SaaS provider] has [http://www.lowendtalk.com/discussion/65135/need-some-help-saas-provider-is-dead-but-my-site-is-still-up-how-should-i-grab-it reportedly] been having infrastructure issues, and removed their social media accounts. Possible impending shutdown.<br />
* [[INTERNETARCHIVE.BAK]]: Grab a slice of the big cake of [[Internet Archive|The Archive]]! '''IRC Channel {{IRC|internetarchive.bak}}'''.<br />
* [[ISP Hosting]]: Finding ISP web hosting services before the Grim Reaper finds them. '''IRC Channel {{IRC|webroasting|network=hackint}}'''.<br />
* [[NewsGrabber]]: Saving all news articles. <!-- Help with server power or by finding more news sites.-->Currently paused. '''IRC Channel {{IRC|newsgrabber|network=hackint}}'''.<br />
* [[Project Newsletter]]: Archiving e-newsletters, currently in development. '''IRC Channel {{IRC|projectnewsletter}}'''.<br />
* [[Quizlet]]: Flashcards and other learning tools '''IRC Channel {{IRC|quizletusin}}'''.<br />
* [[Tumblr]]: [[Yahoo!]] considered killing it, now Yahoo has been acquired and Verizon declared war on NSFW blogs. '''IRC Channel {{IRC|tumbledown|network=hackint}}'''.<br />
* [[yuku]]: Lately yuku is very unstable and hosting thousands of forums. Project currently paused. '''IRC Channel {{IRC|archiveteam|network=hackint}}'''.<br />
<br />
<small>ArchiveTeam primarily uses the hackint IRC network – ircs://irc.hackint.org:6697 (TLS required) – webchat: https://webirc.hackint.org/ – [[Archiveteam:IRC|More info]]<br />
<small>ArchiveTeam also has some channels left on the EFnet IRC network – irc://irc.efnet.org – webchat: http://chat.efnet.org:9090 – [[Archiveteam:IRC|More info]]</small><br></div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=IRC_Channel&diff=45548IRC Channel2020-09-29T00:06:06Z<p>Kpcyrd: Point primary irc channel to hackint</p>
<hr />
<div>The official Archive Team '''IRC Channel''' is [ircs://irc.hackint.org:6697#archiveteam #archiveteam @ irc.hackint.org].<br />
<br />
Starring:<br />
*[[User:Jscott|Jscott]] as @SketchCow!<br />
*[[User:LesOrchard|LesOrchard]] as @lmorchard!<br />
*[[User:Morbus_Iff|Morbus_Iff]] as @MorbusIff!<br />
*[[User:Bbot|bbot]] as bierwagen, since EFnet services stole "bbot"!<br />
*[[User:Cassilda|Cassilda]] as Cassilda!<br />
*[[User:Liam|Liam]] as Inky!<br />
*[[User:Scumola|Scumola]] as swebb*!<br />
*[[User:Soult|Soult]] as soultcer!<br />
*[[User:Mattl|Mattl]] as mattl!<br />
*[[User:geneb|geneb]] as geneb!<br />
*[[User:Sevenspade|Sevenspade]] as Sevens!<br />
*[[User:Emijrp|emijrp]] as emijrp<br />
*[[User:Chronomex|chronomex]] as himself<br />
*[[User:Djsmiley2k|DJ Smiley2k]] as Smiley :)<br />
<br />
'''A list of other Archive Team project channels can be found at [[Archiveteam:IRC]].'''<br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Current_Projects&diff=45547Current Projects2020-09-29T00:01:59Z<p>Kpcyrd: Refer to hackint as the primary irc network</p>
<hr />
<div>__NOTOC__<br />
== Archive Team recruiting ==<br />
* [[Dev|Want to code for Archive Team? Here's a starting point.]]<br />
* Help us: '''[[warrior|☞ Download and run your warrior ☜]]'''.<br><br />
* What's on: [http://tracker.archiveteam.org/ online tracker].<br><br />
<!--Combined project activity graphs [http://zeppelin.xrtc.net/corp.xrtc.net/shilling.corp.xrtc.net/project_items.html here].--><br />
<br />
== Warrior-based projects ==<br />
{{:CurrentWarriorProject}}<br />
* [[GitHub]]: Embraced-uh, I mean, bought by Microsoft. '''IRC Channel {{IRC|gitgud|network=hackint}}'''.<br />
* [[Tencent Weibo]]: Chinese Twitter-clone miniblog shutting down on September 28, 2020. '''IRC Channel {{IRC|twocents|network=hackint}}'''.<br />
<br />
<!-- Urgent projects --><br />
<!-- Long-term projects --><br />
* [[URLTeam]]: URL shorteners were a fucking awful idea. '''IRC Channel {{IRC|urlteam}}'''.<br />
<br />
=== Scripts only ===<br />
* No script-only projects at this moment.<br />
<br />
== Manual projects ==<br />
* [[Coronavirus|2019-2020 coronavirus outbreak]]: Documenting and preserving data, events, and impacts of the virus on society. '''IRC Channel {{IRC|coronarchive}}'''<br />
* [[Yahoo! Groups]]: Years of internet threads, soon to go private-only. '''IRC Channel {{IRC|yahoosucks|network=hackint}}'''<br />
* [[ArchiveBot]]: For those with lots of disk space, bandwidth and long-term commitment. '''IRC Channel {{IRC|archivebot}}'''.<br />
* [[WikiTeam]]: Saving wikis dumps (XML). And their external links for the Wayback Machine (WARC) as well as exporting MediaWiki databases. Permanent effort, [https://github.com/WikiTeam/wikiteam/wiki/Tutorial#I_have_no_shell_access_to_server everyone can help] (you choose the size of your downloads). '''IRC Channel {{IRC|wikiteam}}'''.<br />
* [[MP3.com]]: Digging through the WayBack Machine's archives to build a database of all the DAM CDs made available through the site.<br />
<br />
== Upcoming & proposed projects ==<br />
<!-- Websites you would like to have archived. Please create a wikipage about the project with information about the website (shutting down? (when), why should it be archived, etc.). --><br />
<!-- Top priority: could disappear anytime now --><br />
<!-- Shutting down, definite deadline given --><br />
<!-- Shutting down, vague deadline given --><br />
* [[Kinja]]: Deleting all user pages, maybe? '''IRC Channel {{IRC|gokinjagokinjago}}'''.<br />
* [[Twitter]]: Deleting inactive accounts <s>2019-12-11</s> sometime. '''IRC Channel {{IRC|twitterdead}}'''.<br />
* Classic [[Google Sites]]: Making sites inaccessible to the public starting November 1, 2020. '''IRC Channel {{IRC|nearlylostmygoogles|network=hackint}}'''.<br />
<!-- Shutting down, no deadline given --><br />
<!-- Archiving the archives --><br />
<!-- Misc. projects (unmaintained sites, distrust in owners) --><br />
* [[Imgur]]: Image hoster decided that using it for hosting images is not permitted. '''IRC Channel {{IRC|imgone}}'''.<br />
* [[JamiiForums]]: the Tanzanian government would like this gone. '''IRC Channel {{IRC|jammedforums}}'''.<br />
* [[LiveJournal]]: Very old, widely regarded as in decline, and has a lot of important stuff buried in it. '''IRC Channel {{IRC|recordedjournal}}'''.<br />
* [[Ownlog]]: Ownlog is losing popularity and support from its owners. '''IRC Channel {{IRC|pwnlog}}'''.<br />
* [[Reddit]]: Banning communities that generate bad PR for Reddit Inc. '''IRC Channel {{IRC|shreddit|network=hackint}}'''.<br />
* [[The Pirate Bay]]: Recently came back up, grabbing an archive for sanity's sake. '''IRC Channel {{IRC|yarharfiddlededee}}'''.<br />
* [[Valhalla]]: Where to store what even the [[Internet Archive]] doesn't have space for? '''IRC Channel {{IRC|huntinggrounds}}'''.<br />
* [[Giphy]]: Bought by Facebook, to be "integrated" (assimilated) into Instagram https://news.knowyourmeme.com/news/facebook-to-buy-giphy<br />
<br />
== Recently finished projects ==<br />
<!-- put projects here that are still in the tracker but not yet deleted so it won't confuse people --><br />
* [[Clutch]]: Game clips site that lost a clutch-or-kick bet, getting kicked on August 14 2020. '''IRC Channel {{IRC|pearls|network=hackint}}'''.<br />
* [[Bitbucket]]: Kicking the bucket on Mercurial repositories by July 1 2020 to worship Git instead. '''IRC Channel {{IRC|kickthebucket|network=hackint}}'''.<br />
* [[Mixer]]: Video game streaming network shutting down 2020-07-23. '''IRC Channel {{IRC|mixdown|network=hackint}}'''<br />
<br />
== Hiatus / Missed the Mark ==<br />
* [[Angelfire]]: Angelfire is a web hosting service that contains big chunks of early WWW history and has no proper backup. '''IRC Channel {{IRC|angelonfire}}'''.<br />
* [[Audit2014|Audit 2014]]: It's time to verify our shit. '''IRC Channel {{IRC|auditteam}}'''. THIS PROJECT IS ON HIATUS AND WILL BE RETURNED TO AS AUDIT2018.<br />
* [[Flickr]]: <s>[[Yahoo!]]</s> SmugMug decided to kill it after finding Yahoo!'s plans to do so before they were bought by Verizon. '''IRC Channel {{IRC|flickrfckr}}'''.<br />
* [[Freeml]]: Japanese mailing list provider is sending its final email 2019-12-02. '''IRC Channel {{IRC|fml}}'''.<br />
* [[FTP]]: Help us find and download all FTP sites! '''IRC Channel {{IRC|effteepee}}'''.<br />
* [[Google Groups]]: "Gone within a year" ([[User:Jscott|SketchCow]], 2016-06-07).<br />
* [[Google News Archive]]: Let's store all newspapers at Google, WCGW? '''IRC Channel {{IRC|papersplease}}'''.<br />
* [[DevPort]]: This [http://developerportfolio.com/ portfolio SaaS provider] has [http://www.lowendtalk.com/discussion/65135/need-some-help-saas-provider-is-dead-but-my-site-is-still-up-how-should-i-grab-it reportedly] been having infrastructure issues, and removed their social media accounts. Possible impending shutdown.<br />
* [[INTERNETARCHIVE.BAK]]: Grab a slice of the big cake of [[Internet Archive|The Archive]]! '''IRC Channel {{IRC|internetarchive.bak}}'''.<br />
* [[ISP Hosting]]: Finding ISP web hosting services before the Grim Reaper finds them. '''IRC Channel {{IRC|webroasting}}'''.<br />
* [[NewsGrabber]]: Saving all news articles. <!-- Help with server power or by finding more news sites.-->Currently paused. '''IRC Channel {{IRC|newsgrabber}}'''.<br />
* [[Project Newsletter]]: Archiving e-newsletters, currently in development. '''IRC Channel {{IRC|projectnewsletter}}'''.<br />
* [[Quizlet]]: Flashcards and other learning tools '''IRC Channel {{IRC|quizletusin}}'''.<br />
* [[Tumblr]]: [[Yahoo!]] considered killing it, now Yahoo has been acquired and Verizon declared war on NSFW blogs. '''IRC Channel {{IRC|tumbledown}}'''.<br />
* [[yuku]]: Lately yuku is very unstable and hosting thousands of forums. Project currently paused. '''IRC Channel {{IRC|archiveteam}}'''.<br />
<br />
<small>ArchiveTeam primarily uses the hackint IRC network – ircs://irc.hackint.org:6697 (TLS required) – webchat: https://webirc.hackint.org/ – [[Archiveteam:IRC|More info]]<br />
<small>ArchiveTeam also has some channels left on the EFnet IRC network – irc://irc.efnet.org – webchat: http://chat.efnet.org:9090 – [[Archiveteam:IRC|More info]]</small><br></div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=TikTok&diff=45274TikTok2020-08-01T22:47:54Z<p>Kpcyrd: Add trump quote regarding tiktok ban</p>
<hr />
<div>{{Infobox project<br />
| title = TikTok<br />
| logo = TikTok logo.png<br />
| image = TikTok home page 2019-11-09.png<br />
| description = tiktok home page as seen on November 9, 2019<br />
| URL = https://www.tiktok.com/<br />
| project_status = {{online}} but possibly {{endangered}}<br />
| archiving_status = {{nosavedyet}}<br />
| irc = TikOff<br />
| irc_network = hackint<br />
}}<br />
<br />
'''TikTok''' is a social media app for short, user generated videos developed by the Chinese company ByteDance. The app was launched internationally in September 2017 and merged with musical.ly on 9 November 2017. It is currently under intense scrutiny for its collection and use of user data, primarily in its relationship with China.<ref>https://en.wikipedia.org/wiki/TikTok#User_privacy_concerns</ref><br />
<br />
== Douyin ==<br />
<br />
Douyin is the China-only version of TikTok.<br />
<br />
Sites:<br />
* https://www.douyin.com | Main page<br />
* https://sso.douyin.com | Some sort of login thing? Unsure<br />
* https://renzheng.douyin.com | Unsure<br />
* https://v.douyin.com | Redirects to iesdouyin, where videos are<br />
* https://open.douyin.com | Unsure<br />
* https://musician.douyin.com | Unsure<br />
* https://creator.douyin.com | Unsure<br />
* https://www.iesdouyin.com | Videos are seen on this page<br />
<br />
If anyone who can read Chinese would like to help out, that'd be great.<br />
<br />
== Archiving tools ==<br />
<br />
[https://github.com/ytdl-org/youtube-dl youtube-dl] is able to grab videos straight from the site<br />
<br />
A tool to [https://github.com/carcabot/tiktok-signature generate the signature] TikTok uses to sign all their requests exists and is actively updated<br />
<br />
=== TikTokTake ===<br />
<br />
Work is being done to create a tool that can get all of a users videos and WARC them up, that's being implemented in a cli tool and irc bot [https://github.com/JackDallas/TikTokTake TikTokTake]<br />
<br />
=== TikUp ===<br />
<br />
TikUp is a Python package that gets all videos from a user or a hashtag, and uploads them to the Internet Archive under `tiktok-<video id>`. [https://github.com/Coloradohusky/TikUp Github link]<br />
<br />
== Vital Signs ==<br />
<br />
* The first request for archival was in [https://old.reddit.com/r/Archiveteam/comments/dazw5l/tiktok/ October 2019] due to removal of pro-LGBTQ content, even in countries where homosexuality has never been illegal. <ref>[https://www.theguardian.com/technology/2019/sep/26/tiktoks-local-moderation-guidelines-ban-pro-lgbt-content "TikTok's local moderation guidelines ban pro-LGBT content"] - Article on ''The Guardian''</ref><br />
* Videos from Douyin (Chinese TikTok) can not be seen outside of China. <ref>[https://www.wired.com/story/tiktok-is-the-latest-window-into-chinas-police-state/ "TikTok - Yes, TikTok - Is the Latest Window Into China’s Police State"] - Article on ''Wired''</ref><br />
* In August 2020 Trump said "As far as TikTok is concerned, we're banning them from the United States," <ref>[https://web.archive.org/web/20200801075923/https://edition.cnn.com/2020/07/31/tech/tiktok-trump-bytedance-sale/index.html "Trump says he will ban TikTok"] - Article on CNN</ref><br />
<br />
== Archival Locations ==<br />
<br />
[https://archive.org/details/tiktoks Tiktok Video Bin] on the [[Internet Archive]] is where the TikToks uploaded with TikUp and all videos uploaded with the identifier 'tiktok-<video id>' go.<br />
<br />
== Notes ==<br />
<br />
* https://m.tiktok.com/v/<id> is a better way to archive videos, versus https://www.tiktok.com/@<username>/video/<id>. (because it requires the ID only, not the username and the ID)<br />
* Videos without sound can't be viewed or downloaded(it just says 'Video currently unavailable') on desktop, and their links don't work, but they can be viewed and downloaded on mobile.<br />
* If we wanted to make a Warrior, we could use https://vm.tiktok.com/*******/, I think it's alphanumeric, but I'm not sure if these links work for every TikTok<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Keybase&diff=44428Keybase2020-06-03T16:35:05Z<p>Kpcyrd: </p>
<hr />
<div>{{Infobox project<br />
| title = Keybase<br />
| logo = Keybase_logo_official.svg.png<br />
| image = Screenshot_2020-06-03_Keybase.png<br />
| description = keybase home page as seen on June 3, 2020<br />
| URL = https://keybase.io/<br />
| project_status = {{online}}<br />
| archiving_status = {{notsavedyet}}<br />
| irc_network = hackint<br />
}}<br />
<br />
'''Keybase''' is a public key directory that allows bi-directionally linking public keys to social media accounts. This is done with proofs to verify the account actually belongs to a given user. Keybase was launched 2014-02-14 and has 407,163 users (as of 2019-08-22).<br />
<br />
== Archiving ==<br />
<br />
There's a signed merkle tree that serves as a public audit log to prevent tampering. This tree could potentially be traversed to replicate the database. Relevant API endpoints are:<br />
<br />
https://keybase.io/_/api/1.0/merkle/root.json<br />
https://keybase.io/_/api/1.0/merkle/block.json?hash=77f89c806fe0f896<br />
<br />
Documentation is located here:<br />
<br />
https://keybase.io/docs/api/1.0/call/merkle/root<br />
https://keybase.io/docs/api/1.0/call/merkle/block<br />
<br />
== Vital Signs ==<br />
<br />
* On 2020-03-07 keybase announced they've been acquired by Zoom.</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Keybase&diff=44427Keybase2020-06-03T16:27:27Z<p>Kpcyrd: Created page with "{{Infobox project | title = Keybase | logo = Keybase_logo_official.svg.png | image = Screenshot_2020-06-03_Keybase.png | description = keybase home page as seen on June 3, 202..."</p>
<hr />
<div>{{Infobox project<br />
| title = Keybase<br />
| logo = Keybase_logo_official.svg.png<br />
| image = Screenshot_2020-06-03_Keybase.png<br />
| description = keybase home page as seen on June 3, 2020<br />
| URL = https://keybase.io/<br />
| project_status = {{online}}<br />
| archiving_status = {{notsavedyet}}<br />
| irc_network = hackint<br />
}}<br />
<br />
'''Keybase''' is a public key directory that allows bi-directionally linking public keys to social media accounts. This is done with proofs to verify the account actually belongs to a given user. Keybase was launched 2014-02-14 and has 407,163 users (as of 2019-08-22).<br />
<br />
== Archiving ==<br />
<br />
There's a signed merkle tree that serves as a public audit log to prevent tampering. This tree could potentially be traversed to replicate the database. Relevant API endpoints are:<br />
<br />
https://keybase.io/_/api/1.0/merkle/root.json<br />
https://keybase.io/_/api/1.0/merkle/block.json?hash=<hash><br />
<br />
== Vital Signs ==<br />
<br />
* On 2020-03-07 keybase announced they've been acquired by Zoom.</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=File:Keybase_logo_official.svg.png&diff=44426File:Keybase logo official.svg.png2020-06-03T16:10:44Z<p>Kpcyrd: </p>
<hr />
<div></div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=File:Screenshot_2020-06-03_Keybase.png&diff=44425File:Screenshot 2020-06-03 Keybase.png2020-06-03T16:08:34Z<p>Kpcyrd: </p>
<hr />
<div></div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=VampireFreaks&diff=43018VampireFreaks2020-02-01T14:33:10Z<p>Kpcyrd: </p>
<hr />
<div>{{Infobox project<br />
| title = VampireFreaks<br />
| logo = Vampirefreaks_logo.png<br />
| image = Screencapture-vampirefreaks-2020-01-31.jpg<br />
| URL = https://vampirefreaks.com/<br />
| project_status = {{offline}}<br />
| archiving_status = {{partiallysaved}}<br />
| source = https://github.com/ArchiveTeam/vampirefreaks-grab<br />
| tracker = http://tracker.archiveteam.org/vampirefreaks/<br />
| irc = lastbyte<br />
| irc_network = hackint<br />
}}<br />
<br />
VampireFreaks.com is an online community for the Gothic–industrial subcultures. Created by site owner Jet Berelson in 1999.<br />
<br />
== Shutdown announcement ==<br />
<br />
It's difficult to find the original source for this, but on 2019-06-17 it has been announced that the social network is shutting down on 2020-02-01.<br />
<br />
== Site structure ==<br />
<br />
The site is quite a rabbit hole and we haven't fully identified everything yet.<br />
<br />
* We've enumerated 121.663 account names and can continuously monitor for new signups.<br />
* Every user has a profile, some of them require a login<br />
* Every user has a gallery that may contain pictures hosted on pics.vampirefreaks.com, some of them require a login<br />
* A profile may embed a number of songs that are loaded from songs.vampirefreaks.com, the cdn structure is identical with pics.vampirefreaks.com<br />
* There seems to be a newsfeed style stream people post into<br />
* There's a forum<br />
* There are so called cults that seem to have their own "homepage" and may contain forums(?). Some(/All?) of them require us to join and some require an application process. We might have to pass on cults.</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Wget_with_Lua_hooks&diff=42978Wget with Lua hooks2020-01-26T20:13:28Z<p>Kpcyrd: Document build dependencies</p>
<hr />
<div>* New idea: add Lua scripting to wget.<br />
<br />
* Get the source from: https://github.com/ArchiveTeam/wget-lua<br />
* Old repo is located at https://github.com/alard/wget-lua/tree/lua<br />
<br />
<!-- If you get errors about 'lua_open' while compiling, try applying [http://paste.archivingyoursh.it/raw/manavagose this] patch. --><br />
* If you get errors about 'wget.pod' while compiling, try applying [http://paste.archivingyoursh.it/raw/dekasuroda this] patch.<br />
* Documentation (possibly outdated): https://github.com/alard/wget-lua/wiki/Wget-with-Lua-hooks<br />
<br />
Example usage:<br />
<pre><br />
wget http://www.archiveteam.org/ -r --lua-script=lua-example/print_parameters.lua<br />
</pre><br />
<br />
= Installation =<br />
<br />
<pre><br />
apt install build-essential git autoconf automake autopoint texinfo flex gperf autogen shtool liblua5.1-0-dev gnutls-dev<br />
git clone https://github.com/ArchiveTeam/wget-lua<br />
cd wget-lua<br />
./bootstrap<br />
./configure<br />
make<br />
mkdir -p ~/bin/ && cp ./src/wget ~/bin/wget-lua<br />
</pre><br />
<br />
= Why would this be useful? =<br />
<br />
== Custom error handling ==<br />
What to do in case of an error? Sometimes you want wget to retry the url if it gets a server error.<br />
<br />
<pre><br />
wget.callbacks.httploop_result = function(url, err, http_stat)<br />
if http_stat.statcode == 500 then<br />
-- try again<br />
return wget.actions.CONTINUE<br />
elseif http_statcode == 404 then<br />
-- stop<br />
return wget.actions.EXIT<br />
else<br />
-- let wget decide<br />
return wget.actions.NOTHING<br />
end<br />
end<br />
</pre><br />
<br />
== Custom decide rules ==<br />
Download this url or not?<br />
<br />
<pre><br />
wget.callbacks.download_child_p = function(urlpos, parent, depth, start_url_parsed, iri, verdict)<br />
if string.find(urlpos.url, "textfiles.com") then<br />
-- always download<br />
return true<br />
elseif string.find(urlpos.url, "archive.org") then<br />
-- never!<br />
return false<br />
else<br />
-- follow wget's advice<br />
return verdict<br />
end<br />
end<br />
</pre><br />
<br />
== Custom url extraction/generation ==<br />
Sometimes it's useful if you can write your own url extraction code, for example to add urls that aren't actually on the page.<br />
<br />
<pre><br />
wget.callbacks.get_urls = function(file, url, is_css, iri)<br />
if string.find(url, ".com/profile/[^/]+/$") then<br />
-- make sure wget downloads the user's photo page<br />
-- and custom profile photo<br />
return {<br />
{ url=url.."photo.html",<br />
link_expect_html=1,<br />
link_expect_css=0 },<br />
{ url=url.."photo.jpg",<br />
link_expect_html=0,<br />
link_expect_css=0 }<br />
}<br />
else<br />
-- no new urls to add<br />
return {}<br />
end<br />
end<br />
</pre><br />
<br />
== More Examples ==<br />
<br />
Archive Team has real life scripts on the [https://github.com/archiveteam Archive Team GitHub organization]. Look for recent <code>-grab</code> projects. The Lua scripts range from simple checks to complex URL scraping.<br />
<br />
* [https://github.com/ArchiveTeam/zapd-grab/blob/master/zapd.lua zapd-grab/zapd.lua]: Avoids JavaScript monstrosity by scraping anything that looks like an URL on CDN.<br />
* [https://github.com/ArchiveTeam/puush-grab/blob/master/puush.lua puush-grab/puush.lua]: Checks the status code and the contents and returns custom error codes.<br />
* [https://github.com/ArchiveTeam/posterous-grab/blob/master/posterous.lua posterous-grab/posterous.lua]: Checks the status code and delays if needed.<br />
* [https://github.com/ArchiveTeam/xanga-grab/blob/master/xanga.lua xanga-grab/xanga.lua]: Implements its own URLs scraping.<br />
* [https://github.com/ArchiveTeam/patch-grab/blob/master/patch.lua patch-grab/patch.lua]: Scrapes URLs as it goes along and sends it off to a server to be done later.<br />
* [https://github.com/ArchiveTeam/formspring-grab/blob/master/formspring.lua formspring-grab/formspring.lua]: Manually behaves like JavaScript and builds its own request URLs.<br />
* [https://github.com/ArchiveTeam/hyves-grab/blob/master/hyves.lua hyves-grab/hyves.lua]: Works around JavaScript calls to pagination. Includes calling external process to decrypt ciphertext.<br />
* [https://github.com/ArchiveTeam/ArchiveBot/blob/master/pipeline/archivebot.lua ArchiveBot/pipeline/archivebot.lua]: Logs results in Redis and implements custom URL checking.<br />
<br />
[[Category:Tools]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Wget_with_Lua_hooks&diff=42976Wget with Lua hooks2020-01-26T00:37:52Z<p>Kpcyrd: Add wget-lua install instructions</p>
<hr />
<div>* New idea: add Lua scripting to wget.<br />
<br />
* Get the source from: https://github.com/ArchiveTeam/wget-lua<br />
* Old repo is located at https://github.com/alard/wget-lua/tree/lua<br />
<br />
<!-- If you get errors about 'lua_open' while compiling, try applying [http://paste.archivingyoursh.it/raw/manavagose this] patch. --><br />
* If you get errors about 'wget.pod' while compiling, try applying [http://paste.archivingyoursh.it/raw/dekasuroda this] patch.<br />
* Documentation (possibly outdated): https://github.com/alard/wget-lua/wiki/Wget-with-Lua-hooks<br />
<br />
Example usage:<br />
<pre><br />
wget http://www.archiveteam.org/ -r --lua-script=lua-example/print_parameters.lua<br />
</pre><br />
<br />
= Installation =<br />
<br />
<pre><br />
git clone https://github.com/ArchiveTeam/wget-lua<br />
cd wget-lua<br />
./bootstrap<br />
./configure<br />
make<br />
mkdir -p ~/bin/ && cp ./src/wget ~/bin/wget-lua<br />
</pre><br />
<br />
= Why would this be useful? =<br />
<br />
== Custom error handling ==<br />
What to do in case of an error? Sometimes you want wget to retry the url if it gets a server error.<br />
<br />
<pre><br />
wget.callbacks.httploop_result = function(url, err, http_stat)<br />
if http_stat.statcode == 500 then<br />
-- try again<br />
return wget.actions.CONTINUE<br />
elseif http_statcode == 404 then<br />
-- stop<br />
return wget.actions.EXIT<br />
else<br />
-- let wget decide<br />
return wget.actions.NOTHING<br />
end<br />
end<br />
</pre><br />
<br />
== Custom decide rules ==<br />
Download this url or not?<br />
<br />
<pre><br />
wget.callbacks.download_child_p = function(urlpos, parent, depth, start_url_parsed, iri, verdict)<br />
if string.find(urlpos.url, "textfiles.com") then<br />
-- always download<br />
return true<br />
elseif string.find(urlpos.url, "archive.org") then<br />
-- never!<br />
return false<br />
else<br />
-- follow wget's advice<br />
return verdict<br />
end<br />
end<br />
</pre><br />
<br />
== Custom url extraction/generation ==<br />
Sometimes it's useful if you can write your own url extraction code, for example to add urls that aren't actually on the page.<br />
<br />
<pre><br />
wget.callbacks.get_urls = function(file, url, is_css, iri)<br />
if string.find(url, ".com/profile/[^/]+/$") then<br />
-- make sure wget downloads the user's photo page<br />
-- and custom profile photo<br />
return {<br />
{ url=url.."photo.html",<br />
link_expect_html=1,<br />
link_expect_css=0 },<br />
{ url=url.."photo.jpg",<br />
link_expect_html=0,<br />
link_expect_css=0 }<br />
}<br />
else<br />
-- no new urls to add<br />
return {}<br />
end<br />
end<br />
</pre><br />
<br />
== More Examples ==<br />
<br />
Archive Team has real life scripts on the [https://github.com/archiveteam Archive Team GitHub organization]. Look for recent <code>-grab</code> projects. The Lua scripts range from simple checks to complex URL scraping.<br />
<br />
* [https://github.com/ArchiveTeam/zapd-grab/blob/master/zapd.lua zapd-grab/zapd.lua]: Avoids JavaScript monstrosity by scraping anything that looks like an URL on CDN.<br />
* [https://github.com/ArchiveTeam/puush-grab/blob/master/puush.lua puush-grab/puush.lua]: Checks the status code and the contents and returns custom error codes.<br />
* [https://github.com/ArchiveTeam/posterous-grab/blob/master/posterous.lua posterous-grab/posterous.lua]: Checks the status code and delays if needed.<br />
* [https://github.com/ArchiveTeam/xanga-grab/blob/master/xanga.lua xanga-grab/xanga.lua]: Implements its own URLs scraping.<br />
* [https://github.com/ArchiveTeam/patch-grab/blob/master/patch.lua patch-grab/patch.lua]: Scrapes URLs as it goes along and sends it off to a server to be done later.<br />
* [https://github.com/ArchiveTeam/formspring-grab/blob/master/formspring.lua formspring-grab/formspring.lua]: Manually behaves like JavaScript and builds its own request URLs.<br />
* [https://github.com/ArchiveTeam/hyves-grab/blob/master/hyves.lua hyves-grab/hyves.lua]: Works around JavaScript calls to pagination. Includes calling external process to decrypt ciphertext.<br />
* [https://github.com/ArchiveTeam/ArchiveBot/blob/master/pipeline/archivebot.lua ArchiveBot/pipeline/archivebot.lua]: Logs results in Redis and implements custom URL checking.<br />
<br />
[[Category:Tools]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Wget_with_Lua_hooks&diff=42975Wget with Lua hooks2020-01-25T20:18:08Z<p>Kpcyrd: Update link to the current repo</p>
<hr />
<div>* New idea: add Lua scripting to wget.<br />
<br />
* Get the source from: https://github.com/ArchiveTeam/wget-lua<br />
* Old repo is located at https://github.com/alard/wget-lua/tree/lua<br />
<br />
<!-- If you get errors about 'lua_open' while compiling, try applying [http://paste.archivingyoursh.it/raw/manavagose this] patch. --><br />
* If you get errors about 'wget.pod' while compiling, try applying [http://paste.archivingyoursh.it/raw/dekasuroda this] patch.<br />
* Documentation (possibly outdated): https://github.com/alard/wget-lua/wiki/Wget-with-Lua-hooks<br />
<br />
Example usage:<br />
<pre><br />
wget http://www.archiveteam.org/ -r --lua-script=lua-example/print_parameters.lua<br />
</pre><br />
<br />
= Why would this be useful? =<br />
<br />
== Custom error handling ==<br />
What to do in case of an error? Sometimes you want wget to retry the url if it gets a server error.<br />
<br />
<pre><br />
wget.callbacks.httploop_result = function(url, err, http_stat)<br />
if http_stat.statcode == 500 then<br />
-- try again<br />
return wget.actions.CONTINUE<br />
elseif http_statcode == 404 then<br />
-- stop<br />
return wget.actions.EXIT<br />
else<br />
-- let wget decide<br />
return wget.actions.NOTHING<br />
end<br />
end<br />
</pre><br />
<br />
== Custom decide rules ==<br />
Download this url or not?<br />
<br />
<pre><br />
wget.callbacks.download_child_p = function(urlpos, parent, depth, start_url_parsed, iri, verdict)<br />
if string.find(urlpos.url, "textfiles.com") then<br />
-- always download<br />
return true<br />
elseif string.find(urlpos.url, "archive.org") then<br />
-- never!<br />
return false<br />
else<br />
-- follow wget's advice<br />
return verdict<br />
end<br />
end<br />
</pre><br />
<br />
== Custom url extraction/generation ==<br />
Sometimes it's useful if you can write your own url extraction code, for example to add urls that aren't actually on the page.<br />
<br />
<pre><br />
wget.callbacks.get_urls = function(file, url, is_css, iri)<br />
if string.find(url, ".com/profile/[^/]+/$") then<br />
-- make sure wget downloads the user's photo page<br />
-- and custom profile photo<br />
return {<br />
{ url=url.."photo.html",<br />
link_expect_html=1,<br />
link_expect_css=0 },<br />
{ url=url.."photo.jpg",<br />
link_expect_html=0,<br />
link_expect_css=0 }<br />
}<br />
else<br />
-- no new urls to add<br />
return {}<br />
end<br />
end<br />
</pre><br />
<br />
== More Examples ==<br />
<br />
Archive Team has real life scripts on the [https://github.com/archiveteam Archive Team GitHub organization]. Look for recent <code>-grab</code> projects. The Lua scripts range from simple checks to complex URL scraping.<br />
<br />
* [https://github.com/ArchiveTeam/zapd-grab/blob/master/zapd.lua zapd-grab/zapd.lua]: Avoids JavaScript monstrosity by scraping anything that looks like an URL on CDN.<br />
* [https://github.com/ArchiveTeam/puush-grab/blob/master/puush.lua puush-grab/puush.lua]: Checks the status code and the contents and returns custom error codes.<br />
* [https://github.com/ArchiveTeam/posterous-grab/blob/master/posterous.lua posterous-grab/posterous.lua]: Checks the status code and delays if needed.<br />
* [https://github.com/ArchiveTeam/xanga-grab/blob/master/xanga.lua xanga-grab/xanga.lua]: Implements its own URLs scraping.<br />
* [https://github.com/ArchiveTeam/patch-grab/blob/master/patch.lua patch-grab/patch.lua]: Scrapes URLs as it goes along and sends it off to a server to be done later.<br />
* [https://github.com/ArchiveTeam/formspring-grab/blob/master/formspring.lua formspring-grab/formspring.lua]: Manually behaves like JavaScript and builds its own request URLs.<br />
* [https://github.com/ArchiveTeam/hyves-grab/blob/master/hyves.lua hyves-grab/hyves.lua]: Works around JavaScript calls to pagination. Includes calling external process to decrypt ciphertext.<br />
* [https://github.com/ArchiveTeam/ArchiveBot/blob/master/pipeline/archivebot.lua ArchiveBot/pipeline/archivebot.lua]: Logs results in Redis and implements custom URL checking.<br />
<br />
[[Category:Tools]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Wget_with_WARC_output&diff=42974Wget with WARC output2020-01-25T19:04:50Z<p>Kpcyrd: Add --no-verbose to --input-file= example</p>
<hr />
<div>From the discussion about [[Working with ARCHIVE.ORG]], we learn that it is important to save not just files but also HTTP headers. With Wget, that's difficult. With a few tricks you can keep the response headers, but there is no option to save the request headers. You also lose the response headers that don't produce an HTML page: Wget doesn't save redirects and 404 responses.<br />
<br />
Since version 1.14<ref>https://twitter.com/anarchivist/statuses/232550155394641920</ref> [[Wget]] supports writing to a [http://www.digitalpreservation.gov/formats/fdd/fdd000236.shtml WARC] file (Web ARChive file format) file, just like Heritrix and other archiving tools. With the WARC format, both the request and the response headers get saved. It also provides a clean way to store redirects and 404 responses.<br />
<br />
There is an additional advantage: if Wget writes these headers to a WARC file, it is no longer necessary to use the <code>--save-headers</code> to save them at the top of each downloaded file. There is no need to remove these headers afterwards to produce a clean copy: the mirror produced by Wget is usable without post-processing.<br />
<br />
== Usage ==<br />
<br />
To download a file and save the request and response data to a WARC file, run this:<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --warc-file="at"<br />
</pre><br />
<br />
This will download the file to <code>index.html</code>, but it will also create a file <code>at-00000.warc.gz</code>. This is a gzipped WARC file that contains the request and response headers (of the initial redirect and of the Wiki homepage) and the html data.<br />
<br />
If you want to have an uncompressed WARC file, use the <code>--no-warc-compression</code> option:<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --warc-file="at" --no-warc-compression<br />
</pre><br />
<br />
Saving one file is nice, but the <code>warc-file</code> option becomes even more powerful if you combine it with Wget's mirror option: (You may want to try this with a smaller site than the AT wiki.)<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --mirror --warc-file="at"<br />
</pre><br />
<br />
If you uncompress <code>at-00000.warc.gz</code> and look at it, you'll see that it contains WARC records for every request and response: it is a complete copy of the mirrored site, while at the same time Wget also created the normal mirror of the site.<br />
<br />
If you have a list of urls that you want to write into an archive, but also want to store the original response for further processing you'd replace <code>--mirror</code> with <code>--input-file=urls.txt --force-directories</code>:<br />
<br />
<pre><br />
wget --no-verbose --input-file=urls.txt --force-directories --tries=3 --warc-file="at"<br />
</pre><br />
<br />
== Options ==<br />
<br />
<code>--warc-file=FILENAME</code> enables the WARC export. WARC files will be based on FILENAME: FILENAME-00000.warc.gz, FILENAME-00001.warc.gz et cetera.<br />
<br />
<code>--warc-max-size=NUMBER</code> defines the maximum size of the WARC files. The default is an infinite limit ("inf"). If you download a large site, the recommended limit is 1GB, set the option to 1G to enable this limit. Note that this is a soft limit: files can get slightly larger than this, depending on the files you download.<br />
<br />
<code>--warc-header=STRING</code> adds STRING as a custom header to the warcinfo record, e.g. "operator: Archive Team". This option can be used multiple times.<br />
<br />
<code>--warc-cdx=FILENAME</code> writes a CDX index file to FILENAME.cdx. The CDX file will contain a list of the records and their locations in the WARC files.<br />
<br />
<code>--warc-dedup=FILENAME</code> can be used to reduce the size of WARC files generated by a recrawl. FILENAME should point to a CDX file, generated with <code>--warc-cdx</code> in a previous run. For each file it downloads, Wget will check the CDX file to see if the response is listed there. If the exact file already exists, a "revisit" record with a reference to the previous record will be added to the WARC file, instead of a duplicate "response" record. Duplicate records are detected by comparing the SHA-1 digest of the payload of the response.<br />
<br />
<code>--no-warc-compression</code> will write uncompressed WARC files. Compression is enabled by default. It is better to use the built-in compression than to compress the WARC files afterwards. The built-in compression will compress each record as an individual GZIP block, which allows other utilities to extract single records from the file.<br />
<br />
<code>--no-warc-digests</code> disables the SHA-1 digests. By default, SHA-1 digests will be calculated for the whole response block and the response payload. If you really need to, you can disable that.<br />
<br />
<code>--no-warc-keep-log</code> can be set if you don't want the Wget log in the WARC file. By default, Wget will add the log file as a separate record to the WARC file.<br />
<br />
<code>--warc-tempdir=DIRECTORY</code> sets the temporary directory used by the WARC writer. The system tempdir will be used by default.<br />
<br />
== WARC file format ==<br />
<br />
The WARC file format is an ISO standard. The official specification of [http://www.iso.org/iso/catalogue_detail.htm?csnumber=44717 ISO 28500:2009] is not available for free. However, the [http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf WARC 1.0 final draft] and [http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1-1_latestdraft.pdf WARC 1.1 latest draft] are free, and are supposed to be technically equivalent to the official standard.<br />
<br />
The WARC usage task force has published [http://netpreserve.org/resources/WARC_Guidelines_v1.pdf WARC implementation guidelines] with additional recommendations.<br />
<br />
[[Category:Tools]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Wget_with_WARC_output&diff=42973Wget with WARC output2020-01-25T18:48:06Z<p>Kpcyrd: Add --input-file= --force-directories example</p>
<hr />
<div>From the discussion about [[Working with ARCHIVE.ORG]], we learn that it is important to save not just files but also HTTP headers. With Wget, that's difficult. With a few tricks you can keep the response headers, but there is no option to save the request headers. You also lose the response headers that don't produce an HTML page: Wget doesn't save redirects and 404 responses.<br />
<br />
Since version 1.14<ref>https://twitter.com/anarchivist/statuses/232550155394641920</ref> [[Wget]] supports writing to a [http://www.digitalpreservation.gov/formats/fdd/fdd000236.shtml WARC] file (Web ARChive file format) file, just like Heritrix and other archiving tools. With the WARC format, both the request and the response headers get saved. It also provides a clean way to store redirects and 404 responses.<br />
<br />
There is an additional advantage: if Wget writes these headers to a WARC file, it is no longer necessary to use the <code>--save-headers</code> to save them at the top of each downloaded file. There is no need to remove these headers afterwards to produce a clean copy: the mirror produced by Wget is usable without post-processing.<br />
<br />
== Usage ==<br />
<br />
To download a file and save the request and response data to a WARC file, run this:<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --warc-file="at"<br />
</pre><br />
<br />
This will download the file to <code>index.html</code>, but it will also create a file <code>at-00000.warc.gz</code>. This is a gzipped WARC file that contains the request and response headers (of the initial redirect and of the Wiki homepage) and the html data.<br />
<br />
If you want to have an uncompressed WARC file, use the <code>--no-warc-compression</code> option:<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --warc-file="at" --no-warc-compression<br />
</pre><br />
<br />
Saving one file is nice, but the <code>warc-file</code> option becomes even more powerful if you combine it with Wget's mirror option: (You may want to try this with a smaller site than the AT wiki.)<br />
<br />
<pre><br />
wget "http://www.archiveteam.org/" --mirror --warc-file="at"<br />
</pre><br />
<br />
If you uncompress <code>at-00000.warc.gz</code> and look at it, you'll see that it contains WARC records for every request and response: it is a complete copy of the mirrored site, while at the same time Wget also created the normal mirror of the site.<br />
<br />
If you have a list of urls that you want to write into an archive, but also want to store the original response for further processing you'd replace <code>--mirror</code> with <code>--input-file=urls.txt --force-directories</code>:<br />
<br />
<pre><br />
wget --input-file=urls.txt --force-directories --tries=3 --warc-file="at"<br />
</pre><br />
<br />
== Options ==<br />
<br />
<code>--warc-file=FILENAME</code> enables the WARC export. WARC files will be based on FILENAME: FILENAME-00000.warc.gz, FILENAME-00001.warc.gz et cetera.<br />
<br />
<code>--warc-max-size=NUMBER</code> defines the maximum size of the WARC files. The default is an infinite limit ("inf"). If you download a large site, the recommended limit is 1GB, set the option to 1G to enable this limit. Note that this is a soft limit: files can get slightly larger than this, depending on the files you download.<br />
<br />
<code>--warc-header=STRING</code> adds STRING as a custom header to the warcinfo record, e.g. "operator: Archive Team". This option can be used multiple times.<br />
<br />
<code>--warc-cdx=FILENAME</code> writes a CDX index file to FILENAME.cdx. The CDX file will contain a list of the records and their locations in the WARC files.<br />
<br />
<code>--warc-dedup=FILENAME</code> can be used to reduce the size of WARC files generated by a recrawl. FILENAME should point to a CDX file, generated with <code>--warc-cdx</code> in a previous run. For each file it downloads, Wget will check the CDX file to see if the response is listed there. If the exact file already exists, a "revisit" record with a reference to the previous record will be added to the WARC file, instead of a duplicate "response" record. Duplicate records are detected by comparing the SHA-1 digest of the payload of the response.<br />
<br />
<code>--no-warc-compression</code> will write uncompressed WARC files. Compression is enabled by default. It is better to use the built-in compression than to compress the WARC files afterwards. The built-in compression will compress each record as an individual GZIP block, which allows other utilities to extract single records from the file.<br />
<br />
<code>--no-warc-digests</code> disables the SHA-1 digests. By default, SHA-1 digests will be calculated for the whole response block and the response payload. If you really need to, you can disable that.<br />
<br />
<code>--no-warc-keep-log</code> can be set if you don't want the Wget log in the WARC file. By default, Wget will add the log file as a separate record to the WARC file.<br />
<br />
<code>--warc-tempdir=DIRECTORY</code> sets the temporary directory used by the WARC writer. The system tempdir will be used by default.<br />
<br />
== WARC file format ==<br />
<br />
The WARC file format is an ISO standard. The official specification of [http://www.iso.org/iso/catalogue_detail.htm?csnumber=44717 ISO 28500:2009] is not available for free. However, the [http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf WARC 1.0 final draft] and [http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1-1_latestdraft.pdf WARC 1.1 latest draft] are free, and are supposed to be technically equivalent to the official standard.<br />
<br />
The WARC usage task force has published [http://netpreserve.org/resources/WARC_Guidelines_v1.pdf WARC implementation guidelines] with additional recommendations.<br />
<br />
[[Category:Tools]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=VampireFreaks&diff=42971VampireFreaks2020-01-25T04:05:38Z<p>Kpcyrd: </p>
<hr />
<div>{{Infobox project<br />
| title = VampireFreaks<br />
| URL = https://vampirefreaks.com/<br />
| project_status = {{closing}}<br />
| archiving_status = {{nosavedyet}}<br />
| irc = lastbyte<br />
| irc_network = hackint<br />
}}<br />
<br />
VampireFreaks.com is an online community for the Gothic–industrial subcultures. Created by site owner Jet Berelson in 1999.<br />
<br />
== Shutdown announcement ==<br />
<br />
It's difficult to find the original source for this, but on 2019-06-17 it has been announced that the social network is shutting down on 2020-02-01.<br />
<br />
== Site structure ==<br />
<br />
The site is quite a rabbit hole and we haven't fully identified everything yet.<br />
<br />
* We've enumerated 121.663 account names and can continuously monitor for new signups.<br />
* Every user has a profile, some of them require a login<br />
* Every user has a gallery that may contain pictures hosted on pics.vampirefreaks.com, some of them require a login<br />
* A profile may embed a number of songs that are loaded from songs.vampirefreaks.com, the cdn structure is identical with pics.vampirefreaks.com<br />
* There seems to be a newsfeed style stream people post into<br />
* There's a forum<br />
* There are so called cults that seem to have their own "homepage" and may contain forums(?). Some(/All?) of them require us to join and some require an application process. We might have to pass on cults.</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=VampireFreaks&diff=42969VampireFreaks2020-01-24T18:41:56Z<p>Kpcyrd: Created page with "{{Infobox project | title = VampireFreaks | URL = https://vampirefreaks.com/ | project_status = {{closing}} | archiving_status = {{nosavedyet}} | irc = lastbyte | irc_network..."</p>
<hr />
<div>{{Infobox project<br />
| title = VampireFreaks<br />
| URL = https://vampirefreaks.com/<br />
| project_status = {{closing}}<br />
| archiving_status = {{nosavedyet}}<br />
| irc = lastbyte<br />
| irc_network = hackint<br />
}}<br />
<br />
VampireFreaks.com is an online community for the Gothic–industrial subcultures. Created by site owner Jet Berelson in 1999.</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42929Archiveteam:IRC2020-01-13T04:02:48Z<p>Kpcyrd: /* Connecting */</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFnet, one of the networks that ArchiveTeam uses, provides a [http://www.efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface]. A comprehensive comparison between the two networks by JAA can be found under [[User:JustAnotherArchivist/hackint vs EFnet]].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [https://archive.fart.website/bin/irclogger_logs search the logs].<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://www.efnet.org/ EFnet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [https://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== hackint specifics ==<br />
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.<br />
<br />
=== Connecting ===<br />
hackint enforces secure connections with TLS (aka "SSL"). The servers have valid certificates, so do ''not'' disable certificate verification in your client when connecting to hackint (or enable it if disabled by default, e.g. use <code>-ssl_verify</code> on irssi and WeeChat).<br />
<br />
==== Weechat ====<br />
<br />
: <code>/server add hackint irc.hackint.org/6697 -ssl -autoconnect</code><br />
: <code>/save</code><br />
: <code>/connect hackint</code><br />
<br />
=== Services & authentication ===<br />
hackint has the usual services one would expect from a sensible IRC network: NickServ to register user accounts, ChanServ to manage channels, HostServ for hostmasks, MemoServ for sending messages (memos) to users currently offline or groups, and GroupServ for groups of people.<br />
<br />
The most important part for most users is registering and authenticating a user account. To register, issue:<br />
<br />
: <code>/msg NickServ REGISTER password email@example.org</code><br />
<br />
A verification email is sent to the email address entered here; this email address is needed for recovery in case you ever lose the authentication data for your nick.<br />
<br />
After registration, you need to authenticate on every connection. There are several ways how you can do that: CertFP (see below), different SASL methods, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>.<br />
<br />
==== Auto Login with SASL (weechat) ====<br />
<br />
After you've followed the instructions to register an account you can setup weechat to automatically log you in when connecting to the irc network. Issue the following commands to configure your account, save the config and then reconnect to test it:<br />
<br />
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code><br />
: <code>/set irc.server.hackint.sasl_username <login></code><br />
: <code>/set irc.server.hackint.sasl_password <password></code><br />
: <code>/save</code><br />
: <code>/reconnect hackint</code><br />
<br />
==== CertFP ====<br />
To authenticate using CertFP, you need to generate a client certificate. For example:<br />
<br />
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code><br />
<br />
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:<br />
<br />
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code><br />
: <code>chmod 600 /secure/path/nick.pem</code><br />
<br />
Then, instruct your client to use this certificate on connecting to hackint. For example, on irssi, you need to add the <code>-ssl_cert /secure/path/nick.pem</code> option to the <code>/server add</code> command. Instructions for other clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].<br />
<br />
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):<br />
<br />
: <code>/msg NickServ CERT ADD</code><br />
<br />
On any later connections, you will get authenticated automatically and immediately.<br />
<br />
=== Creating a channel ===<br />
If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the <code>!archiveteam-core</code> group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
: <code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
This grants everyone in that group full control over the channel.<br />
<br />
=== Virtual hosts (vhosts) ===<br />
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:<br />
<br />
: <code>/msg HostServ TAKE archiveteam/$account</code><br />
<br />
(<code>$account</code> is not a placeholder; enter it literally.)<br />
<br />
If you are not part of the group, you can use the general hackint vhost:<br />
<br />
: <code>/msg HostServ TAKE hackint/user/$account</code><br />
<br />
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42928Archiveteam:IRC2020-01-13T04:02:01Z<p>Kpcyrd: /* Auto Login with SASL (weechat) */</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFnet, one of the networks that ArchiveTeam uses, provides a [http://www.efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface]. A comprehensive comparison between the two networks by JAA can be found under [[User:JustAnotherArchivist/hackint vs EFnet]].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [https://archive.fart.website/bin/irclogger_logs search the logs].<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://www.efnet.org/ EFnet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [https://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== hackint specifics ==<br />
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.<br />
<br />
=== Connecting ===<br />
hackint enforces secure connections with TLS (aka "SSL"). The servers have valid certificates, so do ''not'' disable certificate verification in your client when connecting to hackint (or enable it if disabled by default, e.g. use <code>-ssl_verify</code> on irssi and WeeChat).<br />
<br />
==== Auto Connecting (weechat) ====<br />
<br />
: <code>/server add hackint irc.hackint.org/6697 -ssl -autoconnect</code><br />
: <code>/save</code><br />
: <code>/connect hackint</code><br />
<br />
=== Services & authentication ===<br />
hackint has the usual services one would expect from a sensible IRC network: NickServ to register user accounts, ChanServ to manage channels, HostServ for hostmasks, MemoServ for sending messages (memos) to users currently offline or groups, and GroupServ for groups of people.<br />
<br />
The most important part for most users is registering and authenticating a user account. To register, issue:<br />
<br />
: <code>/msg NickServ REGISTER password email@example.org</code><br />
<br />
A verification email is sent to the email address entered here; this email address is needed for recovery in case you ever lose the authentication data for your nick.<br />
<br />
After registration, you need to authenticate on every connection. There are several ways how you can do that: CertFP (see below), different SASL methods, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>.<br />
<br />
==== Auto Login with SASL (weechat) ====<br />
<br />
After you've followed the instructions to register an account you can setup weechat to automatically log you in when connecting to the irc network. Issue the following commands to configure your account, save the config and then reconnect to test it:<br />
<br />
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code><br />
: <code>/set irc.server.hackint.sasl_username <login></code><br />
: <code>/set irc.server.hackint.sasl_password <password></code><br />
: <code>/save</code><br />
: <code>/reconnect hackint</code><br />
<br />
==== CertFP ====<br />
To authenticate using CertFP, you need to generate a client certificate. For example:<br />
<br />
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code><br />
<br />
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:<br />
<br />
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code><br />
: <code>chmod 600 /secure/path/nick.pem</code><br />
<br />
Then, instruct your client to use this certificate on connecting to hackint. For example, on irssi, you need to add the <code>-ssl_cert /secure/path/nick.pem</code> option to the <code>/server add</code> command. Instructions for other clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].<br />
<br />
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):<br />
<br />
: <code>/msg NickServ CERT ADD</code><br />
<br />
On any later connections, you will get authenticated automatically and immediately.<br />
<br />
=== Creating a channel ===<br />
If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the <code>!archiveteam-core</code> group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
: <code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
This grants everyone in that group full control over the channel.<br />
<br />
=== Virtual hosts (vhosts) ===<br />
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:<br />
<br />
: <code>/msg HostServ TAKE archiveteam/$account</code><br />
<br />
(<code>$account</code> is not a placeholder; enter it literally.)<br />
<br />
If you are not part of the group, you can use the general hackint vhost:<br />
<br />
: <code>/msg HostServ TAKE hackint/user/$account</code><br />
<br />
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42927Archiveteam:IRC2020-01-13T03:59:17Z<p>Kpcyrd: /* Auto Connecting (weechat) */</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFnet, one of the networks that ArchiveTeam uses, provides a [http://www.efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface]. A comprehensive comparison between the two networks by JAA can be found under [[User:JustAnotherArchivist/hackint vs EFnet]].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [https://archive.fart.website/bin/irclogger_logs search the logs].<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://www.efnet.org/ EFnet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [https://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== hackint specifics ==<br />
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.<br />
<br />
=== Connecting ===<br />
hackint enforces secure connections with TLS (aka "SSL"). The servers have valid certificates, so do ''not'' disable certificate verification in your client when connecting to hackint (or enable it if disabled by default, e.g. use <code>-ssl_verify</code> on irssi and WeeChat).<br />
<br />
==== Auto Connecting (weechat) ====<br />
<br />
: <code>/server add hackint irc.hackint.org/6697 -ssl -autoconnect</code><br />
: <code>/save</code><br />
: <code>/connect hackint</code><br />
<br />
=== Services & authentication ===<br />
hackint has the usual services one would expect from a sensible IRC network: NickServ to register user accounts, ChanServ to manage channels, HostServ for hostmasks, MemoServ for sending messages (memos) to users currently offline or groups, and GroupServ for groups of people.<br />
<br />
The most important part for most users is registering and authenticating a user account. To register, issue:<br />
<br />
: <code>/msg NickServ REGISTER password email@example.org</code><br />
<br />
A verification email is sent to the email address entered here; this email address is needed for recovery in case you ever lose the authentication data for your nick.<br />
<br />
After registration, you need to authenticate on every connection. There are several ways how you can do that: CertFP (see below), different SASL methods, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>.<br />
<br />
==== Auto Login with SASL (weechat) ====<br />
<br />
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code><br />
: <code>/set irc.server.hackint.sasl_username <login></code><br />
: <code>/set irc.server.hackint.sasl_password <password></code><br />
: <code>/save</code><br />
<br />
==== CertFP ====<br />
To authenticate using CertFP, you need to generate a client certificate. For example:<br />
<br />
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code><br />
<br />
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:<br />
<br />
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code><br />
: <code>chmod 600 /secure/path/nick.pem</code><br />
<br />
Then, instruct your client to use this certificate on connecting to hackint. For example, on irssi, you need to add the <code>-ssl_cert /secure/path/nick.pem</code> option to the <code>/server add</code> command. Instructions for other clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].<br />
<br />
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):<br />
<br />
: <code>/msg NickServ CERT ADD</code><br />
<br />
On any later connections, you will get authenticated automatically and immediately.<br />
<br />
=== Creating a channel ===<br />
If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the <code>!archiveteam-core</code> group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
: <code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
This grants everyone in that group full control over the channel.<br />
<br />
=== Virtual hosts (vhosts) ===<br />
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:<br />
<br />
: <code>/msg HostServ TAKE archiveteam/$account</code><br />
<br />
(<code>$account</code> is not a placeholder; enter it literally.)<br />
<br />
If you are not part of the group, you can use the general hackint vhost:<br />
<br />
: <code>/msg HostServ TAKE hackint/user/$account</code><br />
<br />
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42926Archiveteam:IRC2020-01-13T03:58:40Z<p>Kpcyrd: Add "Auto Connecting (weechat)"</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFnet, one of the networks that ArchiveTeam uses, provides a [http://www.efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface]. A comprehensive comparison between the two networks by JAA can be found under [[User:JustAnotherArchivist/hackint vs EFnet]].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [https://archive.fart.website/bin/irclogger_logs search the logs].<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://www.efnet.org/ EFnet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [https://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== hackint specifics ==<br />
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.<br />
<br />
=== Connecting ===<br />
hackint enforces secure connections with TLS (aka "SSL"). The servers have valid certificates, so do ''not'' disable certificate verification in your client when connecting to hackint (or enable it if disabled by default, e.g. use <code>-ssl_verify</code> on irssi and WeeChat).<br />
<br />
==== Auto Connecting (weechat) ====<br />
<br />
: <code>/server add hackint irc.hackint.org/6697 -ssl -autoconnect</code><br />
<br />
=== Services & authentication ===<br />
hackint has the usual services one would expect from a sensible IRC network: NickServ to register user accounts, ChanServ to manage channels, HostServ for hostmasks, MemoServ for sending messages (memos) to users currently offline or groups, and GroupServ for groups of people.<br />
<br />
The most important part for most users is registering and authenticating a user account. To register, issue:<br />
<br />
: <code>/msg NickServ REGISTER password email@example.org</code><br />
<br />
A verification email is sent to the email address entered here; this email address is needed for recovery in case you ever lose the authentication data for your nick.<br />
<br />
After registration, you need to authenticate on every connection. There are several ways how you can do that: CertFP (see below), different SASL methods, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>.<br />
<br />
==== Auto Login with SASL (weechat) ====<br />
<br />
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code><br />
: <code>/set irc.server.hackint.sasl_username <login></code><br />
: <code>/set irc.server.hackint.sasl_password <password></code><br />
: <code>/save</code><br />
<br />
==== CertFP ====<br />
To authenticate using CertFP, you need to generate a client certificate. For example:<br />
<br />
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code><br />
<br />
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:<br />
<br />
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code><br />
: <code>chmod 600 /secure/path/nick.pem</code><br />
<br />
Then, instruct your client to use this certificate on connecting to hackint. For example, on irssi, you need to add the <code>-ssl_cert /secure/path/nick.pem</code> option to the <code>/server add</code> command. Instructions for other clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].<br />
<br />
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):<br />
<br />
: <code>/msg NickServ CERT ADD</code><br />
<br />
On any later connections, you will get authenticated automatically and immediately.<br />
<br />
=== Creating a channel ===<br />
If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the <code>!archiveteam-core</code> group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
: <code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
This grants everyone in that group full control over the channel.<br />
<br />
=== Virtual hosts (vhosts) ===<br />
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:<br />
<br />
: <code>/msg HostServ TAKE archiveteam/$account</code><br />
<br />
(<code>$account</code> is not a placeholder; enter it literally.)<br />
<br />
If you are not part of the group, you can use the general hackint vhost:<br />
<br />
: <code>/msg HostServ TAKE hackint/user/$account</code><br />
<br />
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42925Archiveteam:IRC2020-01-13T03:57:44Z<p>Kpcyrd: Add "Auto Login with SASL (weechat)"</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFnet, one of the networks that ArchiveTeam uses, provides a [http://www.efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface]. A comprehensive comparison between the two networks by JAA can be found under [[User:JustAnotherArchivist/hackint vs EFnet]].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [https://archive.fart.website/bin/irclogger_logs search the logs].<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>https://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>https://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://www.efnet.org/ EFnet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [https://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== hackint specifics ==<br />
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.<br />
<br />
=== Connecting ===<br />
hackint enforces secure connections with TLS (aka "SSL"). The servers have valid certificates, so do ''not'' disable certificate verification in your client when connecting to hackint (or enable it if disabled by default, e.g. use <code>-ssl_verify</code> on irssi and WeeChat).<br />
<br />
=== Services & authentication ===<br />
hackint has the usual services one would expect from a sensible IRC network: NickServ to register user accounts, ChanServ to manage channels, HostServ for hostmasks, MemoServ for sending messages (memos) to users currently offline or groups, and GroupServ for groups of people.<br />
<br />
The most important part for most users is registering and authenticating a user account. To register, issue:<br />
<br />
: <code>/msg NickServ REGISTER password email@example.org</code><br />
<br />
A verification email is sent to the email address entered here; this email address is needed for recovery in case you ever lose the authentication data for your nick.<br />
<br />
After registration, you need to authenticate on every connection. There are several ways how you can do that: CertFP (see below), different SASL methods, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>.<br />
<br />
==== Auto Login with SASL (weechat) ====<br />
<br />
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code><br />
: <code>/set irc.server.hackint.sasl_username <login></code><br />
: <code>/set irc.server.hackint.sasl_password <password></code><br />
: <code>/save</code><br />
<br />
==== CertFP ====<br />
To authenticate using CertFP, you need to generate a client certificate. For example:<br />
<br />
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code><br />
<br />
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:<br />
<br />
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code><br />
: <code>chmod 600 /secure/path/nick.pem</code><br />
<br />
Then, instruct your client to use this certificate on connecting to hackint. For example, on irssi, you need to add the <code>-ssl_cert /secure/path/nick.pem</code> option to the <code>/server add</code> command. Instructions for other clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].<br />
<br />
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):<br />
<br />
: <code>/msg NickServ CERT ADD</code><br />
<br />
On any later connections, you will get authenticated automatically and immediately.<br />
<br />
=== Creating a channel ===<br />
If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the <code>!archiveteam-core</code> group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
: <code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
This grants everyone in that group full control over the channel.<br />
<br />
=== Virtual hosts (vhosts) ===<br />
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:<br />
<br />
: <code>/msg HostServ TAKE archiveteam/$account</code><br />
<br />
(<code>$account</code> is not a placeholder; enter it literally.)<br />
<br />
If you are not part of the group, you can use the general hackint vhost:<br />
<br />
: <code>/msg HostServ TAKE hackint/user/$account</code><br />
<br />
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42896Archiveteam:IRC2020-01-07T15:40:20Z<p>Kpcyrd: Document hackint specifics</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
The ArchiveTeam uses IRC as its one-stop shop for coordinating official and unofficial AT projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.'''<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFNet, the network that Archive Team uses, provides a [http://efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
Since September 2019, most project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [http://archive.fart.website/bin/irclogger_logs search the logs].<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://efnet.org EFNet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| Archive Team || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [http://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at http://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
== Hackint specifics ==<br />
<br />
This section is documenting how to successfully run archiveteam channels on the hackint irc network.<br />
<br />
=== Creating a channel ===<br />
<br />
If you're opening a channel for archiveteam usage it is recommended to register it and setting the right flags for the archiveteam-core group. Make sure you're identified with NickServ.<br />
<br />
Registering the channel is done with:<br />
<br />
<code>/msg ChanServ REGISTER #example</code><br />
<br />
And setting the flags is done with:<br />
<br />
<code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code><br />
<br />
=== Using an archiveteam hostmask ===<br />
<br />
If you are part of the archiveteam group in GroupServ you can use an archiveteam host mask with:<br />
<br />
<code>/msg hostserv take archiveteam-core/$account</code><br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Archiveteam:IRC&diff=42748Archiveteam:IRC2019-12-20T04:40:23Z<p>Kpcyrd: Add a link for hackint web interface</p>
<hr />
<div>'''IRC''' (Internet Relay Chat) is an internet protocol that allows multiple users to connect to a server and chat. Each IRC "server" can be connected to by a person, then someone joins a "channel" with the particular subject they are interested in.<br />
<br />
The ArchiveTeam uses IRC as its one-stop shop for coordinating official and unofficial AT projects.<br />
<br />
'''Before you go ahead and jump in, if there's nothing else you read on this page please at least take a moment to review the [[#Special ArchiveTeam IRC rules|Special ArchiveTeam IRC rules]] section below.<br />
<br />
== How do I chat on IRC? ==<br />
<br />
You will need an IRC client, or you can use a web interface.<br />
<br />
EFNet, the network that Archive Team uses, provides a [http://efnet.org/ web interface called Webchat]. Enter a nickname (such as your first name, your pet's name, or a cool pseudonym of your choice) and then the channel's name, ie <code>#archiveteam</code>.<br />
<br />
In recent months, newer project-specific channels have been hosted on the [https://www.hackint.org/ hackint IRC network] due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a [https://webirc.hackint.org/#irc://irc.hackint.org/#archiveteam web interface].<br />
<br />
{{notice|1=Please learn IRC '''netiquette'''.<br />
<br />
''Do not barge into an IRC channel demanding help or disparage installation instructions.''<br />
<br />
Archive Team is not a professional support team.<br />
}}<br />
<br />
=== Do I have to use IRC? ===<br />
<br />
We prefer IRC because there is no central point of failure, but see the question about social media on [[Frequently Asked Questions]].<br />
<br />
=== Why does IRC need chat logs? ===<br />
<br />
Unlike a bulletin board or SMS, IRC is a transient medium of communication. As a result, if you aren't there to receive the message, you will never receive it at all.<br />
<br />
If you check the chat logs, your question may already be answered. Unfortunately, some channels are not logged. Don't worry if you accidentally interrupt someone's conversation or repeat a question.<br />
<br />
See the section [[#IRC_Logs|IRC Logs]].<br />
<br />
=== I asked a question and waited but it scrolled off the window and was ignored. ===<br />
<br />
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.<br />
<br />
=== How do I get someone's attention in a public channel? ===<br />
<br />
Some chat clients will alert the user if you say their nickname.<br />
<br />
Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.<br />
<br />
=== Why won't anyone respond? ===<br />
<br />
If no one answers, please be patient. We're volunteers so we can't always respond immediately. We eat, drink, sleep, and archive just like you! Note that IRC channels are '''not''' like Discord, Telegram, Slack, or similar channels - do not expect real-time responses the next second. Wait a few minutes, but be prepared to stay around for a little bit.<br />
<br />
Sometimes it may be the [https://en.wikipedia.org/wiki/Bystander_effect bystander effect]. Try an [https://en.wiktionary.org/wiki/icebreaker icebreaker] to get the conversation going.<br />
<br />
=== I can't wait; I need immediate attention. Who's in charge? ===<br />
<br />
See [[Who We Are]].<br />
<br />
=== Special ArchiveTeam IRC rules ===<br />
<br />
Besides the expectation of being civilized, patient and tactful, there are some rules you should follow when in ArchiveTeam IRC channels. Breaking them makes you become annoying in the community and you can easily find yourself banned. The most pertinent of these are as follows:<br />
<br />
* <code>#archiveteam</code> is generally reserved for short and important information exchange, e.g. concise announcements about websites shutting down, project status updates, easily answerable important questions, etc. '''All general and in-depth archiving-related discussion happens in <code>#archiveteam-bs</code>''' (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their [[Projects|respective]] channels. General topics not related to computers and/or archiving at all are not welcome even in <code>#archiveteam-bs</code> (try <code>#archiveteam-ot</code> for such topics instead).<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=110#l106</ref><br />
* Don't ask too many questions, don't demand answers from others. Sometimes you can look it up yourself, sometimes you need to filter your questions for important ones. You can also [http://archive.fart.website/bin/irclogger_logs search the logs].<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2014-09-09,Tue&sel=126#l122</ref><br />
* Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-02,Sat&sel=143#l139</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-02-15,Mon&sel=43#l39</ref> If you have a remark/idea, be concrete and constructive (and polite and patient), and if you can, realize it yourself (we're volunteers otherwise busy). Remember the money-back guarantee!<ref name="moneybackguarantee">http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-07-05,Sun&sel=170#l166</ref><br />
* Don't try to convince ArchiveTeam about that archiving is bad. We make very few exceptions when it's about archiving. Also, our rule of thumb is "archive first, ask questions later".<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-25,Thu&sel=58#l54</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=154#l150</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=231#l227</ref> Our IRC channels are the #1 worst place to ask "why we are keeping this"!<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-10-17,Sat&sel=233#l229</ref><br />
* Don't be childish.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2015-10-28,Wed&sel=7#l3</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-01-09,Sat&sel=285#l281</ref><ref name="moneybackguarantee" /><br />
* Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-06-10,Wed&sel=442#l438</ref><br />
* Don't explain us evident things in detail.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-03-10,Thu&sel=425#l421</ref><br />
* Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-12-14,Mon&sel=232#l228</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam-bs?date=2016-06-11,Sat&sel=140#l136</ref><br />
<br />
<div style="font-size:80%"><references/></div><br />
<br />
== ArchiveTeam on IRC ==<br />
<br />
Below is a list of ArchiveTeam's '''general-purpose''' IRC channels. '''Project-specific''' channels can be found in the [[Projects]]' list. All the channels listed below are on the [http://efnet.org EFNet] network. <br />
<br />
(Back then we had a separate list of project-specific IRC channels, under the general channels. For historical interest, you can find them on the [[IRC/Old]] page.)<br />
<br />
{| border="1" align="center" style="text-align:center;" cellpadding="6"<br />
! Channel name !! Channel hashtag !! Channel description<br />
|-<br />
| Archive Team || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.<br />
|-<br />
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.<br />
|-<br />
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development<br />
|-<br />
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion<br />
|-<br />
| -twitter || [irc://irc.efnet.org/archiveteam-twitter #archiveteam-twitter] || <s>We have a twitter bot and it owns you.</s> All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.<br />
|-<br />
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior<br />
|-<br />
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.<br />
|}<br />
<br />
== IRC Logs ==<br />
<br />
You can log the channels where you are using your client, generally. But if you want a 24/7 bot logging your channel, you can use a script like [http://web.archive.org/web/20100323000206/http://toolserver.org/~bryan/TsLogBot/TsLogBot.py this] (change the server and channel variables).<br />
<br />
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at http://archive.fart.website/bin/irclogger_logs. It also has a search function.<br />
<br />
<!--<br />
== Unofficial ArchiveTeam QDB (Offline) ==<br />
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].<br />
--><br />
<br />
[[Category:Archive Team]]<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=IRC&diff=42747IRC2019-12-20T04:30:36Z<p>Kpcyrd: Add hackint to List of IRC URLS</p>
<hr />
<div>:''Are you looking for '''[[Archiveteam:IRC|ArchiveTeam's IRC]]'''?''<br />
<br />
'''Internet Relay Chat (IRC)''' is an old chat protocol, being designed in 1988. IRC clients are simple and available for every platform imaginable, including your old Nintendo DS. IRC is fully decentralized, with anybody being able to run a server. There are numerous large networks with their own histories. With the advent of modern chat platforms that are more mobile-friendly among other advantages, IRC usage has been on the decline, and lately (2019) it is being abandoned even by techie folks.<br />
<br />
== IRC network aggregators ==<br />
There are a few IRC network aggregators, but the biggest one is probably [http://irc.netsplit.de/networks/top100.php irc.netsplit.de], which also scrapes channels, their historical topics and number of users.<br />
<br />
* [http://irc.netsplit.de/networks/top100.php irc.netsplit.de] ({{job|2emzfqe3gkdnus4wsdozh1mo5}} on 2019-04-30)<br />
<br />
== IRC networks ==<br />
<br />
On 2019-04-26, Mozilla announced the plan to deprecate and decommission its IRC network in the "next small number of months"[http://exple.tive.org/blarg/2019/04/26/synchronous-text/], with the Rust community already making the move to [[Discord]][https://blog.rust-lang.org/2019/04/26/Mozilla-IRC-Sunset-and-the-Rust-Channel.html].<br />
<br />
== IRC logs ==<br />
IRC servers typically do not provide logs. Clients usually keep local logs of chats, however, unless run on a reliable server running 24/7 those logs will contain blind spots.<br />
<br />
There is an implicit agreement between IRC participants to not publish IRC logs. However, some channels have a notice about public logs in their topic. Some logs are available online, for example:<br />
* [https://freenode.logbot.info/ Freenode LogBot]<br />
* [https://mozilla.logbot.info/ Mozilla LogBot (moznet)]<br />
* [https://irclogs.ubuntu.com/ Ubuntu IRC logs]<br />
<br />
== List of IRC URLS ==<br />
<br />
* ircs://irc.hackint.org/<br />
* irc://irc.efnet.org/<br />
* irc://irc.dal.net/<br />
* irc://chat.freenode.net/<br />
* irc://irc.undernet.org/<br />
* irc://dalnet<br />
<br />
{{Template:Instant messengers}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=TikTok&diff=41601TikTok2019-11-13T19:43:49Z<p>Kpcyrd: Add irc channel</p>
<hr />
<div>{{Infobox project<br />
| title = tiktok<br />
| logo = TikTok logo.png<br />
| image = TikTok home page 2019-11-09.png<br />
| description = tiktok home page as seen on November 9, 2019<br />
| URL = https://www.tiktok.com/<br />
| project_status = {{online}}<br />
| archiving_status = {{nosavedyet}}<br />
| irc = TikOff@irc.hackint.org:6697<br />
}}<br />
<br />
TikTok is a social media app for short, user generated videos developed by the Chinese company '''ByteDance'''. The app was launched internationally in September 2017 and merged with musical.ly on 9 November 2017.<br />
<br />
== Vital Signs ==<br />
<br />
* The first request for archival was in [https://old.reddit.com/r/Archiveteam/comments/dazw5l/tiktok/ October 2019] due to removal of pro-LGBTQ content, even in countries where homosexuality has never been illegal. <ref>[https://www.theguardian.com/technology/2019/sep/26/tiktoks-local-moderation-guidelines-ban-pro-lgbt-content "TikTok's local moderation guidelines ban pro-LGBT content"] - Article on ''The Guardian''</ref><br />
* Videos from chinese TikTok can not be seen outside of china. <ref>[https://www.wired.com/story/tiktok-is-the-latest-window-into-chinas-police-state/ "TikTok - Yes, TikTok - Is the Latest Window Into China’s Police State"] - Article on ''Wired''</ref><br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Dev/New_Project&diff=41600Dev/New Project2019-11-13T16:42:01Z<p>Kpcyrd: typo</p>
<hr />
<div>Starting a '''new project''' is a giant leap into getting things done. <br />
<br />
== Website Structure ==<br />
<br />
Take a good look at how the website is structured:<br />
<br />
* Is everything hosted under one domain name? <br />
* Is there a throttling system?<br />
* How can I discover usernames or page IDs?<br />
* Is there an API?<br />
* Is there a sitemap.xml?<br />
* Can I guess URLs by incrementing a value?<br />
* Does disabling cookies or using specific cookies affect anything?<br />
* Does the website break if you make special requests?<br />
* Can you Google <code>site:example.com</code> for some URLs?<br />
** Hint: <code>site:example.com inurl:show_thread</code><br />
* Is it a video? Try [https://github.com/monsieurvideo/get-flash-videos get-flash-videos]<br />
<br />
=== JavaScript ===<br />
<br />
JavaScript is a pain. <br />
<br />
* Check to see if there's a noscript or mobile version.<br />
* Use a web inspector to observe its behavior and simulate POST requests made by the scripts.<br />
* Scrape URLs from JavaScript templates with regular expressions.<br />
<br />
=== Static Assets ===<br />
<br />
Websites sometimes do not host static media such as images and stylesheets under their primary domain name. Be sure to take those under consideration.<br />
<br />
=== IP Address Bans & Throttling ===<br />
<br />
Find out if there is IP address banning. Use a sacrificial IP address if you need to.<br />
<br />
== Items ==<br />
<br />
Once you determine the website structure, you need to determine how to split up work units up efficiently by an item name. An item name is a short string describing the work unit, for example, a username.<br />
<br />
Because the Tracker uses Redis as its database, memory usage is a concern. The maximum number of items supported ranges from 5,000,000 to 10,000,000 depending on the item name length.<br />
<br />
* If a user site is USERNAME.example.com, a good candidate is USERNAME.<br />
** Be careful of large subdomain sites.<br />
* If the content is by some numerical ID, consider whether ranges of IDs are appropriate.<br />
<br />
== Call for Action ==<br />
<br />
* ProTip™: Get things done.<br />
<br />
=== Wiki Page ===<br />
<br />
Ensure there is documentation on this wiki about the project.<br />
<br />
Include:<br />
<br />
* an overview of the website<br />
* the shutdown notice<br />
* "how to help" instructions<br />
* a (future) link to the archives<br />
<br />
=== Writing Grab Scripts ===<br />
<br />
If you do not have permissions to create Archive Team's repository, please ask on [[IRC]].<br />
<br />
For detailed information about what goes inside grab scripts, take a look at [[Dev/Seesaw|writing Seesaw scripts]].<br />
<br />
=== Tracker Access ===<br />
<br />
If you do not have permission to access the Tracker, please see [[Tracker#People]].<br />
<br />
=== IRC Channel ===<br />
<br />
Archive Team uses per-project [[IRC]] channels to reduce noise in the main channel. It also serves as a technical support channel.<br />
<br />
IRC channel names must be humorous.<br />
<br />
* If an employee of the website in danger appears on the channel, please do cooperate.<br />
<br />
=== Project Management ===<br />
<br />
Successful projects are a result of successful management. See [[Dev/Project Management|Project Management]] for details.<br />
<br />
=== Getting Attention ===<br />
<br />
Many Twitter followers? Got connections? Become a loudmouth!<br />
<br />
Otherwise, take initiative yourself and encourage other team members to take initiative.<br />
<br />
{{devnav}}<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=Gfycat&diff=41570Gfycat2019-11-09T17:52:10Z<p>Kpcyrd: Add legal threats section</p>
<hr />
<div>{{Infobox project<br />
| title = Gfycat<br />
| image = Gfycat-logo.png<br />
| URL = https://gfycat.com/<br />
| project_status = {{online}}<br />
| irc = deadcat@irc.hackint.org:6697<br />
| tracker = [http://tracker.archiveteam.org/gfycat/#show-all gfycat]<br />
| source = [https://github.com/ArchiveTeam/gfycat-grab gfycat-grab]<br />
| archiving_status = {{inprogress}}<br />
}}<br />
'''Angelfire''' is a User-generated content short video hosting company founded by Richard Rabbat, Dan McEleney, and Jeff Harris. It was a pioneer of the video alternative to GIF<br />
== Why archiving ==<br />
on 5/11/2019 <br />
<br />
https://old.reddit.com/r/gfycat/comments/drzj4g/nov_18_removal_of_infrequently_accessed_anonymous/<br />
== Status ==<br />
<br />
== Legal Threats ==<br />
* Dan McEleney accused the ArchiveTeam of a DDoS attack and threatened with legal action on [https://twitter.com/textfiles/status/1192518136878321664 November 7, 2019].</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=TikTok&diff=41569TikTok2019-11-09T17:38:18Z<p>Kpcyrd: </p>
<hr />
<div>{{Infobox project<br />
| title = tiktok<br />
| logo = TikTok logo.png<br />
| image = TikTok home page 2019-11-09.png<br />
| description = tiktok home page as seen on November 9, 2019<br />
| URL = https://www.tiktok.com/<br />
| project_status = {{online}}<br />
| archiving_status = {{nosavedyet}}<br />
}}<br />
<br />
TikTok is a social media app for short, user generated videos developed by the Chinese company '''ByteDance'''. The app was launched internationally in September 2017 and merged with musical.ly on 9 November 2017.<br />
<br />
== Vital Signs ==<br />
<br />
* The first request for archival was in [https://old.reddit.com/r/Archiveteam/comments/dazw5l/tiktok/ October 2019] due to removal of pro-LGBTQ content, even in countries where homosexuality has never been illegal. <ref>[https://www.theguardian.com/technology/2019/sep/26/tiktoks-local-moderation-guidelines-ban-pro-lgbt-content "TikTok's local moderation guidelines ban pro-LGBT content"] - Article on ''The Guardian''</ref><br />
* Videos from chinese TikTok can not be seen outside of china. <ref>[https://www.wired.com/story/tiktok-is-the-latest-window-into-chinas-police-state/ "TikTok - Yes, TikTok - Is the Latest Window Into China’s Police State"] - Article on ''Wired''</ref><br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=TikTok&diff=41568TikTok2019-11-09T16:56:08Z<p>Kpcyrd: Created page with "{{Infobox project | title = tiktok | logo = TikTok logo.png | image = TikTok home page 2019-11-09.png | description = tiktok home page as seen on November 9, 2019 | URL = http..."</p>
<hr />
<div>{{Infobox project<br />
| title = tiktok<br />
| logo = TikTok logo.png<br />
| image = TikTok home page 2019-11-09.png<br />
| description = tiktok home page as seen on November 9, 2019<br />
| URL = https://www.tiktok.com/<br />
| project_status = {{online}}<br />
| archiving_status = {{nosavedyet}}<br />
}}<br />
<br />
{{Navigation box}}</div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=File:TikTok_home_page_2019-11-09.png&diff=41567File:TikTok home page 2019-11-09.png2019-11-09T16:53:45Z<p>Kpcyrd: </p>
<hr />
<div></div>Kpcyrdhttps://wiki.archiveteam.org/index.php?title=File:TikTok_logo.png&diff=41566File:TikTok logo.png2019-11-09T16:40:23Z<p>Kpcyrd: </p>
<hr />
<div></div>Kpcyrd