DOCSLIB.ORG

Srain Documentation Release 1.3.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Srain Documentation Release 1.3.0 Srain Documentation Release 1.3.0 Shengyu Zhang Sep 21, 2021 Contents 1 All pages 3 1.1 Srain...................................................3 1.2 Quick Start................................................4 1.3 Installation................................................9 1.4 Commands Manual............................................ 14 1.5 Configuration Manual.......................................... 22 1.6 Development Specification........................................ 29 1.7 Miscellaneous.............................................. 30 1.8 Frequently Asked Questions....................................... 30 1.9 Change Log............................................... 34 1.10 Support Tables.............................................. 44 2 Indices and Tables 47 i ii Srain Documentation, Release 1.3.0 Welcome to Srain documentation! Latest version: 2021-09-23 Version 1.3.0. The source code of this documentation is hosted on GitHub. If you found any mistake, feel free to file issue or pull request. Contents 1 Srain Documentation, Release 1.3.0 2 Contents CHAPTER 1 All pages 1.1 Srain Modern IRC client written in GTK. Home| Documentation| Source code 3 Srain Documentation, Release 1.3.0 1.1.1 Packaging Status 1.1.2 Features • Fully open source • RFC {1459,2812} compatible • Partial IRCv3 support • Multi-platform support (Linux, Windows, macOS and BSD) • Act like modern IM client – Graphical user interface – Convenient connection panel – Interactive channel search – Forward message in one click – URL preview – Desktop notificaion – Special optimization for bridge/relay bot • Act like geek IRC client – Anything can be done via commands – Fine-grained configuration with hot update support – Regex based message render and filter mechanisms – IPC based plugin system (TODO) 1.1.3 Need Help? Frequently Asked Questions may be helpful. Feel free to contact us if you have any question about Srain. • IRC Channel: #srain @ Libera Chat • Github: file an issue Here 1.1.4 License GNU General Public License Version 3 1.2 Quick Start 4 Chapter 1. All pages Srain Documentation, Release 1.3.0 • Start Srain • Connect to IRC server – Predefined Server – Custom Server – Using Command • Join Channel – Directly Join – Search Channel – Using Command Note: For your information, the following screenshots are taken under GNOME 3.34.4 with Wayland backed with Arc GTK theme and Breeze icon theme. 1.2.1 Start Srain After the Installation of Srain, you will find Srain in your applications list, if not, just type srain in your shell to run it. Then you will see Srain’s initial interface. 1.2. Quick Start 5 Srain Documentation, Release 1.3.0 1.2.2 Connect to IRC server freenode is a famous IRC network, the official channel of Srain #srain is also hosted on it. Let’s start by connecting to freenode. Predefined Server Srain has a predefined list of commonly used IRC servers, freenode is one of it. If you want to add server into this list, refer to Configuration Manual. Click the connection button on the Srain header bar, select the page “Quick Mode”, select the item “freenode” from candidate box with label “Server”, enter your nickname, then click the “Connect” button: If everything goes well, Srain should connected to freenode, then your would see some message from freenode’s server: Custom Server While the server your want to connect to is not listed in the predefined list, switch to the page “Advanced Mode”, enter the hostname, port, and etc. Note: • If the port is a TLS port, make sure that the option “Use secure connection” is checked. • If the server’s certificate is untrusted and you insist on continuing, check the option “Do not verify certificate”. 6 Chapter 1. All pages Srain Documentation, Release 1.3.0 Then click the “Connect” button: Using Command Refer to /server and /connect. If you want to automatically execute commands at each time Srain starts, please refer to Playground. 1.2.3 Join Channel After connecting to freenode, now let’s try to join #srain, the official channel of Srain. Directly Join While your has a clear channel to join, such as #srain, just click the join button, select the page “Join Channel”, enter the channel name in the input entry with label “Channel”, then click the “Join” button: Now you should joined the channel: Search Channel While you don’t know the exact name of the channel, click the join button, switch to page “Search Channel”, click the button with “refresh” icon, Srain should start receiving channel list from server. 1.2. Quick Start 7 Srain Documentation, Release 1.3.0 8 Chapter 1. All pages Srain Documentation, Release 1.3.0 Then you can enter the keyword or specify the filter conditions to search channel. For example we enter “#s”, select the channel you want to join from channe list, then click “Join” button to join it. Note: If the channel requires a join password, try double click the row of channel. Using Command Refer to /join. 1.3 Installation Srain is available on GNU/Linux, Windows, macOS and BSD. • Dependencies • Building – Play with Meson – Makefile Helper • Distribution Packages 1.3. Installation 9 Srain Documentation, Release 1.3.0 – GNU/Linux * Arch Linux * Debian · Pre-built package · Build byself * Fedora * Flatpak * Gentoo * openSUSE – Windows * Pre-built package * Build byself – macOS – BSD * OpenBSD 10 Chapter 1. All pages Srain Documentation, Release 1.3.0 1.3.1 Dependencies Name Notes Version meson Only for Building > 0.45.0 make Optional, only for development appstream Only for building, on Debian-based distributions coreutils Only for building gcc Only for building pkg-config Only for building gettext Only for building glib2 glib-networking Optional, for TLS connection support gtk+3 >= 3.18 libsoup libconfig >= 1.5 libsecret openssl python-sphinx Optional, for building documentation 1.3.2 Building You should install the aboved Dependencies on your platform before the following steps. Firstly, download source code of srain, you can get source code of latest release: $ wget https://github.com/SrainApp/srain/archive/1.3.0.tar.gz $ tar -xvzf 1.3.0.tar.gz $ cd srain-1.3.0 Or get git version: $ git clone https://github.com/SrainApp/srain.git $ cd srain Play with Meson Srain use Meson with ninja backend as its build system. You can build it via the following commands: $ meson setup builddir $ cd builddir $ ninja Install(root privileges required): $ cd builddir # ninja install HTML documentation and manpage are built and installed by default, if you don’t need them, just set meson option doc_builders to an empty array when setup: $ meson setup -Ddoc_builders=[] builddir 1.3. Installation 11 Srain Documentation, Release 1.3.0 Makefile Helper We also provide a simple Makefile helper to simplify meson commands. It is convenient for development. $ make # Build srain $ make build # Same as above $ make install # Install srain to prefix under project root $ make run # Run srain with isolated $HOME and XDG Directory $ make debug # Same as `make run`, but with GDB attached $ make inspect # Same as `make run`, but with GtkInspector $ make clean # Remove all compilation and installation result $ make doc # View installed HTML documentation 1.3.3 Distribution Packages GNU/Linux Arch Linux Packages srain and srain-git (git version) are available on AUR, it is quite easy to install using AUR helper(yay as an example): $ yay -S srain $ yay -S srain-git # git version If you are the user of Arch Linux CN Repository, try: # pacman -S archlinuxcn/srain # pacman -S archlinuxcn/srain-git # git version Debian There is no srain package in the official repository yet. Pre-built package We provide pre-built deb package that you can get it from Github release page. Build byself Copy the debian folder on srain-contrib to srain folder. Then type following command on your terminal: $ dpkg-buildpackage -b -us -uc Note that the dependencies mentioned above also should be installed. The details could be found on debian/crontrol file. Then install the package (replace package name with the name of your package): $ sudo apt-get install -f ../srain_1.3.0-1_amd64.deb 12 Chapter 1. All pages Srain Documentation, Release 1.3.0 Fedora Srain now in offical repository of fedora, use dnf to install it. # dnf install srain Flatpak cpba is maintaining Flatpak manifest for Srain and The built package is available on Flathub, just execute the following commands to install if you already have flatpak installed: $ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub. ,!flatpakrepo $ flatpak install flathub im.srain.Srain Gentoo Please refers to gentoo portage overlays. openSUSE alois is maintaining openSUSE package for Srain, following this link to install it. Windows Srain requires Windows 7 or later. Pre-built package After 2020-08-10 Version 1.1.2, we provide Windows portable binary that you can get it from Github release page. Build byself If you want to build Srain on Windows youself, you should use the toolchains provided by MSYS2 project. Firstly install MSYS2, then open a MSYS2 shell, install the basic build tools: $ pacman -S base-devel $ pacman -S mingw-w64-i686-toolchain # For 32-bit Windows $ pacman -S mingw-w64-x86_64-toolchain # For 64-bit Windows Then download the package script from MinGW PKGBUILD for Srain, run the following commands at the directory of PKGBUILD: $ MINGW_INSTALLS=mingw32 makepkg-mingw -fsi # For 32-bit Windows $ MINGW_INSTALLS=mingw64 makepkg-mingw -fsi # For 64-bit Windows 1.3. Installation 13 Srain Documentation, Release 1.3.0 If everything goes well, Srain is installed under your MinGW prefix. Note: If you suffer the “error while loading shared libraries: xxxx.dll: cannot open shared object file: No such file or directory” problem when running, please run it in cmd but not msys2 shell, and it will show you real missing library.1 macOS Warning: macOS support of Srain is still experimental. There is not a distribution package or package script for Srain on macOS, you should build Srain by yourself.
Load more

