DOCSLIB.ORG

Code» Governance in IRC Channels 65 4.1 Principalchanneldesign

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Code» Governance in IRC Channels 65 4.1 Principalchanneldesign Code Governance «Code» as Regulation in a Self-governed Internet Application from a Computer Science Perspective vorgelegt von Diplom-Informatiker Kei Ishii von der Fakutät IV – Elektrotechnik und Informatik der Technischen Universität Berlin zur Erlangung des akademischen Grades Doktor der Ingenieurswissenschaften – Dr. Ing. – genehmigte Dissertation Promotionsausschuss: Vorsitzender: Prof. Dr. Bernd Mahr Berichter: Prof. Dr. Bernd Lutterbeck Berichter: Prof. Dr. Hans-Ulrich Heiß Tag der wissenschaftlichen Aussprache: 7. Juli 2005 Berlin 2005 D 83 Contents Main Hypotheses 15 Introduction 17 I Internet, Governance, and «Code» 21 1 Internet Governance and «Code» 23 1.1 InternetGovernance. .. .. .. .. .. .. .. .. 23 1.2 ”AndHowShallthe’NetBeGoverned”? . .. 23 1.3 Governance ................................... 25 1.4 «Code»asRegulationModality . .. 26 2 «Code» Governance: An Empirical Analysis 29 2.1 TheChoiceoftheObjectofAnalysis. .... 29 2.2 MainHypothesis ................................ 30 2.3 TwoModelsofRegulation . 30 2.3.1 ”Lex Informatica”: Key Aspects of a Regulation System ....... 31 2.3.2 TypesofRules ............................. 33 2.4 TechnicalNotesontheAnalysis . ... 34 II Empirical Analysis of the Internet Relay Chat 37 3 The Internet Relay Chat 39 3.1 TheFunctionalPerspective–UsingtheIRC . ...... 40 3.1.1 Ahypotheticaluserscenario . 40 3.1.1.1 Channels........................... 41 3.1.1.2 PrivateMessages . 42 3.1.1.3 CTCP(Client-to-ClientProtocol) . 43 3.1.1.4 IRCCommands ....................... 43 3 Contents 3.1.2 SizeandGrowthoftheIRC . 44 3.2 AConceptualViewoftheTechnologyofIRC . .... 46 3.2.1 ”Polity”:StructuralOverviewoftheIRC . .... 46 3.2.1.1 IRCServer.......................... 47 3.2.1.2 IRCClient.......................... 47 3.2.1.3 IRCUserBot ........................ 48 3.2.1.4 IRCService ......................... 49 3.2.1.5 IRCNetwork ........................ 50 3.2.2 ”Politics”:AProcessualViewoftheIRC . ... 52 3.2.2.1 TheClient-serverarchitecture . 52 3.2.2.2 InsidetheIRCserverprocess . 53 3.2.3 ”Policy”: IRC Server Installation and Configuration . ........ 54 3.2.3.1 InstallationoftheIRCserver . 55 3.2.3.2 IRCserverconfiguration . 58 3.2.4 Technicalenvironmentandcodedistribution . ...... 59 3.3 MainSocialRolesintheIRC. 60 3.3.1 IRCadministrator ........................... 61 3.3.2 IRCServiceadministrator . 61 3.3.3 Coder.................................. 62 3.3.4 IRCuser ................................ 62 3.3.5 IRCoperator .............................. 63 3.3.6 Channeloperator ............................ 64 4 «Code» Governance in IRC Channels 65 4.1 PrincipalChannelDesign. .. 66 4.2 NumberedChannels............................... 68 4.2.1 FunctionalDesign ........................... 69 4.2.2 TechnicalImplementation . 70 4.2.3 The ”Maximum Users Per Channel” Channel Property . .... 72 4.3 NamedChannels - a Major Change in«Code» Governance . ...... 77 4.3.1 Names,modes,andthechanneloperator. ... 77 4.3.2 «Code» Evolves – Further Changes in Channel Design . ..... 81 5 Sanctions in the IRC 87 5.1 The/killCommand–ImmediateSanction . .... 88 5.1.1 FunctionalityandImplementation . ... 88 5.1.2 Changesinthe/killcommand . 89 5.2 TheK-Line–EntryDenialSanctions . ... 92 4 Contents 5.2.1 Functional description and technical implementation......... 92 5.2.2 Config linescomplementingK-linesanctioning . ...... 94 5.3 AccesstoK-linesforIRCoperators . .... 97 5.3.1 First experiment – Undernet’s /kline and /addline commands .. .. 98 5.3.2 /klineandexceptionsintheEFnet . 100 5.4 Beyond/killsandK-lines. 101 5.4.1 Delegating sanctioning power – Channel modes, kicks andbans . 101 5.4.2 Non-Sanctioning«Code»Remedies . 102 6 Nickname and Channel Ownership 109 6.1 Nicknames, Channel Names, and Early Ownership Policies .......... 110 6.1.1 Nicknames ............................... 110 6.1.2 Channelnames ............................. 112 6.2 PolicyChangesWithBotsandServices . .... 113 6.2.1 ChannelControlwiththeEggdropuserbot . 113 6.2.2 TheNickServservicebot. 116 6.3 IRCChannelRegistrationServices . ..... 118 6.3.1 Channel Registration in the DALnet: ChanServ Service ........ 119 6.3.1.1 Channelregistration . 120 6.3.1.2 Channelmanagementfeatures. 121 6.3.2 Channel Registration in the Undernet: The X/W Service ....... 123 6.3.2.1 Channelregistration . 123 6.3.2.2 Channel management: The X and W channel service bots . 125 7 Controlling the Controllers? 129 7.1 IRCOperator–PowerandControl . 129 7.2 NominatingIRCoperatorsandIRCopNetiquette . ....... 132 7.3 NoticesandLogs ................................ 135 7.3.1 Notices ................................. 136 7.3.2 Logging................................. 140 7.4 TheUndernetUWorldService . 140 7.4.1 AbouttheUWorldService . 141 7.4.2 Functionality .............................. 142 7.4.2.1 UWorldcommands . 143 7.4.2.2 UWorldautomaticfunctions . 146 7.4.3 UWorldUserAccess . 148 7.4.4 Control in UWorld: Information,Notices, and Logs . ...... 149 5 Contents 8 IRC Network Issues 155 8.1 «Code» Architecture Shapes the Social Constitution . ........... 155 8.1.1 IRC: Topology, Data Distribution and Technical Rationale . 155 8.1.2 DNS: Topology, Data Distribution and Technical Rationale. 158 8.1.3 Comparison between the IRC and DNS architectures . ..... 160 8.1.4 ArchitectureasConstitution . 161 8.2 The"GreatSplit": TheForkingofAnetandEFnet . ....... 162 8.2.1 Open-server servers vs. closed-server servers . ........ 163 III Some Notes on the Concept of «Code» Governance 165 9 Lex Informatica Revisited 169 9.1 Framework ................................... 169 9.2 Jurisdiction ................................... 170 9.3 Content ..................................... 172 9.4 Source...................................... 173 9.5 CustomizedRulesandCustomizationProcesses . ........ 174 9.5.1 Rulecustomizationonthe«code»level . 175 9.5.1.1 Sourcecodeaccess . 175 9.5.1.2 Systemaccess . .. .. .. .. .. .. 178 9.5.1.3 Interfaceaccess . 179 9.5.1.4 Useraccess ......................... 180 9.6 PrimaryEnforcement .............................. 181 10 Rule Types in «Code» 183 11 Outlook 185 11.1 Validating and Refining the «Code» Governance model . ......... 185 11.2 Computer Science Implications from «Code» Governance .......... 188 IV Appendix 191 12 IRC Chronology 193 12.1 1989–TheBirthoftheInternetRelayChat . ...... 193 12.2 1989-1990 – Copyright, named channels and the "great split"......... 194 12.3 1990-1992–GrowthandDevelopment. .... 195 12.4 1993–Thefirstsuccessfulfork:Undernet . ....... 196 6 Contents 12.5 1994–Anotherfork:DALnet . 196 12.6 1996–IRCnetforksoffEFnet . 196 12.7 TheIRCSourceCodeCopyright . 197 13 Tools for the Examination of the IRC Source Code 199 13.1 InSearchoftheRightTool . 199 13.2 AMakeshiftSolution . 202 13.3TheAnalysis .................................. 203 14 List of IRC server source code packages 205 14.1Onet....................................... 205 14.2EFnet ...................................... 205 14.2.1 Standard ................................ 205 14.2.2 +CS................................... 205 14.2.3 +thandHybrid ............................. 207 14.3Undernet .................................... 207 14.4IRCnet...................................... 209 Bibliography 211 7 Contents 8 List of Tables 2.1 LexInformatica(Reidenberg,1998,p.569) . ....... 31 3.1 Configuration lines in server version irc2.1.1 (Oct. 1989)........... 59 3.2 SocialRolesintheIRC............................. 61 4.1 Common commands in connection with IRC channels (Pioch, 1993) ..... 68 5.1 Changes inthe /kill commandcode..................... 92 6.1 DALnetChannelServiceOfficials . 122 6.2 X/Wuserlevels................................. 125 7.1 IRCoperatorprivilegedcommands. .... 131 7.2 Notices sent to IRCops in irc server versionirc2.1.1 . ........... 138 7.3 Uworldcommandsandaccesslevel . 149 7.4 Uworldcommandstriggeringnotices. ..... 151 14.1 Onetserverversions. 205 14.2 EFnetserverversions2.5and2.6. ..... 206 14.3 EFnetserverversions2.7and2.8. ..... 206 14.4 EFnet+CS(comstud)versions . 207 14.5 EFnet server versions +th and HybridUndernet server versions u2.9 and u2.10 208 14.6 Undernetserverversions2.8 . .... 208 14.7 Undernetserverversionsu2.9andu2.10 . ....... 209 14.8 EFnetserverversions2.7and2.8. ..... 210 9 List of Tables 10 List of Figures 1.1 Four RegulationModalities(Lessig,1999a, p.88) . .......... 27 3.1 Initial messages when joining an IRC network (Undernet, onJan6,2004) . 41 3.2 Exampleconversation in the IRC channel ”#hottub” . ......... 42 3.3 SnapshotofachannellistintheUndernet . ...... 44 3.4 IRCgrowthfrom1988tolate1995. .. 45 3.5 ElementsofanIRCnetwork . 47 3.6 Treetopology .................................. 50 3.7 Undernetnetwork(around1993).. .... 51 3.8 BasicIRCclient-serverconfiguration . ...... 52 3.9 Modeloftheserverprocess. .. 54 3.10 IRCserverinstallationsteps . ..... 55 4.1 IRCTimeline–NumberedChannels . .. 69 4.2 Linkedlistforchannels . .. 71 5.1 Flood block with /ignore .......................... 104 5.2 Flood block with /silence .......................... 105 6.1 StepstoSetUpanEggdropBot . 114 8.1 Spanningtreetopology . 156 8.2 Treetopologyasa”tree” . 159 8.3 QueryingaDomainName ........................... 160 11 List of Figures 12 List of Algorithms 1 The struct Channel datastructure(slightlysimplified) . 70 2 Channellimitcheckin m_channel() .................... 73 3 is_full()andUnLimChannel()functions . ..... 74 4 MAXUSERSPERCHANNELdirective . 74 5 Startup option (commented out) for maxusersperchannel . ......... 75 6 OPER_KILL directive .............................
Load more

