Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seenserv #20

Closed
kaniini opened this issue Jun 28, 2012 · 9 comments
Closed

seenserv #20

kaniini opened this issue Jun 28, 2012 · 9 comments
Milestone

Comments

@kaniini
Copy link
Contributor

kaniini commented Jun 28, 2012

implement a seenserv for atheme -- should be pretty simple to do.

use a patricia tree to index seenserv db entries by nickname and prune them occasionally based on time. other ideas: hook into WHOWAS command...

@HelixSpiral
Copy link

What exactly do you mean by seenserv? Couldn't you just use the nickserv 'last seen' time?

@kaniini
Copy link
Contributor Author

kaniini commented Jun 29, 2012

seenserv is a hybserv service that is basically a giant whowas database. nickserv 'last seen' times are associated only with registered nicknames, running atheme without an authentication service (e.g. without nickserv) is an entirely valid configuration.

@hackthecode
Copy link

SeenServ is very popular service among ordinary users. With it, users can search for information about other
users, such as when recently logged in IRC whether nickname is registered or not.
Also can use seen as a nickname and the host and to earn example last five matches.

@Arkadietz
Copy link

Awesome... This is such a good idea! Make it real pls :)

@PVasileff
Copy link
Contributor

I have a very good suggestion, in case you decide to add Seen / SeenServ atheme as a service. In one network I found very interesting Seenserv that can seen and host to ask him the number of results to show. I know this is a lot of code, but I think it would be a big plus for atheme services. Here to HELP Seenserv that I mentioned above:

(14:01:32) Vasilev: help
(14:01:32) SeenServ: Syntax: SEEN [nickname][[!]ident@hostmask] [d(NUM)] [s(NUM)] [+|-]

(14:01:33) SeenServ: [nickname] - nickname to query for
(14:01:33) SeenServ: [ident] - ident(also known as username) to query for
(14:01:33) SeenServ: [hostmask>] - hostmask(ip address or hostname) to query for
(14:01:33) SeenServ: [d(NUM)] - specifies (up to) how many results to return, valid values are 1-5, default is 1
(14:01:33) SeenServ: [s(NUM)] - specifies results offset to help you search for more than 5 matches, default is 0
(14:01:33) SeenServ: [+|-] - search for identified(+) or not identified(-) to services users only
(14:01:33) SeenServ: IRC-style wild chars '*' and '?' can be used for nickname, ident and/or hostmask.

@moontaker
Copy link

Sounds great. I say => go for it!

@jdhore
Copy link
Member

jdhore commented Nov 8, 2012

@PVasileff We'd likely support many options. We've implemented similar fine-grained searching options for ALIS, so implementing them for SeenServ shouldn't be too difficult (assuming we decide to implement SeenServ).

@jillest
Copy link
Contributor

jillest commented Nov 12, 2012

Given that most users are invisible (+i), searching by ident or host will be rather useless (as in /who). Therefore, seenserv cannot do much more than search by exact nick -- a slightly different version of /whowas.

@kaniini
Copy link
Contributor Author

kaniini commented Nov 25, 2012

I am unconvinced that we actually need this given that there is now a protocol module to enhance the last-seen information in nickserv. "Oh, but what about unregistered nicks?" Perhaps they should register. Don't know what to tell them, honestly.

We'll accept a patch adding SeenServ if someone brings one forward and it is sufficiently efficient.

@kaniini kaniini closed this as completed Nov 25, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants