Things we need:
- Easy way for users to upload levels and levelpacks
- Simple and usable way to find and download other's addons
- Make a secure system to prevent spam and hackers
- Simple rating system to help find quality content
odamite {l Wrote}:Simple rating system to help find quality content
acme_pjz {l Wrote}:PS: maybe level name and description can be loaded from level file (currently level name is present, maybe we can add description, author and license into it)
Edward_Lii {l Wrote}:About the license field, all (public) levels will have to be licensed under GNU GPLv3.
acme_pjz {l Wrote}:I don't think so. There are even GPL games with proprietary levels, for example, Frogatto & Friends, Nikki and Robots, PlaneShift, etc. I think our levels (and uploaded levels) could also be CC-BY 3 or CC-BY-SA 3 or even proprietary (of course, not recommended ), but it is up to the level author.
Edward_Lii {l Wrote}:odamite {l Wrote}:Simple rating system to help find quality content
I've been thinking about this recently and maybe we don't need a rating system.
Allowing ratings by users will require some form of database storage, although not impossible I would like to keep the server load as low as possible.
We could also go for the same approach as STK, certain addons can be featured, placing them at the top of the addon list.
Edward_Lii {l Wrote}:we decided to settle on public domain (CC0), just to be sure.
type = <TYPE>
name = <name>
description = "<description>" (encoded with json_encode( ... ) )
update = <1 or 0>
username = <username>
email = <email> (not verified)
-- (delimiter)
<BODY>
odamite {l Wrote}:The server side looks good and working. However I think that there should be more advanced way to prevent spamming. If I understand correctly, at the moment spamming the queue to maximum will prevent others completely. We don't want that...
odamite {l Wrote}:I would like to know what protocol the moderation part is going to use? Is it based on PHP and HTTP? I think that the best would be FTP bacause doesn't it provide secure authentication out of the box? However I'm not sure what kind of things sourceforge allows...
User uploads level(pack) --> put in the queue --> moderator downloads (one) queue entry --> moderator changes/corrects/tests queue entry --> moderator commits to git repository (Sf authentication) --> moderator removes queue file from server (own authentication).
odamite {l Wrote}:Also we should think about implementing a rating system. This isn't obligatory but just nice thing to have. This could be created using a simple text file and HTTP POST and it shouldn't require any "spam" prevention system.
odamite {l Wrote}:Yeah, we already have pretty good plans and something is already implemented. It's going to be great to see the final system and people using it.
Users browsing this forum: Bing [Bot] and 1 guest