napster.txt

P2P NAP的C实现 P2P在网络应用中越来越流行

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <nick> <sharing> <linespeed>

	Example:

	80's DLongley 23 7

408 (0x198)	channel user list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user> <sharing> <link-type>

	this message is identical to the join (406) message.  the server will
	send the list of users in the channel prior to the client join command
	in this message.  joins that occur after the client has joined will
	be noted by a 406 message.

409 (0x199)	end of channel user list [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel>

	this message is sent by the server to indicate it has sent all information
	about the users in a channel

410 (0x19a)	channel topic [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <topic>

	sent when joining a channel or a new topic is set.  a client requesting
	topic change also uses this message.

	[why didn't they put a field to indicate WHO changed the topic?  as
	it is now you can only tell that it was changed.  -ed]

420 (0x1a4)	channel ban list [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <channel>

	This command is used by clients to request the list of channel bans,
	and by the server to indicate the end of the channel ban list for
	a channel (also see 421).

421 (0x1a5)	channel ban list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

422 (0x1a6)	channel ban [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user|ip> [ "<reason>" ]

423 (0x1a7)	channel unban [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user|ip> [ "<reason>" ]

424 (0x1a8)	channel ban clear [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <channel>

425	channel motd (alternate topic (?)) [SERVER]

	[NAPSTER]

	Format: <message>

	[The server sends this command when a user joins one of the
	predefined channels.  It seems to send a default message if the
	topic for the channel is the default, otherwise it sends the current
	channel topic.  -ed]

430	invite a user [CLIENT, SERVER]                                                 

	[NAPSTER,SLAVANAP]

	Client: <nick> <channel>                                               
        Server: <nick> <channel> "<topic>" <unknown> <unknown>       
                                                                                
        This command is used by Napster 2.0 BETA 9.6+ to invite a user to
        a channel. The funniest thing about this command is that it is
	supported by Napster clients but not supported by Napster servers ;)
	Napster implementation of this command is a little bit buggy.

        client:                                                                 
                <nick> - nick of invited user                                   
                <channel> - channel user <nick> was invited to                  
        server:                                                                 
                <nick> - nick of user who was inviting                          
                <channel> - channel                                             
                <topic> - channel's topic                                       
                <unknown> - ??? ("0" works fine)                          
                                                                                
        When user receives 430 message user should reply with 431 or 432
	and, if invitation accepted, user should join channel with 400.
                                                                                
        Client example:                                                         
                                                                                
        CyberAlien2 #test_channel                                               
                                                                                
        Server  example:                                                        
                                                                                
        CyberAlien3 #test_channel "Welcome to the #test_channel." 0 0      
                                                                                
431	invitation accepted [CLIENT]                                                    

	[NAPSTER,SLAVANAP]

	Format: <user> <channel>                                                        
                                                                                
        <user> - user who was inviting                                          
                                                                                
432	invitation declined [CLIENT]

	[NAPSTER,SLAVANAP]

        Format: copy of command received in 430 message works fine.

500 (0x1f4)	alternate download request [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>"

	requests that <nick> make an outgoing connection to the requesters
	client and send <filename>.  this message is for use when the
	person sharing the file can only make an outgoing tcp connection
	because of firewalls blocking incoming messages.  this message should
	be used to request files from users who have specified their data
	port as 0 in their login message

501 (0x1f5)	alternate download ack [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> <ip> <port> "<filename>" <md5> <speed>

	this message is sent to the uploader when their data port is set to
	0 to indicate they are behind a firewall and need to push all data
	outware.  the uploader is responsible for connecting to the
	downloader to transfer the file.

600 (0x258)	request user's link speed [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick>

601 (0x259)	link speed response [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> <linespeed>

602 (0x25a)	??? [CLIENT]

	[NAPSTER]

	<?>

	server returns a 404 with "*gulp* Drink milk, it does a body good!"

603 (0x25b)	whois request [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick>

604 (0x25c)	whois response [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<user-level>" <time> "<channels>" "<status>" <shared>
	<downloads> <uploads> <link-type> "<client-info>" [ <total downloads>
	<total_uploads> <ip> <connecting port> <data port> <email> [<server>]]

	<user-level> is one of "User", "Moderator", "Admin" or "Elite"
	<time> is seconds this user has been connected
	<channels> is the list of channels the client is a member of, each
		separated by a space (ASCII 32)
	<status> is one of "Active", "Inactive" (offline) or "Remote" (on a
		different server)
	<shared> is number of files user has available for download
	<downloads> is the current number of downloads in progress
	<uploads> is the current number of uploads in progress
	<link-type> see 0x02 (client login) above
	<client-info> see 0x02 (client login) above

	The following fields are displayed for user level moderator and
	above:

	<total uploads>
	<total downloads>
	<ip>			note: can be "unavailable"
	<connecting port>
	<data port>
	<email>			note: can be unavailable
	<server> used only by SlavaNap and opennap servers. It shows
		which server client is connected to.

	Example:

	lefty "User" 1203 "80's " "Active" 0 0 0 3 "nap v0.8"

605 (0x25d)	whowas response [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user> <level> <last-seen>

	if the user listed in a 603 request is not currently online, the
	server sends this message.

	<user> is the user for which information was requested
	<level> is the user's last known userlevel (user/mod/admin)
	<last-seen> is the last time at which this user was seen, measured
		as seconds since 12:00am on January 1, 1970 (UNIX time_t).

606 (0x25e)	change user level [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> <level>

	changes the privileges for <nick> to <level>.  client must be admin
	level to execute this request

	[I have not verified this message since I don't have admin status
	on any of Napster servers.  -ed]

607 (0x25f)	upload request [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>" <speed>

	this message is used to notify the client that user <nick> has
	requested upload of <filename>

	Example:

	lefty "generic band - generic song.mp3" 7

608 (0x260)	accept upload request [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>"

	client is notifying server that upload of <filename> to <nick> is
	accepted, and that the requesting client may begin download

	Example:

	lefty "generic band - generic song.mp3"

609 (0x261)     accept failed [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

        <nick> "<filename>"

	This message is sent by the server when the client that the file was
	requested from does not accept the upload request.

	This message also used by AudioGnome to notify other user that upload
	or download was canceled.

610 (0x262)	kill (disconnect) a user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> [ "<reason>" ]

	client request to disconnect a user.

611 (0x263)	nuke a user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick>

	client request to delete account for <nick>

612 (0x264)	ban user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick | ip> [ "<reason>" [<timeout>]]

	client request to place a ban on either a specific nickname or
	an ip address. <timeout> is ban timeout in seconds.

613 (0x265)	set data port for user [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <user> <port>
	server: <port>

	This command is used by administrators to request that another
	client set the port used for data transfers to <port>.  The server
	sends a message with the requested port number to the target
	client.  NOTE: the target client can change its port number to
	whatever it wishes using the 703 command.

614 (0x266)	unban user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <nick | ip> [ "<reason>" ]

615 (0x267)	show bans for server [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: (empty)

	client requests the list of banned ips for the current server

616 (0x268)	(ip?) ban list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <ip> <nick> "<reason>" <time> <n>

	<ip> is the string version of the ip banned
	<nick> is the user setting the ban
	<reason> is the reason given
	<time> is the time_t when the ban was set
	<n> is ???.  value is either 0 or 1

	This message is sent in response to the 615 client request, one
	for each ban.  The list is terminated with a 0 length 615 message
	from the server.

	Example:
	
	207.172.245. valkyrie "DoS exploit" 947304224 0

617 (0x269)	list channels [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: (empty)

	client requests a list of channels on the server.  server responds
	with 618/617

	server indicates end of channel list using this message.

618 (0x26a)	channel list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <channel-name> <number-of-users> <topic>

	this is the server response to a 617 client request, one for each
	channel.

	Example:

	Help 50 OpenNap help channel

619 (0x26b)	queue limit [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <nick> "<filename>" <n>

	a client may limit the number of downloads from a particular client.
	once the limit for a particular user has been reached, the uploading
	client can send this message to notify the downloader that they
	have hit the limit and can't have any more simultaneous downloads.
	<nick> is the user who hit the limit, <filename> is the file they
	were trying to download when they hit the limit, and <n> is the
	number of simultaneous downloads allowed.

	Example:

	joebob "C:\MP3\Generic Band - Generic Song.mp3" 3

620 (0x26c)	queue limit [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>" <filesize> <digit>

	This message is sent by the server in response to the 619 client
	request, when one user needs to notify another that they have
	reached the maximum allowed simultaneous downloads.  When the server
	recieves the 619 request from the uploading client, it sends the 620
	message to the downloading client.  The only difference in format is
	the addition of the <nick> field in the 620 message which specifies
	the username of the uploading agent which is notifying the
	downloader that the queue is full.

	Example:

	joebob "C:\MP3\Generic Band - Generic Song.mp3" 1234567 3

621 (0x26d)	message of the day [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <text>

	Server: each 621 message contains a single line of text.
		OpenNap and SlavaNap servers send string
		"VERSION opennap 0.41" or "VERSION SlavaNap 1.1.3"
		among other MOTD strings. This might be used to
		detect server version.

	Client: client sends a 621 command with no data to request the
		motd be sent.  The server will usually send this
		automatically after a user logs in, so this command
		allows a user to reread it upon	request.

622 (0x26e)	muzzle a user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> [ "<reason>" ]

	client requests that <nick> not be allowed to send public messages

623 (0x26f)	unmuzzle a user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> [ "<reason>" ]

	client requests that the enforced silence on <nick> be lifted

624 (0x270)	un-nuke a user [CLIENT]

	[NAPSTER]

	<user>

625 (0x271)	change user's linespeed [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user> <speed>

626 (0x272)	data port error [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]