>From IGnatius T Foobar in email with my answers and comments interspersed > > >*/Let's have this conversation in the Citadel Development room. I like >what you're saying and we should work on it./* > >*/If I understand you correctly, you're talking about the way Citadel >populates a user's vCard based on information loaded from LDAP, and >expressing concern over the difference between doing that at account creation >time vs. at every single login. If that is the case, you're correct, it >should be a configurable behavior./*
Yes, you are correct. I would like to see that as a configuration (I do like the ability to update the information in one place, and have it update automatically) but with the current setup there are a couple problems, and I hope that an overhaul on the configs and way citadel handles things could fix it. (more later relating to user database) > > >*/Also know that the role of the GAB is changing. The original intention >was that you could share that room on a Citadel network and it would drive >the population of a table mapping Internet email addresses to users anywhere >on the network. Well it turns out no one is using it that way, so we're >going to simplify it. I might even make the Internet email table populate >directly from the user table, eliminating that role of the GAB completely (so >it would really be nothing more than a published directory)./* / / I am glad to hear that the GAB is changing. I could put to use the federated model, but would rather see more done in the way of having a hot standby etc. If the GAB could just be a Public Contact Room (with entries being able to be added and removed by the aide without affecting the transmittal of email to users) and have an internal user list which in the case of LDAP polls the server search base for valid users and builds the mail table based on mail: entries, with the first entry being primary, the rest being aliases (you could put the requirement for the citadel.schema to make an alias entry) and have the poll time be configured based on a 1 off command and/or time (so that you could have a system that ONLY polls when the aide presses a button, or polls at the press of a button / command and at a certain default interval). I am sure others have different use cases, but I do not need users editing their own email addresses. I would like to see more control from an aide perspective to locking down certain fields to user edit vs aide edit. If this seems doable, I can express more of my thoughts. / / > > >*/The goal here is to simplify, and I'd like to thank you for defending >Citadel against the harsh criticism it received yesterday. We're focusing >on the use cases that actually exist, and removing a lot of the places where >things can go wrong. But I do have reason to believe that for every person >who posts an installation problem (which often happens because they didn't >read the instructions) there are dozens of others who we don't hear from >because Citadel installed and ran correctly on the very first try./* */ /* I understand. I know that the only times I have really had issues is because we do not "fit" in the "standard" use case and because of my own mistakes (well, there were a couple bugs that dothebart was able to fix as well)... We appreciate Citadel and what you offer to the community. I guess to sum up what I would like to work towards: A more flexible citserver with the ability to have multiple auth schemes available at once (native, plus optional host, plus optional LDAP OR AD) with the ability to poll host or LDAP at login, and at set interval for updates to information. A New and Improved webcit Possible Webmin module for interfacing with Aide functions of citserver. More customizations of information and who can edit it. Also, a "simple" request to be able to edit a draft message through webcit, and to mark all as read without having to use an external client. Also support extended IMAP things like flags (like desktop clients)