Recommended publications
  • Desynched Channels on Ircnet
    Desynched channels on IRCnet Michael Hansen and Jeroen F. J. Laros [email protected] October 29, 2018 Abstract In this paper we describe what a desynchronised channel on IRC is. We give procedures on how to create such a channel and how to remove desyn- chronisation. We explain which types of desynchronisation there are, what properties desynchronised channels have, and which properties can be ex- ploited. 1 Introduction IRC [1] is one of the oldest digital communication protocols on the internet [2]. This protocol is a form of synchronous conferencing which is mainly used for its one-to-many communication capabilities. Although its popularity has somewhat diminished since the introduction of instant messaging applications [3] like the MSN messenger [4], it is still widely used. In this paper, we first give some background information about IRC in Sec- tion 2. In Section 3 we elaborate on the phenomenon of desynched channels and in Section 4 we describe how to place a boundary, Section 5 covers the occurrence of fake modes and Section 6 describes how to remove a desync. In Section 7, we give some examples of possible uses of fake modes and we conclude in Section 8. arXiv:0811.3140v1 [cs.NI] 19 Nov 2008 2 Background An IRC network consists of multiple servers connected to each other, there are no cycles in this network, so the topology of this network is an undirected tree (acyclic graph). An IRC network also has clients connected to its servers, and messages are relayed from server to server to transfer a message from one client to another.
    [Show full text]
  • Some Touching News the New Rules of Digital Media
    Some Touching News the new rules of digital media Josh Clark @globalmoxie Interaction designer but also what might be called: design strategist I work mainly in mobile. I wrote a book called Tapworthy about designing iPhone apps. Fill my days: Help people/companies think through crafting terrific experiences for non-desktop systems. Means figuring out how phones, tablets fit into overall digital diet. But it’s also about how these devices are creating entirely new kinds of interaction, new kinds of digital products and interfaces. That’s what I’m going to talk about today. How this explosion of new devices means we have to rethink how we approach design. Especially excited about possibilities of touch interfaces. I believe touch forces—or should force—important, FUNDAMENTAL changes in how we approach the designs of these interfaces. When you get rid of the mouse and cursor, these prosthetics that we’ve been using to point at stuf for 25 years, you get a VERY diferent experience. And it suggests entirely new interfaces. Touch will help us sweep away decades of buttons—menus—folders—tabs—administrative debris to work directly with content. This is very diferent from what came before. And certainly VERY diferent from print. I’m going to talk about two things today: 1. How we should/shouldn’t go about conceiving entirely new interfaces for news; particularly its relationship to print. Then: nitty-gritty techniques for pushing touch interfaces in exciting new directions. iPad in particular giving many of us opportunity to experiment. EXCITING. But also means we see a lot of misfires, too.
    [Show full text]
  • STEM Subjects Face the Haptic Generation: the Ischolar Tesis
    STEM Subjects Face the Haptic Generation: The iScholar Tesis doctoral Nuria Llobregat Gómez Director Dr. D. Luis Manuel Sánchez Ruiz Valencia, noviembre 2019 A mi Madre, a mi Padre (†), a mis Yayos (†), y a mi Hija, sin cuya existencia esto no hubiese podido suceder. Contents Abstract. English Version Resumen. Spanish Version Resum. Valencian Version Acknowledgements Introduction_____________________________________________________________________ 7 Outsight ____________________________________________________________________________________ 13 Insight ______________________________________________________________________________________14 Statement of the Research Questions __________________________________________________________ 15 Dissertation Structure ________________________________________________________________________16 SECTION A. State of the Art. The Drivers ____________________________________________ 19 Chapter 1: Haptic Device Irruption 1.1 Science or Fiction? Some Historical Facts ______________________________________________ 25 1.2 The Irruptive Perspective ___________________________________________________________ 29 1.2.1 i_Learn & i_Different ____________________________________________________________________ 29 1.2.2 Corporate Discourse and Education ________________________________________________________ 31 1.2.3 Size & Portability Impact _________________________________________________________________ 33 First Devices _____________________________________________________________________________ 33 Pro Models
    [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]
  • 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]
  • There Are Two Dedicated Dspace IRC (Internet Relay Chat) Channels (I.E
    IRC Code of Conduct All DSpace support channels, mailing lists and meetings follow the LYRASIS Code of Conduct. We ask you to remain respectful in all discussions. We also encourage you to report any violations of the code of conduct to LYRASIS (see the Code of Conduct for more details). DSpace chat has moved to Slack Our old IRC channels are essentially unmonitored these days. Instead, we recommend joining our DSpace.org Slack for any chat-based support. You are also welcome to email your question to the dspace-tech Mailing List as an alternative, or choose one of the other DSpace Sup port options. There are two dedicated DSpace IRC (internet relay chat) channels (i.e. "rooms") on the irc.freenode.net server: #dspace (irc://irc.freenode.net/dspace) - all DSpace discussions and live Q & A. This channel is unlogged. #duraspace (irc://irc.freenode.net/duraspace) - Old duraspace community channel (no longer used). As of July 2018, this channel is unlogged. Pri or years logs are still available/archived. If you do not have access to an IRC client, or are new to IRC, the following web interfaces are very easy way to get started: Login to #dspace IRC at: http://webchat.freenode.net?channels=dspace Enter in a nickname of your choice (e.g. firstName_lastName) & click "Connect" Login to #duraspace IRC at: http://webchat.freenode.net?channels=duraspace Enter in a nickname of your choice (e.g. firstName_lastName) & click "Connect" Or you can login to both IRC channels at the same time: http://webchat.freenode.net?channels=duraspace,dspace For a list of IRC client software, see: http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients Many current Instant Messaging (IM) clients also support IRC.
    [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]
  • Coleman-Coding-Freedom.Pdf
    Coding Freedom !" Coding Freedom THE ETHICS AND AESTHETICS OF HACKING !" E. GABRIELLA COLEMAN PRINCETON UNIVERSITY PRESS PRINCETON AND OXFORD Copyright © 2013 by Princeton University Press Creative Commons Attribution- NonCommercial- NoDerivs CC BY- NC- ND Requests for permission to modify material from this work should be sent to Permissions, Princeton University Press Published by Princeton University Press, 41 William Street, Princeton, New Jersey 08540 In the United Kingdom: Princeton University Press, 6 Oxford Street, Woodstock, Oxfordshire OX20 1TW press.princeton.edu All Rights Reserved At the time of writing of this book, the references to Internet Web sites (URLs) were accurate. Neither the author nor Princeton University Press is responsible for URLs that may have expired or changed since the manuscript was prepared. Library of Congress Cataloging-in-Publication Data Coleman, E. Gabriella, 1973– Coding freedom : the ethics and aesthetics of hacking / E. Gabriella Coleman. p. cm. Includes bibliographical references and index. ISBN 978-0-691-14460-3 (hbk. : alk. paper)—ISBN 978-0-691-14461-0 (pbk. : alk. paper) 1. Computer hackers. 2. Computer programmers. 3. Computer programming—Moral and ethical aspects. 4. Computer programming—Social aspects. 5. Intellectual freedom. I. Title. HD8039.D37C65 2012 174’.90051--dc23 2012031422 British Library Cataloging- in- Publication Data is available This book has been composed in Sabon Printed on acid- free paper. ∞ Printed in the United States of America 1 3 5 7 9 10 8 6 4 2 This book is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE !" We must be free not because we claim freedom, but because we practice it.
    [Show full text]
  • Tomenet-Guide.Pdf
    .==========================================================================+−−. | TomeNET Guide | +==========================================================================+− | Latest update: 17. September 2021 − written by C. Blue ([email protected]) | | for TomeNET version v4.7.4b − official websites are: : | https://www.tomenet.eu/ (official main site, formerly www.tomenet.net) | https://muuttuja.org/tomenet/ (Mikael’s TomeNET site) | Runes & Runemastery sections by Kurzel ([email protected]) | | You should always keep this guide up to date: Either go to www.tomenet.eu | to obtain the latest copy or simply run the TomeNET−Updater.exe in your | TomeNET installation folder (desktop shortcut should also be available) | to update it. | | If your text editor cannot display the guide properly (needs fixed−width | font like for example Courier), simply open it in any web browser instead. +−−− | Welcome to this guide! | Although I’m trying, I give no guarantee that this guide | a) contains really every detail/issue about TomeNET and | b) is all the time 100% accurate on every occasion. | Don’t blame me if something differs or is missing; it shouldn’t though. | | If you have any suggestions about the guide or the game, please use the | /rfe command in the game or write to the official forum on www.tomenet.eu. : \ Contents −−−−−−−− (0) Quickstart (If you don’t like to read much :) (0.1) Start & play, character validation, character timeout (0.1a) Colours and colour blindness (0.1b) Photosensitivity / Epilepsy issues (0.2) Command reference
    [Show full text]
  • Getting Started with Ubuntu 12.04
    Getting Started withUbuntu 12.04 Second Edition The Ubuntu Manual Team Copyright © – by e Ubuntu Manual Team. Some rights reserved. cba is work is licensed under the Creative Commons Aribution–Share Alike . License. To view a copy of this license, see Appendix A, visit http://creativecommons.org/licenses/by-sa/./, or send a leer to Creative Commons, Second Street, Suite , San Francisco, California, , USA. Geing Started with Ubuntu . can be downloaded for free from http:// ubuntu-manual.org/ or purchased from http://ubuntu-manual.org/buy/ gswue/en_US. A printed copy of this book can be ordered for the price of printing and delivery. We permit and even encourage you to dis- tribute a copy of this book to colleagues, friends, family, and anyone else who might be interested. http://ubuntu-manual.org Second Edition Revision number: Revision date: -- :: + Contents Prologue Welcome Ubuntu Philosophy A brief history of Ubuntu Is Ubuntu right for you? Contact details About the team Conventions used in this book Installation Geing Ubuntu Trying out Ubuntu Installing Ubuntu—Geing started Finishing Installation Ubuntu installer for Windows e Ubuntu Desktop Understanding the Ubuntu desktop Unity Using Launcher e Dash Workspaces Managing windows Browsing files on your computer Nautilus file manager Searching for files and folders on your computer Customizing your desktop Accessibility Session options Geing help Working with Ubuntu All the applications you need Geing online Browsing the web Reading and composing email Using instant messaging Microblogging Viewing and editing photos Watching videos and movies Listening to audio and music Burning CDs and DVDs Working with documents, spreadsheets, and presentations Ubuntu One Hardware Using your devices Hardware identification .
    [Show full text]
  • A Tool for Internet Chatroom Surveillance
    A Tool for Internet Chatroom Surveillance Ahmet C¸amtepe, Mukkai S. Krishnamoorthy, and B¨ulent Yener ? Department of Computer Science, RPI, Troy, NY 12180, USA. {camtes, moorthy, yener}@cs.rpi.edu Abstract. Internet chatrooms are common means of interaction and communications, and they carry valuable information about formal or ad-hoc formation of groups with diverse objectives. This work presents a fully automated surveillance system for data collection and analysis in Internet chatrooms. The system has two components: First, it has an eavesdropping tool which collects statistics on individual (chatter) and chatroom behavior. This data can be used to profile a chatroom and its chatters. Second, it has a computational discovery algorithm based on Singular Value Decomposition (SVD) to locate hidden communities and communication patterns within a chatroom. The eavesdropping tool is used for fine tuning the SVD-based discovery algorithm which can be deployed in real-time and requires no semantic information processing. The evaluation of the system on real data shows that (i) statistical prop- erties of different chatrooms vary significantly, thus profiling is possible, (ii) SVD-based algorithm has up to 70-80% accuracy to discover groups of chatters. 1 Introduction and Background Internet chatrooms provide for an interactive and public forum of communica- tion for participants with diverse objectives. Two properties of chatrooms make them particularly vulnerable for exploitation by malicious parties. First, the real identity of participants are decoupled from their chatroom nicknames. Second, multiple threads of communication can co-exists concurrently. Although human- monitoring of each chatroom to determine who-is-chatting-with-whom is possible, it is very time consuming hence not scalable.
    [Show full text]