-
Notifications
You must be signed in to change notification settings - Fork 198
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
More ideas #23
Comments
Hi man, I didn't get the first point. For the second point. Why not. The tool is not really complicated thought, so the added value may not be hight capared to the work required to setup a decent i18n architecture (remember it runs on bottle). |
If we can remove the python backend and use a single HTML template file or even JST, it could be really easy to create fr.html en.html and de.html with the specific JST translated. We could also use a javascript dictionnary to handle the translation. |
Bottle already comes with a template language and using only python is We can add translation on bottle (we do have to do it be hand I I may be wrong, and if more people tell me we should translate it, then We could also switch from jQuery to http://angularjs.com/. It will make I will require a lot of work though. I'm not ready to do this right now. Le jeu. 31 janv. 2013 11:51:14 CET, Natim a écrit :
|
I think that his first point was to add comments (discussion), just like in ZeroBin (PHP). Is this a planned feature ? |
I think we could implement this with DisqUs. Do you mind doing a PR @ArthurHoaro ? |
Nope, I was just asking. I barely know Python actually. :) |
Ok so we should implement everything inside even the url shortener. |
Actually we can't implement the URL shortener because it would mean that we detail the key on the server, which is precisely what we want to avoid. Remember: 0bin first goal is to protect the host, not the user. As for comments, this was a planned feature but we decided not to implement it: we though we woudn't use such a feature. However, if somebody comes with a PR for this, I'm ok with it. We could make the comments this way :
What do you think ? |
So basically you would like a comment to be a paste linked to the first one and encrypted with the same key? |
No it should be stored in the same file (if we use the local backend and not discuss) and have some different properties that a paste : no coloration, a generated avar with hashviz on the IP and auto linking of the URL. But yes, it should be encrypted with the same key, otherwise there is no point. |
Ok understood. |
I'll open a new one. |
Perfect source, thanks, sametmax and Natim also ;)
More ideas:
detect with help of user_agent for example
The text was updated successfully, but these errors were encountered: