]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000557.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000557.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] New services implementations &amp; Updates?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000555.html">
11 <LINK REL="Next" HREF="000558.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] New services implementations &amp; Updates?</H1>
15 <B>Sinan Ku&#351;do&#287;an</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To="
17 TITLE="[IRCServices] New services implementations &amp; Updates?">kusdogan at boun.edu.tr
18 </A><BR>
19 <I>Mon May 29 14:04:16 PDT 2000</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000555.html">[IRCServices] New services implementations &amp; Updates?
22 </A></li>
23 <LI>Next message: <A HREF="000558.html">[IRCServices] New services implementations &amp; Updates?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#557">[ date ]</a>
27 <a href="thread.html#557">[ thread ]</a>
28 <a href="subject.html#557">[ subject ]</a>
29 <a href="author.html#557">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>The idea of using SQL sounds good at first. But these services are generally
35 used by small or medium IRC networks all over the world. Some of them have
36 low configurations and smaller bandwidths. These implementation would need
37 an additional SQL server as Andy pointed out. Also having statistics on web
38 would result to another performance decrease. Security is another point.
39
40 On the other hand i agree to the idea of updating. It can be improved by
41 lots of useful commands. CGI/ASP or PHP3 would give us better results in a
42 less amount of time due to the need of updating all the code for SQL.
43
44 Other advices for current services :
45 - /chanserv ban command would be very useful
46 - /nickserv ridentify nick pass (as identifying for a channel, likely LINK
47 command but only for the active connection, it is necessary when u use
48 another nick and try to use your accesses)
49 - /chanserv set #chan Exitmsg (as entrymsg)
50 - /nickserv chaninfo nick #chan (if user sets chaninfo on for himself) (this
51 command can give the information about nick as the last time he parted the
52 channel)
53
54
55
56 ---------------------------------------------------------------
57 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
58 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
59
60
61 </PRE>
62
63 <!--endarticle-->
64 <HR>
65 <P><UL>
66 <!--threads-->
67 <LI>Previous message: <A HREF="000555.html">[IRCServices] New services implementations &amp; Updates?
68 </A></li>
69 <LI>Next message: <A HREF="000558.html">[IRCServices] New services implementations &amp; Updates?
70 </A></li>
71 <LI> <B>Messages sorted by:</B>
72 <a href="date.html#557">[ date ]</a>
73 <a href="thread.html#557">[ thread ]</a>
74 <a href="subject.html#557">[ subject ]</a>
75 <a href="author.html#557">[ author ]</a>
76 </LI>
77 </UL>
78
79 </body></html>