multi-chat-enduser-chat Mailing List for multiple access chat server
Status: Inactive
Brought to you by:
ttlanhil
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
(6) |
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Adam I. <OZ_...@au...> - 2004-09-09 20:20:09
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 well, it's finally happened, I have nick changes and non-member logins=20 working (mostly)! that's two of the three remaining critical features (the= =20 other being able to join and leave different rooms) things like norobot aren't working yet, but there are methods for removing= =20 people, so it's not too bad for this stage of development. at this stage it's getting more important for me to get feedback, as well a= s=20 testing. offers of help are appreciated Adam =2D --- bash: cd: /dev/mouse: No such file or directory. Should I `killall -5 cat` = ?=20 (y or n) http://counter.li.org registered linux user number 345171 http://counter.li.org registered linux box number 237153 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFBQLrvam7MwmW4OTwRAltyAJ9xI5sjALFKVO7JmXUJ/NU5rZqLVACfUJOw MgQgSm+4CXyMljYViKreoyc=3D =3D4kXF =2D----END PGP SIGNATURE----- |
From: Adam I. <OZ_...@au...> - 2004-05-15 00:18:41
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a big event... I've got the telnet login working! okay, so that in itself isn't too interesting, because very few people woul= d=20 use telnet. but it will be the basis of the interfaces for IRC and the IMs= =20 and others, and the core is now able to deal with multiple interfaces at=20 once (previously if you wanted to use a web browser then no other=20 interfaces should be loaded) now, don't get too excited yet, getting IRC working will be a lot more=20 complicated than getting telnet, so it's still a while off... but it is=20 getting closer. the other new thing is the /broadcast command, allowing someone of=20 sufficient level to send a message to all rooms, and an update of the=20 commands to stop the server and restart it to take advantage of /broadcast also, since I'm running it off of my laptop nowadays, it's a lot faster. I= =20 rarely notice the time it takes to load the next page, however people=20 connecting over the net will get a little lag, I'm only on dial-up after=20 all... however that lag might be about as much as you get at alamak anyway. the server is needing more and more testing as well, though it needs people= =20 poking around, looking for problems, all the basic things should have been= =20 noticed (and fixed) suggestions are always welcome as well till the next one, Adam =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFApWFcam7MwmW4OTwRAv/aAKCftavFhm2nDcFsK9w5bwAztlVRYACfSH9M UHAYBZN6wNrcGgjEh9tp8ik=3D =3DIMTt =2D----END PGP SIGNATURE----- |
From: Adam I. <OZ_...@au...> - 2004-04-25 01:18:10
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 as you may well have noticed, there hasn't been an update from me for a=20 while... mostly because I haven't done much, what with uni and all. well,=20 since I've had some time over my mid-semester break when not working on all= =20 the homework I got, I've managed to get more done. it's mostly cleaning up= =20 some errors, including a problem that could enable an attacker to crash the= =20 server (yes, it's fixed, don't worry, and more testing for this sort of=20 thing will happen before the server officially opens) there is some added functionality as well though, one of the areas is the=20 mail interface, it should be a lot easier to use the hyper-linked version=20 now (as in clicking with mouse, the command line version (such as "/mail=20 list in-box" still works the same)) though more than just the interface has= =20 been improved, thanks to some consultation with Gaidheil, we now have Next= =20 and Previous for navigating through the messages in each folder, still no=20 sending, but it'll come eventually. the other thing that'll be noticed that's been improved on is the word-mods= =20 and line-mods (like //bo in alamak) with alamak, once you have a //bo for the line, you can't turn bold off, an= d=20 the same for words. I've now fixed it so that you can toggle bold, italic,= =20 etc on and off throughout a word or line. links have also been added to each command in the list /commands=20 (think /help in alamak, but my /help will actually give you help) there's also a grabber for /? or --help or -h or mixes thereof as a first=20 parameter of a command, to give you the help on that command instead (eg=20 `/example -h' gives the usage and long help for the command /example) this= =20 is done before the command is invoked, so this will work for every command= =20 (and be up-to-date, like all the command-help, it's automatically=20 generated, so it'll be as new as the commands themselves, unlike alamak) from now on I'll try to get some done now and then during uni time, but no= =20 promises, this is lower priority. if anyone has any suggestions, as always, send 'em my way. might have=20 already considered it, but I might not have, and you might help me make it= =20 better. till the next one, Adam =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAixG9am7MwmW4OTwRAr4xAJ97bFiZiXE1ZZ6YaeyvhB/q9S7n7wCfRL64 4IkoaWwPBYqFU4BdpF9kK74=3D =3D30jl =2D----END PGP SIGNATURE----- |
From: Adam I. <OZ_...@au...> - 2004-02-05 20:11:44
|
okay, it seems that some people didn't get this email when I sent it a few days ago, so I'll send it again. no changes have been made since I wrote it apart from an append to the subject and this intro explanation. I've got great news, bad news, and great news. first the background. any of you who I've previously shown the server to have all noticed the same thing: it's slow, very slow. I told some of you that I intend to get some other software working that would improve the speed, and a week or so ago I finally got around to installing it, and the speed up for scripts was incredible, instead of 4 seconds loading time, it can be as low as half a second. now the bad news. because this meant changes to the interface code, I've been having a lot of trouble adapting the existing code, it was all able to work fine after minor tweaks, all except for one thing, communication with the server itself (which you'll agree is rather vital). I won't go into the details, though if people are curious I can explain. but finally today I believe I've hit a solution. so it's back to great news again, I have it running, and it's fast. because of the details of the improvement, I won't be certain it's fixed until it's been tested more, but it seems okay so far. at some stage I'll also have to make sure that these changes are backwards compatible with the old method, but I doubt there'll be a problem there. so now the web interface will run up to 10x faster, and after a week or two trying to get this to work, I can back to coding the interesting parts. if people are interested in the details of any of this, or other parts, just ask. any ideas, questions, comments, suggestions, etc, are (as always) welcome to this list or to me. till the next one, Adam |
From: Adam I. <OZ_...@au...> - 2004-02-04 09:02:42
|
I've got great news, bad news, and great news. first the background. any of you who I've previously shown the server to have all noticed the same thing: it's slow, very slow. I told some of you that I intend to get some other software working that would improve the speed, and a week or so ago I finally got around to installing it, and the speed up for scripts was incredible, instead of 4 seconds loading time, it can be as low as half a second. now the bad news. because this meant changes to the interface code, I've been having a lot of trouble adapting the existing code, it was all able to work fine after minor tweaks, all except for one thing, communication with the server itself (which you'll agree is rather vital). I won't go into the details, though if people are curious I can explain. but finally today I believe I've hit a solution. so it's back to great news again, I have it running, and it's fast. because of the details of the improvement, I won't be certain it's fixed until it's been tested more, but it seems okay so far. at some stage I'll also have to make sure that these changes are backwards compatible with the old method, but I doubt there'll be a problem there. so now the web interface will run up to 10x faster, and after a week or two trying to get this to work, I can back to coding the interesting parts. if people are interested in the details of any of this, or other parts, just ask. any ideas, questions, comments, suggestions, etc, are (as always) welcome to this list or to me. till the next one, Adam |
From: Adam I. <OZ_...@au...> - 2004-01-13 15:33:02
|
well, it's time for another status update, for all you lucky subscribers! I've got most of the data flushing working better, though there's still work to do on that, which means now I can set up /kill and /kline (think kick and ban from alamak)... in fact, /kill and /unkill are now working, though they're not quite finished, they are close. there's also been added logging to a bunch of commands (like the ban logs in alamak, but with other types as well), and soon there'll be commands to read this. other than that, it's been mostly little fixes, bug hunting, etc, so far, though the work with /kill means that most of the work for /kline is already in place, just needs to be adapted. any questions, comments, suggestions, requests, etc, feel free to post to this list (please do, in fact, that's what it's here for) till the next one Adam |
From: Adam I. <OZ_...@au...> - 2003-12-27 16:02:03
|
well, it's been a fair while, and stuff has been done, so it's time for another update. /msg is working again (thanks to a safeguard around the error so it can't crop up from other commands as easily) I have call channels (think /callcomm on alamak) and bulletin boards (read/ post on alamak) though I have it built so that all it takes to add another board or call channel is an entry in the database. the change does mean you need to specify the call channel or BB name, but that shouldn't be too big a price to pay to have multiple boards/channels. logging now also works(though since there's not much that issues any logs, not a lot is received, but it does work) and a country guesser has been added to comm /id some new blocking commands are also available, noips, noproxy, nologin, blacklist, etc etc, though since there's still only op login many of these won't be used much yet either deop/restore have been added, as well as /zlev and /zcheck an autoleveler script has been added (to levelup those who are due) as well as numerous other additions/improvements. the main things still to be worked on are /mail (I plan to try to finish this soon) /nick (a lot of the problems with nick changing and following should be worked out now, so it's just a matter of spending the time getting the rest and adding all that's needed), /join (currently there's only the one room, again it's the need for some more work), support for other protocols (IRC, instant messengers, telnet, ssh, etc etc), the application script (it works, but it limits all form entries to one word per, which is a problem I need to investigate), and user data flushing (forget info about people who quit or are /kill-ed, once this is working the /kill and /kline commands should have all they need to be added easily), as well as a number of other things. so as you can see, progress is being made but there's still plenty to do. any questions, requests, suggestions, chat about the server, or whatever else is welcome (this list is for all of you to use, afterall). till the next one Adam |
From: Adam I. <OZ_...@au...> - 2003-12-07 20:46:37
|
well, it's been a while since any activity on this list, so you're due for me to try to start up the conversations again 8^) I've been a little busy and/or distracted with other things, so I haven't been working on it much, but I have added another command and fixed a bug today, so there's progress again, and I'll be trying to get more done again now. I'm still looking for ideas for new features and commands, as well as people to help out with the project, so speak up any time. And once again, this list is for all of you to use, email the list and everyone sees it, you can discuss ideas and all without needing my input on it. Till the next time Adam. |
From: Adam I. <OZ_...@au...> - 2003-09-28 17:56:08
|
On Mon, 29 Sep 2003 03:03, Adam Ingerman wrote: > some intro info is ready in regards to room-ops, kick, ban, etc. > > kick/ban/mute/clear/hush/voice/et al are all room-based. that means whoever > is in the room can deal with it, and it doesn't go higher > for server-wide issues like flooding, harassment, advertising, nicks, and > anything else that's important or wide-ranging enough to need to be dealt > with at the server level, there's /kill and /kline > a full list of modes should be in the commands.txt sent out a while back > (you should be able to find it in the mailing list archives) > > please have a look over the file, and reply with any ideas, queries, > questions, thoughts, whatever you may have. the usual drill. > > trying to decide how to do room-ops was one of the things still holding up > the works (changing rooms and changing nicks are also still to come), so > hopefully I can push forwards some more now > > till the next thrilling installment > Adam well, the next installment came a lot sooner than I thought it would... I forgot to attach the file. silly me. okay, sending the file, take two. -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Sandy C. <sho...@ho...> - 2003-09-21 01:18:09
|
Adam, Everything seems ok to me......I don't really understand all the computer talk but you know better than I do about that.....You seem to have everything well thought out and are very determined to get it done.....I am excited about it and can't wait to see all the neat things you have put together.... Take care and I will talk to you later... shortgal >From: Adam Ingerman <OZ_...@au...> >Reply-To: mul...@li... >To: mul...@li... >Subject: [Multi-chat-enduser-chat] Re: chat mail >Date: Wed, 17 Sep 2003 22:39:32 +0930 > >On Wed, 17 Sep 2003 20:27, Druss wrote: > > Adam, > > To be honest I cant think of anything that Alamak doesnt already have in > > its cmail that is needed. Having folders would be good, as you could >move > > important stuff like addresses and phone numbers to a folder instead of > > deleting them. Just make sure your cmail has an option to delete >specific > > cmails. Alamak has that /mail - command which deletes all your cmails >when > > you really only want to delete a couple from the list. > > > > Thanks, > > Druss. > >with alamak, you can '/mail - 6' to delete cmail number 6, so it is there. >it's just like so many other things on alamak, not well known, lack of >documentation and information and such. > >what I'll be aiming for from the start will be for it to be ready to >include >real email, which means I'll want to be able to have folders, filters >(emails >from this person go to this folder, emails from this domain go to trash, >that >sort of thing), searching your mail, hopefully at a later stage some email >security/encryption/signing, possibly spell check and attachments. > >later on I will also have an interface (possibly somewhat like hotmail or >yahoo mail) so that you don't have to log into the chat to do mail, though >stuff like that isn't a high priority yet. >but being able to do all those real email things means I'll have the >features >and have to prepare for them now, to save having to make radical changes if >I >hadn't considered it > >depending on how viable it is, I may have some more advanced features such >as >message threading, pop mail, etc, at a later date, I'll have to look into >it. > >having a dual mail system, email and cmail will make it a bit more >complicated >to set up, but my having it designed to work that way from the start saves >major changes at a later date. > >I know I should really have put a bit more info in my plans in the previous >email, so people know what I'm aiming at. > >hopefully I've addressed the issues there, if not, hopefully someone can >prompt me for filling it all in. > >cheers, adam. > >-- >Quidquid latine dictum sit, altum viditur. > >(Whatever is said in Latin sounds profound.) > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Multi-chat-enduser-chat mailing list >Mul...@li... >https://lists.sourceforge.net/lists/listinfo/multi-chat-enduser-chat _________________________________________________________________ Share your photos without swamping your Inbox. Get Hotmail Extra Storage today! http://join.msn.com/?PAGE=features/es |
From: Adam I. <OZ_...@au...> - 2003-09-17 13:10:41
|
On Wed, 17 Sep 2003 20:27, Druss wrote: > Adam, > To be honest I cant think of anything that Alamak doesnt already have in > its cmail that is needed. Having folders would be good, as you could move > important stuff like addresses and phone numbers to a folder instead of > deleting them. Just make sure your cmail has an option to delete specific > cmails. Alamak has that /mail - command which deletes all your cmails when > you really only want to delete a couple from the list. > > Thanks, > Druss. with alamak, you can '/mail - 6' to delete cmail number 6, so it is there. it's just like so many other things on alamak, not well known, lack of documentation and information and such. what I'll be aiming for from the start will be for it to be ready to include real email, which means I'll want to be able to have folders, filters (emails from this person go to this folder, emails from this domain go to trash, that sort of thing), searching your mail, hopefully at a later stage some email security/encryption/signing, possibly spell check and attachments. later on I will also have an interface (possibly somewhat like hotmail or yahoo mail) so that you don't have to log into the chat to do mail, though stuff like that isn't a high priority yet. but being able to do all those real email things means I'll have the features and have to prepare for them now, to save having to make radical changes if I hadn't considered it depending on how viable it is, I may have some more advanced features such as message threading, pop mail, etc, at a later date, I'll have to look into it. having a dual mail system, email and cmail will make it a bit more complicated to set up, but my having it designed to work that way from the start saves major changes at a later date. I know I should really have put a bit more info in my plans in the previous email, so people know what I'm aiming at. hopefully I've addressed the issues there, if not, hopefully someone can prompt me for filling it all in. cheers, adam. -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-09-15 16:08:53
|
today i got notification of new chatmail working. but don't get too excited just yet, so far it's useless. being able to send and receive mails is the next thing on the list. I intend to have a number of options about who can send, filters, folders, etc, but does anyone have any suggestions? I'll start on it tomorrow, most likely, after reading my email, so if anyone does have any ideas, speak up, and you might be able to help make it all work better 8^) cheers adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-09-15 13:58:53
|
On Sun, 14 Sep 2003 15:35, Druss wrote: > Adam, > I've finished reading your Comm page and I have to say that it all seems > well thought out and logical. I see no problems with it, the only problem I > can see from here is getting people to go to your site. Alachat hardly gets > anyone and is technically better than Alamak. How many rooms are you going > to have? > > I guess the proof is in the pudding, so we shall have to wait and see how > it all works in practice. > > Druss. alachat and all others like it are basically alamak clones with a feature or two thrown in. there's no where near enough for it to overcome the lack of people. alamak clones don't deserve to prosper. and I'm not doing anything like that. many of the alamak clones are probably running on modified versions of old stolen alamak code. they don't deserver to even be allowed on the 'net. you can probably tell how little I think of these places I'm doing something completely different. I'll be offering nearly every good feature that I've seen in many different chats, and even different kinds of chats. I'll also be offering some origional stuf fof my own. there will be nothing else out there that has half of what I offer, and it will all by my own code. up until the first official opening, at least. after then I'll open up the development so other coders can get involved. as far as number of rooms, I'll be offering a hybrid between the way alamak works, and how most IRC networks go. I'll go into a bit more detail for those who haven't experienced IRC. I'll also be offering IRC access later on, and at some stage I'll come up with an intro to it. I intend to have heaps mroe information available than anyone needs, that way when something out of the ordinary is needed, it'll be available. but especially docs on being an op, a number on different aspects of comm, etc. as any people who've been to an IRC network much know, there are no public rooms, the way there are on alamak. anyone, member or not, can crate a room, and set a topic. if it seems interesting, then other people will come. if it's not interesting, people leave. when no-one is left, the room is closed. also with IRC, you can be in several rooms at once, most clients capable of this deal with it in a similar way to the 'tabbed browsing' any decent web browser today has (though I hear IE doesn't. but then IE lacks a lot of features that are otherwise common). now for how I'll be doing it. note that as with everything else, this is only a plan, and can be changed. I will have set public rooms. all members will be able to kick people (remember, kick is only remove from the room, not the server) subject to the level checks and whatnot. your room-level* will be based on your server-level*. apart from having room-based kick and ban, these won't operate too differently from the rooms in alamak. I will probably only have a few perm rooms, perhaps two or three meeting places, a comm lounge, I dunno. the so-called private rooms will have their own op list. the people in charge of the room get to decide who is a room-op, and also what they can do. kick/ban, clear, mute, etc. any private room will _not_ be running on a pre-set list of rules. when a private room is made, it will have a default set which are a general guide, but those in charge of the room can remove tham all if they want, and replace them with almost anything else. but the server-wide rules will always override the room rules, in areas of overlap. if you don't like the rules/topic/people/whatever else in a room, there will be plenty of others to join, or if you're a member, create your own. since people can join several rooms at once, it's a lot easier to get people to come to a new room. you can have one window for the room you were in and open another for the new room. it sounds complicated, but is quite easy and makes a lot of sence once you get used to it. (and then you miss it when you don't have it, of course, but that's life 8^) this should help lead to less crowding of rooms, no arguements about topic (join to room for the other topic you want, or make one), less troubles (hopefully) with room kick/bans, since they don't have to be monitored at all in the private rooms. the owner/admin of that room is the highest the issue has to go to. and they can remove anyone from that rooms op list if there's a problem. comm will have to keep a bit of an idea on members /kicking in the designated public rooms, but they'll mostly only need to deal with the /kill and the like (/kill is remove from server, like /kick in alamak), which will probably be used a lot less. one of the main areas where I expect there will be conflict that will be a server-wide issue is peoples nicks, and there will be a /renick command to change it for them, so it's only if they change it back that a /kill will be needed. and lastly, yes, it won't be until it's officially opened up and is sporting many of the features I want to include that we'll actually see if people consider them enough to swap chats. until then I'll keep plodding on and adding stuff, and getting people to test drive it now and then. till the next installment PS I have an apology to make. I had said that hitting 'reply' would send to the list. I had a setting wrong, now fixed. _now_ hitting 'reply' should work as I said footnote: *you'll have several levels at at any one time, though you shouldn't have to worry about them too much. natural level is what you're normally at, as recorded in the op database server level is what level you get when you log on. the changes to natural level are stuff like /lev to drop you if you misbehave, being raised to comm, etc. you'll also have at least one room level (if you're in several rooms at once, one room level for each room, though being in several rooms at once isn't going to be that common for people who chat via a web browser) -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-09-13 13:53:34
|
enclosed is a draft of a document on how comm are chosen, and advancement as comm. please read over it and discuss it, suggest things that could improve it, or question anything that doesn't follow. if you reply to the email address mul...@li... (just hitting reply from your mail client should do this), then your message will be sent to everyone subscribed to this list, and doing so lets people discuss different ideas in the open, without needing to send multiple emails for each person cheers Adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-31 19:58:26
|
well, tonight's coding was on extending something that no-one except a developer is ever likely to see, but it should come in handy for a number of other ideas. I'd like to hear peoples opinions about and discussion of playing streaming music with the chat server. because of the set-up requirements, it wouldn't be something that's put in until the server is pulling in a moderate profit, enough to pay for the costs, but I can start adding support in the code now. getting the software to do this is easy, but it will also require more bandwidth, and a lot of music to play, among other things (like a set up on which songs to play, whether people can request, etc) who thinks that it would be worth the cost and effort to set-up, and who thinks that it just wouldn't be worth the effort? or any other ideas? Adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-30 13:41:24
|
well, last night I got /pref and /settings working /pref saves your settings, while /settings lets you see them (hopefully you'll be able to set multiple settings at once with /settings in the future) so far, the interesting* things I have that www.alamak.com doesn't are: multi-messaging icons and wordmods in fades background images different font settings toggle display of icons (you can `/icons off` so that you see [smile icon] instead of the //smile icon, for example) *interesting doesn't include commands like /time, because stuff like that is useful but not that interesting. as always, any suggestions/requests/queries about features or anything else are welcome, and everything on this list is open to discussion (provided it stays polite enough, of course) so feel free to jump in and chat about anything that strikes your interest (preferably related to the server, but I guess it doesn't all have to be) Adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-26 16:26:30
|
As a follow-up to the levels list posted recently, here's a provisional commands list. many of the commands listed are names for other commands. ie: /man is the same as /commands -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-26 13:31:26
|
On Tue, 26 Aug 2003 22:29, you wrote: > Adam, > I think your levels are reasonably fair.. but making Comm seems really > hard.. What rewards will be there for those who stay with your site but do > not want Comm? Also.. 2 years to make a trial Comm is a long time.. I made > one at Alamak in 5 months.. sometimes the best Comm are not always the ones > who are with the site the longest.. just look at Jeremy. Will that be > flexible? > > Cheers, > Druss. comm will be needed less on this server, but when there is need for comm it won't be too hard for people who deserve it to get there. people who don't want to be comm get the higher levels, but I don't know what commands I can put at senior levels, because if it's available for non-comm it's generally made available reasonably soon. I'll have a provisional commands list out soon though, with levels shown. the level 40 for consideration of comm is not strict, it's a guide, in that people who make that rank should know enough about the server and how it's run. also, I'll have opinion ratings, if people in higher levels notice you doing good, your rating goes up, if you're bad, your rating goes down. at current, a maximum good rating will get you leveling up at twice the speed, while a maximum bad will get you going up at half the speed. this modifier might be altered later on, but it will probably be left in. I'd have a minimum of 6 months learning the chat before you can be comm as a hard limit, but some of that can include before you were an op if need be, or less if you're used to other systems, like alamak, and you only need an orientation course for my server. I'm not sure how often I'd want to rotate comm. on one hand, if they're good, then they could help by being there, if they're not, then you want someone better there soon. I plan to have a public vote on new comm though. something along the lines of: comm discuss possible candidates comm select a number of candidates a higher comm then approves the list of candidates (so you won't get comm selected just on how much they're liked, this seems to happen on alamak a bit) a vote is started, and every member gets to vote while it's open (higher leveled members get a bit more weighting to their vote, not sure how much it will be yet though) the vote is closed and the server calculates the voting. the successful candidate (or two or more if there's enough reason to have several) is then put in a trial position, usually a level or two below the proper rank for that comm. after a while (when comm feel the person is ready) they're put up to the proper rank people who are considered as possible comm candidates are selected like this and put at the pre-comm level. people at pre-comm can then be selected for the lower comm (guide or guardian) people in the lower comm can be selected for teacher or sentinel teachers and sentinels can be selected for gurus and overseers. if there's need (a sudden vacancy or several, or server size increases(esp when starting up)) comm can be selected from lower positions. techs are selected on a completely different scale, based a fair amount on technical ability, planning, etc. admin are like the office staff of alamak, and have final say on any problems that have to go that high bots and services can also be ignored by most people, because most people won't have anything to do with them (except for using the services of a bot while chatting) higher level members will have more grant points (you use a certain number of them when you /give or /grant someone) and have a bit more weight in voting, but I haven't come up with much else that can be reserved for higher level members if anyone does have ideas on what could be put in for higher level ops that doesn't seem unfair to new users, please let me know at some stage I'll have to make up some docs on the jobs of each member class and the committees, grant points, kicking/banning (it's not the same as in alamak), grievance procedure, and all those other things. unless someone else wants to get the basic info from me and work it into an easy-to-read document. (anything that's relevant to someone who just surfed in and hasn't used the Internet much should be easy to read for such a person. docs for higher ranked members and comm can be based on the assumption that they know a reasonable amount about the chat, but it's still got to be easy to read. only the docs for techs will be allowed to be jargon-ed and blunt) any suggestions or queries on any of this or other matters are always welcome Adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-26 04:53:28
|
Enclosed is a proposed level scheme. if anyone has any thoughts, problems, queries, or suggestions, please speak up. -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |
From: Adam I. <OZ_...@au...> - 2003-08-22 19:13:12
|
This is the first posting to enduser-chat This list is for people who use the chat to talk about it, share information, disucuss ideas, etc. Please do not ask questions of developers on this list though, as most developers will probably not read this list. There are other lists for bug reports and feature requests. welcome to the list! ~Adam -- Quidquid latine dictum sit, altum viditur. (Whatever is said in Latin sounds profound.) |