| Summary: | Virtual users | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | Oswald Buddenhagen <ossi> |
| Component: | general | Assignee: | Konversation Developers <konversation-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | hein |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Oswald Buddenhagen
2010-04-10 17:05:59 UTC
Just dumping from the surrounding IRC discussion: [17:03] <Sho_> ossi: It's a pretty complex request though, it requires a persistent way to attach data (like an alias) to a virtual user object, an extensible facility to match people encountered on IRC against those virtual users (e.g. "hostmask matches this regex" or "nickserv tells us this about user") to be able to retrieve the data, server/network sniffing because nickserv is anything but standardized and its API differs considerably from network to network, implementatons [17:03] <Sho_> for different networks, good network transmission queue scheduling to deal with the huge amount of traffic caused by asking nickserv for that much stuff, lots of state tracking for the communication with nickserv and a way to deal with the latency issue of the data not being available immediately (e.g. buffering or retrofitting logs) [17:04] <Sho_> ossi: konversation has all of the above to some degree, but not quite to the level that it would make your request trivial, and even the best possible implementation will most likely be brittle given the realities of IRC |