Originally posted by Surlent

---

I pronunce simply the English letters

"A See Em El En" - dunno know the fitting phonetic transcription for that

---

Originally posted by Jesper

---

Hm. Forum feeds are valid, however thread feeds fail because I accidently made the code use the htmlentities function, which translates some characters such as

Originally posted by Gavin

---

Originally posted by Cellar Dweller

---

This sounds like a great idea. Here is some more stuff to consider.

I urge you to reject documents in word processor formats, or any format other that plain text or HTML. I like to read stuff in an my web browser. If the author of a document doesn't make the document availible in plain text or HTML, convert it.

Ticalc.org has a great feature that allows people to view text files inside archives without downloading the whole archive. I wish more rom hacking sites had such a feature. To support such a feature and to prevent people from having to get extra archive software, I think that it would be a good idea to ban archive formats other than ZIP. *cough*RAR*cough* Normally, I would suggest that tar.gz should also be allowed, but in tar.gz archives there is no index, and even getting a list of the files in the archive would require decompressing the entire archive, thus using a lot of CPU time.

Another thing to consider is a Advogato style certification system. At Advogato, users can certify other users as "observer", "apperntice", "journeyer", or "master". The server calculates a final certification for each user by how much trust flows from the site owners, and those that are presumed by the site owner to be masters, through the certifications. Thus, while any user can certify any other user at any level, those who are trusted more have more of an impact on the final certification. SourceForge has a certification system based on the Advogato system.

You may also want to look into adapting GForge, a which is based in the last GPL release of the SourceForge software. It has some features, such as file uploads, project pages, and account management, that would be useful for your proposal. It should not be too hard to adapt because it is written in PHP and most programmers here know PHP. On problem is that it will probably not work on standard web hosts. It requires PostgreSQL instead of MySQL, and may require root access to the server to install.

---

ah, these are very good ideas. Exactly the kind of input i was looking for. I agree that standardized file formats are a must, and i like the text file viewing idea.

That certification system is very interesting. The system i had envisioned was nowhere near as robust as the one used by Advogato, but partially beacuse i was not entirely sure a more complex system was feasible. I will certainly take this into consideration, and if we are unable to aquire the necessary SQL specifications, perhaps we can either find or create a system similar.

Originally posted by knuck

---

Originally posted by MathOnNapkins

---

Tsk tsk, always a negative nancy.

---

It's better to you keep your angst at me out of the board.
Let's just see. That consortium thing has the SAME concept of the HackArchives. And look at the hack archives!
I know that consortium idea for a time and i never really agreed with it. It's lame and impossible to happen.

---

if you weren't so completely incompetant, i might actually give a shit what you think. too bad i don't. isn't that so sad? . now please go away and don't bother the big kids when we're talking business, mmkay?

Originally posted by Vystrix Nexoth

---

I'd love to do the site part, although I need to get MySQL working on my computer, unless you can provide a server running PHP5+SQLite in which case I'm game.

---

, you're help would be invaluable from planning to implimentation. The server i'm not entirely sure about as of right now, although it's not exactly my number 1 concern at the current time. I'd rather muck around and lay some framework before securing domain and space. I think that means as of right now we can use what is best for everyone, then when we find out the situation of the server conform to a standard?



To anyone else that i did not directly respond to but has shown interest in this project:

PHP Coders : As i have stated, right now is the time to build up the site structure and figure out which features we want, and what is the best way to impliment them. The greatest help that you can give me at the current time is feedback.

• What are site features you would like to see?


• What are site features i have listed that won't work?


• anything else that relates to practical application

HTML Designers : This is also going to be a very very big part of the project. The visual presentation of the site. We're going to need some quick test layouts based on the currently available information, but i understand that information may not be a lot. This part of the project will be much easier when we have a concrete list of what will be shown on each page.

The end product site design will probably need to end up as CSS and XHTML 1.0 strict validated in the least, but that's nothing to be concerned with right now. The test site layouts won't need to be in any sort of specialized format at all, simple shoddy HTML coding is accepted, it's all about the visual appearance for now .

thanks a lot everyone for the responses, they are greatly appreciated.

---