[WIP] Website update

.gitignore

@@ -1,6 +1,115 @@
 cache
 public
-content
 *.pyc
 pelican.pid
 srv.pid
+themes/i18n/translations/*/LC_MESSAGES/*.mo
+env
+
+# This is a generic Python gitignore
+# https://github.com/github/gitignore/blob/2eba0d635f6f5f1b22a4ad99dcc9da0c11da2208/Python.gitignore
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/

content/blog/2015-07-11_current-situation-3.de.md

@@ -0,0 +1,74 @@
+Title: Current Situation
+Date: 2015-07-11 00:55
+Author: Project Tox
+Category: Uncategorized
+Status: published
+
+As many of you in the Tox community have likely already heard, a serious
+situation was brought to our attention which has forced the
+Tox development team to disassociate itself from the Tox Foundation,
+along with its sole board member, Sean Qureshi (aka Stqism, aka
+AlexStraunoff, aka NikolaiToryzin). We learned by Sean’s own
+admission that he "took a loan against the Tox Foundation", and used the
+entirety of the foundation’s funds on personal expenses completely
+unrelated to the project. He did not inform anyone about his actions
+prior to taking them, then proceeded to disappear for weeks once we
+found out, ignoring our attempts to contact him and get an explanation.
+
+The exact amount that he took is unknown due to his having complete
+control over our finances, but it is in the low-thousands. This fund
+regrettably included a small amount of donation money, but was primarily
+made up of money that we received by participating in Google Summer of
+Code last summer.
+
+First, we want to sincerely apologize to the community and take
+responsibility. We could not have predicted that something like this
+would happen, but we certainly could have handled our finances in a more
+responsible and transparent manner. While our development team consists
+of many skilled programmers and designers, none of us are experienced in
+business or financial matters. This led us to put too much trust and
+power into the hands of a single person, who turned out to be just the
+sort of person who would take advantage of such a situation. We can
+blame no one but ourselves for this.
+
+Unfortunately, Sean refuses to take responsibility for what he has done,
+and seems to carry the attitude that what he did was perfectly
+acceptable. Despite our having spent a great deal of time and effort
+trying to engage with him, giving him opportunities to pay us back and
+redeem himself (which is part of the reason why we have waited this long
+to make an official post about it), he has shown no remorse for his
+actions, and continues to hold some of our infrastructure "hostage".
+This includes the tox.im, toxme.se, and libtoxcore.so domains. For this
+reason, we have have also been forced to disassociate ourselves with the
+aforementioned domains and begin again from scratch with a new domain,
+tox.chat.
+
+In spite of the damage that has been done—which we do not wish to
+understate—we'd like to look on the bright side of things and consider
+this a very expensive lesson learned in project management, and life in
+general. We've lost some money, but we've gained a ton of insight. We
+have also been lucky enough to have a few long-standing members of the
+community step up and help us out with things like server management,
+and we should have everything back to normal in a short while, with a
+stronger and better equipped team than before.
+
+As far as finances go, we are not going to repeat the same mistakes
+twice. We will not be taking any official donations\* until we have set
+up a proper organization with an emphasis on transparency and protection
+of assets (more details on this at a future date).
+
+In the mean time, we hope that you will continue to support us, if not
+financially, then in spirit. Despite all of this drama, we have not lost
+sight of our vision to provide secure, private communications for
+everyone. Tox development hasn't had so much as a hiccup in the midst of
+all this; our second run at Google Summer of Code is going better than
+our first, and the number of enthusiastic developers who share our
+vision continues to grow.
+
+Thank you for your understanding and continued support.
+
+\* If you still want to give personal donations to individual
+developers, most of us have bitcoin wallets or paypal accounts and can
+be reached in IRC ([\#tox](https://webchat.freenode.net/?channels=#tox)
+and [\#tox-dev](https://webchat.freenode.net/?channels=#tox-dev) @
+freenode)

content/blog/2015-07-11_current-situation-3.en.md

@@ -0,0 +1,74 @@
+Title: Current Situation
+Date: 2015-07-11 00:55
+Author: Project Tox
+Category: Uncategorized
+Status: published
+
+As many of you in the Tox community have likely already heard, a serious
+situation was brought to our attention which has forced the
+Tox development team to disassociate itself from the Tox Foundation,
+along with its sole board member, Sean Qureshi (aka Stqism, aka
+AlexStraunoff, aka NikolaiToryzin). We learned by Sean’s own
+admission that he "took a loan against the Tox Foundation", and used the
+entirety of the foundation’s funds on personal expenses completely
+unrelated to the project. He did not inform anyone about his actions
+prior to taking them, then proceeded to disappear for weeks once we
+found out, ignoring our attempts to contact him and get an explanation.
+
+The exact amount that he took is unknown due to his having complete
+control over our finances, but it is in the low-thousands. This fund
+regrettably included a small amount of donation money, but was primarily
+made up of money that we received by participating in Google Summer of
+Code last summer.
+
+First, we want to sincerely apologize to the community and take
+responsibility. We could not have predicted that something like this
+would happen, but we certainly could have handled our finances in a more
+responsible and transparent manner. While our development team consists
+of many skilled programmers and designers, none of us are experienced in
+business or financial matters. This led us to put too much trust and
+power into the hands of a single person, who turned out to be just the
+sort of person who would take advantage of such a situation. We can
+blame no one but ourselves for this.
+
+Unfortunately, Sean refuses to take responsibility for what he has done,
+and seems to carry the attitude that what he did was perfectly
+acceptable. Despite our having spent a great deal of time and effort
+trying to engage with him, giving him opportunities to pay us back and
+redeem himself (which is part of the reason why we have waited this long
+to make an official post about it), he has shown no remorse for his
+actions, and continues to hold some of our infrastructure "hostage".
+This includes the tox.im, toxme.se, and libtoxcore.so domains. For this
+reason, we have have also been forced to disassociate ourselves with the
+aforementioned domains and begin again from scratch with a new domain,
+tox.chat.
+
+In spite of the damage that has been done—which we do not wish to
+understate—we'd like to look on the bright side of things and consider
+this a very expensive lesson learned in project management, and life in
+general. We've lost some money, but we've gained a ton of insight. We
+have also been lucky enough to have a few long-standing members of the
+community step up and help us out with things like server management,
+and we should have everything back to normal in a short while, with a
+stronger and better equipped team than before.
+
+As far as finances go, we are not going to repeat the same mistakes
+twice. We will not be taking any official donations\* until we have set
+up a proper organization with an emphasis on transparency and protection
+of assets (more details on this at a future date).
+
+In the mean time, we hope that you will continue to support us, if not
+financially, then in spirit. Despite all of this drama, we have not lost
+sight of our vision to provide secure, private communications for
+everyone. Tox development hasn't had so much as a hiccup in the midst of
+all this; our second run at Google Summer of Code is going better than
+our first, and the number of enthusiastic developers who share our
+vision continues to grow.
+
+Thank you for your understanding and continued support.
+
+\* If you still want to give personal donations to individual
+developers, most of us have bitcoin wallets or paypal accounts and can
+be reached in IRC ([\#tox](https://webchat.freenode.net/?channels=#tox)
+and [\#tox-dev](https://webchat.freenode.net/?channels=#tox-dev) @
+freenode)

content/blog/2015-08-08_tox-dev-talks-1.de.md

@@ -0,0 +1,52 @@
+Title: Tox Dev Talks - #1
+Date: 2015-08-08 23:29
+Author: areashr
+Category: Tox Dev Talks
+Status: published
+
+*(If you don't already know, Tox Dev Talks is a series of weekly
+meetings that bring the Tox developer community together to share ideas,
+progress, and miscellaneous chatter. They take place every Saturday at
+03:00 UTC.)*
+
+This week's Tox Dev Talk turned out exceptionally well, especially as it
+was the first one. The primary focus was on mobile issues; here is a
+summary of what was discussed.
+
+-   How do we deal with doze mode in Android M?
+    -   Do we use GCM?
+-   Is a "passive mode" for toxcore so we can reduce battery and data
+    usage possible?
+-   How do we deal with backgrounding restrictions on iOS?
+    -   Possible solution: use VoIP sockets.
+-   No concrete decisions as of now.
+
+<!-- -->
+
+-   qTox: as tux3 has been absent for a while, the main repo might be
+    moved to DaSpirit's fork.
+
+**Progress updates and to-do:**
+
+-   **installgen2 (Web)**
+    -   ToxKek - Fix connection and crash bugs, add mobile frontend
+        design, add avatars, add file transfers, add ToxDNS support, add
+        groupchat support, add memes, and add remote server support.
+        *(ToxKek is an early-stage HTML/JS Tox client.)*
+    -   Tox.Party - Add Tox3 support and get https certificate.
+    -   Tox Wiki - Add missing pages and clean up mess
+-   **chuongv (iOS)**
+    -   Antidote: Implement video calls for this week.
+-   **subliun (Android)**
+    -   Antox: working on encrypted profile support, fixing some bugs,
+        and getting ready for av support.
+    -   New ToxDNS host is toxme.io
+-   **Impyy (C\#/Windows)**
+    -   SharpTox - finish new groupchat bindings, write documentation
+        for both new av api and new groupchat api.
+-   **oranges (Build infrastructure)**
+    -   Jenkins is up and building libraries, some clients are building.
+    -   Waiting on client devs for some of the other clients.
+
+We hope to see more of the same kind of constructive discussion, and
+more developers in attendance next week!

content/blog/2015-08-08_tox-dev-talks-1.en.md

@@ -0,0 +1,52 @@
+Title: Tox Dev Talks - #1
+Date: 2015-08-08 23:29
+Author: areashr
+Category: Tox Dev Talks
+Status: published
+
+*(If you don't already know, Tox Dev Talks is a series of weekly
+meetings that bring the Tox developer community together to share ideas,
+progress, and miscellaneous chatter. They take place every Saturday at
+03:00 UTC.)*
+
+This week's Tox Dev Talk turned out exceptionally well, especially as it
+was the first one. The primary focus was on mobile issues; here is a
+summary of what was discussed.
+
+-   How do we deal with doze mode in Android M?
+    -   Do we use GCM?
+-   Is a "passive mode" for toxcore so we can reduce battery and data
+    usage possible?
+-   How do we deal with backgrounding restrictions on iOS?
+    -   Possible solution: use VoIP sockets.
+-   No concrete decisions as of now.
+
+<!-- -->
+
+-   qTox: as tux3 has been absent for a while, the main repo might be
+    moved to DaSpirit's fork.
+
+**Progress updates and to-do:**
+
+-   **installgen2 (Web)**
+    -   ToxKek - Fix connection and crash bugs, add mobile frontend
+        design, add avatars, add file transfers, add ToxDNS support, add
+        groupchat support, add memes, and add remote server support.
+        *(ToxKek is an early-stage HTML/JS Tox client.)*
+    -   Tox.Party - Add Tox3 support and get https certificate.
+    -   Tox Wiki - Add missing pages and clean up mess
+-   **chuongv (iOS)**
+    -   Antidote: Implement video calls for this week.
+-   **subliun (Android)**
+    -   Antox: working on encrypted profile support, fixing some bugs,
+        and getting ready for av support.
+    -   New ToxDNS host is toxme.io
+-   **Impyy (C\#/Windows)**
+    -   SharpTox - finish new groupchat bindings, write documentation
+        for both new av api and new groupchat api.
+-   **oranges (Build infrastructure)**
+    -   Jenkins is up and building libraries, some clients are building.
+    -   Waiting on client devs for some of the other clients.
+
+We hope to see more of the same kind of constructive discussion, and
+more developers in attendance next week!