auspice and unreal ?

[aquanight]

irc services are by far the most stable services you can find... and there isn't anyone who can defeat that

Well, I've got anope 1.6.2 running on my winxp machine, and I've yet to find something that will cause it to core. Of course, I've yet to see what happens if it links when someone is using one of the service's nick . (@Auspice users: for instant segfault, link services while a normal user is using the nick of a BotServ bot. "PANIC! Buffer = NICK <blah>" "Received SQUIT from <blah> (Services terminating: segmentation fault)" Hint: I am not responsible for any damages that might occur. You have been warned. This may occur if you use a plain service name too (NickServ/ChanServ/etc) This might not always work.) Of course, that's why you have SQLINEs but your opers can still raise some heck.

[tabrisnet]

Otoh, it can be fixed too.

I personally am patching it and coding some minor features for it.

I also hope to have a new services package, similar in features to Auspice but much more stable, done in a couple months to a year.

If anybody wants the patchsets for Auspice 2.8.1, email me and I'll make up a distributable patchset.

--
tabris
owner irc.surrealchat.net

[w00t]

I just want to know why people use Auspice 2.8.1[uIRC.Net]

For chrissakes people, it was last worked on in '99-'00. It is buggy as hell.
Sure, it has nice features. I'll be the first to admit that. But it has serious security problems, and lots and lots of crashbugs.

Personally, I want to know what happened to In Mean...

[tabrisnet]

Inmean is around. you can find him on irc.uirc.net

the services running on that network is Auspice 3.0. Unfortunately his plans for when he will release it is unknown, and I hear he's NOT putting it under a free license like GPL or BSD. some bs about 'security'.

I haven't talked to him since December or so.

As to why to use it... it's not an all bad question. But I think my first question is, who else has services like it, that WORKS?

Not everybody likes Anope or IRCServices featureset. I personally hate the nick behaviour (in re identifying to multiple registered nicks, and requiring you to link all nicks together or have an auto-identify script). Tho I do understand at least part of why.

The real problem is a lot of schroedinbugs coming from not zeroing free'd pointers, unitialized [global] variables, etc. In the end it ends up with timers that don't work (which is why nickserv protect doesn't work lately), and fandango on core.

I won't say I love it. But, I don't want anope either. nor IRCservices. and i've used both (Anope extensively)

--
tabris
owner/netadmin irc.SurrealChat.net
technician irc.webchatting.com

[w00t]

My idea is that I like the features of Auspice, (and bits and pieces of Anope and ircservices) as well as the stability of ircservices.

My solution? To write my own services. At the moment, they are for windows only. With the advent of Mono, they'll go *nix too. Written in VB6, aquanight is (Unless he's chickened out) planning on helping me write them, and then port to vb.net.

So far they are going fairly well, the main problem I am currently encountering is how to keep EASY track of who is in a channel, and remove them from that channel on recieve of a QUIT without looping through the occupants of each channel, seeing if they match, and removing them. That is WAY too time consuming...

As for Auspice 3 not being GPL, what [removed] fodder is that. I thought decent of that man... Ah well, guess I'll stick to what I thought and stay clear of Auspice. I notice he didnt post anything on sf.net/projects/auspice about him still being around

I actually went looking for him once, but didnt find him. Just a bunch of bad english speakers

[tabrisnet]

Well, he doesn't speak good english himself (he's Cambodian, as his ircnetwork irc.uirc.net is)

If you had written your services in C, i'd jump on it. as it is, I have no plans on getting Mono.

solution to your channel problem.. hmm. well, we're trying SQL.

tho why not store the channels that a user is in in a linked list (u->chans)? the data duplication shouldn't be too expensive. and it needn't even be like that. instead, you have the channels which have a linked list of pointers to user structures. or just have ch->nick, and to find the user structure, you have a find_user(ch->nick)?

This is largely offtopic, and if you want to, you can take this to email with me, or come to irc.surrealchat.net and look for me.

[aquanight]

Written in VB6, aquanight is (Unless he's chickened out) planning on helping me write them, and then port to vb.net.

It would help if your netronet server thingy had a working DNS... * Unable to resolve server.

Other than that, no I haven't chickend out. I just haven't been able to connect to your network...

[w00t]

Yes *moan* we've been having some troubles. Try irc.netronet.com, that is our current pooling DNS. (.org was an individual server that is having SEVERE difficulties...)

We're changing stuff round, but .com should stay stable.

[Jason]

So far they are going fairly well, the main problem I am currently encountering is how to keep EASY track of who is in a channel, and remove them from that channel on recieve of a QUIT without looping through the occupants of each channel, seeing if they match, and removing them. That is WAY too time consuming...

If you want you can email me your code. I will see if I can figure something out. Im pretty good with VB6, or even if I only get your code on how you are storing the users in a channel. I may be able to find a way to remove a user from it without too much processing. Or I may be able to reccommend a better storage system. Anyhow, if you need any help, I'm very open to helping!

(I PMed you my Email Address)

[aquanight]

If you want the latest status of the code me and w00t have got, you can just hit the SF CVS servers... project name is 'winse' .

[w00t]

Yay for ancient topic. From memory, aquanight was overhauling the data structures and things. I'm busy doing... I dont really know at the moment (only 4 hrs sleep last night [!])

We certainly welcome any input, just keep in mind that these are still early times at the moment (the API is going all over the place, and we havent ported to .NET yet)