cl-irc-devel

cl-irc-devel@common-lisp.net

99 discussions

[cl-irc-devel] Www.RiniaMp3.NET Free Mp3 Site
by cl-irc-devel＠common-lisp.net 11 Jan '08

11 Jan '08

RiniaMp3.NET - http://www.Riniamp3.NET Hi Mr/Mrs. You are welcome to the http://www.riniamp3.net About 15.000 songs and video clips for free We do not charge for something. You do not need to put Credit Card or something to pay. All you have to do is to download your best songs. It iss all for free at www.riniamp3.net

1 0

[cl-irc-devel] [SPAM] I just saw your blog and had a few questionsq
by chinapolling 07 Jul '07

07 Jul '07

Spam detection software, running on the system "clnet", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Today’s world is getting smaller Today’s world is getting smaller, communication is everything. When you can't get online to make a post, send a message, jot down an idea or check up on your friends' pages you feel like part of you has been taken away. Your opinions and views matter to us. Tell us more about yourself and win a brand new iPod Nano. [...] Content analysis details: (7.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 TO_ADDRESS_EQ_REAL To: repeats address as real name 1.7 MSGID_FROM_MTA_ID Message-Id for external message added locally 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 HTML_TAG_EXIST_TBODY BODY: HTML has "tbody" tag 0.1 MPART_ALT_DIFF BODY: HTML and text parts are different 0.2 MIME_HTML_ONLY BODY: Message only has text/html MIME parts -2.0 BAYES_20 BODY: Bayesian spam probability is 5 to 20% [score: 0.0784] 0.6 FORGED_OUTLOOK_HTML Outlook can't send HTML message only 2.4 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts 3.9 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

[cl-irc-devel] Re: server-2 stream issue
by Erik Huelsmann 09 May '07

09 May '07

Hi Mikhail, I'm CC-ing the development list because I've seen this question before and that way it will be available in the archives for posterity. I hope you don't mind. See my comments inline below. In summary, there are 2 problems in your code. On 5/9/07, Mikhail Shevchuk <mikhail.shevchuk(a)gmail.com> wrote: > Hi, Eric > There are two following threads in my application: > > IRC-UTR-BOT> (make-thread #'irc-read-loop) > #<THREAD {B30F869}> > IRC-UTR-BOT> (server-2) > #<THREAD {B3801F1}> > > Here is the source of the package: > > (defpackage :irc-utr-bot > (:use "CL" "SB-THREAD" "SB-EXT")) > > (in-package :irc-utr-bot) > > (defvar *irc-channel* (string "#utr")) > > ;; connect to IRC-server > (defvar *irc-connection* (cl-irc:connect :nickname "xmpp-" > :server "irc.tomsk.ru" > :port 6667)) You need to do 2 additional things to make the connection work: 1) You need to add the default hooks for the cl-irc library to work correctly 2) You need to call read-message-loop on the connection to handle the incoming IRC messages. The above means that this code is missing: (cl-irc:add-default-hooks *irc-connection*) > (defvar *jabber-bot-conn* (usocket:socket-stream > (usocket:socket-connect "213.183.100.107" 9999))) > > (cl-irc:join *irc-connection* *irc-channel*) ;; joining channel > > (defvar *serv*) > > (defun server-2 () > (let ((sock (usocket:socket-listen "88.204.87.138" 3690 :backlog 4 > :reuseaddress t))) > (setf *serv* sock) > (sb-thread:make-thread #'(lambda () > (let ((csock (usocket:socket-accept sock))) > (let ((cstream (usocket:socket-stream csock))) > (when cstream > (loop for line = (read-line cstream nil) Here you may want to check whether the socket is actually still connected before reading from it. See cl-irc:read-message. > while line do (progn > (cl-irc:privmsg *irc-connection* *irc-channel* (format nil > "~A" line)))) > (close cstream)))))))) > > (defun msg-hook (message) > (progn > (format *jabber-bot-conn* "_~A_: /~a/" > (cl-irc:source message) (second (cl-irc:arguments message))) > (force-output *jabber-bot-conn*) > (format t "_~a_: /~a/" > (cl-irc:user message) (second (cl-irc:arguments message))))) > > (cl-irc:remove-hooks *irc-connection* 'cl-irc-privmsg-message) > (cl-irc:add-hook *irc-connection* 'cl-irc:irc-privmsg-message #'msg-hook) > > (defun irc-read-loop () > (cl-irc:read-message-loop *irc-connection*)) > > But this doesn't work well because of the following exception, that is > raised after some time. > I don't know the reason of this crash, but I hope you have some ideas. The problem is that the server sends you IRC messages to which you have to send an answer. The default cl-irc library does that for you IFF you configure it correctly; by adding the default hooks to allow it to handle those messages. By not adding the hooks, you are effectively telling cl-irc *not* to handle any IRC traffic for you - meaning that you'll have to provide all protocol behaviours implemented in cl-irc yourself. HTH, Erik.

2 1

[cl-irc-devel] message nickname
by Mikhail Shevchuk 07 May '07

07 May '07

Hi, I have a simple msg-hook here: (defun msg-hook (message) (progn (format *jabber-bot-conn* "_~A_: /~a/" (cl-irc:user message) (second (cl-irc:arguments message))) (force-output *jabber-bot-conn*))) (cl-irc:user message) expression evaluates to strings like: ~mico or ~user, how can I get real nicknames instead of this ? Thank you. -- A vivid and creative mind characterizes you.

2 1

[cl-irc-devel] Support for IRC+SSL
by Stephan Maka 29 Apr '07

29 Apr '07

Hello, developers of cl-irc Encrypting IRC connections with SSL is supported by almost any common IRC client and is used in many small IRC nets. I would love to see that in cl-irc. The attached file contains a connect-ssl function which is a big code duplication of connect from command.lisp. There should be a cleaner way, but it already works and I'm still a bloody Lisp beginner. Stephan PS: How do I enable IPv6 support?

2 1

[cl-irc-devel] DCC status update
by Erik Huelsmann 25 Apr '07

25 Apr '07

Yesterday, I committed the basic infrastructure required to make DCC connections behave similarly to IRC connections. I write similarly, because DCC isn't an actual protocol: each line transmitted is assumed to be a message for the client. There's not even a basic command/response structure as with IRC. So, what I did is interpret every DCC line as it were a private PRIVMSG message. The new code reads lines from the connection, creates a dcc-chat-privmsg-message and applies it to any registered hooks, just as we do with normal IRC messages. Why message types? Well, some DCC clients *do* support CTCP messages. Which means that we'll be able to have different message classes after all (even though they'll all stem from the PRIVMSG super type). So, what I did (Todone): - Implement an abstract DCC-connection type - Implement a non-abstract DCC-CHAT-connection type - Implement a dcc-chat-message type - Implement the infrastructure to receive and dispatch dcc-chat-message class messages Todo: - Initiate (passive) chat connection - Accept (active) chat connection - Reject (passive+active) chat connection requests - Implement chat-connection interaction functionality (ie sending messages and handling default messages). As soon as the TODO list above has been implemented, the new DCC chat functionality only lacks active DCC initiation requests and a myriad of binary (file) transfer protocols. Basically, usocket provides the functionality required to implement active DCC connection requests, but given that it would open a port on the initiating client, I'm not yet sure what to do there: I don't want to introduce too many security problems... So, skipping the active connection setup first, I'm going to implement the original (DCC SEND) binary file transmission scheme, much in the same way I did with DCC CHAT. One of the problems with DCC SEND is that it's a block-oriented protocol and at the same time it's also used for transmitting binary data, meaning normally you wouldn't want to have it call hooks, but pass the data into a stream right away. Our current scheme actually already supports that: our connections have a client -stream in which we have a 'send all input from the network here' stored. This is exactly what I'll be doing. The only thing which bothers me is that there currently is no 'this connection finished' hook or callback, but that probably fits nicely with the 'we're going to remove start/stop-background-message-handler, so write your own!' scheme, where the basic message handler is just a read-message-loop call. This could be extended with a call to, say, finish-my-dcc-file-receiving-stream on the level of the client which uses the cl-irc library. Thanks for your attention and please send your comments if you have any! bye, Erik.

1 0

[cl-irc-devel] DCC support rewrite
by Erik Huelsmann 21 Apr '07

21 Apr '07

Hi, Just for your information so any commits don't come unexpected: I'm rewriting cl-irc DCC support to make DCC CHAT connections behave more like normal IRC connections: with the same event/message structure. This also allows me to support CTCP-over-DCC. After rewriting the DCC CHAT side, I'll have a look at supporting DCC SEND and possibly a number of its variants. bye, Erik.

1 0

[cl-irc-devel] Debian administration files in repository
by Erik Huelsmann 20 Apr '07

20 Apr '07

Hi Peter, I see Debian etch has much newer debian admin files associated with its cl-irc package than the ones in the repository. Would you like to update them? In case you don't, I'd rather remove the old ones from the repository to prevent confusion. Thanks for your continued efforts for the lisp packages in Debian! bye, Erik.

1 0

[cl-irc-devel] Small patch for svn rev.177
by Lars Rune Nøstdal 15 Mar '07

15 Mar '07

Hi, I couldn't get latest version from SVN working (rev.177), but this seems to have fixed this: Index: event.lisp =================================================================== --- event.lisp (revision 177) +++ event.lisp (working copy) @@ -158,7 +158,7 @@ (declare (ignore nick)) (let ((channel (find-channel connection channel))) (setf (visibility channel) - (or (car (assoc chan-visibility + (or (second (assoc chan-visibility '(("=" :public) ("*" :private) ("@" :secret)) :test #'string=)) :unknown)) -- Mvh, Lars Rune Nøstdal http://nostdal.org/

2 1

[cl-irc-devel] Fwd: [cl-irc-cvs] r165 - trunk
by Erik Huelsmann 04 Jan '07

04 Jan '07

Now that I've moved implementation specific socket code, I'd like to remove implementation specific threading code: the last bit of implementation specific code we have is located in 'start-process', which is used by 'start-background-handler'. When using CLIM to develop GUI apps, CLIM has its own threading which should be used to handle threads. When *not* using CLIM, developers can use bordeaux-threads (which uses the CLIM model, but in a stand-alone library). All in all, it seems bizarre we take on the problem of providing our own threading functions. (bordeaux-threads provides threading for ECL, which we currently don't support in our threading lib; usocket does support ECL though, so there's nothing but our threading dependency holding us back) What I want to do is move 'start-background-handler' to an example program - which is based on bordeaux-threads - to show first time users how to get an irc client instance up and running quickly. Comments? bye, Erik. ---------- Forwarded message ---------- From: ehuelsmann(a)common-lisp.net <ehuelsmann(a)common-lisp.net> Date: Jan 4, 2007 11:48 PM Subject: [cl-irc-cvs] r165 - trunk To: cl-irc-cvs(a)common-lisp.net Author: ehuelsmann Date: Thu Jan 4 17:48:22 2007 New Revision: 165 Modified: trunk/cl-irc.asd trunk/command.lisp trunk/protocol.lisp trunk/utility.lisp Log: Change trivial-sockets dependency to usocket as discussed many moons ago. This commit adds support for all usocket supported lisps, except that they're not all supported by (cl-irc::start-process ...). Modified: trunk/cl-irc.asd ============================================================================== --- trunk/cl-irc.asd (original) +++ trunk/cl-irc.asd Thu Jan 4 17:48:22 2007 @@ -16,7 +16,7 @@ :version "0.5.2" :licence "MIT" :description "Common Lisp interface to the IRC protocol" - :depends-on (:split-sequence :trivial-sockets :flexi-streams) + :depends-on (:split-sequence :usocket :flexi-streams) :properties ((#:author-email . "cl-irc-devel(a)common-lisp.net") (#:date . "$Date$") ((#:albert #:output-dir) . "doc/api-doc/") Modified: trunk/command.lisp ============================================================================== --- trunk/command.lisp (original) +++ trunk/command.lisp Thu Jan 4 17:48:22 2007 @@ -249,8 +249,11 @@ (connection-type 'connection) (logging-stream t)) "Connect to server and return a connection object." - (let* ((stream (socket-connect server port)) + (let* ((socket (usocket:socket-connect server port + :element-type 'flexi-streams:octet)) + (stream (usocket:socket-stream socket)) (connection (make-connection :connection-type connection-type + :socket socket :network-stream stream :client-stream logging-stream :server-name server)) Modified: trunk/protocol.lisp ============================================================================== --- trunk/protocol.lisp (original) +++ trunk/protocol.lisp Thu Jan 4 17:48:22 2007 @@ -122,6 +122,9 @@ :initarg :server-port :accessor server-port :initform *default-irc-server-port*) + (socket + :initarg :socket + :documentation "Slot to store socket (for internal use only).") (network-stream :initarg :network-stream :accessor network-stream @@ -199,6 +202,7 @@ (password nil) (server-name "") (server-port nil) + (socket nil) (network-stream nil) (outgoing-external-format *default-outgoing-external-format*) (client-stream t) @@ -212,6 +216,7 @@ :password password :server-name server-name :server-port server-port + :socket socket :network-stream network-stream :output-stream output-stream :client-stream client-stream))) Modified: trunk/utility.lisp ============================================================================== --- trunk/utility.lisp (original) +++ trunk/utility.lisp Thu Jan 4 17:48:22 2007 @@ -101,10 +101,6 @@ (fourth (ldb (byte 8 0) integer))) (vector first second third fourth))) -(defun socket-connect (server port) - "Create a socket connected to `server':`port' and return stream for it." - (trivial-sockets:open-stream server port :element-type '(unsigned-byte 8))) - (defun external-format-fixup (format) (let ((new-format (copy-list format))) (setf (getf (cdr new-format) :eol-style) :crlf) _______________________________________________ cl-irc-cvs mailing list cl-irc-cvs(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cl-irc-cvs

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

cl-irc-devel