Difference between revisions of "Archiveteam:IRC"

From Archiveteam
Jump to navigation Jump to search
(→‎ArchiveTeam on IRC: add #archivebot-bs)
(→‎Creating a channel: Add MLOCK, topic, and explanations on private channels and granting op/voice/flags)
(39 intermediate revisions by 14 users not shown)
Line 1: Line 1:
'''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.
'''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.


The ArchiveTeam uses IRC as its one-stop shop for coordinating official and unofficial AT projects.
ArchiveTeam uses IRC as its one-stop shop for coordinating projects.
 
'''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.'''


== How do I chat on IRC? ==
== How do I chat on IRC? ==


You will need a IRC client, or you can use a web interface.
You will need an IRC client, or you can use a web interface.


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>.
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>.
 
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]].


{{notice|1=Please learn IRC '''netiquette'''.
{{notice|1=Please learn IRC '''netiquette'''.
Line 25: Line 29:


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.
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.
See the section [[#IRC_Logs|IRC Logs]].


=== I asked a question and waited but it scrolled off the window and was ignored. ===
=== I asked a question and waited but it scrolled off the window and was ignored. ===


Don't get discouraged and ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.
''Don't'' get discouraged; '''do''' ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.


=== How do I get someone's attention in a public channel? ===
=== How do I get someone's attention in a public channel? ===
Line 38: Line 44:
=== Why won't anyone respond? ===
=== Why won't anyone respond? ===


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!
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.


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.
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.
Line 45: Line 51:


See [[Who We Are]].
See [[Who We Are]].
=== Special ArchiveTeam IRC rules ===
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:
* <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>
* 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>
* 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>
* 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>
* 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" />
* 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>
* 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>
* 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>
<div style="font-size:80%"><references/></div>


== ArchiveTeam on IRC ==
== ArchiveTeam on IRC ==


Below are a list of the IRC channels the ArchiveTeam uses to control all its projects, in no particular order. All these channels are on the [http://efnet.org EFNet] network. This list is not complete but available to document long-term channels.
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.  
 
(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.)


{| border="1" align="center" style="text-align:center;" cellpadding="6"
{| border="1" align="center" style="text-align:center;" cellpadding="6"
|Channel name||Channel hashtag||Channel description||Status
! Channel name !! Channel hashtag !! Channel description
|-
|colspan="4"|<b>General Channels</b>
|-
|Archive Team
|[irc://irc.efnet.org/archiveteam #archiveteam]
|The main ArchiveTeam channel, mainly used for news, announcement and early project planning.
|N/A
|-
| -bs
|[irc://irc.efnet.org/archiveteam-bs #archiveteam-bs]
|Off-topic discussion for things not directly related to ArchiveTeam and its projects.
|N/A
|-
| -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.
|N/A
|-
|Warrior
|[irc://irc.efnet.org/warrior #warrior]
|Channel for the discussion and development of the ArchiveTeam Warrior
|N/A
|-
|ArchiveBot
|[irc://irc.efnet.org/archivebot #archivebot]
|Channel for controlling [[ArchiveBot]].  Discussions about ArchiveBot development also take place here.
|N/A
|-
|ArchiveBot-bs
|[irc://irc.efnet.org/archivebot-bs #archivebot-bs]
|Off-topic discussion for things not directly related to ArchiveBot.
|N/A
|-
|Valhalla
|[irc://irc.efnet.org/huntinggrounds #huntinggrounds]
|Project [[Valhalla]]: Discussing where and how to store archives that are too big for the [[Internet Archive]] at the moment.
|N/A
|-
|colspan="4"|<b>Active projects on a deadline</b>
|-
|TwitPic
|[irc://irc.efnet.org/quitpic #quitpic]
|Acquired by Twitter, [[TwitPic]] may cease to exist in its current form.
|<font color=#0000ff>Active</font>
|-
|Halo
|[irc://irc.efnet.org/yolohalo #yolohalo]
|Bungie's disks are filling up, so they are deleting old [[Halo]] game statistics and user content.
|<font color=#0000ff>Active</font>
|-
|Microsoft Clip Art
|[irc://irc.efnet.org/clipfart #clipfart]
|[[Microsoft]] is phasing out its clip art collection.
|<font color=#0000ff>Active</font>
|-
|Cobook
|[irc://irc.efnet.org/cookbook #cookbook]
|[[Cobook]] has been acquired and is being absorbed into FullContact.
|<font color=#0000ff>Active</font>
|-
|RapidShare
|[irc://irc.efnet.org/rapidscare #rapidscare]
|[[RapidShare]] is getting a RapidScare, shutting down on March 31, 2015.
|<font color=#0000ff>Active</font>
|-
|Odysee
|[irc://irc.efnet.org/spaceodysee #spaceodysee]
|[[Odysee]] is joining the Google+ Team and ending its voyage on February 23, 2015.
|<font color=#0000ff>Active</font>
|-
|RadioShack
|[irc://irc.efnet.org/unshackled #unshackled]
|[[RadioShack]] is going bankrupt.
|<font color=#0000ff>Active</font>
|-
|TestFlight
|[irc://irc.efnet.org/crashed #crashed]
|[[Apple]] is crashing [[TestFlight]] on February 26, 2015.
|<font color=#0000ff>Active</font>
|-
|Internet Centrum
|[irc://irc.efnet.org/internetcentury #internetcentury]
|[[Internet Centrum]] gets terminated on February 28, 2015.
|<font color=#0000ff>Active</font>
|-
|Google Business Sitebuilder
|[irc://irc.efnet.org/sitebreaker #sitebreaker]
|[[Google]] is replacing [[Google Business Sitebuilder]] with Google My Business on March 15, 2015.
|<font color=#0000ff>Active</font>
|-
|Trovebox
|[irc://irc.efnet.org/treasuretrove #treasuretrove]
|[[Trovebox]] is closing on March 15, 2015.
|<font color=#0000ff>Active</font>
|-
|Club Nintendo
|[irc://irc.efnet.org/clubnintendont #clubnintendont]
|[[Club Nintendo]] has ran out of lives. Game over for North America on July 30, 2015, September 30, 2015 for Europe and Japan.
|<font color=#0000ff>Active</font>
|-
|Music Unlimited
|[irc://irc.efnet.org/limitedmusic #limitedmusic]
|[[Music Unlimited]]'s time is limited. Getting phased out by Sony on March 29, 2015.
|<font color=#0000ff>Active</font>
|-
|Ovi Store
|[irc://irc.efnet.org/downlovi #downlovi]
|[[Microsoft]] and [[Nokia]] are killing [[Ovi Store]] in the first half of 2015. Downloading all the things!
|<font color=#0000ff>Active</font>
|-
|Panoramio
|[irc://irc.efnet.org/paranormio #paranormio]
|[[Google]] is migrating [[Panoramio]] pictures into Maps without metadata.
|<font color=#0000ff>Active</font>
|-
|exfm
|[irc://irc.efnet.org/exexfm #exexfm]
|Grabbing everything from archive.[[exfm|ex.fm]].
|<font color=#0000ff>Active</font>
|-
|Orkut
|[irc://irc.efnet.org/throatkut #throatkut]
|[[Orkut]] got kut on September 30, 2014. However, it still lives on as a read-only archive.
|<font color=#0000ff>Active</font>
|-
|-
|The Pirate Bay
| ArchiveTeam || [irc://irc.efnet.org/archiveteam #archiveteam] || The main ArchiveTeam channel, mainly used for news, announcement and early project planning.
|[irc://irc.efnet.org/yarharfiddlededee #yarharfiddlededee]
|[[The Pirate Bay]] has recently rose from the grave, grabbing an archive for sanity's sake.
|<font color=#0000ff>Active</font>
|-
|-
|Madden GIFERATOR
| -bs || [irc://irc.efnet.org/archiveteam-bs #archiveteam-bs] || Lengthy discussion for general archival and projects which don't have a separate channel.
|[irc://irc.efnet.org/jiferator #jiferator]
|[[Madden GIFERATOR]]: promotional site + EA + lots of user generated content + meme = a site that will probably shut down with little to no notice. Preemptively being archived (but not starting until there are less upcoming projects with looming deadlines).
|<font color=#0000ff>Active</font>
|-
|-
|Ownlog
| -dev || [irc://irc.efnet.org/archiveteam-dev #archiveteam-dev] || Discussion about general (i.e. not project-specific) ArchiveTeam software development
|[irc://irc.efnet.org/pwnlog #pwnlog]
|Polish blogging website [[Ownlog]] is losing popularity and support from its owners.
|<font color=#0000ff>Active</font>
|-
|-
|colspan="4"|<b>Long term ongoing projects</b>
| -ot || [irc://irc.efnet.org/archiveteam-ot #archiveteam-ot] || Off-topic discussion
|-
|-
|Audit Team 2014
| -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.
|[irc://irc.efnet.org/auditteam #auditteam]
|It's time to verify our shit.
|<font color=#0000f>Active</font>
|-
|-
|AOL
| Warrior || [irc://irc.efnet.org/warrior #warrior] || Channel for the discussion and development of the ArchiveTeam Warrior
|[irc://irc.efnet.org/aohell #aohell]
|The channel for old-school [[AOL]] archiving.
|<font color=#0000f>Active</font>
|-
|-
|BashUp
| ArchiveBot || [irc://irc.efnet.org/archivebot #archivebot] || Channel for controlling [[ArchiveBot]]. Discussions about ArchiveBot development also take place here.
|[irc://irc.efnet.org/bashup #bashup]
|The ArchiveTeam [[IRC Quotes|Quote Backup Project]], dedicated to backing up quote databases (such as Bash.org) and similar websites (similar to FMyLife or MyLifeIsAverage).
|<font color=#ff0000>Idle</font>
|-
|ISP Hosting
|[irc://irc.efnet.org/webroasting #webroasting]
|Finding [[ISP Hosting|ISP web hosting services]] before the Grim Reaper finds them.
|<font color=#0000ff>Active</font>
|-
|URLTeam
|[irc://irc.efnet.org/urlteam #urlteam]
|The [[URLTeam|URL shortener backup project]] of the ArchiveTeam. To quote: "URL shortening = fucking bad idea"
|<font color=#0000ff>Active</font>
|-
|WikiTeam
|[irc://irc.efnet.org/wikiteam #wikiteam]
|The [[WikiTeam|Wiki backup project]]. Any wiki can be backed up here.
|<font color=#ff0000>Mostly idle (work, don't chat!)</font>
|-
|FTP
|[irc://irc.efnet.org/effteepee #effteepee]
|[[FTP]] archiving project.
|<font color=#0000ff>Active</font>
|-
|colspan="4"|<b>Currently idle or complete projects</b>
|-
|MediaCrush
|[irc://irc.efnet.org/mediacrushed #mediacrushed]
|[[MediaCrush]] is getting crushed.
|<font color=#36B355>Completed</font>
|-
|Inkblazers
|[irc://irc.efnet.org/inkerasers #inkerasers]
|[[Inkblazers]] is erased on February 1, 2015.
|<font color=#36B355>Completed</font>
|-
|Brace.io
|[irc://irc.efnet.org/braceyourself #braceyourself]
|[[Brace.io]] is killed by Squarespace on January 19, 2015.
|<font color=#36B355>Completed</font>
|-
|Vstreamers
|[irc://irc.efnet.org/destreamers #destreamers]
|Video hosting service [[Vstreamers]] to shut down on January 15, 2015.
|<font color=#36B355>Completed</font>
 
|-
|Nokia Memories
|[irc://irc.efnet.org/backtorubber #backtorubber]
|[[Nokia Memories]] gets forgotten on January 12, 2015.
|<font color=#36B355>Completed</font>
|-
|Roon
|[irc://irc.efnet.org/rooined #rooined]
|The blogging website [[Roon]] gets ruined on December 31, 2014.
|<font color=#36B355>Completed</font>
|-
|Viddy
|[irc://irc.efnet.org/viddiot #viddiot]
|A lot of viddios will be gone with [[Viddy]] on December 15, 2014.
|<font color=#36B355>Completed</font>
|-
|ZipList
|[irc://irc.efnet.org/zipyourlips #zipyourlips]
|[[ZipList]] gets zipped up on December 10, 2014.
|<font color=#36B355>Completed</font>
|-
|Jux
|[irc://irc.efnet.org/juxsux #juxsux]
|[[Jux]] is a creative blogging platform. But just until November 30, 2014.
|<font color=#ff0000>Idle</font>
|-
|Qwiki
|[irc://irc.efnet.org/quickie #quickie]
|No, it's not a wiki. [[Qwiki]] was acquired in 2013 by Yahoo!, shutting down on November 1, 2014.
|<font color=#ff0000>Idle</font>
|-
|Ancestry Sites
|[irc://irc.efnet.org/ancienthistory #ancienthistory]
|[[Ancestry.com]] is pulling the plug on four of its sites.
|<font color=#36B355>Completed</font>
|-
|Quizilla
|[irc://irc.efnet.org/fizzilla #fizzilla]
|Nickelodeon failed [[Quizilla]] and gets expelled on October 1st, 2014.
|<font color=#36B355>Completed</font>
|-
|Verizon user sites
|[irc://irc.efnet.org/verizoff #verizoff]
|[[Geocities|Deja vu]]? [[Verizon Personal Web Space|Verizon]] decides it's a great idea to pull a Geocities with their user sites.
|<font color=#36B355>Completed</font>
|-
|Swipnet
|[irc://irc.efnet.org/swiped #swiped]
|[[Swipnet|Swipnet.se]] gets swiped on August 31, 2014.
|<font color=#36B355>Completed (by self)</font>
|-
|Canvas
|[irc://irc.efnet.org/canvas #canvas]
|[[Canv.as]] wants a permanent home at IA.
|<font color=#36B355>Completed</font>
|-
|Fotopedia
|[irc://irc.efnet.org/fotofinished #fotofinished]
|[[Fotopedia]] is taking its last photo on August 10, 2014.
|<font color=#36B355>Completed</font>
|-
|Twitch
|[irc://irc.efnet.org/burnthetwitch #burnthetwitch]
|[[Twitch]] announced they were going to be mass-deleting old broadcasts.
|<font color=#ff0000>Idle</font>
|-
|puu.sh
|[irc://irc.efnet.org/pushharder #pushharder]
|[[puu.sh]] archival before they add an image expiry limit
|<font color=#ff0000>Idle</font>
|-
|Yahoo! Voices
|[irc://irc.efnet.org/shutup #shutup]
|Self-destruct sequence initiated of [[Yahoo! Voices]]. ETA July 31, 2014.
|<font color=#36B355>Completed</font>
|-
|MLKSHK
|[irc://irc.efnet.org/totheyard #totheyard]
|[[MLKSHK]] announced that they were going to shut down, but then didn't.
|<font color=#ff0000>Cancelled</font>
|-
|Bebo
|[irc://irc.efnet.org/cockandballs #cockandballs]
|Archival of [[Bebo]].
|<font color=#ff0000>Idle</font>
|-
|Mochi Media
|[irc://irc.efnet.org/mochibaibai #mochibaibai]
|Goodbye Flash games. [[Mochi Media]] was forced to shut down on March 31, 2014.
|<font color=#36B355>Completed</font>
|-
|My Opera
|[irc://irc.efnet.org/fatlady #fatlady]
|Archival of [[My Opera]]
|<font color=#36B355>Completed</font>
|-
|Dogster/Catster
|[irc://irc.efnet.org/rawdogster #rawdogster]
|Archival of [[Dogster]] and Catster.
|<font color=#36B355>Completed (for now)</font>
|-
|Viddler
|[irc://irc.efnet.org/fiddler #fiddler]
|Saving [[Viddler]] before it goes paid-only on March 11, 2014.
|<font color=#ff0000>Idle</font>
|-
|The Phoenix
|[irc://irc.efnet.org/theashes #theashes]
|This news site is shutting down and we already grabbed blog.thephoenix.com.
|<font color=#ff0000>Idle</font>
|-
|ispygames
|[irc://irc.efnet.org/ispygames #ispygames]
|Gamespy, 1up, UGO and IGN (most of the sites) are being closed. Planning and action here.
|<font color=#ff0000>Idle</font>
|-
|AnyHub
|[irc://irc.efnet.org/AnyHubTeam #AnyHubTeam]
|The [[AnyHub]] team.
|<font color=#ff0000>Idle</font>
|-
|Last.fm
|[irc://irc.efnet.org/lastchance.fm #lastchance.fm]
|The channel for [[Last.fm]] archiving.
|<font color=#ff0000>Idle</font>
|-
|isoPrey
|[irc://irc.efnet.org/isoprey #isoprey]
|[[isoHunt]] was forced to shutdown.
|<font color=#ff0000>Idle</font>
|-
|Blip.tv
|[irc://irc.efnet.org/blooper.tv #blooper.tv]
|[[Blip.tv]] decides to "clean up" their library.
|<font color=#ff0000>Idle</font>
|-
|Xanga
|[irc://irc.efnet.org/jenga #jenga]
|[[Xanga]] archival before potentially going paid-only or transitioning to Wordpress.
|<font color=#ff0000>Idle</font>
|-
|Formspring
|[irc://irc.efnet.org/firespring #firespring]
|[[Formspring|Formspring announced its closure on March 15, 2013]]. Plans for archiving and general closure chat were located here.
|<font color=#36B355>Completed (for now)</font>
|-
|Snapjoy
|[irc://irc.efnet.org/snapshut #snapshut]
|[[Snapjoy]] archival. Closed July 24th, 2013.
|<font color=#ff0000>Idle</font>
|-
|Webshots
|[irc://irc.efnet.org/webshots #webshots]
|Discussion of everything related to the [[webshots]] shutdown.
|<font color=#ff0000>Idle</font>
|-
|Posterous
|[irc://irc.efnet.org/preposterus #preposterus]
|[[Posterous]] project discussion
|<font color=#36B355>Completed</font>
|-
|FanFiction.Net
|[irc://irc.efnet.org/fanfriction #fanfriction]
|The channel for coordinating preemptive [[FanFiction.Net]] archiving.
|<font color=#36B355>Completed</font>
|-
|FlickrFckr
|[irc://irc.efnet.org/flickrfckr #flickrfckr]
|The [[FlickrFckr|Flickr backup project]] of the Archive Team. Not needed just yet, but it's a Yahoo owned service, so we're always prepped.
|<font color=#ff0000>Idle</font>
|-
|ProdigalSon
|[irc://irc.efnet.org/prodigalson #prodigalson]
|The [[Pages|backup project for pages.prodigy.net]].
|<font color=#ff0000>Idle</font>
|-
|GetMUD
|[irc://irc.efnet.org/getmud #getmud]
|The multi-user-dungeon backup project of the Archive Team. Currently no progress as of yet.
|<font color=#ff0000>Idle</font>
|-
|Space Invaders
|[irc://irc.efnet.org/spaceinvaders #spaceinvaders]
|The [[Talk:Windows Live Spaces|Windows Live Spaces backup project]].
|<font color=#ff0000>Idle</font>
|-
|ArchiveTeam Philly
|[irc://irc.efnet.org/archiveteam-philly #archiveteam-philly]
|For team members in the Philadelphia area (there's a lot). Discussion and possible physical meetups?
|<font color=#ff0000>Idle</font>
|-
|Forever Alone
|[irc://irc.efnet.org/foreveralone #foreveralone]
|The [[Friendster]] backup project.
|<font color=#ff0000>Idle</font>
|-
|Magically Delicious
|[irc://irc.efnet.org/magicallydelicious #magicallydelicious ]
|[[Delicious]] backup project
|<font color=#ff0000>Idle</font>
|-
|Google Grape||[irc://irc.efnet.org/googlegrape #googlegrape]
|Main channel for coordinating the [[Google Video Warroom|Google Video project]].
|<font color=#ff0000>Idle</font>
|-
|BOINC Google
|[irc://irc.efnet.org/boincgoogle #boincgoogle]
|Sub-channel for the [[Google Video Warroom|Google Video project]], for details about running the distributed-download software
|<font color=#ff0000>Idle</font>
|-
|Upcoming
|[irc://irc.efnet.org/outgoing #outgong]
|[[Upcoming]] gave us 11 days' notice. It shut down on April 30.
|<font color=#36B355>Completed</font>
|-
|Lulu Poetry
|[irc://irc.efnet.org/lulupoetry #lulupoetry]
|Channel for the brief but intense [[Poetry.com]] archiving project.
|<font color=#ff0000>Idle</font>
|-
|Archive Strikes Back
|[irc://irc.efnet.org/archivestrikesback #archivestrikesback ]
|Channel for [[Forums.starwars.com]] archive project.
|<font color=#36B355>Completed</font>
|-
|ArchiveMeme
|[irc://irc.efnet.org/archivememe #archivememe]
|An unofficial fan channel started by BlueMax. http://memegenerator.net/ArchiveTeam
|N/A
|}
|}


== IRC Logs ==
== IRC Logs ==


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).
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).
 
[[User:Chfoo|chfoo]] is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.
 
== hackint specifics ==
This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.
 
=== Connecting ===
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).
 
==== Weechat ====
 
: <code>/server add hackint irc.hackint.org/6697 -ssl -autoconnect</code>
: <code>/save</code>
: <code>/connect hackint</code>
 
=== Services & authentication ===
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.
 
The most important part for most users is registering and authenticating a user account. To register, issue:
 
: <code>/msg NickServ REGISTER password email@example.org</code>


[[User:Scumola|Scumola]]/swebb is also hosting chatlogs of some channels at [http://badcheese.com/~steve/atlogs/ http://badcheese.com/~steve/atlogs/].  Though only logs from the last ten days are listed, older chatlogs can still be accessed by changing the URL.
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.


If the one above seems to be out of order, try [[User:Chfoo|chfoo]]'s one: http://archive.fart.website/bin/irclogger_logs.
After registration, you need to authenticate on every connection. There are several ways how you can do that: SASL PLAIN, SASL EXTERNAL, SASL ECDSA-NIST256P, CertFP, or the traditional but least reliable <code>/msg NickServ IDENTIFY password</code>. It is recommended to use SASL since this will authenticate you immediately during the initial connection establishment; CertFP and messaging NickServ may have a delay, which can cause joins to protected channels to fail, for example.


==== SASL PLAIN (weechat) ====
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:
: <code>/set irc.server.hackint.sasl_mechanism PLAIN</code>
: <code>/set irc.server.hackint.sasl_username <login></code>
: <code>/set irc.server.hackint.sasl_password <password></code>
: <code>/save</code>
: <code>/reconnect hackint</code>
==== Certificate authentication (SASL EXTERNAL or CertFP) ====
To authenticate using a certificate through either CertFP or SASL EXTERNAL, you need to generate a client certificate. For example:
: <code>openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer</code>
Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:
: <code>cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem</code>
: <code>chmod 600 /secure/path/nick.pem</code>
Then, instruct your client to use this certificate on connecting to hackint. Instructions for various clients can be found on the [https://www.oftc.net/NickServ/CertFP/ CertFP documentation by OFTC].
On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with <code>IDENTIFY</code>):
: <code>/msg NickServ CERT ADD</code>
On any later connections, you will get authenticated automatically.
It is recommended to use SASL EXTERNAL rather than relying on CertFP; only the former will ensure that the authentication happens immediately on connecting and you will be able to join access-restricted channels without issues.
=== Creating a channel ===
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.
Registering the channel is done with:
: <code>/msg ChanServ REGISTER #example</code>
And setting the flags is done with:
: <code>/msg ChanServ FLAGS #example !archiveteam-core +*SF</code>
This grants everyone in that group full control over the channel.
You should also utilise extbans to mirror the banlist from #archiveteam:
: <code>/mode #example +b $j:#archiveteam</code>
... and set a mode lock to enforce certain channel options:
: <code>/msg ChanServ SET MLOCK #example +ntcC-lk</code>
This enforces +n (people must be in the channel to send messages to it), +t (only ops can set the topic), +c (strip colours), and +C (disable CTCP messages) and disables the use of +l (limits) and +k (channel key).
Further, you should set a reasonable topic that ideally links to the corresponding wiki page (if one exists).
==== Private channels ====
For private, access-restricted channels, add to the mode lock +i (only invited users can join), +s (hide channel from whois and list), and if desired +p (disable /knock). Grant all people that should be able to join the channel at least the +i flag (i.e. <code>/msg ChanServ FLAGS #example robert +i</code>), and to make rejoining easier, add an invite exemption on the account (<code>/mode #example +I $a:robert</code>). Note that <code>robert</code> is the name of the NickServ account, which may be different from the nickname currently used by that user; if <code>robert</code> is currently connected as <code>bob</code>, you can <code>/whois bob</code>, and the server's response will include a line <code>account: robert</code> if the user is registered and authenticated.
==== Granting permissions ====
To grant a person permanent op or voice, make them register with NickServ if they haven't already, then do <code>/msg ChanServ AOP #example ADD account</code> for op or <code>/msg ChanServ VOP #example ADD account</code> for voice. Note that <code>account</code> is the NickServ account name, not the current nickname (see the bob/robert example above).
For other permissions you can grant, check the more powerful <code>FLAGS</code>: <code>/msg ChanServ HELP FLAGS</code>
=== Virtual hosts (vhosts) ===
If you are part of the <code>!archiveteam-core</code> group in GroupServ, you can use an ArchiveTeam vhost with:
: <code>/msg HostServ TAKE archiveteam/$account</code>
(<code>$account</code> is not a placeholder; enter it literally.)
If you are not part of the group, you can use the general hackint vhost:
: <code>/msg HostServ TAKE hackint/user/$account</code>
The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.
<!--
== Unofficial ArchiveTeam QDB (Offline) ==
== Unofficial ArchiveTeam QDB (Offline) ==
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].
ArchiveTeamsters are encouraged to visit and contribute to the unofficial [http://www.deaddyingdamned.com/qdb/ ArchiveTeam quote database].
-->


[[Category:Archive Team]]
[[Category:Archive Team]]
{{Navigation box}}

Revision as of 12:43, 15 September 2020

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.

ArchiveTeam uses IRC as its one-stop shop for coordinating projects.

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 section below.

How do I chat on IRC?

You will need an IRC client, or you can use a web interface.

EFnet, one of the networks that ArchiveTeam uses, provides a 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 #archiveteam.

Since September 2019, most project-specific channels have been hosted on the hackint IRC network due to desires like less netsplits, channel/nickname registration, secure IRC by default, etc. It too also has a web interface. A comprehensive comparison between the two networks by JAA can be found under User:JustAnotherArchivist/hackint vs EFnet.

Archiveteam1.png Please learn IRC netiquette.

Do not barge into an IRC channel demanding help or disparage installation instructions.

Archive Team is not a professional support team.

Do I have to use IRC?

We prefer IRC because there is no central point of failure, but see the question about social media on Frequently Asked Questions.

Why does IRC need chat logs?

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.

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.

See the section IRC Logs.

I asked a question and waited but it scrolled off the window and was ignored.

Don't get discouraged; do ask again. Topics get intermixed and timezones break up normal conversations. Be persistent but friendly.

How do I get someone's attention in a public channel?

Some chat clients will alert the user if you say their nickname.

Some clients support nickname auto-completion. Start typing the first few letters of their nickname and press tab.

Why won't anyone respond?

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.

Sometimes it may be the bystander effect. Try an icebreaker to get the conversation going.

I can't wait; I need immediate attention. Who's in charge?

See Who We Are.

Special ArchiveTeam IRC rules

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:

  • #archiveteam 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 #archiveteam-bs (this channel is monitored and you will very likely not need to wait hours for an answer). Project-specific discussions go in their respective channels. General topics not related to computers and/or archiving at all are not welcome even in #archiveteam-bs (try #archiveteam-ot for such topics instead).[1]
  • 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 search the logs.[2]
  • Don't maliciously/demandingly criticize Archive Team, its members, nor the Internet Archive, especially in general, empty phrases.[3][4] 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![5]
  • 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".[6][7][8] Our IRC channels are the #1 worst place to ask "why we are keeping this"![9]
  • Don't be childish.[10][11][5]
  • Don't feed the trolls. (Don't engage into arguments with people not behaving appropriately.)[12]
  • Don't explain us evident things in detail.[13]
  • Don't let your IRC client flood the channels with join/leave notifications due to you unstable connection.[14][15]

ArchiveTeam on IRC

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 EFnet network.

(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.)

Channel name Channel hashtag Channel description
ArchiveTeam #archiveteam The main ArchiveTeam channel, mainly used for news, announcement and early project planning.
-bs #archiveteam-bs Lengthy discussion for general archival and projects which don't have a separate channel.
-dev #archiveteam-dev Discussion about general (i.e. not project-specific) ArchiveTeam software development
-ot #archiveteam-ot Off-topic discussion
-twitter #archiveteam-twitter We have a twitter bot and it owns you. All tweets by us, to us, or about us used to be displayed here by swebb bot, until twitter killed API v1.
Warrior #warrior Channel for the discussion and development of the ArchiveTeam Warrior
ArchiveBot #archivebot Channel for controlling ArchiveBot. Discussions about ArchiveBot development also take place here.

IRC Logs

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 this (change the server and channel variables).

chfoo is hosting chat logs of some channels at https://archive.fart.website/bin/irclogger_logs. It also has a search function.

hackint specifics

This section is documenting how to properly and successfully run ArchiveTeam channels on the hackint IRC network.

Connecting

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 -ssl_verify on irssi and WeeChat).

Weechat

/server add hackint irc.hackint.org/6697 -ssl -autoconnect
/save
/connect hackint

Services & authentication

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.

The most important part for most users is registering and authenticating a user account. To register, issue:

/msg NickServ REGISTER password email@example.org

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.

After registration, you need to authenticate on every connection. There are several ways how you can do that: SASL PLAIN, SASL EXTERNAL, SASL ECDSA-NIST256P, CertFP, or the traditional but least reliable /msg NickServ IDENTIFY password. It is recommended to use SASL since this will authenticate you immediately during the initial connection establishment; CertFP and messaging NickServ may have a delay, which can cause joins to protected channels to fail, for example.

SASL PLAIN (weechat)

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:

/set irc.server.hackint.sasl_mechanism PLAIN
/set irc.server.hackint.sasl_username <login>
/set irc.server.hackint.sasl_password <password>
/save
/reconnect hackint

Certificate authentication (SASL EXTERNAL or CertFP)

To authenticate using a certificate through either CertFP or SASL EXTERNAL, you need to generate a client certificate. For example:

openssl req -nodes -newkey rsa:4096 -keyout /secure/path/nick.key -x509 -days 36500 -out /secure/path/nick.cer

Depending on the client and/or its SSL/TLS library, you may need to combine the two into one file:

cat /secure/path/nick.cer /secure/path/nick.key >/secure/path/nick.pem
chmod 600 /secure/path/nick.pem

Then, instruct your client to use this certificate on connecting to hackint. Instructions for various clients can be found on the CertFP documentation by OFTC.

On the first connection using this certificate, you need to add its fingerprint to NickServ (after authenticating with IDENTIFY):

/msg NickServ CERT ADD

On any later connections, you will get authenticated automatically.

It is recommended to use SASL EXTERNAL rather than relying on CertFP; only the former will ensure that the authentication happens immediately on connecting and you will be able to join access-restricted channels without issues.

Creating a channel

If you're opening a channel for ArchiveTeam usage, it is recommended to register it and set the right flags for the !archiveteam-core group. Make sure you're identified with NickServ.

Registering the channel is done with:

/msg ChanServ REGISTER #example

And setting the flags is done with:

/msg ChanServ FLAGS #example !archiveteam-core +*SF

This grants everyone in that group full control over the channel.

You should also utilise extbans to mirror the banlist from #archiveteam:

/mode #example +b $j:#archiveteam

... and set a mode lock to enforce certain channel options:

/msg ChanServ SET MLOCK #example +ntcC-lk

This enforces +n (people must be in the channel to send messages to it), +t (only ops can set the topic), +c (strip colours), and +C (disable CTCP messages) and disables the use of +l (limits) and +k (channel key).

Further, you should set a reasonable topic that ideally links to the corresponding wiki page (if one exists).

Private channels

For private, access-restricted channels, add to the mode lock +i (only invited users can join), +s (hide channel from whois and list), and if desired +p (disable /knock). Grant all people that should be able to join the channel at least the +i flag (i.e. /msg ChanServ FLAGS #example robert +i), and to make rejoining easier, add an invite exemption on the account (/mode #example +I $a:robert). Note that robert is the name of the NickServ account, which may be different from the nickname currently used by that user; if robert is currently connected as bob, you can /whois bob, and the server's response will include a line account: robert if the user is registered and authenticated.

Granting permissions

To grant a person permanent op or voice, make them register with NickServ if they haven't already, then do /msg ChanServ AOP #example ADD account for op or /msg ChanServ VOP #example ADD account for voice. Note that account is the NickServ account name, not the current nickname (see the bob/robert example above).

For other permissions you can grant, check the more powerful FLAGS: /msg ChanServ HELP FLAGS

Virtual hosts (vhosts)

If you are part of the !archiveteam-core group in GroupServ, you can use an ArchiveTeam vhost with:

/msg HostServ TAKE archiveteam/$account

($account is not a placeholder; enter it literally.)

If you are not part of the group, you can use the general hackint vhost:

/msg HostServ TAKE hackint/user/$account

The vhost is activated automatically when you authenticate. Note that your actual host address may still be visible to others.