Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mod request feature #9

Open
steveowashere opened this issue Sep 22, 2015 · 6 comments
Open

Mod request feature #9

steveowashere opened this issue Sep 22, 2015 · 6 comments

Comments

@steveowashere
Copy link

I thought it would be a good idea if the site had a 'request mod support' function. Instead of users using the github to request mod support (which should be for issues, bugs, ect).

The mod request page would be user list generated of mods, where users can submit a mod name and a link to the mod. Once a mod has been submitted, it will be added to the list, and cannot be added again. Instead, users can 'vote' for existing mods on the list. That way mods get ranked by demand.
For mods we already support, but don't have full support for yet, the mod can still be added to the this, but perhaps a tag could be applied such as 'needs full support'.

Basically the whole design philosophy is to get user input, and to prioritize development of new textures based off of popular demand.

To prevent trolling/spamming. Submissions are limited 3 per 24 hours based off of IP. Voting is also limited to one vote per mod and 5 votes per 24 hours based off of IP. Submitter of a mod automatically receives one vote, and thus cannot vote him/herself. Similar to Reddit's karma system.

Let me know if this is a good or bad idea, I welcome honest opinions and constructive criticism.
I'm not really a web developer, I know some html, but this project would probably be over my head, I would however help out wherever I can.

@ghost
Copy link

ghost commented Sep 23, 2015

I am sorry but this won't be happening unless someone contributes all the code. I am not even remotely a web developer; I just happen to know a bit of the various languages needed.

There is a large variety of challenges to support such a system. The regex system to ensure a mod isn't submitted twice would be a significant thing by itself. If I could pull off that kind of work I would have a Straw Poll with more than 4 options.

@steveowashere
Copy link
Author

I understand the problem. I'm really not a web developer either, and have no experience with databases that are probably needed to get something like this running.

It might just be better all together to create a subreddit. And post a monthly voting stickied post, on what uses would like to see next. That way we also have another method of reporting bugs/issues, address problems, ect. What do you think?

@Guichaguri
Copy link
Contributor

I may do this, how you think it should be designed? What functionality it will need?

@steveowashere
Copy link
Author

I was thinking it should be pretty simple and minimalist. Similar to how the site it now, same background color and button color). A 'Request Mod Support' link/button on the home page that would take you to another page. The page would have two boxes at the top, one for the mod name and one for the link to the mod.(Maybe simple instructions at the top on how to submit) Then a submit button. Below this would be a simple list of mods that have been submitted, and voting options of some kind (thumbs up/down, whatever) beside each mod name. That's roughly what I'm thinking.

Functionality wise, it just needs to be able to take mod names with a valid link, (Maybe whitelist certain domains? for example: minecraft.curseforge.com or http://www.minecraftforum.net/) and check that mod name against existing ones and then add it to the list if it doesn't exist. Then allow users to vote on those mods, and have the most voted mods at the top in descending order. Also for anti-spamming purposes, limit users voting/submitting in some way (IP based I guess?).

Would really appreciate if you decided to do this, but no pressure.

@ghost
Copy link

ghost commented Sep 26, 2015

Domain whitelisting won't be necessary, I will be the only one checking the log and can just post the results to Github. Even if a user submitted one of the infamous shock sites I would sigh at the lack of originality and move onto the next line.

As for limiting submissions and voting, I can handle that fairly easily if needed.

Using a flat file format for the log we just need to save the $_SERVER['REMOTE_ADDR'] to a 45 character string along with the URL provided by the submission. If the user IP matches an existing URL submission, move the user IP to a new submission and decrease the old URL submission value by 1. If a new user IP matches an existing submission, increase the value of the submission by one.

Format:

Timestamp - User IP - URL - Value

08:52 UTC-07:00 - 2600:3c01::f03c:91ff:fe73:66ff - http://www.f32.me/ - 1

@Guichaguri
Copy link
Contributor

Added in #10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants