]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Suggestion | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&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="001619.html"> | |
11 | <LINK REL="Next" HREF="001621.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Suggestion</H1> | |
15 | <B>Imran Ali Rashid</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=" | |
17 | TITLE="[IRCServices] Suggestion">u970042 at giki.edu.pk | |
18 | </A><BR> | |
19 | <I>Sun Mar 18 16:08:00 PST 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001619.html">[IRCServices] Suggestion | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001621.html">[IRCServices] Suggestion | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1620">[ date ]</a> | |
27 | <a href="thread.html#1620">[ thread ]</a> | |
28 | <a href="subject.html#1620">[ subject ]</a> | |
29 | <a href="author.html#1620">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Assuming this is done, a simpler system would be to follow the current | |
35 | dalnet system. | |
36 | ||
37 | 1. Force users to give a valid email address and have an authentication | |
38 | system via that, so that email address is valid. | |
39 | 2. Implement a sendpass command which services admins may use to | |
40 | have services send the password to the users email address. | |
41 | ||
42 | You might find 1 necessary to ensure that they don't give the wrong | |
43 | address to begin with, although this would probably take a very low | |
44 | priority in terms of developement as compared to 2, assuming its | |
45 | even implemented. | |
46 | ||
47 | Point 2 is in the todo list. | |
48 | ||
49 | ----- Original Message ----- | |
50 | From: "Partizanu" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">silvius at expres.ro</A>> | |
51 | To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>> | |
52 | Sent: Sunday, March 18, 2001 6:18 PM | |
53 | Subject: [IRCServices] Suggestion | |
54 | ||
55 | ||
56 | ><i> I think it would be nice to see a "Last modif by" when useing "/msg | |
57 | </I>><i> chanserv access #channel list". | |
58 | </I>><i> | |
59 | </I>><i> And another thing...this is more a question then a suggestion. | |
60 | </I>><i> We have problems with users takeing others nickname password. | |
61 | </I>><i> We enforced the use of an email adress when registering a nickname, but | |
62 | </I>><i> of course, first thing when somebody take a password is to change that | |
63 | </I>><i> address. So we don't have any sure way to check if the new password goes | |
64 | </I>><i> to the right address. | |
65 | </I>><i> | |
66 | </I>><i> And I was thinking...I know it may sound silly...but can we have a | |
67 | </I>><i> duplicate db with emails that can be changed just by services admins? Or | |
68 | </I>><i> any other way to secure this thing? Ideas? Suggestions? Thanx a lot. | |
69 | </I>><i> | |
70 | </I>><i> Partizanu | |
71 | </I>><i> | |
72 | </I>><i> | |
73 | </I>><i> | |
74 | </I>><i> ----------------------------------------------------------- | |
75 | </I>><i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A> | |
76 | </I>><i> with the word UNSUBSCRIBE in the subject of the mail. | |
77 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
78 | </I>><i> | |
79 | </I> | |
80 | ||
81 | ||
82 | </PRE> | |
83 | ||
84 | <!--endarticle--> | |
85 | <HR> | |
86 | <P><UL> | |
87 | <!--threads--> | |
88 | <LI>Previous message: <A HREF="001619.html">[IRCServices] Suggestion | |
89 | </A></li> | |
90 | <LI>Next message: <A HREF="001621.html">[IRCServices] Suggestion | |
91 | </A></li> | |
92 | <LI> <B>Messages sorted by:</B> | |
93 | <a href="date.html#1620">[ date ]</a> | |
94 | <a href="thread.html#1620">[ thread ]</a> | |
95 | <a href="subject.html#1620">[ subject ]</a> | |
96 | <a href="author.html#1620">[ author ]</a> | |
97 | </LI> | |
98 | </UL> | |
99 | ||
100 | </body></html> |