Recommended publications
  • Configuring DNS
    Configuring DNS The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname. The Cisco IOS software maintains a cache of hostname-to-address mappings for use by the connect, telnet, and ping EXEC commands, and related Telnet support operations. This cache speeds the process of converting names to addresses. Note You can specify IPv4 and IPv6 addresses while performing various tasks in this feature. The resource record type AAAA is used to map a domain name to an IPv6 address. The IP6.ARPA domain is defined to look up a record given an IPv6 address. • Finding Feature Information, page 1 • Prerequisites for Configuring DNS, page 2 • Information About DNS, page 2 • How to Configure DNS, page 4 • Configuration Examples for DNS, page 13 • Additional References, page 14 • Feature Information for DNS, page 15 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
    [Show full text]
  • Adopting Encrypted DNS in Enterprise Environments
    National Security Agency | Cybersecurity Information Adopting Encrypted DNS in Enterprise Environments Executive summary Use of the Internet relies on translating domain names (like “nsa.gov”) to Internet Protocol addresses. This is the job of the Domain Name System (DNS). In the past, DNS lookups were generally unencrypted, since they have to be handled by the network to direct traffic to the right locations. DNS over Hypertext Transfer Protocol over Transport Layer Security (HTTPS), often referred to as DNS over HTTPS (DoH), encrypts DNS requests by using HTTPS to provide privacy, integrity, and “last mile” source authentication with a client’s DNS resolver. It is useful to prevent eavesdropping and manipulation of DNS traffic. While DoH can help protect the privacy of DNS requests and the integrity of responses, enterprises that use DoH will lose some of the control needed to govern DNS usage within their networks unless they allow only their chosen DoH resolver to be used. Enterprise DNS controls can prevent numerous threat techniques used by cyber threat actors for initial access, command and control, and exfiltration. Using DoH with external resolvers can be good for home or mobile users and networks that do not use DNS security controls. For enterprise networks, however, NSA recommends using only designated enterprise DNS resolvers in order to properly leverage essential enterprise cybersecurity defenses, facilitate access to local network resources, and protect internal network information. The enterprise DNS resolver may be either an enterprise-operated DNS server or an externally hosted service. Either way, the enterprise resolver should support encrypted DNS requests, such as DoH, for local privacy and integrity protections, but all other encrypted DNS resolvers should be disabled and blocked.
    [Show full text]
  • Praktikum2-Fh.Pdf
    SS Bericht im zweiten praktischen Studiensemester Hauptthemen Installation und Betreuung eines NetNewsServers Installation und Dokumentation von IRC und MailClients Feyrer Hub ert Name Vorname Studiengrupp e IT Ausbildungsb etrieb Rechenzentrum der a t Regensburg Universit Universit a tsstr Regensburg Juni Abgab etermin Kenntnis genommen ::::::::::::::::::::::::::::::::::::::::: Hr K Wur Praktikumsb etreuer Vorwort Dieser Praktikumsb ericht gliedert sich in drei Teile auf entsprechend den drei im Praktikum b ehandelten Themengebieten Zuerst wird ausfuhrlich das Thema NetNews diskutiert darauf folgt eine Einfu hrung in das Internet Relay Chat IRC und die Beschreibung einiger Features des MailClients Elm art was NetNews sind und welche Konventionen im Die Einfu hrung zum Thema NetNews erkl achstes folgt dann eine Beschreibung angig sind Als n origen Netzwerk dem Usenet g zugeh ahlung der Leistungsmerk der Server und ClientInstallation gefolgt von einer allgemeinen Aufz o tigt male von Newsreadern Am Beispiel von TIN und XRn wird gezeigt welche Funktionen b en alt eine Kurzb eschreibung opfen Der weitere Text enth werden um das Medium News auszusch der zur Zeit an der Uni Regensburg existierenden Grupp en sowie eine Auistung interessanter Grupp en zu den einzelnen Betriebssystemen Der letzte Teil gibt Hinweise fur die Installation der b ereits ub ersetzten Newsreader auf eigenen Workstations auterung was IRC Die Einfu hrung ins IRC im zweiten Teil b esteht aus einer allgemeinen Erl ist und welche Konventionen gelten
    [Show full text]
  • Chapter 2. Application Layer Table of Contents 1. Context
    Chapter 2. Application Layer Table of Contents 1. Context ........................................................................................................................................... 1 2. Introduction .................................................................................................................................... 2 3. Objectives ....................................................................................................................................... 2 4. Network application software ....................................................................................................... 2 5. Process communication ................................................................................................................. 3 6. Transport Layer services provided by the Internet ....................................................................... 3 7. Application Layer Protocols ........................................................................................................... 4 8. The web and HTTP .......................................................................................................................... 4 8.1. Web Terminology ................................................................................................................... 5 8.2. Overview of HTTP protocol .................................................................................................... 6 8.3. HTTP message format ...........................................................................................................
    [Show full text]
  • SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst
    ISSN (Print) : 2320 – 3765 ISSN (Online): 2278 – 8875 International Journal of Advanced Research in Electrical, Electronics and Instrumentation Engineering Vol. 2, Issue 5, May 2013 SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst. Prof, Dept. of ECE, Siliguri Institute of Technology, Sukna, Siliguri, West Bengal, India 1 Network Engineer, Network Dept, Ericsson Global India Ltd, India2 Abstract:-. The Secure Internet Live Conferencing (SILC) protocol, a new generation chat protocol provides full featured conferencing services, compared to any other chat protocol. Its main interesting point is security which has been described all through the paper. We have studied how encryption and authentication of the messages in the network achieves security. The security has been the primary goal of the SILC protocol and the protocol has been designed from the day one security in mind. In this paper we have studied about different keys which have been used to achieve security in the SILC protocol. The main function of SILC is to achieve SECURITY which is most important in any chat protocol. We also have studied different command for communication in chat protocols. Keywords: SILC protocol, IM, MIME, security I.INTRODUCTION SILC stands for “SECURE INTERNET LIVE CONFERENCING”. SILC is a secure communication platform, looks similar to IRC, first protocol & quickly gained the status of being the most popular chat on the net. The security is important feature in applications & protocols in contemporary network environment. It is not anymore enough to just provide services; they need to be secure services. The SILC protocol is a new generation chat protocol which provides full featured conferencing services; additionally it provides security by encrypting & authenticating the messages in the network.
    [Show full text]
  • Universidad Pol Facultad D Trabajo
    UNIVERSIDAD POLITÉCNICA DE MADRID FACULTAD DE INFORMÁTICA TRABAJO FINAL DE CARRERA ESTUDIO DEL PROTOCOLO XMPP DE MESAJERÍA ISTATÁEA, DE SUS ATECEDETES, Y DE SUS APLICACIOES CIVILES Y MILITARES Autor: José Carlos Díaz García Tutor: Rafael Martínez Olalla Madrid, Septiembre de 2008 2 A mis padres, Francisco y Pilar, que me empujaron siempre a terminar esta licenciatura y que tanto me han enseñado sobre la vida A mis abuelos (q.e.p.d.) A mi hijo icolás, que me ha dejado terminar este trabajo a pesar de robarle su tiempo de juego conmigo Y muy en especial, a Susana, mi fiel y leal compañera, y la luz que ilumina mi camino Agradecimientos En primer lugar, me gustaría agradecer a toda mi familia la comprensión y confianza que me han dado, una vez más, para poder concluir definitivamente esta etapa de mi vida. Sin su apoyo, no lo hubiera hecho. En segundo lugar, quiero agradecer a mis amigos Rafa y Carmen, su interés e insistencia para que llegara este momento. Por sus consejos y por su amistad, les debo mi gratitud. Por otra parte, quiero agradecer a mis compañeros asesores militares de Nextel Engineering sus explicaciones y sabios consejos, que sin duda han sido muy oportunos para escribir el capítulo cuarto de este trabajo. Del mismo modo, agradecer a Pepe Hevia, arquitecto de software de Alhambra Eidos, los buenos ratos compartidos alrrededor de nuestros viejos proyectos sobre XMPP y que encendieron prodigiosamente la mecha de este proyecto. A Jaime y a Bernardo, del Ministerio de Defensa, por haberme hecho descubrir las bondades de XMPP.
    [Show full text]
  • A Short IRC Primer
    A short IRC primer Nicolas Pioch Nap on IRC <Nicolas Pi och g ras p ins al yo nf r> Text conversion by Owe Rasmussen Sorg <drasmus d tek ch al mer s se> Edition b February Abstract Have you ever wanted to talk with other computer users in other parts of the world Well guess what::: You can The program is called IRC Internet Relay Chat and it is networked much over North America Asia Europ e and Oceania This program is a substitution for talk and many other multiple talk programs you might have read ab out When you are talking on IRC everything you type will instantly b e transmitted around the world to other users that might b e watching their terminals at the time they can then type something and respond to your messages and vice versa I should warn you that the program can b e very addictive once you b egin to make friends and contacts on IRC esp ecially when you learn how to discuss in languages::: Topics of discussion on IRC are varied just like the topics of Usenet newsgroups are varied Technical and p olitical discussions are p opular es p ecially when world events are in progress IRC is also a way to expand your horizons as p eople from many countries and cultures are on hours a day Most conversations are in English but there are always channels in German Japanese French Finnish and o ccasionally other languages IRC gained international fame during the late Persian Gulf War when up dates from around the world came across the wire and most p eople on IRC gathered on a single channel to hear these rep orts CONTENTS Contents
    [Show full text]
  • Abstract Introduction Methodology
    Kajetan Hinner (2000): Statistics of major IRC networks: methods and summary of user count. M/C: A Journal of Media and Culture 3(4). <originally: http://www.api-network.com/mc/0008/count.html> now: http://www.media-culture.org.au/0008/count.html - Actual figures and updates: www.hinner.com/ircstat/ Abstract The article explains a successful approach to monitor the major worldwide Internet Relay Chat (IRC) networks. It introduces a new research tool capable of producing detailed and accurate statistics of IRC network’s user count. Several obsolete methods are discussed before the still ongoing Socip.perl program is explained. Finally some IRC statistics are described, like development of user figures, their maximum count, IRC channel figures, etc. Introduction Internet Relay Chat (IRC) is a text-based service, where people can meet online and chat. All chat is organized in channels which a specific topic, like #usa or #linux. A user can be taking part in several channels when connected to an IRC network. For a long time the only IRC network has been EFnet (Eris-Free Network, named after its server eris.berkeley.edu), founded in 1990. The other three major IRC networks are Undernet (1993), DALnet (1994) and IRCnet, which split off EFnet in June 1996. All persons connecting to an IRC network at one time create that IRC network’s user space. People are constantly signing on and off, the total number of users ever been to a specific IRC network could be called social space of that IRC network. It is obvious, that the IRC network’s social space by far outnumbers its user space.
    [Show full text]
  • Users As Co-Designers of Software-Based Media: the Co-Construction of Internet Relay Chat
    Users as Co-Designers of Software-Based Media: The Co-Construction of Internet Relay Chat Guillaume Latzko-Toth Université Laval AbsTrAcT While it has become commonplace to present users as co-creators or “produsers” of digital media, their participation is generally considered in terms of content production. The case of Internet Relay Chat (IRC) shows that users can be fully involved in the design process, a co-construction in the sense of Science and Technology Studies (STS): a collective, simultaneous, and mutual construction of actors and artifacts. A case study of the early de - velopment of two IRC networks sheds light on that process and shows that “ordinary users” managed to invite themselves as co-designers of the socio-technical device. The article con - cludes by suggesting that IRC openness to user agency is not an intrinsic property of software- based media and has more to do with its architecture and governance structure. Keywords Digital media; Communication technology; Co-construction; Design process; Ordinary user résumé Il est devenu banal de présenter l’usager comme cocréateur ou « produtilisateur » des médias numériques, mais sa participation est généralement envisagée comme une production de contenus. Le cas d’IRC (Internet Relay Chat) montre que les usagers des médias à support logiciel peuvent s’engager pleinement dans le processus de conception, une co-construction au sens des Science and Technology Studies : une construction collective, simultanée et mutuelle des acteurs et des artefacts. Une étude de cas portant sur le développement de deux réseaux IRC éclaire ce processus et montre que les « usagers ordinaires » sont parvenus à s’inviter comme co-concepteurs du dispositif.
    [Show full text]
  • Internet Relay Chat. ERIC Digest
    ED425743 1999-01-00 Internet Relay Chat. ERIC Digest. ERIC Development Team www.eric.ed.gov Table of Contents If you're viewing this document online, you can click any of the topics below to link directly to that section. Internet Relay Chat. ERIC Digest............................................... 1 WHY USE INTERNET RELAY CHAT?..................................... 2 WHAT IS REQUIRED?........................................................ 2 HOW IS IRC ORGANIZED?.................................................. 3 NETS..............................................................................3 CHANNELS......................................................................3 OPS............................................................................... 3 NICKS.............................................................................4 HOW DO YOU FIND, JOIN, OR CREATE A CHANNEL?............... 4 CAN YOU SEND A PRIVATE MESSAGE?................................ 4 HOW DOES ONE EXIT AN IRC CHAT?................................... 4 WHAT ARE THE DISADVANTAGES OF IRC?............................4 WHAT EDUCATIONAL BENEFITS CAN I EXPECT?....................5 ERIC Identifier: ED425743 Publication Date: 1999-01-00 Author: Simpson, Carol Source: ERIC Clearinghouse on Information and Technology Syracuse NY. Internet Relay Chat. ERIC Digest. ED425743 1999-01-00 Internet Relay Chat. ERIC Digest. Page 1 of 6 www.eric.ed.gov ERIC Custom Transformations Team THIS DIGEST WAS CREATED BY ERIC, THE EDUCATIONAL RESOURCES INFORMATION CENTER. FOR MORE
    [Show full text]
  • Instalación Y Administración De Servicios De Mensajería Instantánea, Noticias Y Listas De Distribución
    Servicios de red e internet Instalación y administración de servicios de mensajería instantánea, noticias y listas de distribución Raquel Castellanos Crespo Instalación y administración de servicios de mensajería instantánea, noticias y listas de distribución Servicios de red e internet Raquel Castellanos Crespo INDICE 2 Servicios de red e internet | Instalación y administración de servicios de mensajería instantánea, noticias y listas de distribución Servicios de red e internet Raquel Castellanos Crespo Protocolos La mensajería instantánea (conocida también en inglés como IM) es una forma de comunicación en tiempo real entre dos o más personas basada en texto. El texto es enviado a través de dispositivos conectados a una red como Internet. La mensajería instantánea requiere el uso de un cliente de mensajería instantánea que realiza el servicio y se diferencia del correo electrónico en que las conversaciones se realizan en tiempo real. La mayoría de los servicios ofrecen el "aviso de presencia", indicando cuando el cliente de una persona en la lista de contactos se conecta o en qué estado se encuentra, si está disponible para tener una conversación. En los primeros programas de mensajería instantánea, cada letra era enviada según se escribía y así, las correcciones de las erratas también se veían en tiempo real. Esto daba a las conversaciones más la sensación de una conversación telefónica que un intercambio de texto. En los programas actuales, habitualmente, se envía cada frase de texto al terminarse de escribir. Además, en algunos, también se permite dejar mensajes aunque la otra parte no esté conectada al estilo de un contestador automático. Otra función que tienen muchos servicios es el envío de ficheros.
    [Show full text]
  • Informational Internet Relay
    Network Working Group C. Kalt Request for Comments: 2813 April 2000 Updates: 1459 Category: Informational Internet Relay Chat: Server Protocol Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract While based on the client-server model, the IRC (Internet Relay Chat) protocol allows servers to connect to each other effectively forming a network. This document defines the protocol used by servers to talk to each other. It was originally a superset of the client protocol but has evolved differently. First formally documented in May 1993 as part of RFC 1459 [IRC], most of the changes brought since then can be found in this document as development was focused on making the protocol scale better. Better scalability has allowed existing world-wide networks to keep growing and reach sizes which defy the old specification. Kalt Informational [Page 1] RFC 2813 Internet Relay Chat: Server Protocol April 2000 Table of Contents 1. Introduction ............................................... 3 2. Global database ............................................ 3 2.1 Servers ................................................ 3 2.2 Clients ................................................ 4 2.2.1 Users ............................................. 4 2.2.2 Services .......................................... 4 2.3 Channels ..............................................
    [Show full text]