To Do

• More stats/charts
  • A list of users that are currently seeding.
  • Stats on “healthy” torrents. As in, stats on the number of torrents that have seeders, etc.
• Messaging
  • The basic framework for this is in place. I’d like to make it a bit nicer before rolling it out, however.
  • Included in this could be a generic “message an admin” that is sent to all users of a given access role (see below).
• Site log
  • It would be nice to have a log of certain activities that happen on the site. Possibly a publicly viewable (at lease some of the information) page could exist, but mainly this would be good for administrators.
    • Deletions
    • uploads
    • registrations
    • account deletions
    • password resets
• Torrent deletion
  • Related to site logs, allowing for a comment when deleting a torrent could be nice to keep track of what’s going on a why. Also, if a public log is available, people can see why their torrent no longer works
  • Users with a given role should be able to delete other’s torrents
• Flag a torrent, with comments
  • Inappropriate ?
  • Duplicate
  • Broken
  • Other
• Flag a comment, with comments
  • Offensive
  • Incorrect
  • Other
• Installer
  • We need to include an installer script to help users set up Yeti for the first time. Something clean and friendly along the lines of WordPress would be ideal.
• Salts and passwords
  • Revisit salts and passwords. We really ought to use dynamic salts (a unique salt for each user) instead of a few global salts. Additionally, we should consider using SHA1 or SHA256 as the hashing algorithm, instead of the weaker MD5. Whatever we decide on, care must be taken to ensure legacy Yeti installations can continue to function—perhaps some kind of one-time forced re-entering of the password by current users?
• Config stuff to database
  • Currently, all site configuration happens in a single file. Some of this (db connection info, etc) needs to stay in that file. However, some things could/should be moved in to the database (admin email address, tracker settings, etc). This would allow us to provide an interface to administrators for editing these settings.
• Clean up hidden user stuff
  • Currently, users can be “invisible.” We’re not exposing this as a setting to the users, just using it in the case of administrators. This works pretty well for the most part (they don’t show up in the charts, on their uploaded torrents, as seeders on the site, or have a profile) but is weird with the (currently disabled) messaging feature. If a hidden user sends you a message, it shows the sender as “Anonymous” … which obviously doesn’t work well for hidden admins. Rather, on a sent message is probably one of those places where even a hidden user’s name should show up (but not as a link to their non-existant profile).
• Access control
  • Right now, I believe all access is tiered to administrators and everyone else. To facilitate larger Yeti installations, we ought to have a robust access control system in place. Among other things, the system should support users existing in one or many roles, and roles being assigned one or many permissions. This same access control system could and probably should be used to ban and warn users of policy violations.
• Ratio Enforcement
  • Related to Access Control. Yeti should have a system in place for ratio enforcement. Some sort of warning period with limited access and finally, a removal of the user (changing their access to “none” ?)
• More browse options
  • I’d like to be able to sort results based the number of seeders, number of leachers, number of snatches, file size, number of comments, etc. It could be hard to build this into the nice urls of LightVC’s routing system. But, you can always throw query strings on these, and this might be the nicest way to achieve this.
  • Right now, I’ve totally hacked in a way to browse only seeded torrents. It exists at browselive/ instead of browse/. It’s shitty and hacky and makes me sad. The above could provide a reasonable way to achieve the same effect.
• Requests
  • A system for users to be able to request certain files would be nice.
  • With this system, a user could say that a torrent fills a given request. Then, all users who “agreed” with the request would be notified.
• Snatches
  • It would be nice to be able to see a list of all torrents that you’ve downloaded. This should probably only be visible to yourself (or users with higher privileges). At the moment, I don’t believe that this data is stored anywhere, so we’d have to figure out a way to do this.
• Invite System
  • Yeti should have support for an invite system. Many private trackers do not want open registration for whatever reason (privacy, quality control, etc.) and we need a way to support that.
  • Something to consider also is a possible system for awarding invites. This may be to arbitrary to code in a general manner (that is to say, what qualifies you for invites), but it’s something to think about.