This is to start a new thread to replace the now closedREQ: Burning (state of the file) [Granted & Closed].
The purpose of the request is simple. As a downloader, if a file is scarce, I would like other users to know, so they could share it again, if they are not already. As a sharer, I would like to know when other people need a file I have so I can reshare it.
To accomplish this, I have two possible implementations.
1) Active Requests
This would be a button somewhere, so that people could ask for a file to be reshared. This could either pop a message to users that have the file, or show up in mylist, ...
Advantages:
* Interface is obvious
Disadvantages:
* Can be abused
* Need to define rules on when request expires
2) Passive Requests
Make a new file status called "Downloading". This status would not count towards the number of people that have a file, but rather would express how much interest there is in the file. Then a score can be derived (based on a ratio of sharers versus downloaders, or how long a file has been in download status, ...). Again, there could be active notifies when something changes status, or just icons in mylist...
Advantages:
* It can show a desirability rating for a file. This can be a gradual scale. This would make it easier for sharers to determine what to share if they have many things people request.
* Less likely to be abused, if a particular user has a lot of things in download state, this can be factored into the equation.
* When a user says they have the file (instead of downloading it), or as people say they share it, the importance shifts automatically.
* You could have statistics similar to BT (# of seeds/sharers/uploads and # of clients/downloads/leeechers)
Disadvantages:
* There is no active request. A file that says it has a lot of people sharing it, but in acuality doesn't have any sources would have a good rating, and would not tell sharers the file is needed.
I like the passive requests better. I believe that if fits better with they system's interface and if people really want to request a share they can go to somewhere lite AnimeReactor...
Reshare Requests [OLDREQ/WAS-ONTODO]
Moderator: AniDB
I'm still in favour of this strategy and it should be implemented for these reasons:I wrote:It could work like this:
A user who wants to request a file will have to add it to his mylist. there he sets the state to 'request'.
If a user requests a file all other users who have got the file not shared can see in their mylist a little icon/mark next to the anime title (and when expanding the tree next to the file).
The request is canceled either if the requesting user changes the file-state from 'request' or after a certain timeout (1 week for example) or after x people have changed their filestate to 'release' for that file.
Multiselecting would be nice (as it works with the other states as well).
Hope this helps you exp when implementing this (I think it shoud be possible with some more sql-statements for the check if there is a request and just adding one state to the filestate-combo.
I wrote: 1. Sometimes there is just one chunk missing and as anidb knows the file it can easily find users who have this file complete. (I guess you do not know the ed2k-link of every file you put on cd, do you?)
2. Less 'spamming' in Animereactor-forum.
3. No need to look for RSRs in the long list of threads, as they will find you.
4. Less work for all people involved.
5. Even lazy people (who don't read AR-forum) might reshare something.
i like point 5.... lazy me...-
spankydam
- Posts: 15
- Joined: Sat Feb 15, 2003 3:26 pm
- Location: UK (still waiting for ride off this planet)
I agree that it would be a useful feature to be able to request a reshare of files (got a few animes in my emule list on the offchance that the original sharers reappear or reshare).
As a suggestion - could we possibly add a section in the MyPlace for received reshare requests, and a button or similar in the main display for that anime's episodes. On clicking the button it would then trigger the file to appear in each relevant persons 'Received Reshare Request' list. We could maybe even have a number beside each entry for the total number of users requesting a reshare of that file.
If we then tag that reshare request against the user, when they add that anime to their list we check against the tag, and remove that tag and the corresponding request from the section in MyPlace.
That way we wouldn't be bombarded by continual popups (for those with the larger lists).
Just a thought on another way of implementing it - and without knowing the schema I've no idea how easy / difficult this would be to implement.
Thanks again for my favourite website... Spanky
As a suggestion - could we possibly add a section in the MyPlace for received reshare requests, and a button or similar in the main display for that anime's episodes. On clicking the button it would then trigger the file to appear in each relevant persons 'Received Reshare Request' list. We could maybe even have a number beside each entry for the total number of users requesting a reshare of that file.
If we then tag that reshare request against the user, when they add that anime to their list we check against the tag, and remove that tag and the corresponding request from the section in MyPlace.
That way we wouldn't be bombarded by continual popups (for those with the larger lists).
Just a thought on another way of implementing it - and without knowing the schema I've no idea how easy / difficult this would be to implement.
Thanks again for my favourite website... Spanky
