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> FW: [IRCServices] Notice Bug (Update) | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=FW%3A%20%5BIRCServices%5D%20Notice%20Bug%20%28Update%29&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="004847.html"> | |
| 11 | <LINK REL="Next" HREF="004850.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>FW: [IRCServices] Notice Bug (Update)</H1> | |
| 15 | <B>EpicIRC Administration</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=FW%3A%20%5BIRCServices%5D%20Notice%20Bug%20%28Update%29&In-Reply-To=" | |
| 17 | TITLE="FW: [IRCServices] Notice Bug (Update)">admin at epicirc.net | |
| 18 | </A><BR> | |
| 19 | <I>Sun Feb 20 09:33:51 PST 2005</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="004847.html">[IRCServices] Chanserv UNBAN bug? | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="004850.html">[IRCServices] Notice Bug (Update) | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#4849">[ date ]</a> | |
| 27 | <a href="thread.html#4849">[ thread ]</a> | |
| 28 | <a href="subject.html#4849">[ subject ]</a> | |
| 29 | <a href="author.html#4849">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>I have posted regarding this bug on the mIRC Bug Forums. They have verified | |
| 35 | that it is infact happening. We have found a 'semi' solution to the problem | |
| 36 | though, that may would be good for your to add on the faq. | |
| 37 | ||
| 38 | If I send the notice " /OperServ Global <really long noitce>" That is when | |
| 39 | the ":" (colon) will appear. | |
| 40 | ||
| 41 | HOWEVER, if I were to do "/msg OperServ Global <really long notice>" The | |
| 42 | colon does not appear. | |
| 43 | ||
| 44 | So... it seems that when mIRC is pulling the alias for /operserv or | |
| 45 | /chanserv it somehow creates this error. For anyone else out there that may | |
| 46 | ever have this problem, until it is fixed just use /msg operserv to get | |
| 47 | around it. | |
| 48 | ||
| 49 | Darvocet | |
| 50 | EpicIRC.Net - irc.epicirc.net | |
| 51 | ||
| 52 | ||
| 53 | ||
| 54 | _____ | |
| 55 | ||
| 56 | Hello... I have noticed a little error, and I just wanted to post here to | |
| 57 | see if anyone had already posted regarding it, or if it was the first time. | |
| 58 | ||
| 59 | I run an IRC Network with Unreal3.2.2b and ircservices-5.0.41 | |
| 60 | ||
| 61 | When I send a global notice that is fairly long it appears that the | |
| 62 | character ":" shows up in the notice. If I were to just sent a global | |
| 63 | notice as an oper, Unreal would cut the message off before the ":" would | |
| 64 | appear, so this only occurs with services. | |
| 65 | ||
| 66 | I have noticed it in Channel Join Notices, Network Connect Notices, and | |
| 67 | Global Notices. Below is an example: | |
| 68 | ||
| 69 | -------------------------- Sending the notice with OperServ global | |
| 70 | ------------------------- | |
| 71 | ||
| 72 | [11:30pm] -Global- [Network Notice] Our network has been experiencing a | |
| 73 | major increase of unattended bots connecting. We are taking many defensive | |
| 74 | actions to make sure that they do not interrupt the normal activity of the | |
| 75 | network. If you receive a CTCP LAG, please ignore it, as it is our Opers | |
| 76 | running :a scan to detect malicious bots. If you have any questions, please | |
| 77 | join #Help and speak to an Oper. - XanaX, Sr. Network Admin. | |
| 78 | ||
| 79 | ------------------------ Sending the same notice as an oper, and not with | |
| 80 | services ----------------------- | |
| 81 | ||
| 82 | [11:32pm] -XanaX- [Network Notice] Our network has been experiencing a major | |
| 83 | increase of unattended bots connecting. We are taking many defensive actions | |
| 84 | to make sure that they do not interrupt the normal activity of the network. | |
| 85 | If you receive a CTCP LAG, please ignore it, as it is our Opers running a | |
| 86 | scan to detect malicious bots. If you have any questions, please join #Help | |
| 87 | and spe | |
| 88 | .... | |
| 89 | .... | |
| 90 | ||
| 91 | -------------- next part -------------- | |
| 92 | An HTML attachment was scrubbed... | |
| 93 | URL: <A HREF="../attachments/20050220/d96e2975/attachment.htm">../attachments/20050220/d96e2975/attachment.htm</A> | |
| 94 | </PRE> | |
| 95 | ||
| 96 | ||
| 97 | <!--endarticle--> | |
| 98 | <HR> | |
| 99 | <P><UL> | |
| 100 | <!--threads--> | |
| 101 | <LI>Previous message: <A HREF="004847.html">[IRCServices] Chanserv UNBAN bug? | |
| 102 | </A></li> | |
| 103 | <LI>Next message: <A HREF="004850.html">[IRCServices] Notice Bug (Update) | |
| 104 | </A></li> | |
| 105 | <LI> <B>Messages sorted by:</B> | |
| 106 | <a href="date.html#4849">[ date ]</a> | |
| 107 | <a href="thread.html#4849">[ thread ]</a> | |
| 108 | <a href="subject.html#4849">[ subject ]</a> | |
| 109 | <a href="author.html#4849">[ author ]</a> | |
| 110 | </LI> | |
| 111 | </UL> | |
| 112 | ||
| 113 | </body></html> |