Last modified: 2009-06-29 16:44:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T21424, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19424 - RC IRC feed coming from "I.still.hate.packets"
RC IRC feed coming from "I.still.hate.packets"
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
IRC (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Fred Vassard
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-28 15:23 UTC by Gurch
Modified: 2009-06-29 16:44 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Gurch 2009-06-28 15:23:39 UTC
Whoever reconfigured the IRC feed last time it was reconfigured changed something, which they doubtless thought was purely internal, such that the user the feeds come from is no longer "rc@localhost" but "rc@I.still.hate.packets". Some tools were checking for precisely "rc!~rc@localhost" (I didn't want to accept messages from just anyone as private messages are enabled on irc.wikimedia.org and that would let people screw with others' clients), and so it broke when this was changed, as probably did other things.

While this was a bit stupid of me, and I will change my code to be a bit more flexible in what it accepts, the "I.still.hate.packets" thing should probably be changed, particularly since IRC has line length limits and we already have problems with messages getting cut off at the end; we don't need 10 superfluous characters in there.
Comment 1 Fred Vassard 2009-06-29 04:55:07 UTC
I will tkae care of that as soon as possible. 
For some reason, I.still.hate.packets is the irc server's default.
However that is easy enough to change.
It will be localhost in ten minutes.

--Fred
Comment 2 Fred Vassard 2009-06-29 05:04:13 UTC
All fixed. Well almost. the server is actually "resolving" locahost for 127.0.0.1, but it is closer than the alternative.
Comment 3 Gurch 2009-06-29 16:44:34 UTC
(In reply to comment #2)
> All fixed. Well almost. the server is actually "resolving" locahost for
> 127.0.0.1, but it is closer than the alternative.

Thanks for the quick response. 127.0.0.1 is fine, it makes sense and also same length as "localhost" so no wasted characters.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links