Let’s discuss the issue of the number of times attachments can be downloaded?
Thread Content
Recently, it was noticed that some users keep downloading attachments from the site. Of course, this is a good thing as it helps increase the site’s popularity. Should there not be a limit set on the number of downloads each user can make per day? Ideas: 1. If the post is about resources, it’s advisable to include screenshots to discourage people from not downloading them. 2. If a post falls under the category of resource posts, those who download it will not refrain from doing so if they read the previous discussions carefully. 3. Some downloaders download the attachments out of pure curiosity about their contents. 4. It is set that the first 5 downloads per day for each ID cost 1 wealth point, 5 downloads cost 2 wealth points, 6 downloads cost 3 wealth points, with the amount increasing gradually. This also allows everyone to download more purposefully. Discussion is welcome.
Why impose restrictions? The limitation is that there’s too much wealth; to allow them to download, there isn’t enough wealth, so they need to top up! RMB! ;P
Some attachments weren’t screenshotted; I only realized that after downloading them – it turns out they had already been downloaded~~~~~ Some resources from certain forums were posted repeatedly as well~~~
Is the poster’s suggestion aimed at downloaders or at uploaders? Why do I seem a bit confused? . . :L
This one has it. The management approach in other forums is to first check for duplicates, then upload the content along with screenshots; otherwise, the post is deleted. Kai Chuan needs popularity; he wouldn’t do such a thing.
As I write, ideas come to mind. . . They all have them. . Hehe~~ I’m not good at expressing myself.....
It was suggested to add an attachment preview feature, so that one can know whether it’s what they want.
The root cause is that the original poster encountered posts with attachments, and the replies were all intended to download those attachments; they didn’t involve much technical content, but still had to be managed. He forgot that it could be categorized as a resource post.