retribuo
08-07-2005, 07:14 AM
Hey guys, this is my first post here. I've been a participating member of the p2p community for quite some time, but I've decided that I want to contribute a little more constructively (something other than bandwidth).
So, I've got some ideas that my help existing (or future) networks function more efficiently and would love some feedback from you guys. I've got moderate technical ability, but haven't ever learned how to code, so I may be fuzzy on the feasibility of some of these ideas...
Here's a brief summary of some concepts that I've been thinking about for the file-sharing scene... keep in mind its very rough.
Here's a link to the PDF (http://s49.yousendit.com/d.aspx?i3KOCILXIVCCV90CRO34TM4UVPB)
Here's the plain text (minus highlighting and formatting):
File-Sharing Concepts for Development
Scheduled Swarming – Instead of individual users leaching away a sharer’s bandwidth through intermittent file requests, a swarm is scheduled according to as-yet undetermined criterion and file requests are collected. When a trigger event occurs, seeding commences and the swarm becomes active. This should promote more efficient (although less immediate) sharing of less popular files.
Standardized Information File – This xml formatted file should allow for easier and more accurate indexing and searching of files across file-sharing networks. It should contain information like: media type, title, publication date, bitrate, version, hashing information, torrent tracker, etc. This file should somehow be seamlessly integrated into the shared file.
Standard File/Directory Structure – This standard should specify the location, filenames, and format of files that are regularly included in a shared archive.
Examples:
a) rls.nfo – Contains information and news from the release group that supplied the file.
b) readme.nfo – Should be included with software. Contains information about version, installation, and cracking.
c) / - Should only contain the files “rls.nfo” and “readme.nfo.”
d) /data/ - Should contain the shared materials.
e) /cs/ - Should contain the crack or serial if applicable.
Text in red is symbolizes a concept in need of further development.
Written by: retribuo
Date: 8/07/2005
So, I've got some ideas that my help existing (or future) networks function more efficiently and would love some feedback from you guys. I've got moderate technical ability, but haven't ever learned how to code, so I may be fuzzy on the feasibility of some of these ideas...
Here's a brief summary of some concepts that I've been thinking about for the file-sharing scene... keep in mind its very rough.
Here's a link to the PDF (http://s49.yousendit.com/d.aspx?i3KOCILXIVCCV90CRO34TM4UVPB)
Here's the plain text (minus highlighting and formatting):
File-Sharing Concepts for Development
Scheduled Swarming – Instead of individual users leaching away a sharer’s bandwidth through intermittent file requests, a swarm is scheduled according to as-yet undetermined criterion and file requests are collected. When a trigger event occurs, seeding commences and the swarm becomes active. This should promote more efficient (although less immediate) sharing of less popular files.
Standardized Information File – This xml formatted file should allow for easier and more accurate indexing and searching of files across file-sharing networks. It should contain information like: media type, title, publication date, bitrate, version, hashing information, torrent tracker, etc. This file should somehow be seamlessly integrated into the shared file.
Standard File/Directory Structure – This standard should specify the location, filenames, and format of files that are regularly included in a shared archive.
Examples:
a) rls.nfo – Contains information and news from the release group that supplied the file.
b) readme.nfo – Should be included with software. Contains information about version, installation, and cracking.
c) / - Should only contain the files “rls.nfo” and “readme.nfo.”
d) /data/ - Should contain the shared materials.
e) /cs/ - Should contain the crack or serial if applicable.
Text in red is symbolizes a concept in need of further development.
Written by: retribuo
Date: 8/07/2005