Changes between Version 13 and Version 14 of WikiStart
- Timestamp:
- Aug 27, 2010, 1:45:16 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v13 v14 44 44 45 45 With subtitles store its encoding. Use [http://mirmodynamics.com/post/2008/12/17/Charset-detection-with-python charset detection] 46 For language detection use TextCat, Python [http://thomas.mangin.com/data/source/ngram.py implementation], [http://code.google.com/p/langdet/ langdet], google translate [http://www.catonmat.net/blog/python-library-for-google-translate python lib]46 For language detection use !TextCat, Python [http://thomas.mangin.com/data/source/ngram.py implementation], [http://code.google.com/p/langdet/ langdet], google translate [http://www.catonmat.net/blog/python-library-for-google-translate python lib] 47 47 48 48 == Movie section == … … 56 56 done it properly, because current implementation (CRC64) is weak and can lead to collisions in 57 57 future (so far there was no collisions). Ideally, system should be coded for more kind of hashes. 58 I think wrong idea is put into hash i nformation such is movielength, fps, dimensions of movie58 I think wrong idea is put into hash itself information such is movielength, fps, dimensions of movie 59 59 and such. Hash should be only file dependent, for example first and last 128kb (sha1), and 60 60 filesize together hashed (sha1). … … 65 65 == User Section == 66 66 67 Registration - simple as possible - UserName, Email, Password, possible login using social sites,67 Registration - simple as possible - username, email, password, possible login using social sites, 68 68 openid and so on (rpxnow.com). 69 69 70 70 Groups and permissions - similar like in current version of opensubtitles. There are permissions, 71 groups got 1 or many permissions, and user can belong to 1 or more groups. 71 groups got 1 or many permissions, and user can belong to 1 or more groups. Django got good resources of libs for this. 72 72 73 73 == Translator Groups == … … 75 75 There should be some good support for subtitle translators and their groups. This need more 76 76 research how to done it properly. 77 * rating system 78 * groups rating 79 * stats 80 81 == Upload section == 82 Website upload: user should upload files first and then fill information needed. Why? Because we can help him to fill these informations - we 83 can analyze subtitles for language, so analyzed subtitle language will be selected. Duplicates should be avoided, or very similar subtitles, 84 so thats why it is wise to let user just select subtitles and upload and then fill needed information. 85 77 86 78 87 == Request section == … … 91 100 92 101 Only registered useragents will have API access by using their key. API should be provided 93 by different standards such as XML-RPC (current), REST, JSON...good example of API is on [http://api.themoviedb.org/ TheMovieDB].102 by different standards such as XML-RPC, REST, JSON...good example of API is on [http://api.themoviedb.org/ TheMovieDB]. 94 103 API [http://alexking.org/blog/2009/12/13/api-versioning-tip versioning] is a must. 95 104 … … 98 107 == Caching == 99 108 100 Cache everything what needs to be cached in memcached :) 109 101 110 102 111 … … 127 136 * maximum two subtitles per language per release 128 137 * preview of subtitles will be AJAX style, fetched from cached subtitles 138 129 139 130 140 == Database Design == … … 147 157 For Caching of subtitles (so subtitles doesn't have to be each time REGENERATED) we can use: 148 158 159 === using of API key for useragent is good idea ? === 160 if somebody wants hack it, he will just look for API key in other app and thats it. So what is difference to have enabled useragents and API keys? 149 161 150 162
