Thursday, July 9, 2009

Youtube Beta Channels Suggestions and Bugs

Small bug report noted: Choosing "More info" on the channel for the default Info view. It breaks the scroll bar in IE 7 (I also uses an addon called IE7 Pro) if there is a lot of text.

Beta suggestions:

Custom ordering by owner.

Here's how I want it.

I want to be able to choose 1 to 9 vids for every category.

Categories:

Uploads
Favorites
Playlist 1
Playlist 2
Playlist 3
....

For each of these I can choose what is shown. The options for each spot is as follows.

First
Last
Newest
Oldest
Most viewed
Most commented
Most rated
Most viewed / day
Most commented / day
Most rated / day
Custom

Let's say I choose to have 6 videos shown for Playlist 1 (out of 200 total).

Generally, I want the first video in a playlist to be the most relevant.

Spot 1 will be "First"

"First" means this is the first video I have in my playlist. Video #1. It does not mean the

"Oldest" video ("Oldest" meaning, a video with the oldest published date)
Spot 2 will also be "First"

Again, this means the first'est video not already showing. In this case, playlist video #2.

Now. Maybe I don't want my next video in the list to be the predictable "third" video (by using "First" again). Now I want the next videos to be the most popular.

So next will be "Views"

This will place whatever playlist video is the most viewed. This will have YT figure it out for me out of a 200 video playlist.

Next I want people who see my playlist to see who the last things I've been adding to my playlist. So the next 3 videos will be.

"Last""Last""Last"

On this 200 video playlist that would be videos: 198, 199, and 200.
Now. That's all well and good. But, what about default behavior? We all know most users are too lazy to go custom (I'm not, my Jinitron channel is anything but standard). Here's my recommended 'default' view.

"First"
"Last"
"Last"

Currently YT only shows 3 playlist videos. Way too small IMO, but, if that's the server's limit, or a compromise with other categories, I don't know. Anyway reasoning for that defaqul is simple.

First is almost always the header. It has to be assumed most users put the first video as the most relevant.

Now, we also want viewers to be aware of the latest changes to a playlist. That's why the next 2 should be "Last".

Now, more default behavior.

I'm not sure what the limit is on the server. Right now it's 3 uploads. 3 favs. 3 playlists at 3 each.

Default behavior should be this:

Uploads:

9Favs: 3
PL1: 1
PL2: 1
PL3: 1

Uploads is the main priority BY FAR (unless the user changes things).

So that 15 slots should be doled out like so...

First, the playlists, if the user makes any. Up to 3. 1 video per playlist. Each one is "First".

Now we have 12 slots left. Next 3 for any favs the user has. Each one is "Last" 9 left. Now the 9 left will be for Uploads. This will be sorted by this algorithm.

"Newest"
"Newest"
"Most viewed"
"Most commented"
"Newest"
"Newest"
"Most viewed / day"
"Most commented / day"
"Newest"
"Most viewed"
"Newest"
"Most commented"
"Newest"
"Most rated"
"Most rated"

If the user does not have enough uploads. Then we start filling in with Favs again. If no favs are left for the 15, then fill in Play Lists again.

This should be the default behavior for a channel.

Example: All a user has is uploads. That means 15 uploads are shown.

Example 2: All a user has is favorites.

15 favorites are shown. "Last" "Last" "Last" ...

Anyway, you get it. The value of this behavior is showing off the most distinctive uniqueness of a channel. The uploads. With a smattering of favs, and playlists.

4 comments:

  1. 3rd: texttexttext ......... [(days ago)thumbs]
    @3rd, 4th: texttexttext.... [(days ago)thumbs]
    @4th, 10th: texttexttext .. [(days ago)thumbs]
    @4th, 7th: texttexttext ... [(days ago)thumbs]
    @3rd, 6th: texttexttext ... [(days ago)thumbs]
    @3rd, 5th: texttexttext ... [(days ago)thumbs]

    8th: texttexttext.......... [(days ago)thumbs]
    @8th, 9th: texttexttext ... [(days ago)thumbs]

    1st: texttexttext ......... [(days ago)thumbs]
    @1st, 2nd: texttexttext ... [(days ago)thumbs]

    ReplyDelete
  2. 3rd: texttexttext _________ [(days ago)thumbs]
    @3rd, 4th: texttexttext ___ [(days ago)thumbs]
    @4th, 10th: texttexttext____[(days ago)thumbs]
    @4th, 7th: texttexttext ___ [(days ago)thumbs]
    @3rd, 6th: texttexttext ___ [(days ago)thumbs]
    @3rd, 5th: texttexttext ___ [(days ago)thumbs]

    8th: texttexttext _________ [(days ago)thumbs]
    @8th, 9th: texttexttext_____[(days ago)thumbs]

    1st: texttexttext _________ [(days ago)thumbs]
    @1st, 2nd: texttexttext ___ [(days ago)thumbs]

    ReplyDelete
  3. 3rd: texttexttext ___________ [(days ago)thumbs]
    @3rd, 4th: texttexttext _____ [(days ago)thumbs]
    @4th, 10th: texttexttext______[(days ago)thumbs]
    @4th, 7th: texttexttext _____ [(days ago)thumbs]
    @3rd, 6th: texttexttext _____ [(days ago)thumbs]
    @3rd, 5th: texttexttext _____ [(days ago)thumbs]

    8th: texttexttext ___________ [(days ago)thumbs]
    @8th, 9th: texttexttext_______[(days ago)thumbs]

    1st: texttexttext ___________ [(days ago)thumbs]
    @1st, 2nd: texttexttext _____ [(days ago)thumbs]

    ReplyDelete
  4. 3rd: texttexttext ___________ [(days ago)thumbs]
    @3rd, 4th: texttexttext _____ [(days ago)thumbs]
    @4th, 10th: texttexttext ____ [(days ago)thumbs]
    @4th, 7th: texttexttext _____ [(days ago)thumbs]
    @3rd, 6th: texttexttext _____ [(days ago)thumbs]
    @3rd, 5th: texttexttext _____ [(days ago)thumbs]

    8th: texttexttext ___________ [(days ago)thumbs]
    @8th, 9th: texttexttext _____ [(days ago)thumbs]

    1st: texttexttext_____________[(days ago)thumbs]
    @1st, 2nd: texttexttext _____ [(days ago)thumbs]

    ReplyDelete