Deprecated - Drupal core

The first and foremost problem with Distributed Authentication (DA) in Drupal is that there is no findable user or code documentation of it anywhere. A drupal.org search produces virtually no hits. A look through www.drupaldocs.org produces nothing because the functions associated with it are unknown. Looking through the handbook there are no topics concerning it. Some other questions and problems:

Where are the drupalids stored? When are they created? how are conflicts resolved?

Can drupalids be manipulated? ex. can a myname@www.site.com/folder be changed to myname@www.site.com?

What is the criteria for DA to work? There always seems to be a problem with using logins between sites. Like at the moment drupal.org users can use there drupalid on my site but my site users cannot use their drupalid on drupal .org

What modules are responsible for DA. Looking at the drupal module it seems that it is has dependacies that are undocumented. What RSS feeds and modules does DA use?

Is DA effected by SSL? (Topic for another thread but is anyone using SSL and Drupal?)

Spaces in usernames is still a problem. There is no warning message for spaces and there is no default repair or removall of the spacing. The email with a username with a space in it is sent out with a truncated drupalid and link.

Is there a flowchart of the Distrubuted Authenication process somewhere from the time of its development?

When I try to edit a post I get a user error returned as for example which follows, although the post is actually published in edited form:

Hi All,
I've been working on creating a "drupal-lite" with very only the bare minimal modules for creating primary/secondary links and pages. Which modules from the base 4.5.2 distro are necessary and which aren't?

Can we move the uncessary ones out of the v4.6 core and make them separate modules?

Thanks,

Devin.

I am designing out a module installation module. I would like to get some feedback and verify it's design will work with and support drupal modules. Sorry I haven't produced any images to go with this. It is fairly easy to understand.

If installing a module is simply uploading it to the modules directory and optionally running a sql statement then you understand the procedure of this module. Here is the blueprint.

******************************************
Installation Module Design
******************************************

Goal:
To allow admins to install or upgrade modules directly from within the administration panel. No ftp or mysql admin needed.

Reason:
Make it easy and convient to install modules. Make installation and maintence of modules conform to the rest of drupal administration (as in from the panel and independent of extra sometimes unavailable tools).

Overview:
With this module installed (or part of core) the administrator will be able to download modules from drupal that they would like to use on their own sites. To install the module they would navigate to the module > install module page. From there they can upload and install a new module without the use of specialized software.

******************************************
Use Case & Design:
******************************************
You the admin, want to add a new module to your site. You navigate to the Admin > Modules page.

I recall seeing some thread a while back where several folks were discussing the flaws with the password reset functionality. Basically the problem boils down to the fact that you can reset someone's password if you know their user name OR their email address. This clearly is open to abuse by trolls if your site displays user names of people that post there.

Anytime I select "configure" in admin

szAppName : iexplore.exe szAppVer : 6.0.2900.2180 szModName : hungapp
szModVer : 0.0.0.0 offset : 00000000