Because people that still wish to use the service for the forum can still take advantage of it. If you want nothing to do with the bot you can ignore it outright.
Because Sheena offers more benefits than that, including (but not limited to): 1. The ability to choose what gets reported to you personally 2. Extended whois information 3. Slightly less fucked title reports 4. Not interfering with the channel text itself Among other things, I imagine, that I can't think of at the moment...
That is something I would've, you know, fixed, if it wasn't immediately rejected. There's no point in fixing something if it won't get used. Then again, now that #reporting has a good number of people, maybe I'll fix it.
I know when we had originally discussed the idea of BetaServ, the idea was that it would move more in the direction of Scarlet—that is, usurp the nick.db for forum-based authentication. I really think a lot of the issue could be solved simply by removing NickServ and making auth the command for nick identification. Moreover, that way, we could assign permissions based on groups rather than having to manually set them for people who don't have registered nicks.
Didn't see this: I wasn't aware that mIRC still beeps on /notice. Yeah that's annoying, and I can make it an option to change it to a PRIVMSG if that's preferred.
If there would be some way to switch from /notice based notification to either in-channel messages only the user would see, or even PM-based (settable by a setting on Sheena) it would also appeal more to me, for notices in general do what has already been mentioned before. If you care what I think, of course... Edit: Looks like Saz just said what I was asking for. Silly simultaneous posting.
Actually, this is a badass idea and I hope we can do something with it. I remember that alexis did with with scarlet now, and I had completely forgotten before—it would certainly make distributing status in #retro much easier to manage. And even in channels outside of #retro, you could simply add a forum nickname to an access list like you would a nickserv name. It's MUCH more convenient, I think.
[20:41] <ScarredSun> Actually, the more I think about this [20:41] <ScarredSun> Wouldn't it make more sense to make BetaServ an Anope module? [20:41] <ScarredSun> That way we wouldn't be ircd-dependent either :X
But with that you lose the ability of having people who aren't on the forum here on the access list, which means people (like me) that would consider bringing a channel over are shunned. Each benefit comes with drawbacks. If you want to keep badnik a primarily Sonic-Retro server with nobody else, then you can ignore me and I'll forget I considered moving.
That's on my TODO list for the service, but it'll come after I port it to a language that's a bit more flexible, such as python or perl, or maybe even C (there's one IRC service based on anope that uses a live database that I could possibly make changes to), as Sheena is currently coded in PHP, and I think an entire replacement for NickServ is really not what PHP was designed for.
I imagine that would quell a number of the complaints. My ultimate preference would be to create a system whereby, optionally, it appears to each user to be a normal message in #retro, but appears based on their customized settings. Of course, that would almost certainly require IRCd modifications, which would nullify the point of making it an anope module.
This CAN be done, and since Badnik uses Inspircd, which is entirely modular, it can be made as a simple module (there already is an m_beta module that handles the changes to WHOIS output that can be modified for such changes).
Well, that sounds like it would basically be awesome then. Only remaining (minor) issue is having to log into IRC services twice (once for nickserv, once for sheena) but it looks like fixing that is already on your todo list, so...
1) Would be nice if it actually remembered your settings between sessions. I've reset it several times now. 4) I like it doing this, actually. It encourages editing. Having said that - PLEASE, yes, make it PRIVMSG rather than notice. If it's privmsg I can make a script to make the text appear in #retro to me as an echo - as notices I can't get the bloody thing to work. =P
