projects / irc.git / blame
| 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="003861.html"> | |
| 11 | <LINK REL="Next" HREF="003863.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] Suggestion</H1> | |
| 15 | <B>Ali Sor</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=" | |
| 17 | TITLE="[IRCServices] Suggestion">alisor at softhome.net | |
| 18 | </A><BR> | |
| 19 | <I>Sun Jun 15 06:38:50 PDT 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="003861.html">[IRCServices] Feature Suggestion | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="003863.html">[IRCServices] Suggestion | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#3862">[ date ]</a> | |
| 27 | <a href="thread.html#3862">[ thread ]</a> | |
| 28 | <a href="subject.html#3862">[ subject ]</a> | |
| 29 | <a href="author.html#3862">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>Hello; | |
| 35 | ------------------ | |
| 36 | First idea is about stealing channels.I know It isnt about services but | |
| 37 | think that if someone can get another users email. He can take his channel | |
| 38 | and nick so services root has to open log files search for that nick and try | |
| 39 | to understand what is going on. | |
| 40 | But how about a services admin command like, | |
| 41 | /chanserv info #XXX detailed | |
| 42 | /nickserv info blabla detailed | |
| 43 | ||
| 44 | then chanserv gives detailed info about channel. The details can be Changing | |
| 45 | founder,changing password with times and nicks. | |
| 46 | nickserv gives changing password and email. And it can be restricted to for | |
| 47 | example last 20 change. | |
| 48 | ||
| 49 | And /cs info #channel all and /ns info nick all commands can be used by | |
| 50 | services operators by this way they can give info to users. | |
| 51 | ||
| 52 | Maybe this all can be done my http easly but how about servers that they | |
| 53 | dont want to use http. | |
| 54 | --------------------- | |
| 55 | And i just want to ask if andrew has plans for official modules (botserv | |
| 56 | loveserv etc...) | |
| 57 | ||
| 58 | Ali | |
| 59 | ||
| 60 | </PRE> | |
| 61 | ||
| 62 | <!--endarticle--> | |
| 63 | <HR> | |
| 64 | <P><UL> | |
| 65 | <!--threads--> | |
| 66 | <LI>Previous message: <A HREF="003861.html">[IRCServices] Feature Suggestion | |
| 67 | </A></li> | |
| 68 | <LI>Next message: <A HREF="003863.html">[IRCServices] Suggestion | |
| 69 | </A></li> | |
| 70 | <LI> <B>Messages sorted by:</B> | |
| 71 | <a href="date.html#3862">[ date ]</a> | |
| 72 | <a href="thread.html#3862">[ thread ]</a> | |
| 73 | <a href="subject.html#3862">[ subject ]</a> | |
| 74 | <a href="author.html#3862">[ author ]</a> | |
| 75 | </LI> | |
| 76 | </UL> | |
| 77 | ||
| 78 | </body></html> |