1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] smart expiration system
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20smart%20expiration%20system&In-Reply-To=000901c4b900%24388a9000%24403d05d5%40server">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"004688.html">
11 <LINK REL=
"Next" HREF=
"004690.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] smart expiration system
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20smart%20expiration%20system&In-Reply-To=000901c4b900%24388a9000%24403d05d5%40server"
17 TITLE=
"[IRCServices] smart expiration system">medice at gmx.at
19 <I>Sat Oct
23 10:
39:
00 PDT
2004</I>
21 <LI>Previous message:
<A HREF=
"004688.html">[IRCServices] smart expiration system
23 <LI>Next message:
<A HREF=
"004690.html">[IRCServices] smart expiration system
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4689">[ date ]
</a>
27 <a href=
"thread.html#4689">[ thread ]
</a>
28 <a href=
"subject.html#4689">[ subject ]
</a>
29 <a href=
"author.html#4689">[ author ]
</a>
34 <PRE>Sounds like a good idea, but:
35 i think it's not necessary to have that much categories -
2-
4 should be
37 I think some sort of setable
"category
" is not really useful, since
38 services may calculate the situation by themselfes...
45 ><i> I was thinking about a system of variable time of expiry of Nicknames /
46 </I>><i> Channels depending on the time that is registered.
47 </I>><i> Something like this:
51 </I>><i> (
1) A nickname/chan that is registered for
<12 months:
1*
30+
5 not
52 </I>><i> used days before expire
53 </I>><i> (
2) A nickname/chan that is registered for
>12 months:
2*
30+
5 not
54 </I>><i> used days before expire
55 </I>><i> (
3) A nickname/chan that is registered for
>24 months:
3*
30+
5 not
56 </I>><i> used days before expire
57 </I>><i> (
4) A nickname/chan that is registered for
>36 months:
6*
30+
5 not
58 </I>><i> used days before expire
59 </I>><i> (
5) A nickname/chan that is registered for
>48 months:
8*
30+
5 not
60 </I>><i> used days before expire
61 </I>><i> (
6) A nickname/chan that is registered for
>60 months:
10*
30+
5 not
62 </I>><i> used days before expire
63 </I>><i> (
7) A nickname/chan that is registered for
>72 months:
12*
30+
5 not
64 </I>><i> used days before expire
66 </I>><i> Of course all numbers (months,days) can be modified from the config file..
67 </I>><i> And when a nickname will pass from a category to another a memo will be
68 </I>><i> sent to inform the owner of this nick.
69 </I>><i> Services administrators should be able to see and modify the category
70 </I>><i> for each user.
72 </I>><i> With this method we will avoid problems with Nicknames / Channels that
73 </I>><i> expires because their owners who are
"old
" on a network for some reason
74 </I>><i> could not be identified for long time (for channels noone accessed join
75 </I>><i> for a long time) .
77 </I>><i> This is also something like a
"present
" for the old users.
80 </I>><i> I'm waiting for your opinions :))
90 <LI>Previous message:
<A HREF=
"004688.html">[IRCServices] smart expiration system
92 <LI>Next message:
<A HREF=
"004690.html">[IRCServices] smart expiration system
94 <LI> <B>Messages sorted by:
</B>
95 <a href=
"date.html#4689">[ date ]
</a>
96 <a href=
"thread.html#4689">[ thread ]
</a>
97 <a href=
"subject.html#4689">[ subject ]
</a>
98 <a href=
"author.html#4689">[ author ]
</a>
projects / irc.git / blob