Difference between revisions of "YTMND:TODO"

Revision as of 21:57, December 24, 2007

YTMND TODO List

Version 1.6 [2006-04-20 00:43:58 CST]

NEW SERVERS
-- Move DB from current db box to mysql 5 on the new db server.
-- Move www1 from current box to new web server.
-- Figure out what to use the 2 old servers for
   I'm thinking Search server and something else.


RSS FEEDS (should be in interface dir)
-- RSS feeds for all the content boxes
-- Search RSS feeds (maybe)
--   Allow saving of searches as rss that are updated once every 60 or so minutes? [PAID]


COMMENTS
-- MySQL 5 will allow VARCHAR comments > 256 chars.
-- Nested comments to allow people to reply to comments (requires layout changes)
-- Ability to delete comments [PAID]
-- Comment paging for sites with a ton of comments.


FILESYSTEM
-- Store MD5 of sound and image files for each site including byte size.
-- Link to sound and image file on profile page.  [PAID]
-- Possibly re-work file layouts to prevent file duplications. 
-- "56k" option to prevent users from opening huge sites.


NEWS
-- DBize the news. 
-- Make an Admin CMS for news.
-- Make news comments. 


USER PROFILES
-- Real user profiles. 
-- Avatars [PAID] (would need to figure out where on the site they are shown).
-- Profile image and text, copy a lot of the VBulletin options.


SESSIONS
-- Standardize sessions, use a wrapper session class.
-- Decide which session engine to use, most likely memcached and Zeus's user tracking feature.


KEYWORDS
-- Work more on keyword relevance, maybe use a separate Xapian.
-- Add more to keywords interface.
-- Start linking to keywords in site profiles.
-- Add ads.


CONTENT BOXES
-- Allow customization of content boxes. [PAID]
-- Allow ordering of content boxes. [PAID].
-- Add new content boxes:
---- Who's online.
---- Top Rated Today
---- Top Rated This Month
---- Most Views Today (External)


HELP SECTION/FAQ
-- A help section with common problems and solutions.
-- A CMS. 


SITE VIEWS
-- Insert a row on each site view with: (IP, site_id, referring url).
-- CRON job uniqify's views and stores a small amount of referring url data.
-- Maybe make Referrers [PAID] feature.


HASH TABLES
-- Rename hash tables so they are easily identifiable as so.
-- Get temp_site_list updated up to the second like temp_comment_list.
-- This will avoid the 30 seconds of downtime every 30 minutes when that table compiles.
-- Use the new MySQL views on queries that are time sensitive without ORDER/GROUP by clauses.


REPORT THIS SITE FEATURE
-- For illegal content.
-- Marked as work safe when not work safe.
-- Craigslist like.


USER LOGINS
-- Clean up and rewrite the code so it uses straight sessions.
-- Redo the cookie so it isnt storing a password.
-- Log new IPs on login, for accounting like VBulletin.


STRIPSLASHES
-- CLEAN UP THE DB, GET RID OF ALL THE SLASHES YOU LAZY FUCK.


ALGORITHMS THAT NEED WRITING
-- Site recommendations. [PAID?]
-- Similar users.
-- User dupes.


MODERATION
-- Figure out if you want to open moderation to everyone.
-- Make some sort of interface to allow people to batch moderate (showing images/thumbnails only)
-- Streamline and prioritize the moderation process so its faster.
-- Clean up mod log table on site image/sound/text change. 
-- Write some sort of approval interface. 
-- Integrate the entire mod panel with admin.ytmnd.com
-- Get rid of the frames, they are too clunky and should be integrated with each site.
-- Allow moderators to mark an asset like they do sites.
--- This will allow moderators to mark all sites using an image or sound as "nsfw" or "kill",
--- effectively making an easy batch moderation, especially good for duplicate sites.



YTMND STORE
-- Real shopping cart. multiple tables and most likely a separate db.
-- Site sponsorship done through store.


USER SIGNUP
-- Rewrite completely.
-- Get more meta data (like age, contact options etc)
-- Completely redo the captcha, it's causing too many problems.
-- Dupe checking, if duplicate email is used offer reset password/resend confirm mail.
-- Integrate forum account creation. This seems to be really easy, only problem is it will need to be remote.
--- more info here: http://www.vbulletin.org/forum/showthread.php?t=82836


EMAIL
-- Inject a unique message ID and then a qmail script to parse the information into a db.
   This way when all the idiots sign up and they require human whitelist interaction it can tell them
   to fuck themselves when they send 1000 emails to support.


SUPPORT ISSUES
-- Decide whether or not to buy kayako. Call them and discuss, as it requires zend decoder and thats a pain in the ass.

ADMIN.YTMND.COM
-- Major clean up needed, move to new cvs.
-- More web stuff, less shell scripts.

LISTS
-- Create a back end system to manage lists of sites.
-- Users could create and publish lists of sites.
-- Back end would allow support for "true" favorite sites.
-- Possibly the ability to have group lists, with a manager.

CLEAN UP ERRORS AND WARNINGS
-- All pages that just consist of die messages or warnings should go through an error class of some sort

SITE TEMPLATE
-- Complete re-do of sound code. Needs to be a lot smarter and take into account user preferences.
-- For instance, allowing the use of media player on firefox, which would solve a lot of sound woes.