If this were to become a reality, i would hope that it would be hosted on a separate virtual server. Someone might be able to do damage to the internals of PM if they were on the same machine. Also, i don't think that a telnet account would be an option since it would need to be a pretty massive set of servers to hold so many users which might not pay off since someone would need to hire a sysadmin.
If I may humbly suggest using Apache's mod_rewrite (brutal huh?) or mod_redirect, to link www.perlmonks.org/BigJoe to his home node, which may actually contain resume information and links to posted code or offsite code. No need to create UNIX users since we shouldn't have such the massive privilege anyway. Perlmonks would die since folks would be ytalking right and left and code could be saved online in files for everyone to see instead of via this nice GUI. I would consider that a mistake.
AgentM Systems nor Nasca Enterprises nor
Bone::Easy nor Macperl is responsible for the
comments made by
AgentM. Remember, you can build any logical system with NOR.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
