[snoj]

For a while now I've been aware of MySpace.com's many problems and general badness. The reasons for everyone are numerous and vary from person to person. My own reasons involving my sisters, CSS, idiots, XSS, ads coming out the wazoo, weird access limits for non-members, and others I cannot think of right now.

After talking with a friend of mine a couple weeks ago I decided to try and make a clone of MySpace. Why? Well because I think I could come close, to have a place where I know my sisters may be safer, and to have my own answer for all my complaints against MySpace.

This is where you all come in. Though I'm not anywhere near completion of my clone, I thought that I could start a Learning Experience thing to document my, and possibly others, code designs, concepts, etc.

So enough with why, lets get down on how this is all gonna go.

I know I can't stop people from stealing my or others code. I ask that either 1) Don't share your work/algorithms. Or 2) Document everything and make clear the ownership of code that is and isn't yours. I really want this to be fair for everyone and I hope anyone reading this won't abuse other's work for their own gain. Saying that, I'm all for taking code posted here and modifying it to make it better. It's one of the best ways to learn new tricks and get better at programming.

What's the point? Well like I said before, this is partially a documentation for me in my project, and it's also part teaching you what I know about PHP, MySQL, HTML, and Javascript.


----------------------------------------------------------------------------------

Grand list o' sessions:
Session 1: Features (This post)
Session 2: Database Layout

----------------------------------------------------------------------------------

Session 1: Features

The first thing I want to do is list the features I want to have. This way I can the start planning out how the code and database will have to operate and be structured.

Any and all large projects IMHO should start out as a features list. This sums up what you're wanting and helps jog your memory when you start to forget. But also if youi start to include others in your project they'll also know what to expect.

User related features:

• Messaging
  
• Extensive profile data
  
• Photos
  
• Blog
  
• Comments (profile, blog, photo, etc.)
  
• Fake profile data
  
• Groups/Communities
  
• Log in "Remember Me"/"Remember User name/Password"
  
• Friends
  
• Extensive control over profile page CSS
  
• Blocking
  
• White list/Blacklist
  
• bbcode style code
  
• WYSIWYG Editors
  
• Profile searching based on fake profile (possibly unless otherwise stated by user)
  
• Report violations of ToS or Agreement.

Admin features:

• Edit, delete, and approve? new and existing users
  
• Change site looks?
  
• Limit, restrict, stop, allow sign ups.
  
• Log view

Front page:

• New/random user profiles?
  
• News about the site
  
• Log in
  
• About the site
  
• Sign up

Advertisements:

• Base viewership based on locality (such as zip codes), regions (i.e. nations/states), or everyone.
  
• Views
  
• Clicks
  
• Purchase
  
• Other account data

Alright, I think that about does it for my planned features tonight. Next time, a look at ways to structure the database.

[knownasilya]

Ah, this looks like It'l be true fun.

What about live AjaxIM via invite only. http://www.unwieldy.net/ajaxim/

And Flickr image hotspot thingies..the boxes used to describe certain sections of an image with a comment. Using css. http://www.frankmann...s/css-imagemap/ or something along the lines.

[eLliDKraM]

This is one hell of a good idea. nuff said.

[strykerhorse]

agreed with above post...Carpe Idea, man.

[knownasilya]

Are you sarcastic or serious? I think its a great idea, myspace is so poorly layed out and coded..And there are plenty of homo's on there.

[eLliDKraM]

There are plenty of homosexuals everywhere and I don't think going on an anti-homo rant would set a great mood for hotsnoj's learning experience. I don't think the entire purpose is to make a non-failure Mypsace because we all believe it sucks but that it is, hence the topic, a truly valuable learning experience as well as being able to provide a less buggy alternative to Myspace for those who enjoy it. Its poor layout is too subjective and I'll be inclined to disagree and its constant database and CSS issues are the only downside to it.

[knownasilya]

Well i had to throw in something fun into my rant. And yeh, mysql and css errors like mad. And poor skinning options, and no skin choices.

[snoj]

Session 2: Database Layout

[R3PL1C4]

Great Idea

[gayatri]

why not cms??
if planning to clone, myspace.com
i mean with whatever features u mentioned, why don't u use a good cms??
it will cover max features, with least efforts
just a thought!

[snoj]

Well the point isn't to use a CMS to solve all our little problems. CMS's can't solve all our problems. Don't rely on them.

Anyway, the two main points of this project are 1) Something to help others with concepts related to database layout, website user security, good programming, etc. In other words a long tutorial like thing that has a real end result. And 2) something that I can put on my resume.

[gayatri]

i am using drupal (drupal.org), i found it very useful and well secured even
hmm, if wanna add to resume,
u shud go for brand new concepts, rather taking skins and adding data

[snoj]

That's awesome, I'm glad you've found a CMS that fits your needs. However, how do you think the makers of drupal made it? They did so by learning the basics of the concepts I hope to teach. They didn't just take another CMS, rip it's guts out and put them back in a new order without knowing this stuff.

Now, if you have anymore problems with me or this learning experience, please either start a new topic someplace so everyone can have their say or get ahold of me via PM or email.


But back on topic. Has anyone any feedback about what I've talked about so far in this learning experience?

[gayatri]

no nothing to add
i will keep my mouth shut now