db.json

{"Asset":[{"_id":"themes/apollo/source/images/icon-reorder@2x.png","path":"images/icon-reorder@2x.png","modified":false},{"_id":"themes/apollo/source/js/script.js","path":"js/script.js","modified":false},{"_id":"themes/apollo/source/css/style.styl","path":"css/style.styl","modified":false},{"_id":"themes/apollo/source/css/fonts/FontAwesome.otf","path":"css/fonts/FontAwesome.otf","modified":false},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.eot","path":"css/fonts/fontawesome-webfont.eot","modified":false},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.svg","path":"css/fonts/fontawesome-webfont.svg","modified":false},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.ttf","path":"css/fonts/fontawesome-webfont.ttf","modified":false},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.woff","path":"css/fonts/fontawesome-webfont.woff","modified":false},{"_id":"themes/apollo/source/fancybox/blank.gif","path":"fancybox/blank.gif","modified":false},{"_id":"themes/apollo/source/fancybox/fancybox_loading.gif","path":"fancybox/fancybox_loading.gif","modified":false},{"_id":"themes/apollo/source/fancybox/fancybox_loading@2x.gif","path":"fancybox/fancybox_loading@2x.gif","modified":false},{"_id":"themes/apollo/source/fancybox/fancybox_overlay.png","path":"fancybox/fancybox_overlay.png","modified":false},{"_id":"themes/apollo/source/fancybox/fancybox_sprite.png","path":"fancybox/fancybox_sprite.png","modified":false},{"_id":"themes/apollo/source/fancybox/fancybox_sprite@2x.png","path":"fancybox/fancybox_sprite@2x.png","modified":false},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.css","path":"fancybox/jquery.fancybox.css","modified":false},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.js","path":"fancybox/jquery.fancybox.js","modified":false},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.pack.js","path":"fancybox/jquery.fancybox.pack.js","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/fancybox_buttons.png","path":"fancybox/helpers/fancybox_buttons.png","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-buttons.css","path":"fancybox/helpers/jquery.fancybox-buttons.css","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-buttons.js","path":"fancybox/helpers/jquery.fancybox-buttons.js","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-media.js","path":"fancybox/helpers/jquery.fancybox-media.js","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-thumbs.css","path":"fancybox/helpers/jquery.fancybox-thumbs.css","modified":false},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-thumbs.js","path":"fancybox/helpers/jquery.fancybox-thumbs.js","modified":false},{"_id":"source/about/index.md.2014-12-30T22-17-28.980Z.bak","path":"about/index.md.2014-12-30T22-17-28.980Z.bak","modified":false},{"_id":"source/images/50ddb4011dc87d2fc7b3ab693dc77612bcd0c032.png","path":"images/50ddb4011dc87d2fc7b3ab693dc77612bcd0c032.png","modified":false},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-17-28.980Z.bak","path":"running-a-bootstrap-node/index.md.2014-12-30T22-17-28.980Z.bak","modified":false},{"_id":"source/about/index.md.2014-12-30T22-29-24.873Z.bak","path":"about/index.md.2014-12-30T22-29-24.873Z.bak","modified":false},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-29-24.873Z.bak","path":"running-a-bootstrap-node/index.md.2014-12-30T22-29-24.873Z.bak","modified":false},{"_id":"source/about/index.md.2014-12-30T22-36-19.296Z.bak","path":"about/index.md.2014-12-30T22-36-19.296Z.bak","modified":false},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-36-19.296Z.bak","path":"running-a-bootstrap-node/index.md.2014-12-30T22-36-19.296Z.bak","modified":false},{"_id":"source/about/index.md.2014-12-31T00-07-51.158Z.bak","path":"about/index.md.2014-12-31T00-07-51.158Z.bak","modified":false},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-31T00-07-51.158Z.bak","path":"running-a-bootstrap-node/index.md.2014-12-31T00-07-51.158Z.bak","modified":false},{"_id":"source/images/vsrykl.png","path":"images/vsrykl.png","modified":false},{"_id":"source/images/antox-0-4-app-info.png","path":"images/antox-0-4-app-info.png","modified":false},{"_id":"source/images/antox-tox-im-certificate.png","path":"images/antox-tox-im-certificate.png","modified":false},{"_id":"source/images/toxcore-over-5000-commits.jpeg","path":"images/toxcore-over-5000-commits.jpeg","modified":false},{"_id":"source/images/antox-0-13-0-1.png","path":"images/antox-0-13-0-1.png","modified":false},{"_id":"source/images/antox-0-13-0-2.png","path":"images/antox-0-13-0-2.png","modified":false},{"_id":"source/images/antox-0-13-0-3.png","path":"images/antox-0-13-0-3.png","modified":false},{"_id":"source/images/antox-0-14-0.png","path":"images/antox-0-14-0.png","modified":false},{"_id":"source/images/qtox-settings-window.png","path":"images/qtox-settings-window.png","modified":false},{"_id":"source/images/ratox-small.png","path":"images/ratox-small.png","modified":false},{"_id":"source/images/toxic-0-5-1.png","path":"images/toxic-0-5-1.png","modified":false},{"_id":"source/images/utox-small.png","path":"images/utox-small.png","modified":false},{"_id":"source/images/Tox_ftl.png","path":"images/Tox_ftl.png","modified":false},{"_id":"source/images/Tox_ftl_message.jpg","path":"images/Tox_ftl_message.jpg","modified":false}],"Cache":[{"_id":"scaffolds/draft.md","mtime":1420586900000},{"_id":"scaffolds/page.md","mtime":1419840743000},{"_id":"scaffolds/photo.md","mtime":1419840743000},{"_id":"scaffolds/post.md","mtime":1420586900000},{"_id":"source/_drafts/The-Road-Ahead-2015-Edition.md","mtime":1420586788000},{"_id":"source/_posts/-ce-bctox-updates-0-0-9.md","mtime":1420586788000},{"_id":"source/_posts/-ce-bctox-updates-0-1-0.md","mtime":1420586788000},{"_id":"source/_posts/-ce-bctox-updates-0-1-1.md","mtime":1420586788000},{"_id":"source/_posts/-ce-bctox-updates-0-1-2.md","mtime":1420586788000},{"_id":"source/_posts/-ce-bctox-updates-0-1-3.md","mtime":1420586788000},{"_id":"source/_posts/a-quick-overlook-at-toxs-mission.md","mtime":1422148791000},{"_id":"source/_posts/achievement-get-groupchat-audio.md","mtime":1420586900000},{"_id":"source/_posts/antox-0-13-0-alpha-release.md","mtime":1422148791000},{"_id":"source/_posts/antox-0-4-pushed-to-google-play.md","mtime":1422148791000},{"_id":"source/_posts/antox-0-5-released.md","mtime":1420586788000},{"_id":"source/_posts/antox-0-6-1-released.md","mtime":1422148791000},{"_id":"source/_posts/antox-0-6-3-released.md","mtime":1420586899000},{"_id":"source/_posts/antox-0-6-4-released.md","mtime":1422148791000},{"_id":"source/_posts/antox-0-6-5-released.md","mtime":1420586899000},{"_id":"source/_posts/antox-0-6-released.md","mtime":1422148791000},{"_id":"source/_posts/antox-0-7-released.md","mtime":1420586788000},{"_id":"source/_posts/antox-jenkins.md","mtime":1422148791000},{"_id":"source/_posts/antox-nightly-builds-google-play-store.md","mtime":1422148791000},{"_id":"source/_posts/antox-release-0-14-0-alpha.md","mtime":1422148791000},{"_id":"source/_posts/antox-v0-12-released.md","mtime":1422148791000},{"_id":"source/_posts/antox-v0-8-1-alpha-released.md","mtime":1422148791000},{"_id":"source/_posts/apt-yum-repos-now-available-for-venom.md","mtime":1422148791000},{"_id":"source/_posts/audio.md","mtime":1420586788000},{"_id":"source/_posts/build-systems-yo.md","mtime":1422148791000},{"_id":"source/_posts/downtime.md","mtime":1422148791000},{"_id":"source/_posts/f-droid-repo-changing-ssl-certificate.md","mtime":1422148791000},{"_id":"source/_posts/gsoc-14-proposals.md","mtime":1420586788000},{"_id":"source/_posts/help-tox-grow-run-a-tox-node-today.md","mtime":1420586899000},{"_id":"source/_posts/how-the-crypto-tox-uses-works.md","mtime":1420586788000},{"_id":"source/_posts/introducing-sts-single-tox-standard.md","mtime":1422148791000},{"_id":"source/_posts/jenkins-ci-and-signed-commits.md","mtime":1422148791000},{"_id":"source/_posts/new-milestone-reached-audio-calling-on-windows.md","mtime":1422148791000},{"_id":"source/_posts/no-antox-gplay-release-for-march-13th.md","mtime":1420586899000},{"_id":"source/_posts/qtox-now-in-tox-repositories.md","mtime":1420586900000},{"_id":"source/_posts/ratox-in-tox-repositories.md","mtime":1420586900000},{"_id":"source/_posts/stf-4-14.md","mtime":1422148791000},{"_id":"source/_posts/sts-approaches-v0-0-5.md","mtime":1422148791000},{"_id":"source/_posts/tcp-branch-merged-with-master.md","mtime":1420586899000},{"_id":"source/_posts/tcp-relay-work-begun.md","mtime":1420586899000},{"_id":"source/_posts/the-tcp-branch-an-explanation.md","mtime":1422148791000},{"_id":"source/_posts/to-5000-and-beyond.md","mtime":1420586900000},{"_id":"source/_posts/took-long-enough.md","mtime":1422148791000},{"_id":"source/_posts/tox-a-new-direction.md","mtime":1422148791000},{"_id":"source/_posts/tox-bootstrap-now-packaging-for-armhf.md","mtime":1420586899000},{"_id":"source/_posts/tox-core-and-api-changes.md","mtime":1422148791000},{"_id":"source/_posts/tox-now-works-through-tor.md","mtime":1420586788000},{"_id":"source/_posts/tox-on-osx.md","mtime":1422148791000},{"_id":"source/_posts/tox-on-your-wii.md","mtime":1422148791000},{"_id":"source/_posts/tox-packaging-and-versions.md","mtime":1422148791000},{"_id":"source/_posts/tox-updates-kinda.md","mtime":1420586788000},{"_id":"source/_posts/toxic-added-to-tox-repositories.md","mtime":1420586900000},{"_id":"source/_posts/toxic-and-threads.md","mtime":1420586788000},{"_id":"source/_posts/toxic-release-v-0-5-2-and-groupchat-issues.md","mtime":1422148791000},{"_id":"source/_posts/toxicity-and-background-and-notifications.md","mtime":1420586899000},{"_id":"source/_posts/toxicity-and-jenkins.md","mtime":1420586899000},{"_id":"source/_posts/utox-now-has-audio-filtering-noise-cancellation-etc.md","mtime":1420586788000},{"_id":"source/_posts/utox-now-in-apt-yum-repos.md","mtime":1420586900000},{"_id":"source/_posts/utox-updates-0-1-8.md","mtime":1422148791000},{"_id":"source/_posts/utox-updates-0-1-a.md","mtime":1420586788000},{"_id":"source/_posts/venom-changes-for-march-12th-2014.md","mtime":1420586899000},{"_id":"source/_posts/warrant-canary-changes.md","mtime":1422148791000},{"_id":"source/_posts/warrant-canary-updated-changes.md","mtime":1422148791000},{"_id":"source/_posts/were-not-dead-just-working-on-tcp.md","mtime":1420586899000},{"_id":"source/about/index.md","mtime":1420586788000},{"_id":"source/running-a-bootstrap-node/index.md","mtime":1420586899000},{"_id":"themes/apollo/README.md","mtime":1419841717000},{"_id":"themes/apollo/_config.yml","mtime":1419841717000},{"_id":"themes/apollo/scripts/fancybox.js","mtime":1419841717000},{"_id":"themes/apollo/layout/archive.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/category.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/index.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/layout.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/page.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/post.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/tag.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/after-footer.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/archive.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/article.ejs","mtime":1420586900000},{"_id":"themes/apollo/layout/_partial/footer.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/google-analytics.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/head.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/header.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/category.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/date.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/gallery.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/nav.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/tag.ejs","mtime":1419841717000},{"_id":"themes/apollo/layout/_partial/post/title.ejs","mtime":1419841717000},{"_id":"themes/apollo/source/images/icon-reorder@2x.png","mtime":1419841717000},{"_id":"themes/apollo/source/js/script.js","mtime":1419841717000},{"_id":"themes/apollo/source/css/style.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_bass/bass.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_bass/syntax.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_bass/variables.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/archive.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/article-gallery.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/article-nav.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/article.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/footer.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/header.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/_partial/rwd.styl","mtime":1419841717000},{"_id":"themes/apollo/source/css/fonts/FontAwesome.otf","mtime":1419841717000},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.eot","mtime":1419841717000},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.svg","mtime":1419841717000},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.ttf","mtime":1419841717000},{"_id":"themes/apollo/source/css/fonts/fontawesome-webfont.woff","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/blank.gif","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/fancybox_loading.gif","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/fancybox_loading@2x.gif","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/fancybox_overlay.png","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/fancybox_sprite.png","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/fancybox_sprite@2x.png","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.css","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.js","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/jquery.fancybox.pack.js","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/fancybox_buttons.png","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-buttons.css","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-buttons.js","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-media.js","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-thumbs.css","mtime":1419841717000},{"_id":"themes/apollo/source/fancybox/helpers/jquery.fancybox-thumbs.js","mtime":1419841717000},{"_id":"source/_posts/hello-world-2.md","mtime":1420586900000},{"_id":"source/_drafts/The-Road-Ahead-2015-Edition.md.2014-12-30T22-17-28.975Z.bak","mtime":1420586788000},{"_id":"source/about/index.md.2014-12-30T22-17-28.980Z.bak","mtime":1420586788000},{"_id":"source/images/50ddb4011dc87d2fc7b3ab693dc77612bcd0c032.png","mtime":1420586900000},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-17-28.980Z.bak","mtime":1420586788000},{"_id":"source/_drafts/The-Road-Ahead-2015-Edition.md.2014-12-30T22-29-24.868Z.bak","mtime":1420586788000},{"_id":"source/about/index.md.2014-12-30T22-29-24.873Z.bak","mtime":1420586788000},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-29-24.873Z.bak","mtime":1420586788000},{"_id":"source/_drafts/The-Road-Ahead-2015-Edition.md.2014-12-30T22-36-19.291Z.bak","mtime":1420586788000},{"_id":"source/about/index.md.2014-12-30T22-36-19.296Z.bak","mtime":1420586788000},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-30T22-36-19.296Z.bak","mtime":1420586788000},{"_id":"source/_drafts/The-Road-Ahead-2015-Edition.md.2014-12-31T00-07-51.153Z.bak","mtime":1420586788000},{"_id":"source/about/index.md.2014-12-31T00-07-51.158Z.bak","mtime":1420586788000},{"_id":"source/running-a-bootstrap-node/index.md.2014-12-31T00-07-51.158Z.bak","mtime":1420586788000},{"_id":"source/images/vsrykl.png","mtime":1420586900000},{"_id":"source/images/antox-0-4-app-info.png","mtime":1420586900000},{"_id":"source/images/antox-tox-im-certificate.png","mtime":1420586900000},{"_id":"source/images/toxcore-over-5000-commits.jpeg","mtime":1420586900000},{"_id":"source/images/antox-0-13-0-1.png","mtime":1420586900000},{"_id":"source/images/antox-0-13-0-2.png","mtime":1420586900000},{"_id":"source/images/antox-0-13-0-3.png","mtime":1420586900000},{"_id":"source/images/antox-0-14-0.png","mtime":1420586900000},{"_id":"source/images/qtox-settings-window.png","mtime":1420586900000},{"_id":"source/images/ratox-small.png","mtime":1420586900000},{"_id":"source/images/toxic-0-5-1.png","mtime":1420586900000},{"_id":"source/images/utox-small.png","mtime":1420586900000},{"_id":"source/_posts/Update-on-the-state-of-Tox.md","mtime":1424725059000},{"_id":"source/_posts/gsoc-translations-more.md","mtime":1426728659000},{"_id":"source/_posts/introducing-toxcoin.md","mtime":1427824269000},{"_id":"source/_posts/tox-friends-2015.md","mtime":1427839160000},{"_id":"source/_posts/tox-chromeos.md","mtime":1427879203000},{"_id":"source/_posts/tox-ftl.md","mtime":1427888844000},{"_id":"source/images/Tox_ftl.png","mtime":1427887512000},{"_id":"source/images/Tox_ftl_message.jpg","mtime":1427888844000},{"_id":"source/_posts/new-api-gsoc-2015.md","mtime":1435184252000},{"_id":"source/_posts/tox-infa-update.md","mtime":1436469764000}],"Category":[{"name":"μTox","_id":"8mjo8a20yy8ruzwh","posts":["q9annh9syrsfm316","bhotzvglhhbga0vr","krvmj28au5ios75j","kgor98zfhyefl0g3","bdwpdom8zw9xahoa","tl9mecwlyh0llmyo","wb9ublewc3t5aac6","7nxuuurzrvn9rud6"]},{"name":"Antox","_id":"q5mc6700pzozi6gl","posts":["iq2yyfhgchs0dqzb","xetw5l7jlqrmvtoy","8mrab8zs938edeed","h9rpapqzo0ch2zpf","31h5i3rwfa7aifhl","nayo66iulovgsjbu","rqhp487k0xp3g73x","fxsensx3tpe1y5me","qq49u1qn7dws1j0m","f6jncan4z3rrztb8","met1gpa2ggqplg37","gt2kt6b8imos8i5d","iaumx32v8u8aihk0","21jlkxvye0bdl5fq","s30rg7tgrpx2c64m","pkk7wr65mftzttap","wm1d8ekx8b3zpzud"]},{"name":"qTox","_id":"n2ucmyxmms5yv6mr","posts":["pbjxv2j5cn2dl2r0","jfwhpdn103yty7yx","xtnxnpx4sx1k8um7","57a990xmw3ju9ba3"]},{"name":"Tox Core","parent":"n2ucmyxmms5yv6mr","_id":"r8wa1580n6ik5nes","posts":["pbjxv2j5cn2dl2r0","57a990xmw3ju9ba3"]},{"name":"μTox","parent":"r8wa1580n6ik5nes","_id":"kuvowwllejwt5uh4","posts":["pbjxv2j5cn2dl2r0"]},{"name":"Tox Core","_id":"nlwrm5tlcr1n8dpi","posts":["vrdf24pa6lzm5on7","jci6fa9luccqfo69","ej9hg7c55lewjeex","zqmdg3z2wnemu31c","dirhuqkxbitdlw6i","hdtpvplt0tk8hhs7","dtb3bcsyoyztlnfi","rglzbd97evl5jzhh","o82x6to410zsc7c5","mw2mkbx3a4tlznud","pdytut5vf1p1xv6n","8risgqer3wnxllzx","nvyau2liy545vx3n","hd0jl08eqsk7mil5","l1osrt9lyciveqc4","ge5fxh8gqg1gknrr"]},{"name":"Jenkins","parent":"q5mc6700pzozi6gl","_id":"6t0r8iadxh2f1p31","posts":["f6jncan4z3rrztb8"]},{"name":"Venom","parent":"n2ucmyxmms5yv6mr","_id":"kie9urux6vjaal4v","posts":["jfwhpdn103yty7yx"]},{"name":"Toxic","_id":"ysh4ufalq2ulbpz8","posts":["69id9djelx2xve66","lpm02fb0deo1d0ya","47apcdc7jj0le6x4","s81rdqqwpxj4foc6"]},{"name":"Google Summer of Code","_id":"63k4kifl4fx5xmzk","posts":["wksc9sf1qxnkb2et","4fozimgtgyx4gqcc"]},{"name":"Uncategorized","_id":"8onc6duauo2iko75","posts":["i8544msdpg9tbbsb"]},{"name":"Jenkins","_id":"rpfxl29wpibc9sbf","posts":["nlg2cl3jkp72bljh","o78q2cq2e32bsa45"]},{"name":"Tox Repositories","parent":"n2ucmyxmms5yv6mr","_id":"kots9n2e471yrjqu","posts":["xtnxnpx4sx1k8um7"]},{"name":"Ratox","_id":"p8mle97ey5sjnf7j","posts":["bnqyaxwvcxeufmpj"]},{"name":"Tox Repositories","parent":"p8mle97ey5sjnf7j","_id":"b1grbwe40a75ur1i","posts":["bnqyaxwvcxeufmpj"]},{"name":"Tox Foundation","_id":"i0yjl3tz23qj3npq","posts":["ekkpozb5wykd8fpw","ln6dmfe83nffr51c","ulim1sdfdxhwdyjq"]},{"name":"STS","_id":"n3qafcv6z7xjcsay","posts":["q28swfj9bkp2ecax"]},{"name":"Tox Core","parent":"n3qafcv6z7xjcsay","_id":"zeqsivfrc306kq3p","posts":["q28swfj9bkp2ecax"]},{"name":"Tox Core","parent":"63k4kifl4fx5xmzk","_id":"ae9xsrnb1o32hh4a","posts":["4fozimgtgyx4gqcc"]},{"name":"Tox Foundation","parent":"nlwrm5tlcr1n8dpi","_id":"upkdnlsjjo67oz6b","posts":["rglzbd97evl5jzhh"]},{"name":"Tox Repositories","parent":"nlwrm5tlcr1n8dpi","_id":"augsl7gp3lhrywul","posts":["pdytut5vf1p1xv6n","ge5fxh8gqg1gknrr"]},{"name":"Poison","parent":"q5mc6700pzozi6gl","_id":"bxds5mqaljzaayrm","posts":["pkk7wr65mftzttap"]},{"name":"Tox Core","parent":"bxds5mqaljzaayrm","_id":"0n0xmqn8bx51wwkb","posts":["pkk7wr65mftzttap"]},{"name":"Toxic","parent":"0n0xmqn8bx51wwkb","_id":"z49sqq3vv4kxk3re","posts":["pkk7wr65mftzttap"]},{"name":"Toxicity","parent":"z49sqq3vv4kxk3re","_id":"hpvfrn75g04b5kk8","posts":["pkk7wr65mftzttap"]},{"name":"Venom","parent":"hpvfrn75g04b5kk8","_id":"ss2kdqby9kb3zb90","posts":["pkk7wr65mftzttap"]},{"name":"Tox Core","parent":"rpfxl29wpibc9sbf","_id":"0r4cfoczye4c9gdv","posts":["o78q2cq2e32bsa45"]},{"name":"Tox Foundation","parent":"0r4cfoczye4c9gdv","_id":"tthwe6ydx6ente4g","posts":["o78q2cq2e32bsa45"]},{"name":"Tox Repositories","parent":"tthwe6ydx6ente4g","_id":"03sb46ncmqp9o8ly","posts":["o78q2cq2e32bsa45"]},{"name":"Tox Repositories","_id":"jhq3nve14qq04ygg","posts":["8za5rho1j52vrt7c","gk9jjem57bx5aw1l"]},{"name":"Toxic","parent":"jhq3nve14qq04ygg","_id":"ubz8ogw0dlh8pv9k","posts":["8za5rho1j52vrt7c"]},{"name":"Toxicity","_id":"jmr06mopc1cr2ep1","posts":["5bvei27mm7kola0s","80c22x83tfu33s35"]},{"name":"μTox","parent":"jhq3nve14qq04ygg","_id":"79izstuei0zdeqwv","posts":["gk9jjem57bx5aw1l"]},{"name":"Venom","_id":"xyv47d59cscxjvsj","posts":["2ae9uyn50tdnxzjs"]}],"Page":[{"title":"About","id":50,"comment":false,"date":1394572655000,"content":"<p>Part of our dedication to the success of Tox is keeping people aware of changes; it’s also apart of our goal to be as transparent as possible. Being transparent, however, usually means users have to sift through numerous commits a day trying to figure out what changed, and what didn’t. This blog aims to bridge the gap between timely updates, and mucking through various Git-related websites. Here, we’ll explain changes made in the Tox Core and its clients, in a way not just for developers, but so that even the average Joe will understand.</p>\n<p>For more information about the Tox project, please visit <a href=\"https://tox.im\" target=\"_blank\" rel=\"external\">https://tox.im</a> or our wiki, <a href=\"https://wiki.tox.im\" target=\"_blank\" rel=\"external\">https://wiki.tox.im</a></p>\n","source":"about/index.md","raw":"title: About\nid: 50\ncomment: false\ndate: 2014-03-11 17:17:35\n---\n\nPart of our dedication to the success of Tox is keeping people aware of changes; it's also apart of our goal to be as transparent as possible. Being transparent, however, usually means users have to sift through numerous commits a day trying to figure out what changed, and what didn't. This blog aims to bridge the gap between timely updates, and mucking through various Git-related websites. Here, we'll explain changes made in the Tox Core and its clients, in a way not just for developers, but so that even the average Joe will understand.\n\nFor more information about the Tox project, please visit [https://tox.im](https://tox.im) or our wiki, [https://wiki.tox.im](https://wiki.tox.im)","updated":1420586788000,"path":"about/index.html","excerpt":"","_id":"dzn4bfqde6r6p2cy","comments":true,"layout":"page"},{"title":"Running a Bootstrap Node","id":499,"comment":false,"date":1412628928000,"content":"<p><img src=\"/images/\" alt=\"preferences-system-network-sharing\"><br>Tox relies on bootstrap nodes (“Tox Nodes”) to help facilitate connections to the DHT, and we need your help to keep Tox strong. By running as many nodes as we can, we make it even harder for third parties, including the government, to censor access to Tox. If you have a spare server, you can run a node that can help keep the Tox Network healthy, and resistant to censorship.</p>\n<h1 id=\"How_does_it_work?\">How does it work?</h1>\n<p>Every client on the Tox Network that is using UDP acts as a node, relaying information about peers its’ currently aware of. However, users log in and out at any given time, which begs a need of a “bootstrap node”, a modified, always-on, client that people can connect to when they start Tox. These nodes act as a beginner directory, and as an initial place to find other peers. By running a Tox Node, you assist users find other users. In addition, nodes will bind on TCP 443 and a couple other ports to help relay connections for peers, this makes Tox faster for people on restrictive networks or using Tor.</p>\n<h1 id=\"What_are_the_requirements?\">What are the requirements?</h1>\n<p>Not much! You just need a server running a Linux distribution (Ubuntu, Debian, RedHat, CentOS, etc.) that has a 24/7 uptime, with a minimum of a 20KBps connection. The hardest hit bootstrap nodes hover around 20-25 kilobytes (200-250 kilobits) per second.</p>\n<h1 id=\"How_do_I_get_started?\">How do I get started?</h1>\n<p>With the <a href=\"https://wiki.tox.im/Binaries#Repositories\" target=\"_blank\" rel=\"external\">Tox Repository</a> and packaging, it’s now easier than ever to setup a Tox Node.</p>\n<p><code>sudo apt-get install tox-bootstrapd</code></p>\n<p><code>sudo yum install tox-bootstrapd</code></p>\n<p>Using the repo is a great way to make sure your bootstrap node is always up-to-date with the latest improvements and security fixes, but for those who wish to compile from source, there’s <a href=\"https://github.com/irungentoo/toxcore/blob/master/INSTALL.md#bootstrapd\" target=\"_blank\" rel=\"external\">instructions on how to do so</a> on our GitHub.</p>\n<p>For more information about a Tox Node, such as configuration, please visit <a href=\"https://wiki.tox.im/\" target=\"_blank\" rel=\"external\">our wiki.</a></p>\n<p>Thank you for your consideration in helping Tox grow. Together, we can build a better messaging service.</p>\n<p><em>Last updated: October 28th, 2014</em></p>\n","source":"running-a-bootstrap-node/index.md","raw":"title: Running a Bootstrap Node\nid: 499\ncomment: false\ndate: 2014-10-06 16:55:28\n---\n\n![preferences-system-network-sharing]({{BASE_PATH}}/images/)\nTox relies on bootstrap nodes (\"Tox Nodes\") to help facilitate connections to the DHT, and we need your help to keep Tox strong. By running as many nodes as we can, we make it even harder for third parties, including the government, to censor access to Tox. If you have a spare server, you can run a node that can help keep the Tox Network healthy, and resistant to censorship.\n\n# How does it work?\n\nEvery client on the Tox Network that is using UDP acts as a node, relaying information about peers its' currently aware of. However, users log in and out at any given time, which begs a need of a \"bootstrap node\", a modified, always-on, client that people can connect to when they start Tox. These nodes act as a beginner directory, and as an initial place to find other peers. By running a Tox Node, you assist users find other users. In addition, nodes will bind on TCP 443 and a couple other ports to help relay connections for peers, this makes Tox faster for people on restrictive networks or using Tor.\n\n# What are the requirements?\n\nNot much! You just need a server running a Linux distribution (Ubuntu, Debian, RedHat, CentOS, etc.) that has a 24/7 uptime, with a minimum of a 20KBps connection. The hardest hit bootstrap nodes hover around 20-25 kilobytes (200-250 kilobits) per second.\n\n# How do I get started?\n\nWith the [Tox Repository](https://wiki.tox.im/Binaries#Repositories) and packaging, it's now easier than ever to setup a Tox Node.\n\n`sudo apt-get install tox-bootstrapd`\n\n`sudo yum install tox-bootstrapd`\n\nUsing the repo is a great way to make sure your bootstrap node is always up-to-date with the latest improvements and security fixes, but for those who wish to compile from source, there's [instructions on how to do so](https://github.com/irungentoo/toxcore/blob/master/INSTALL.md#bootstrapd) on our GitHub.\n\nFor more information about a Tox Node, such as configuration, please visit [our wiki.](https://wiki.tox.im/)\n\nThank you for your consideration in helping Tox grow. Together, we can build a better messaging service.\n\n_Last updated: October 28th, 2014_","updated":1420586899000,"path":"running-a-bootstrap-node/index.html","excerpt":"","_id":"7w6rusc8ihxm9x2n","comments":true,"layout":"page"}],"Post":[{"title":"μTox updates [0.1.1]","id":339,"categories":["8mjo8a20yy8ruzwh"],"date":1407193879000,"tags":[],"content":"<p><strong>New features:</strong></p>\n<ul>\n<li><p>Ability to drag and drop files to send them (for Windows, Xlib version already had this)<br><strong>Bugfixes:</strong></p>\n</li>\n<li><p>Fixed lag issue (Xlib)</p>\n</li>\n<li>Fix possible file transfer issue (<a href=\"https://github.com/notsecure/uTox/pull/189\" target=\"_blank\" rel=\"external\">contribution by doughdemon</a>)</li>\n<li>File transfers are now only marked as complete when the receiver confirms that the file is received completely (fixes possible issue with friend disconnecting as the file transfer nears completion)</li>\n<li><p>Some toxcore bug fixes<br><strong>Other:</strong></p>\n</li>\n<li><p>Audio and video are now decoded on a separate thread for each call, fixes an issue with the decoding being slow and causing the main thread to get stuck in its receive loop</p>\n</li>\n<li>Set thread stack size (Xlib) - reduces memory usage (<a href=\"https://github.com/notsecure/uTox/pull/192\" target=\"_blank\" rel=\"external\">contribution by doughdemon</a>)</li>\n<li>Option to build without DBUS (<a href=\"https://github.com/notsecure/uTox/pull/193\" target=\"_blank\" rel=\"external\">contribution by doughdemon</a>)</li>\n<li>Enabled pixel subrendering for text (Xlib)</li>\n</ul>\n","source":"_posts/-ce-bctox-updates-0-1-1.md","raw":"title: \"μTox updates [0.1.1]\"\nid: 339\ncategories:\n  - μTox\ndate: 2014-08-04 19:11:19\ntags:\n---\n\n**New features:**\n\n*   Ability to drag and drop files to send them (for Windows, Xlib version already had this)\n**Bugfixes:**\n\n*   Fixed lag issue (Xlib)\n*   Fix possible file transfer issue ([contribution by doughdemon](https://github.com/notsecure/uTox/pull/189))\n*   File transfers are now only marked as complete when the receiver confirms that the file is received completely (fixes possible issue with friend disconnecting as the file transfer nears completion)\n*   Some toxcore bug fixes\n**Other:**\n\n*   Audio and video are now decoded on a separate thread for each call, fixes an issue with the decoding being slow and causing the main thread to get stuck in its receive loop\n*   Set thread stack size (Xlib) - reduces memory usage ([contribution by doughdemon](https://github.com/notsecure/uTox/pull/192))\n*   Option to build without DBUS ([contribution by doughdemon](https://github.com/notsecure/uTox/pull/193))\n*   Enabled pixel subrendering for text (Xlib)","slug":"-ce-bctox-updates-0-1-1","updated":1420586788000,"excerpt":"","_id":"q9annh9syrsfm316","comments":true,"layout":"post","photos":[],"link":""},{"title":"μTox updates [0.1.2]","id":344,"categories":["8mjo8a20yy8ruzwh"],"date":1407789857000,"tags":[],"content":"<p><strong>New features:</strong></p>\n<ul>\n<li>Pasting inline images from the clipboard (paste an image and it displays in the chat) (<a href=\"https://github.com/notsecure/uTox/pull/200\" target=\"_blank\" rel=\"external\">code for Xlib by blucoat</a>)</li>\n<li>Search bar to search friends list (<a href=\"https://github.com/notsecure/uTox/pull/210\" target=\"_blank\" rel=\"external\">contribution by CowInAPie</a>)</li>\n<li>Better viewing of large inline images: horizontal scrolling by dragging the image when it is zoomed (unzooming now takes a doubleclick)</li>\n<li><p>Xlib: pasting files from a file manager to send them (<a href=\"https://github.com/notsecure/uTox/pull/200\" target=\"_blank\" rel=\"external\">code by blucoat</a>)<br><strong>Bugfixes:</strong></p>\n</li>\n<li><p>Fixed some clipboard related issues (mostly middle-click issues)</p>\n</li>\n<li>Xlib: set WM_CLASS for better behaviour with some window managers</li>\n<li><p>Fixed a possible segfault in the DNS code<br><strong>Other:</strong></p>\n</li>\n<li><p>Updated the bootstrap <a href=\"https://wiki.tox.im/Nodes\" target=\"_blank\" rel=\"external\">Nodes</a></p>\n</li>\n<li>Changed the font used in the chat (now matches the font used in edit boxes)</li>\n<li>New updater features (requires redownload), get it <a href=\"https://wiki.tox.im/Binaries\" target=\"_blank\" rel=\"external\">here</a></li>\n<li>Updater renamed to “runner” so that it does not require admin permissions (…)</li>\n</ul>\n","source":"_posts/-ce-bctox-updates-0-1-2.md","raw":"title: \"μTox updates [0.1.2]\"\nid: 344\ncategories:\n  - μTox\ndate: 2014-08-11 16:44:17\ntags:\n---\n\n**New features:**\n\n*   Pasting inline images from the clipboard (paste an image and it displays in the chat) ([code for Xlib by blucoat](https://github.com/notsecure/uTox/pull/200))\n*   Search bar to search friends list ([contribution by CowInAPie](https://github.com/notsecure/uTox/pull/210))\n*   Better viewing of large inline images: horizontal scrolling by dragging the image when it is zoomed (unzooming now takes a doubleclick)\n*   Xlib: pasting files from a file manager to send them ([code by blucoat](https://github.com/notsecure/uTox/pull/200))\n**Bugfixes:**\n\n*   Fixed some clipboard related issues (mostly middle-click issues)\n*   Xlib: set WM_CLASS for better behaviour with some window managers\n*   Fixed a possible segfault in the DNS code\n**Other:**\n\n*   Updated the bootstrap [Nodes](https://wiki.tox.im/Nodes)\n*   Changed the font used in the chat (now matches the font used in edit boxes)\n*   New updater features (requires redownload), get it [here](https://wiki.tox.im/Binaries)\n*   Updater renamed to \"runner\" so that it does not require admin permissions (...)","slug":"-ce-bctox-updates-0-1-2","updated":1420586788000,"excerpt":"","_id":"bhotzvglhhbga0vr","comments":true,"layout":"post","photos":[],"link":""},{"title":"μTox updates [0.0.9]","id":315,"categories":["8mjo8a20yy8ruzwh"],"date":1406224011000,"tags":[],"content":"<p>I will now be writing a blog post for every weekly μTox update, including a list of new features and bug fixes. This week’s update includes:</p>\n<p><strong>New features:</strong></p>\n<ul>\n<li><p>Experimental Android support, includes audio calling. Get the .apk <a href=\"https://jenkins.libtoxcore.so/job/uTox_android/lastSuccessfulBuild/artifact/future.apk\" target=\"_blank\" rel=\"external\">[here]</a><br><strong>Bugfixes:</strong></p>\n</li>\n<li><p>Fixed inline PNGs having red/blue channels swapped when saved</p>\n</li>\n<li><p>Shift+HOME/END in text boxes now behaves correctly<br><strong>Other:</strong></p>\n</li>\n<li><p>The core A/V protocol has changed: A/V is not compatible with older versions of uTox</p>\n</li>\n<li>Update 0.0.8 introduced a new major feature, allowing uTox users select a section of their desktop and send it as an inline image</li>\n<li>Some people have been asking how the μTox updater for Windows works. You can read about how it works <a href=\"https://github.com/notsecure/utox-update\" target=\"_blank\" rel=\"external\">[here]</a></li>\n<li>Jenkins now builds 32-bit builds of uTox for Linux</li>\n<li>uTox for Linux no longer relies on Xft, instead it uses Freetype directly</li>\n<li>uTox for Linux now has a —version command</li>\n</ul>\n","source":"_posts/-ce-bctox-updates-0-0-9.md","raw":"title: \"μTox updates [0.0.9]\"\nid: 315\ncategories:\n  - μTox\ndate: 2014-07-24 13:46:51\ntags:\n---\n\nI will now be writing a blog post for every weekly μTox update, including a list of new features and bug fixes. This week's update includes:\n\n**New features:**\n\n*   Experimental Android support, includes audio calling. Get the .apk [[here]](https://jenkins.libtoxcore.so/job/uTox_android/lastSuccessfulBuild/artifact/future.apk)\n**Bugfixes:**\n\n*   Fixed inline PNGs having red/blue channels swapped when saved\n*   Shift+HOME/END in text boxes now behaves correctly\n**Other:**\n\n*   The core A/V protocol has changed: A/V is not compatible with older versions of uTox\n*   Update 0.0.8 introduced a new major feature, allowing uTox users select a section of their desktop and send it as an inline image\n*   Some people have been asking how the μTox updater for Windows works. You can read about how it works [[here]](https://github.com/notsecure/utox-update)\n*   Jenkins now builds 32-bit builds of uTox for Linux\n*   uTox for Linux no longer relies on Xft, instead it uses Freetype directly\n*   uTox for Linux now has a --version command","slug":"-ce-bctox-updates-0-0-9","updated":1420586788000,"excerpt":"","_id":"krvmj28au5ios75j","comments":true,"layout":"post","photos":[],"link":""},{"title":"μTox updates [0.1.0]","id":318,"categories":["8mjo8a20yy8ruzwh"],"date":1406679085000,"tags":[],"content":"<p><strong>New features:</strong></p>\n<ul>\n<li>Ability to start sending video (one way) during an audio call, or stop sending video during a video call</li>\n<li>Playing 2 channel audio (note: uTox does not currently support sending 2 channel audio, only receiving)</li>\n<li><p>These changes break compatibility with older clients<br><strong>Bugfixes:</strong></p>\n</li>\n<li><p>Windows XP fixes: uTox should now work on Windows XP</p>\n</li>\n<li>Audio playback fixes for Android</li>\n<li>Fixed a number of segfaults/crashes (mostly Linux-exclusive)</li>\n<li>Fixed flickering on Linux when resizing the window (<a href=\"https://github.com/notsecure/uTox/pull/175\" target=\"_blank\" rel=\"external\">contribution by mk21</a>)</li>\n<li><p>Fixed an issue with the red and blue channels being swapped on inline images<br><strong>Other:</strong></p>\n</li>\n<li><p>The uTox Updater for Windows has been updated and now has a GUI (the updater has a self update feature and should automatically update itself, please report any issues related to the updater)</p>\n</li>\n</ul>\n","source":"_posts/-ce-bctox-updates-0-1-0.md","raw":"title: \"μTox updates [0.1.0]\"\nid: 318\ncategories:\n  - μTox\ndate: 2014-07-29 20:11:25\ntags:\n---\n\n**New features:**\n\n*   Ability to start sending video (one way) during an audio call, or stop sending video during a video call\n*   Playing 2 channel audio (note: uTox does not currently support sending 2 channel audio, only receiving)\n*   These changes break compatibility with older clients\n**Bugfixes:**\n\n*   Windows XP fixes: uTox should now work on Windows XP\n*   Audio playback fixes for Android\n*   Fixed a number of segfaults/crashes (mostly Linux-exclusive)\n*   Fixed flickering on Linux when resizing the window ([contribution by mk21](https://github.com/notsecure/uTox/pull/175))\n*   Fixed an issue with the red and blue channels being swapped on inline images\n**Other:**\n\n*   The uTox Updater for Windows has been updated and now has a GUI (the updater has a self update feature and should automatically update itself, please report any issues related to the updater)","slug":"-ce-bctox-updates-0-1-0","updated":1420586788000,"excerpt":"","_id":"kgor98zfhyefl0g3","comments":true,"layout":"post","photos":[],"link":""},{"title":"μTox updates [0.1.3]","id":382,"categories":["8mjo8a20yy8ruzwh"],"date":1408453462000,"tags":[],"content":"<p><strong>New features:</strong></p>\n<ul>\n<li>Network options: IPv6/UDP enable/disable</li>\n<li>SOCKS 5 proxy support (makes it possible to use Tox through Tor)</li>\n<li>Right click menus (Xlib, Windows already had them)</li>\n<li>Option to copy messages without the names (through a right click menu)</li>\n<li>Option to show only online friends</li>\n<li><p>Support for translations<br><strong>Bugfixes:</strong></p>\n</li>\n<li><p>Many small fixes<br><strong>Other:</strong></p>\n</li>\n<li><p>toxcore has a new congestion control algorithm, file transfers should have better performance now</p>\n</li>\n</ul>\n","source":"_posts/-ce-bctox-updates-0-1-3.md","raw":"title: \"μTox updates [0.1.3]\"\nid: 382\ncategories:\n  - μTox\ndate: 2014-08-19 09:04:22\ntags:\n---\n\n**New features:**\n\n*   Network options: IPv6/UDP enable/disable\n*   SOCKS 5 proxy support (makes it possible to use Tox through Tor)\n*   Right click menus (Xlib, Windows already had them)\n*   Option to copy messages without the names (through a right click menu)\n*   Option to show only online friends\n*   Support for translations\n**Bugfixes:**\n\n*   Many small fixes\n**Other:**\n\n*   toxcore has a new congestion control algorithm, file transfers should have better performance now","slug":"-ce-bctox-updates-0-1-3","updated":1420586788000,"excerpt":"","_id":"bdwpdom8zw9xahoa","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.13.0-alpha Release","id":418,"categories":["q5mc6700pzozi6gl"],"date":1411856210000,"tags":[],"content":"<p>Another day another release. This release is probably the biggest in the recent past and there’s some screenshots to go along with it.</p>\n<p>The Login activity has been changed to be given a nice background. Also, instead of having to write the name of your profile, the text box has been swapped for a dropdown list of all the profiles you have created to make logging in a much simpler and quicker process.</p>\n<a id=\"more\"></a>\n\n<img src=\"/images/antox-0-13-0-1.png\">\n\n\n<p>The Create Account activity has also been changed to be given a nice looking background. The weird looking checkbox from before has been turned into an incognito button.</p>\n<img src=\"/images/antox-0-13-0-2.png\">\n\n\n<p>The last design change to take place was to the friend requests. You can now accept and reject them right from the contacts list so you don’t have to bring in the new pane or long hold on them.</p>\n<img src=\"/images/antox-0-13-0-3.png\">\n\n\n<p>Non-design wise, there have been various crash fixes. The app will also wake the CPU when doing network activity to try and keep you online over extended periods of time, and most importantly, you can now send any file in a file transfer, not just attach an image. Lastly, changing the app’s language will no longer require a restart.</p>\n<p>Edit: A couple more things that I forgot I implemented since the last release. The app now comes with Wi-Fi only enabled by default and you can turn this off in the settings if you want to use your mobile connection as well as Wi-Fi. Also, the app comes with TCP only by default which uses less battery and less data (about 50-100mb a day) at the expense of slower file transfers and slightly slower times for friend requests to go through. To speed things up, you can enabled UDP in the settings.</p>\n","source":"_posts/antox-0-13-0-alpha-release.md","raw":"title: Antox 0.13.0-alpha Release\nid: 418\ncategories:\n  - Antox\ndate: 2014-09-27 18:16:50\ntags:\n---\n\nAnother day another release. This release is probably the biggest in the recent past and there's some screenshots to go along with it.\n\nThe Login activity has been changed to be given a nice background. Also, instead of having to write the name of your profile, the text box has been swapped for a dropdown list of all the profiles you have created to make logging in a much simpler and quicker process.\n\n<!-- more -->\n\n{% limg antox-0-13-0-1.png %}\n\n\nThe Create Account activity has also been changed to be given a nice looking background. The weird looking checkbox from before has been turned into an incognito button.\n\n{% limg antox-0-13-0-2.png %}\n\n\nThe last design change to take place was to the friend requests. You can now accept and reject them right from the contacts list so you don't have to bring in the new pane or long hold on them.\n\n{% limg antox-0-13-0-3.png %}\n\n\nNon-design wise, there have been various crash fixes. The app will also wake the CPU when doing network activity to try and keep you online over extended periods of time, and most importantly, you can now send any file in a file transfer, not just attach an image. Lastly, changing the app's language will no longer require a restart.\n\n\nEdit: A couple more things that I forgot I implemented since the last release. The app now comes with Wi-Fi only enabled by default and you can turn this off in the settings if you want to use your mobile connection as well as Wi-Fi. Also, the app comes with TCP only by default which uses less battery and less data (about 50-100mb a day) at the expense of slower file transfers and slightly slower times for friend requests to go through. To speed things up, you can enabled UDP in the settings.\n","slug":"antox-0-13-0-alpha-release","updated":1422148791000,"excerpt":"<p>Another day another release. This release is probably the biggest in the recent past and there’s some screenshots to go along with it.</p>\n<p>The Login activity has been changed to be given a nice background. Also, instead of having to write the name of your profile, the text box has been swapped for a dropdown list of all the profiles you have created to make logging in a much simpler and quicker process.</p>\n","_id":"iq2yyfhgchs0dqzb","comments":true,"layout":"post","photos":[],"link":""},{"title":"Achievement Get: Groupchat Audio","id":561,"categories":["n2ucmyxmms5yv6mr","r8wa1580n6ik5nes","kuvowwllejwt5uh4"],"date":1416071894000,"tags":[],"content":"<p>We’ve been promising it since our inception, and by God that time has finally come. With recent Toxcore commits, alongside implementation in our two leading clients, qTox and uTox, Tox users can now join groupchats and start audio calls.<br><a id=\"more\"></a><br>If you’re currently running either qTox or uTox, we heavily suggest upgrading to the newest versions, as we’ve made great strides recently to implement one of the most requested features of Tox.</p>\n<img src=\"/images/vsrykl.png\">\n\n<p>Here’s an audio sample of a music clip being played over group audio:</p>\n<iframe width=\"100%\" height=\"160\" scrolling=\"no\" frameborder=\"no\" src=\"https://w.soundcloud.com/player/?url=https%3A%2F%2Fsoundcloud.com%2Fplebtier%2Ftox-group-audio&auto_play=false&hide_related=true&show_comments=true&show_user=true&show_reposts=false&color=ff5500&show_artwork=true\"></iframe>\n\n<p>Song: <a href=\"http://cathndadrecords.bandcamp.com/track/london\" target=\"_blank\" rel=\"external\">London by Satan &amp; Megastar</a> Licensed CC-BY 3.0</p>\n","source":"_posts/achievement-get-groupchat-audio.md","raw":"title: \"Achievement Get: Groupchat Audio\"\nid: 561\ncategories:\n  - qTox\n  - Tox Core\n  - μTox\ndate: 2014-11-15 12:18:14\ntags:\n---\n\nWe've been promising it since our inception, and by God that time has finally come. With recent Toxcore commits, alongside implementation in our two leading clients, qTox and uTox, Tox users can now join groupchats and start audio calls. \n<!-- more -->\nIf you're currently running either qTox or uTox, we heavily suggest upgrading to the newest versions, as we've made great strides recently to implement one of the most requested features of Tox.\n{% limg vsrykl.png %}\n\nHere's an audio sample of a music clip being played over group audio:\n{% soundcloud https://soundcloud.com/plebtier/tox-group-audio default %}\n\nSong: [London by Satan & Megastar](http://cathndadrecords.bandcamp.com/track/london) Licensed CC-BY 3.0\n","slug":"achievement-get-groupchat-audio","updated":1420586900000,"excerpt":"<p>We’ve been promising it since our inception, and by God that time has finally come. With recent Toxcore commits, alongside implementation in our two leading clients, qTox and uTox, Tox users can now join groupchats and start audio calls.<br>","_id":"pbjxv2j5cn2dl2r0","comments":true,"layout":"post","photos":[],"link":""},{"title":"A Quick Overlook at Tox's Mission","id":103,"categories":["nlwrm5tlcr1n8dpi"],"date":1395016123000,"tags":[],"content":"<div class=\"video-container\"><iframe src=\"//www.youtube.com/embed/9Q4uoIjk3RA\" frameborder=\"0\" allowfullscreen></iframe></div>\n","source":"_posts/a-quick-overlook-at-toxs-mission.md","raw":"title: \"A Quick Overlook at Tox's Mission\"\nid: 103\ncategories:\n  - Tox Core\ndate: 2014-03-16 20:28:43\ntags:\n---\n\n{% youtube 9Q4uoIjk3RA %}\n","slug":"a-quick-overlook-at-toxs-mission","updated":1422148791000,"excerpt":"","_id":"vrdf24pa6lzm5on7","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.6.1 Released","id":74,"categories":["q5mc6700pzozi6gl"],"date":1394698185000,"tags":[],"content":"<p>We don’t normally push two APKs to Google Play in one day, but the recent commits urged us to do so. Various bugs that prevented a pleasant user experience were discovered and appropriately fixed. The total changes include:</p>\n<ul>\n<li>Updating status icons</li>\n<li>Properly fixing UI not updating on friend requests</li>\n<li>Move QR codes back to external storage so they may be shared<br>That’s it. Sorry for the double-update folks!</li>\n</ul>\n","source":"_posts/antox-0-6-1-released.md","raw":"title: Antox 0.6.1 Released\nid: 74\ncategories:\n  - Antox\ndate: 2014-03-13 04:09:45\ntags:\n---\n\nWe don't normally push two APKs to Google Play in one day, but the recent commits urged us to do so. Various bugs that prevented a pleasant user experience were discovered and appropriately fixed. The total changes include:\n\n*   Updating status icons\n*   Properly fixing UI not updating on friend requests\n*   Move QR codes back to external storage so they may be shared\nThat's it. Sorry for the double-update folks!","slug":"antox-0-6-1-released","updated":1422148791000,"excerpt":"","_id":"xetw5l7jlqrmvtoy","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.4 Released","id":46,"categories":["q5mc6700pzozi6gl"],"date":1394549607000,"tags":[],"content":"<p>Those who have joined the Antox Alpha Test Group will find an update arriving fairly soon. The changes include commit 8076421: “history loads instantly rather than waiting for a message to be sent”. Very minor changes since 0.3 but still a change nonetheless.</p>\n<img src=\"/images/antox-0-4-app-info.png\">","source":"_posts/antox-0-4-pushed-to-google-play.md","raw":"title: Antox 0.4 Released\nid: 46\ncategories:\n  - Antox\ndate: 2014-03-11 10:53:27\ntags:\n---\n\nThose who have joined the Antox Alpha Test Group will find an update arriving fairly soon. The changes include commit 8076421: \"history loads instantly rather than waiting for a message to be sent\". Very minor changes since 0.3 but still a change nonetheless.\n\n{% limg antox-0-4-app-info.png %}","slug":"antox-0-4-pushed-to-google-play","updated":1422148791000,"excerpt":"","_id":"8mrab8zs938edeed","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.6.5 Released","id":110,"categories":["q5mc6700pzozi6gl"],"date":1395029878000,"tags":[],"content":"<p>Let’s just rename this blog to the Antox development blog.</p>\n<p>Antox 0.6.5 is out and, like yesterday, with only minor changes that are mostly cosmetic. The total changes are:</p>\n<ul>\n<li>Change receipt icons to something less arbitrary</li>\n<li>Updated Italian translation</li>\n<li>Updated German translation</li>\n<li>Add Turkish translation</li>\n<li>Timestamps of messages now update based on the local time of your device</li>\n<li>Antox now waits to fully load the database information before accepting input. This may result in about a 1 second delay in starting the app, but it prevents force closing by a user interacting too quickly.</li>\n<li>Deleted chat threads are now removed from the interface immediately<br>That’s it for today! Unfortunately, Google’s Developer Console seems to be down so it might take awhile. If you want to see the changes immediately without having to wait, you can download the<a href=\"http://vexx.us/Clients/Antox/antox-0.6.5.apk\" target=\"_blank\" rel=\"external\"> APK here.</a> The update is signed with the same keys used for Google Play, which means it can’t be spoofed.</li>\n</ul>\n","source":"_posts/antox-0-6-5-released.md","raw":"title: Antox 0.6.5 Released\nid: 110\ncategories:\n  - Antox\ndate: 2014-03-17 00:17:58\ntags:\n---\n\nLet's just rename this blog to the Antox development blog.\n\nAntox 0.6.5 is out and, like yesterday, with only minor changes that are mostly cosmetic. The total changes are:\n\n*   Change receipt icons to something less arbitrary\n*   Updated Italian translation\n*   Updated German translation\n*   Add Turkish translation\n*   Timestamps of messages now update based on the local time of your device\n*   Antox now waits to fully load the database information before accepting input. This may result in about a 1 second delay in starting the app, but it prevents force closing by a user interacting too quickly.\n*   Deleted chat threads are now removed from the interface immediately\nThat's it for today! Unfortunately, Google's Developer Console seems to be down so it might take awhile. If you want to see the changes immediately without having to wait, you can download the[ APK here.](http://vexx.us/Clients/Antox/antox-0.6.5.apk) The update is signed with the same keys used for Google Play, which means it can't be spoofed.","slug":"antox-0-6-5-released","updated":1420586899000,"excerpt":"","_id":"h9rpapqzo0ch2zpf","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.6.3 Released","id":88,"categories":["q5mc6700pzozi6gl"],"date":1394851707000,"tags":[],"content":"<p>An update has been pushed to the Google Play Alpha Testing Group with a brand-spankin’ new APK.</p>\n<p>This update focuses more on aesthetics, with most changes relating to animation-smoothing, notification polishing, and ActionBar backward compatibility. Delivery and read receipts were also added, but will receive a face-lift very shortly. To those who may experience Antox crashing when selecting a friend, re-installing the app will usually fix the problem. If not, please open an issue on GitHub and we’ll get it sorted out.</p>\n<p>A new permission (Android.VIBRATE) has been added. You will have to manually update the app through Google Play, as permission changes, no matter how minor, require your approval. This permission was necessary, as notifications now have permission to vibrate your phone when the screen is off.</p>\n<p>Thanks for being apart of the Alpha Test Group, your feedback is always appreciated.</p>\n","source":"_posts/antox-0-6-3-released.md","raw":"title: Antox 0.6.3 Released\nid: 88\ncategories:\n  - Antox\ndate: 2014-03-14 22:48:27\ntags:\n---\n\nAn update has been pushed to the Google Play Alpha Testing Group with a brand-spankin' new APK.\n\nThis update focuses more on aesthetics, with most changes relating to animation-smoothing, notification polishing, and ActionBar backward compatibility. Delivery and read receipts were also added, but will receive a face-lift very shortly. To those who may experience Antox crashing when selecting a friend, re-installing the app will usually fix the problem. If not, please open an issue on GitHub and we'll get it sorted out.\n\nA new permission (Android.VIBRATE) has been added. You will have to manually update the app through Google Play, as permission changes, no matter how minor, require your approval. This permission was necessary, as notifications now have permission to vibrate your phone when the screen is off.\n\nThanks for being apart of the Alpha Test Group, your feedback is always appreciated.","slug":"antox-0-6-3-released","updated":1420586899000,"excerpt":"","_id":"31h5i3rwfa7aifhl","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.6.4 Released","id":97,"categories":["q5mc6700pzozi6gl"],"date":1394930051000,"tags":[],"content":"<p>With our main developer, Astonex out on vacation for this week, not many changes have been made since yesterday. Those currently enrolled in the ATG will be receiving 0.6.4 with two small, cosmetic changes within the next few hours. These changes include:</p>\n<ul>\n<li>A fix on the timestamp not appearing in the ChatFragment (pull out menu, where your contacts are)</li>\n<li>Adding a missing space in the dialog window when you long-press a contact<br>*<br>Happy (An)Toxing! As always, your feedback is welcomed.</li>\n</ul>\n","source":"_posts/antox-0-6-4-released.md","raw":"title: Antox 0.6.4 Released\nid: 97\ncategories:\n  - Antox\ndate: 2014-03-15 20:34:11\ntags:\n---\n\nWith our main developer, Astonex out on vacation for this week, not many changes have been made since yesterday. Those currently enrolled in the ATG will be receiving 0.6.4 with two small, cosmetic changes within the next few hours. These changes include:\n\n*   A fix on the timestamp not appearing in the ChatFragment (pull out menu, where your contacts are)\n*   Adding a missing space in the dialog window when you long-press a contact\n*\nHappy (An)Toxing! As always, your feedback is welcomed.","slug":"antox-0-6-4-released","updated":1422148791000,"excerpt":"","_id":"nayo66iulovgsjbu","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.7 Released","id":165,"categories":["q5mc6700pzozi6gl"],"date":1395674783000,"tags":[],"content":"<p>We’ve finally arrived at a new version of Antox after a period of slow development. With this release comes two new major features, as well as a myriad of small bug fixes and slight changes not worth mentioning.</p>\n<p><strong>New Features</strong></p>\n<ol>\n<li>Your friends now have profiles, just long hold on them to access it. The profiles contain all your friend’s information including a QR image of their Tox key for easier sharing amongst your social group.</li>\n<li><p>You can now give your friends nicknames/aliases to easier identify your friend. This can be set when adding them for the first time, and later updated in their profile. Clearing their alias altogether will return to displaying their Tox nickname.<br><strong>Upcoming Features in the Next Release</strong></p>\n</li>\n<li><p>Typing indicators to show when your friends are writing to you. You’ll also send a typing status to your friends. These indicators will be a setting so you can turn them off should you wish to do so.</p>\n</li>\n<li>Manually set your language. Currently you will be shown translated strings automatically if they exist based upon your locale, however to give you more control a setting will also be added to let you change the language.</li>\n<li>Welcome Tour to show off all the Antox features and gently introduce new users to Tox itself.</li>\n<li>Continued effort like always to fix the disconnects and any crashes.<br>You can get the updated APKs as always from <a href=\"http://download.tox.im\" target=\"_blank\" rel=\"external\">here</a></li>\n</ol>\n","source":"_posts/antox-0-7-released.md","raw":"title: Antox 0.7 Released\nid: 165\ncategories:\n  - Antox\ndate: 2014-03-24 11:26:23\ntags:\n---\n\nWe've finally arrived at a new version of Antox after a period of slow development. With this release comes two new major features, as well as a myriad of small bug fixes and slight changes not worth mentioning.\n\n**New Features**\n\n1.  Your friends now have profiles, just long hold on them to access it. The profiles contain all your friend's information including a QR image of their Tox key for easier sharing amongst your social group.\n2.  You can now give your friends nicknames/aliases to easier identify your friend. This can be set when adding them for the first time, and later updated in their profile. Clearing their alias altogether will return to displaying their Tox nickname.\n**Upcoming Features in the Next Release**\n\n1.  Typing indicators to show when your friends are writing to you. You'll also send a typing status to your friends. These indicators will be a setting so you can turn them off should you wish to do so.\n2.  Manually set your language. Currently you will be shown translated strings automatically if they exist based upon your locale, however to give you more control a setting will also be added to let you change the language.\n3.  Welcome Tour to show off all the Antox features and gently introduce new users to Tox itself.\n4.  Continued effort like always to fix the disconnects and any crashes.\nYou can get the updated APKs as always from [here](http://download.tox.im)","slug":"antox-0-7-released","updated":1420586788000,"excerpt":"","_id":"rqhp487k0xp3g73x","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.5 Released ","id":54,"categories":["q5mc6700pzozi6gl"],"date":1394599737000,"tags":[],"content":"<p>Another day, another release with 40+ changes and bug fixes. A summary of the main changes are given below,</p>\n<ol>\n<li>You can no longer add the same friend multiple times</li>\n<li>An exclamation mark is added to friends on a new message</li>\n<li>If you change your user key, the QR image should properly update as well</li>\n<li>Fixed truncating the last letter of strings in names, messages etc.</li>\n<li>User is alerted to no internet connectivity when using Antox</li>\n<li>Italian and German translations updated<br>The updated APK will take a while to propagate through the Google servers but you should be receiving it shortly. As always, if you find a bug please report it on the Github issues page so it can be fixed. Please submit Google crash reports as well when possible.</li>\n</ol>\n","source":"_posts/antox-0-5-released.md","raw":"title: \"Antox 0.5 Released \"\nid: 54\ncategories:\n  - Antox\ndate: 2014-03-12 00:48:57\ntags:\n---\n\nAnother day, another release with 40+ changes and bug fixes. A summary of the main changes are given below,\n\n1.  You can no longer add the same friend multiple times\n2.  An exclamation mark is added to friends on a new message\n3.  If you change your user key, the QR image should properly update as well\n4.  Fixed truncating the last letter of strings in names, messages etc.\n5.  User is alerted to no internet connectivity when using Antox\n6.  Italian and German translations updated\nThe updated APK will take a while to propagate through the Google servers but you should be receiving it shortly. As always, if you find a bug please report it on the Github issues page so it can be fixed. Please submit Google crash reports as well when possible.","slug":"antox-0-5-released","updated":1420586788000,"excerpt":"","_id":"fxsensx3tpe1y5me","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox 0.6 Released","id":65,"categories":["q5mc6700pzozi6gl"],"date":1394676826000,"tags":[],"content":"<p>An update to Antox has been released to the Google Play Alpha Testing group. This update includes notifications, a redesigned ActionBar, new launcher icon, and various other changes such as storing all Tox data on internal storage, rather than the SD card if one existed.</p>\n<p>Changes:</p>\n<ul>\n<li>Icon updated</li>\n<li>ActivityBar now a dark blue/green</li>\n<li>Option to clear chat after deleting a user from the friend list</li>\n<li>Notifications of messages when not in app</li>\n<li>Moved QR code and Tox datafile to internal storage</li>\n<li>QR codes are now checked to ensure they match your Tox ID (previously, if you uninstalled, and then reinstalled Antox, your Tox ID change but your QR code wouldn’t have updated. This change fixes that)</li>\n<li>Alert user if there is no network connection</li>\n<li>Verify the connection to the bootstrap server is completed upon startup.</li>\n<li>Chat messaging debugged heavily<br>The updated APK will take a while to propagate through the Google servers but you should be receiving it shortly. As always, if you find a bug please report it on the Github issues page so it can be fixed. Please submit Google crash reports as well when possible.</li>\n</ul>\n","source":"_posts/antox-0-6-released.md","raw":"title: Antox 0.6 Released\nid: 65\ncategories:\n  - Antox\ndate: 2014-03-12 22:13:46\ntags:\n---\n\nAn update to Antox has been released to the Google Play Alpha Testing group. This update includes notifications, a redesigned ActionBar, new launcher icon, and various other changes such as storing all Tox data on internal storage, rather than the SD card if one existed.\n\nChanges:\n\n*   Icon updated\n*   ActivityBar now a dark blue/green\n*   Option to clear chat after deleting a user from the friend list\n*   Notifications of messages when not in app\n*   Moved QR code and Tox datafile to internal storage\n*   QR codes are now checked to ensure they match your Tox ID (previously, if you uninstalled, and then reinstalled Antox, your Tox ID change but your QR code wouldn't have updated. This change fixes that)\n*   Alert user if there is no network connection\n*   Verify the connection to the bootstrap server is completed upon startup.\n*   Chat messaging debugged heavily\nThe updated APK will take a while to propagate through the Google servers but you should be receiving it shortly. As always, if you find a bug please report it on the Github issues page so it can be fixed. Please submit Google crash reports as well when possible.\n","slug":"antox-0-6-released","updated":1422148791000,"excerpt":"","_id":"qq49u1qn7dws1j0m","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox + Jenkins","id":146,"categories":["q5mc6700pzozi6gl","6t0r8iadxh2f1p31"],"date":1395297017000,"tags":[],"content":"<p>Just a quick post, we’ve finally got Antox working on<a href=\"http://http://jenkins.tox.im/job/Android-Antox\" target=\"_blank\" rel=\"external\"> Jenkins</a>.</p>\n<p>Antox downloads from our <a href=\"http://download.tox.im\" title=\"download.tox.im\" target=\"_blank\" rel=\"external\">download.tox.im</a> site are now built up to the commit, with no more than a 10 minute delay after irungentoo or Astonex push a commit.</p>\n<p>Also note that the gplay signing key is going to change, and will share one with the Jenkins build.</p>\n<p>The latest Antox apk is also always available <a href=\"https://c1cf.https.cdn.softlayer.net/80C1CF/192.254.75.110:8080/job/Android-Antox/lastSuccessfulBuild/artifact/antox.apk\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<p>Note: I <em>just</em> noticed <a href=\"https://blog.libtoxcore.so/141/antox-nightly-builds-google-play-store\" target=\"_blank\" rel=\"external\">this.</a></p>\n","source":"_posts/antox-jenkins.md","raw":"title: Antox + Jenkins\nid: 146\ncategories:\n  - Antox\n  - Jenkins\ndate: 2014-03-20 02:30:17\ntags:\n---\n\nJust a quick post, we've finally got Antox working on[ Jenkins](http://http://jenkins.tox.im/job/Android-Antox).\n\nAntox downloads from our [download.tox.im](http://download.tox.im \"download.tox.im\") site are now built up to the commit, with no more than a 10 minute delay after irungentoo or Astonex push a commit.\n\nAlso note that the gplay signing key is going to change, and will share one with the Jenkins build.\n\nThe latest Antox apk is also always available [here](https://c1cf.https.cdn.softlayer.net/80C1CF/192.254.75.110:8080/job/Android-Antox/lastSuccessfulBuild/artifact/antox.apk).\n\nNote: I _just_ noticed [this.](https://blog.libtoxcore.so/141/antox-nightly-builds-google-play-store)","slug":"antox-jenkins","updated":1422148791000,"excerpt":"","_id":"f6jncan4z3rrztb8","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox Nightly Builds & Google Play Store","id":141,"categories":["q5mc6700pzozi6gl"],"date":1395286959000,"tags":[],"content":"<p>You can now finally get up to date Antox releases on the <a href=\"http://wiki.tox.im/binaries\" target=\"_blank\" rel=\"external\">Tox Downloads</a> page. These APKs are updated automagically every time there’s a change to Antox or the Tox core, which is usually several times a day.</p>\n<p>This comes just in time as unfortunately we’ve had to pull Antox from the Google Play Store Alpha. This is due to a technical mishap with our key signing. Check back here and the current Google+ group for more news on how we fix this.</p>\n<p>Lastly as a small note, you can now get bitcoins for your commits to Antox thanks to anonymous doners on <a href=\"http://tip4commit.com/projects/654\" target=\"_blank\" rel=\"external\">tip4commit</a>.</p>\n","source":"_posts/antox-nightly-builds-google-play-store.md","raw":"title: \"Antox Nightly Builds & Google Play Store\"\nid: 141\ncategories:\n  - Antox\ndate: 2014-03-19 23:42:39\ntags:\n---\n\nYou can now finally get up to date Antox releases on the [Tox Downloads](http://wiki.tox.im/binaries) page. These APKs are updated automagically every time there's a change to Antox or the Tox core, which is usually several times a day.\n\nThis comes just in time as unfortunately we've had to pull Antox from the Google Play Store Alpha. This is due to a technical mishap with our key signing. Check back here and the current Google+ group for more news on how we fix this.\n\nLastly as a small note, you can now get bitcoins for your commits to Antox thanks to anonymous doners on [tip4commit](http://tip4commit.com/projects/654).","slug":"antox-nightly-builds-google-play-store","updated":1422148791000,"excerpt":"","_id":"met1gpa2ggqplg37","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox v0.12 released","id":371,"categories":["q5mc6700pzozi6gl"],"date":1408306314000,"tags":[],"content":"<p><strong>Edit:</strong> <span style=\"color: #000000;\">There seems to be a problem of crashing when registering (both skipping and not skipping). I’d recommend not upgrading just yet and I’ll try and get it fixed by the end of the week. Sorry for the wait</span></p>\n<p>It’s been a long time since I’ve written a blog post for a release of Antox but I felt with the major changes in this version, it would be best if I did.</p>\n<p>The major change in this release which may cause confusion is the introduction of an account system. When you create an account, it assigns the account a new tox id as well as its own friends list and chat logs, so that you can easily create and manage multiple identities from the same application. You just logout of one account, and login to another to swap tox id’s. No hassle in dragging tox save files about. It also takes the account name and registers it on <a href=\"https://toxme.se\" target=\"_blank\" rel=\"external\">https://toxme.se</a> so that others can add you using just the account name. If you don’t want to be signed up on toxme, you should tick “skip registration” in the registration screen. I’ve taken these steps to try and make the application extremely easy to use. Regular users are used to creating accounts and having people add that account name and this is what I’m trying to emulate for tox. Hopefully others like the changes I’ve made and that other clients follow so that the experience is the same across all platforms.</p>\n<p>Some other notable changes are:</p>\n<ul>\n<li>Nicer looking tabs in the main section</li>\n<li>You can now accept and reject file transfers</li>\n<li>File transfer speed is now displayed</li>\n<li>Better ordering and searching of the contacts list</li>\n<li>The Tox ID can now be found under the ‘Advanced’ tab of Settings<br>We will soon have A/V in antox as well. The functions have already been wrapped in jToxCore and are just being proof-read as we speak to make sure it’s correct. Once merged and ready, audio is the first function I want to get into antox.</li>\n</ul>\n<p><strong>Edit: </strong>If you tick “skip registration” an account name is still required so that multiple tox id’s can be used. It uses the account name you entered as the file name for the tox save so that when you login, it loads the appropriate tox id</p>\n","source":"_posts/antox-v0-12-released.md","raw":"title: Antox v0.12 released\nid: 371\ncategories:\n  - Antox\ndate: 2014-08-17 16:11:54\ntags:\n---\n\n**Edit:** <span style=\"color: #000000;\">There seems to be a problem of crashing when registering (both skipping and not skipping). I'd recommend not upgrading just yet and I'll try and get it fixed by the end of the week. Sorry for the wait</span>\n\nIt's been a long time since I've written a blog post for a release of Antox but I felt with the major changes in this version, it would be best if I did.\n\nThe major change in this release which may cause confusion is the introduction of an account system. When you create an account, it assigns the account a new tox id as well as its own friends list and chat logs, so that you can easily create and manage multiple identities from the same application. You just logout of one account, and login to another to swap tox id's. No hassle in dragging tox save files about. It also takes the account name and registers it on [https://toxme.se](https://toxme.se) so that others can add you using just the account name. If you don't want to be signed up on toxme, you should tick \"skip registration\" in the registration screen. I've taken these steps to try and make the application extremely easy to use. Regular users are used to creating accounts and having people add that account name and this is what I'm trying to emulate for tox. Hopefully others like the changes I've made and that other clients follow so that the experience is the same across all platforms.\n\nSome other notable changes are:\n\n*   Nicer looking tabs in the main section\n*   You can now accept and reject file transfers\n*   File transfer speed is now displayed\n*   Better ordering and searching of the contacts list\n*   The Tox ID can now be found under the 'Advanced' tab of Settings\nWe will soon have A/V in antox as well. The functions have already been wrapped in jToxCore and are just being proof-read as we speak to make sure it's correct. Once merged and ready, audio is the first function I want to get into antox.\n\n**Edit: **If you tick \"skip registration\" an account name is still required so that multiple tox id's can be used. It uses the account name you entered as the file name for the tox save so that when you login, it loads the appropriate tox id","slug":"antox-v0-12-released","updated":1422148791000,"excerpt":"","_id":"gt2kt6b8imos8i5d","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox v0.8.1-alpha Released","id":213,"categories":["q5mc6700pzozi6gl"],"date":1396513786000,"tags":[],"content":"<p>A new version of Antox has been released with the following changes:</p>\n<ul>\n<li>Filter the friends list by groups e.g. Online, Offline.</li>\n<li>You can now block friends so that you no longer receive messages or friend requests from them. As well as this, neither of you will see each other come online.</li>\n<li>Friends can now be added using the Tox DNS Discovery Version 1 and Version 2. For more information, see the <a href=\"https://blog.libtoxcore.so/182/introducing-sts-single-tox-standard\" target=\"_blank\" rel=\"external\">STS</a>. This is a very technical feature at the moment but in the feature it will mean you can add each other with usernames once some more things have been ironed out.</li>\n<li>You can manually set your language in the settings window should the default language picked for you by Android not suffice.</li>\n<li>A Russian translation has been added to Antox.</li>\n<li><p>Improved and more efficient backend to help reduce network connection issues<br><strong>Still to come in new releases</strong></p>\n</li>\n<li><p>Typing indicators and a welcome tour (I promised these in the last blog post)</p>\n</li>\n<li>Ability to create custom groups which you can then assign friends to<br><strong>Antox is now on F-Droid</strong></li>\n</ul>\n<p>Since the last release, you can now get Antox on F-Droid by adding <a href=\"http://markwinter.me/fdroid/repo\" target=\"_blank\" rel=\"external\">http://markwinter.me/fdroid/repo</a> to your repo list. To do this, go to ‘Manage Repos’ in F-Droid. These will only be updated with every major release (or when a bug is fixed) rather than with every slight change.</p>\n","source":"_posts/antox-v0-8-1-alpha-released.md","raw":"title: Antox v0.8.1-alpha Released\nid: 213\ncategories:\n  - Antox\ndate: 2014-04-03 04:29:46\ntags:\n---\n\nA new version of Antox has been released with the following changes:\n\n*   Filter the friends list by groups e.g. Online, Offline.\n*   You can now block friends so that you no longer receive messages or friend requests from them. As well as this, neither of you will see each other come online.\n*   Friends can now be added using the Tox DNS Discovery Version 1 and Version 2\\. For more information, see the [STS](https://blog.libtoxcore.so/182/introducing-sts-single-tox-standard). This is a very technical feature at the moment but in the feature it will mean you can add each other with usernames once some more things have been ironed out.\n*   You can manually set your language in the settings window should the default language picked for you by Android not suffice.\n*   A Russian translation has been added to Antox.\n*   Improved and more efficient backend to help reduce network connection issues\n**Still to come in new releases**\n\n*   Typing indicators and a welcome tour (I promised these in the last blog post)\n*   Ability to create custom groups which you can then assign friends to\n**Antox is now on F-Droid**\n\nSince the last release, you can now get Antox on F-Droid by adding http://markwinter.me/fdroid/repo to your repo list. To do this, go to 'Manage Repos' in F-Droid. These will only be updated with every major release (or when a bug is fixed) rather than with every slight change.\n","slug":"antox-v0-8-1-alpha-released","updated":1422148791000,"excerpt":"","_id":"iaumx32v8u8aihk0","comments":true,"layout":"post","photos":[],"link":""},{"title":"Apt & Yum Repos Now Available for Venom","id":320,"categories":["n2ucmyxmms5yv6mr","kie9urux6vjaal4v"],"date":1406878761000,"tags":[],"content":"<p>It’s been a long timesince we’ve starting packaging Venom builds as .deb and .rpm, but they never made it into their own repository’s. Today, that changes. For those of you who’ve wanted to install and update your Tox clients via your built-in package manager, your dream has come true.</p>\n<h3 id=\"Apt/Aptitude_(Debian,_Ubuntu,_Mint,_etc-)\">Apt/Aptitude (Debian, Ubuntu, Mint, etc.)</h3>\n<p>If you want to set the repo up under Debian or any of its’ derivatives, simply run <code>wget https://repo.tox.im/tox-apt.sh &amp;&amp; sudo chmod +x ./tox-apt.sh &amp;&amp; ./tox-apt.sh</code> in your favorite terminal and then <code>apt-get install venom</code>.<br>If you want to update venom, simply run <code>apt-get update &amp;&amp; apt-get upgrade</code></p>\n<h3 id=\"Yum_(Fedora,_CentOS,_RHEL,_etc-)\">Yum (Fedora, CentOS, RHEL, etc.)</h3>\n<p>Simply add <code>https://repo.tox.im/tox.repo</code> to your repo list, and then <code>yum install venom</code></p>\n","source":"_posts/apt-yum-repos-now-available-for-venom.md","raw":"title: \"Apt & Yum Repos Now Available for Venom\"\nid: 320\ncategories:\n  - qTox\n  - Venom\ndate: 2014-08-01 03:39:21\ntags:\n---\n\nIt's been a long timesince we've starting packaging Venom builds as .deb and .rpm, but they never made it into their own repository's. Today, that changes. For those of you who've wanted to install and update your Tox clients via your built-in package manager, your dream has come true.\n\n### Apt/Aptitude (Debian, Ubuntu, Mint, etc.) \n\nIf you want to set the repo up under Debian or any of its' derivatives, simply run `wget https://repo.tox.im/tox-apt.sh && sudo chmod +x ./tox-apt.sh && ./tox-apt.sh` in your favorite terminal and then `apt-get install venom`.\nIf you want to update venom, simply run `apt-get update && apt-get upgrade`\n\n### Yum (Fedora, CentOS, RHEL, etc.) \n\nSimply add `https://repo.tox.im/tox.repo` to your repo list, and then `yum install venom`","slug":"apt-yum-repos-now-available-for-venom","updated":1422148791000,"excerpt":"","_id":"jfwhpdn103yty7yx","comments":true,"layout":"post","photos":[],"link":""},{"title":"The joys of build systems, and the future of Toxic","id":87,"categories":["ysh4ufalq2ulbpz8"],"date":1395033572000,"tags":[],"content":"<p>In a time long ago Tox used cmake.</p>\n<p>Cmake was first purely because it matched our goals, sort of. It provided a nice run everywhere interface that the average person who compiled the then build only Tox could use without issues. Cmake wasn’t all golden though, maintaining it was a sea of unneeded complexities and overkill, too much for the average developer to deal with for the size of Tox. While this wasn’t a major issue, one developer took it on himself to switch to autotools, with the promise that he’d maintain it.</p>\n<p> Toxic starts to look all pretty</p>\n<p>Our first client, the API test, was nTox. Not long after, Toxic followed. Toxic was pretty client in core, composed of a couple files and real ui, development on it skyrocketed. It wasn’t long till Toxic was a fully featured client, almost like the shiny new GUI clients in development. I had a crazy idea that ended up perfect with the timing, moving Toxic from a part of core to its own repo, Tox/toxic. When this happened, autotools were inherited over, as they were an accepted part of core.</p>\n<p>That’s cool, what about the future of Toxic?</p>\n<p>And now, the fun part. A couple days ago IRIXuser and myself were talking about the GSoC project on a replacement build system, we wanted something smooth and easy, without unneeded complexities. (We’re a dozen files and headers, after all.) We stumbled upon <a href=\"http://hypertriton.com/bsdbuild/\" title=\"BSDBuild\" target=\"_blank\" rel=\"external\">BSDBuild</a>, a simple build system based off 4.4BSD make libraries. A bit of look in to it and we discovered that it was easy. Like <em>very easy</em>. The entire system for end users was a configure that someone editing it generated and a Makefile made by hand. This was something our iOS developer could understand without a learning curve, with a quick glance.</p>\n<p>4.4BSD? iOS? But I use Linux!</p>\n<p>Before I go any further, I’ll take a moment to explain how the existing build system works, what users see, and how BSDBuild works. GNU autotools is composed of about 7 separate binaries and 8 files, though for this I’ll focus on just the ones Toxic used. To compile Toxic, the entire set of autotools binaries is required, along with a GNU make. A user installs all of these and runs autoreconf -i to generate configure. This process takes around 13 seconds. Afterwards the user runs the configure, making the compiled Makefile in the process. This process takes about 12 seconds. Afterwards the user runs make and make install, building the program. BSDBuild is based off 4.4BSD make libraries, built around a standard POSIX bourne shell and makefile. The developers provide the configure and Makefile, who are interpreted, and not system specific. To compile BSDBuild Toxic, a user installs zero extra files, as the configure is provided. a user runs the configure we provide, generating a Makefile.config. This process takes around 4 seconds. Afterwards the user uses make to compile and install like normal.</p>\n<p>What could be so wrong with GNU autotools?</p>\n<p>The design of autotools is an over complex one, composed of m4, marcos, and dozens of files and commands. This results in a slow and bloated install process for users, along with something that even developers who have been using it <em>for decades </em><a href=\"http://esr.ibiblio.org/?p=1877\" title=\"still run in to undefined behavior.\" target=\"_blank\" rel=\"external\">still run in to undefined behavior</a>. The result of this means that things like —disable-av being <a href=\"https://github.com/Tox/toxic/pull/100\" target=\"_blank\" rel=\"external\">broken</a> go unnoticed, without support for things like —enable-debug (A BSDBuild specific flag we implemented with ease). From an end user perspective, this means a configure process that takes 9 times longer and lacks features, requiring more software installed.</p>\n<p>But BSDBuild couldn’t be perfect, I mean you <strong>did</strong> drop cmake!</p>\n<p>One of the major issues with BSDBuild is that support for checks (REQUIRE(toxcore) can’t be done without making them first. Thankfully, the design of the pm file used for a check is so simple, we had toxcore, toxav, sodium, and openal done in half an hour. Since configure is provided by us, this means no extra work for the end user. Now, BSDBuild does have some other side effects, developers editing either configure.in or Makefile (The entire BSDBuild) do need to have BSDBuild installed, in order to run the mkconfigure command.</p>\n<p>BSDBuild doesn’t work on GNU/HURD, right?</p>\n<p>Wrong! Something to consider is that while BSD Makefiles run on GNU make, GNU Makefiles may not run on BSD make. While GNU autotools produce GNU Makefiles, the POSIX compliant BSDBuild files are more supported on more platforms than the autotools equivalent, going as far as supporting making Visual Studio and DOS Watcom projects, despite Toxic not running on Windows.</p>\n<p>Reactions</p>\n<p>Reactions to BSDBuild have been mixed, while the autotools maintainer has made some rather ignorant remarks about the compile process with BSDBuild, stating that perl is required (It is not), we do forgive him, BSDBuild isn’t a well known system. A few people have stated that the work was a bit of a waste of time, autotools is working. We disagree with this ideology, something like this might seem trivial in the short term, though the ease of use will aide future Toxic developers and helping them focus on the code, and not the build system.</p>\n<p>The last group of people have been supportive, these have generally been users of more popular and more exotic systems, from praising the easy debugging, to the following:</p>\n<blockquote>\n<p>&lt;rhaps0dy&gt; so, uhm</p>\n<p>&lt;rhaps0dy&gt; where do I get the BSDBuild version of libtoxcore?</p>\n<p>&lt;LordAro&gt; rhaps0dy: there isn’t one</p>\n<p>&lt;LordAro&gt; only toxic has a bsdbuild build system so far</p>\n<p>&lt;LordAro&gt; and that’s not in master until people can be convinced that it’s “a good thing” (tm)</p>\n<p>&lt;rhaps0dy&gt; :/</p>\n<p>&lt;LordAro&gt; (which it is)</p>\n<p>&lt;rhaps0dy&gt; I agree lol</p>\n</blockquote>\n<p>Why isn’t this in master yet?</p>\n<p>With a couple of the reactions coming from other developers who I do like, I would greatly like them to try the system out, explore it a bit, get some honest feedback. As of now, this has not happened, though I do try to push them whenever I can. As well, being new, the new build system may have a couple of quirks that we would really like to get out first. When the time comes I’ll merge the branch in to master, just not right now.</p>\n<p>I encourage you to try it now, tell me what works, what doesn’t work, and most of all, your thoughts on this pending switch.</p>\n<p>Testing it is easy, just do a new clone of Toxic, specifying the bsdmake branch: <code>git clone https://github.com/Tox/toxic -b bsdmake</code></p>\n","source":"_posts/build-systems-yo.md","raw":"title: \"The joys of build systems, and the future of Toxic\"\nid: 87\ncategories:\n  - Toxic\ndate: 2014-03-17 01:19:32\ntags:\n---\n\nIn a time long ago Tox used cmake.\n\nCmake was first purely because it matched our goals, sort of. It provided a nice run everywhere interface that the average person who compiled the then build only Tox could use without issues. Cmake wasn't all golden though, maintaining it was a sea of unneeded complexities and overkill, too much for the average developer to deal with for the size of Tox. While this wasn't a major issue, one developer took it on himself to switch to autotools, with the promise that he'd maintain it.\n\n Toxic starts to look all pretty\n\nOur first client, the API test, was nTox. Not long after, Toxic followed. Toxic was pretty client in core, composed of a couple files and real ui, development on it skyrocketed. It wasn't long till Toxic was a fully featured client, almost like the shiny new GUI clients in development. I had a crazy idea that ended up perfect with the timing, moving Toxic from a part of core to its own repo, Tox/toxic. When this happened, autotools were inherited over, as they were an accepted part of core.\n\nThat's cool, what about the future of Toxic?\n\nAnd now, the fun part. A couple days ago IRIXuser and myself were talking about the GSoC project on a replacement build system, we wanted something smooth and easy, without unneeded complexities. (We're a dozen files and headers, after all.) We stumbled upon [BSDBuild](http://hypertriton.com/bsdbuild/ \"BSDBuild\"), a simple build system based off 4.4BSD make libraries. A bit of look in to it and we discovered that it was easy. Like _very easy_. The entire system for end users was a configure that someone editing it generated and a Makefile made by hand. This was something our iOS developer could understand without a learning curve, with a quick glance.\n\n4.4BSD? iOS? But I use Linux!\n\nBefore I go any further, I'll take a moment to explain how the existing build system works, what users see, and how BSDBuild works. GNU autotools is composed of about 7 separate binaries and 8 files, though for this I'll focus on just the ones Toxic used. To compile Toxic, the entire set of autotools binaries is required, along with a GNU make. A user installs all of these and runs autoreconf -i to generate configure. This process takes around 13 seconds. Afterwards the user runs the configure, making the compiled Makefile in the process. This process takes about 12 seconds. Afterwards the user runs make and make install, building the program. BSDBuild is based off 4.4BSD make libraries, built around a standard POSIX bourne shell and makefile. The developers provide the configure and Makefile, who are interpreted, and not system specific. To compile BSDBuild Toxic, a user installs zero extra files, as the configure is provided. a user runs the configure we provide, generating a Makefile.config. This process takes around 4 seconds. Afterwards the user uses make to compile and install like normal.\n\nWhat could be so wrong with GNU autotools?\n\nThe design of autotools is an over complex one, composed of m4, marcos, and dozens of files and commands. This results in a slow and bloated install process for users, along with something that even developers who have been using it _for decades _[still run in to undefined behavior](http://esr.ibiblio.org/?p=1877 \"still run in to undefined behavior.\"). The result of this means that things like --disable-av being [broken](https://github.com/Tox/toxic/pull/100) go unnoticed, without support for things like --enable-debug (A BSDBuild specific flag we implemented with ease). From an end user perspective, this means a configure process that takes 9 times longer and lacks features, requiring more software installed.\n\nBut BSDBuild couldn't be perfect, I mean you **did** drop cmake!\n\nOne of the major issues with BSDBuild is that support for checks (REQUIRE(toxcore) can't be done without making them first. Thankfully, the design of the pm file used for a check is so simple, we had toxcore, toxav, sodium, and openal done in half an hour. Since configure is provided by us, this means no extra work for the end user. Now, BSDBuild does have some other side effects, developers editing either configure.in or Makefile (The entire BSDBuild) do need to have BSDBuild installed, in order to run the mkconfigure command.\n\nBSDBuild doesn't work on GNU/HURD, right?\n\nWrong! Something to consider is that while BSD Makefiles run on GNU make, GNU Makefiles may not run on BSD make. While GNU autotools produce GNU Makefiles, the POSIX compliant BSDBuild files are more supported on more platforms than the autotools equivalent, going as far as supporting making Visual Studio and DOS Watcom projects, despite Toxic not running on Windows.\n\nReactions\n\nReactions to BSDBuild have been mixed, while the autotools maintainer has made some rather ignorant remarks about the compile process with BSDBuild, stating that perl is required (It is not), we do forgive him, BSDBuild isn't a well known system. A few people have stated that the work was a bit of a waste of time, autotools is working. We disagree with this ideology, something like this might seem trivial in the short term, though the ease of use will aide future Toxic developers and helping them focus on the code, and not the build system.\n\nThe last group of people have been supportive, these have generally been users of more popular and more exotic systems, from praising the easy debugging, to the following:\n\n> &lt;rhaps0dy&gt; so, uhm\n> \n> &lt;rhaps0dy&gt; where do I get the BSDBuild version of libtoxcore?\n> \n> &lt;LordAro&gt; rhaps0dy: there isn't one\n> \n> &lt;LordAro&gt; only toxic has a bsdbuild build system so far\n> \n> &lt;LordAro&gt; and that's not in master until people can be convinced that it's \"a good thing\" (tm)\n> \n> &lt;rhaps0dy&gt; :/\n> \n> &lt;LordAro&gt; (which it is)\n> \n> &lt;rhaps0dy&gt; I agree lol\n\nWhy isn't this in master yet?\n\nWith a couple of the reactions coming from other developers who I do like, I would greatly like them to try the system out, explore it a bit, get some honest feedback. As of now, this has not happened, though I do try to push them whenever I can. As well, being new, the new build system may have a couple of quirks that we would really like to get out first. When the time comes I'll merge the branch in to master, just not right now.\n\nI encourage you to try it now, tell me what works, what doesn't work, and most of all, your thoughts on this pending switch.\n\nTesting it is easy, just do a new clone of Toxic, specifying the bsdmake branch: `git clone https://github.com/Tox/toxic -b bsdmake`","slug":"build-systems-yo","updated":1422148791000,"excerpt":"","_id":"69id9djelx2xve66","comments":true,"layout":"post","photos":[],"link":""},{"title":"F-Droid Repo Changing SSL Certificate","id":403,"categories":["q5mc6700pzozi6gl"],"date":1411218729000,"tags":[],"content":"<p><strong>Edit:</strong> This certificate was causing some problems as it was intended for a *.tox.im domain but the repo was on my markwinter.me domain. For now, I have reverted the certificate back to the original markwinter.me cert.</p>\n<p>Just a quick post to let F-Droid users know that I have changed the SSL certificate. Instead of using my own cert, it will now serve a Tox one. The certificate should match<br><a id=\"more\"></a></p>\n<p><img src=\"/images/antox-tox-im-certificate.png\"><br>Some time next month, the URL will also change to fdroid.tox.im or repo.tox.im but I will write another post when that happens</p>\n","source":"_posts/f-droid-repo-changing-ssl-certificate.md","raw":"title: F-Droid Repo Changing SSL Certificate\nid: 403\ncategories:\n  - Antox\ndate: 2014-09-20 09:12:09\ntags:\n---\n\n**Edit:** This certificate was causing some problems as it was intended for a *.tox.im domain but the repo was on my markwinter.me domain. For now, I have reverted the certificate back to the original markwinter.me cert.\n\nJust a quick post to let F-Droid users know that I have changed the SSL certificate. Instead of using my own cert, it will now serve a Tox one. The certificate should match\n<!-- more -->\n{% limg antox-tox-im-certificate.png %}\nSome time next month, the URL will also change to fdroid.tox.im or repo.tox.im but I will write another post when that happens","slug":"f-droid-repo-changing-ssl-certificate","updated":1422148791000,"excerpt":"<p><strong>Edit:</strong> This certificate was causing some problems as it was intended for a *.tox.im domain but the repo was on my markwinter.me domain. For now, I have reverted the certificate back to the original markwinter.me cert.</p>\n<p>Just a quick post to let F-Droid users know that I have changed the SSL certificate. Instead of using my own cert, it will now serve a Tox one. The certificate should match<br>","_id":"21jlkxvye0bdl5fq","comments":true,"layout":"post","photos":[],"link":""},{"title":"Student proposals for GSoC 2014","id":160,"categories":["63k4kifl4fx5xmzk"],"date":1395446975000,"tags":[],"content":"<p>As we’ve hit the deadline for student applications, I thought I’d take a moment to share the outcome.</p>\n<p>For 2014, Google accepted 190 organizations, with 4420 students sending in 6313 proposals. This means that on average a random organization received around 33 proposals, if divided evenly. This means that on average, each org would receive around 0.5% of all proposals.</p>\n<p>Now, the number of proposals being divided equally does not happen, some organizations might be more known, some might have few areas to do proposals, others might be umbrellas.</p>\n<p>Project Tox received 88 proposals, meaning over 1.39% of all proposals were sent to us. As Project Tox is a bit of an umbrella, students applied to one of 6 major categories; being Core, AV, Qt, Venom, iOS, and Android. Stats on where proposals went have yet to be calculated, though a good majority went to Android and Qt.</p>\n<p>This rush of students was surprisingly successful, for our first GSoC, I can’t wait to see what good comes out of the chosen students, and what comes out of future summers.</p>\n","source":"_posts/gsoc-14-proposals.md","raw":"title: Student proposals for GSoC 2014\nid: 160\ncategories:\n  - Google Summer of Code\ndate: 2014-03-21 20:09:35\ntags:\n---\n\nAs we've hit the deadline for student applications, I thought I'd take a moment to share the outcome.\n\nFor 2014, Google accepted 190 organizations, with 4420 students sending in 6313 proposals. This means that on average a random organization received around 33 proposals, if divided evenly. This means that on average, each org would receive around 0.5% of all proposals.\n\nNow, the number of proposals being divided equally does not happen, some organizations might be more known, some might have few areas to do proposals, others might be umbrellas.\n\nProject Tox received 88 proposals, meaning over 1.39% of all proposals were sent to us. As Project Tox is a bit of an umbrella, students applied to one of 6 major categories; being Core, AV, Qt, Venom, iOS, and Android. Stats on where proposals went have yet to be calculated, though a good majority went to Android and Qt.\n\nThis rush of students was surprisingly successful, for our first GSoC, I can't wait to see what good comes out of the chosen students, and what comes out of future summers.","slug":"gsoc-14-proposals","updated":1420586788000,"excerpt":"","_id":"wksc9sf1qxnkb2et","comments":true,"layout":"post","photos":[],"link":""},{"title":"Help Tox Grow, Run a Tox Node Today","id":530,"categories":["nlwrm5tlcr1n8dpi"],"date":1412633051000,"tags":[],"content":"<p>In light of packaging the bootstrap daemon, we’re going to be running a month-long campaign to expand our current node list. For more information, visit our <a href=\"https://blog.libtoxcore.so/running-a-bootstrap-node\" title=\"Running a Bootstrap Node\" target=\"_blank\" rel=\"external\">Running a Bootstrap Node</a> page or join us on IRC #tox@freenode.<br><a id=\"more\"></a><br>(Page will be fixed soon)</p>\n","source":"_posts/help-tox-grow-run-a-tox-node-today.md","raw":"title: \"Help Tox Grow, Run a Tox Node Today\"\nid: 530\ncategories:\n  - Tox Core\ndate: 2014-10-06 18:04:11\ntags:\n---\n\nIn light of packaging the bootstrap daemon, we're going to be running a month-long campaign to expand our current node list. For more information, visit our [Running a Bootstrap Node](https://blog.libtoxcore.so/running-a-bootstrap-node \"Running a Bootstrap Node\") page or join us on IRC #tox@freenode.\n<!-- more -->\n(Page will be fixed soon)\n","slug":"help-tox-grow-run-a-tox-node-today","updated":1420586899000,"excerpt":"<p>In light of packaging the bootstrap daemon, we’re going to be running a month-long campaign to expand our current node list. For more information, visit our <a href=\"https://blog.libtoxcore.so/running-a-bootstrap-node\" title=\"Running a Bootstrap Node\" target=\"_blank\" rel=\"external\">Running a Bootstrap Node</a> page or join us on IRC #tox@freenode.<br>","_id":"jci6fa9luccqfo69","comments":true,"layout":"post","photos":[],"link":""},{"title":"Downtime, DNS, and a reliance on others","id":226,"categories":["8onc6duauo2iko75"],"date":1397381148000,"tags":[],"content":"<p>At around 4 pm PST tox.im and its subdomains failed to load, along with libtoxcore.so.</p>\n<p>About 6 hours later it returned, after my late notice and quick action.</p>\n<p>After a quick investigation I determined that the web server was up and the nameservers were up, all working at 100%. Further investigation determined that the nameservers that powered the domain the nameservers were at went down, and after quickly moving that domains nameservers and a bit of DNS propagation service was restored.</p>\n<p>So, what exactly went wrong? Tox’s DNS is provided by service X, behind nameservers on domain b. Domain b once used service X, though for DNSSEC support moved to service Y. Service Y was chosen because DNSSEC DNS providers are rather rare, and these servers provided faster response times. Service Y’s 4 nameservers were all taken down as a result of what we suspect was a DDoS attack, rendering queries on the nameservers for Tox useless. DNS glue was designed to prevent this issue, stop that catch-22, done by providing nameserver names and IPs in the whois record itself. This managed to get ignored by every DNS resolver, resulting in no queries going through. I was able to address this issue by fetching the bind file from X for domain b and deploying nameservers with service Z. After a bit of mitigation everything was all fine, with availability all around.</p>\n<p>Service Y was chosen due to price and limited selection, though this later turned out to be a poor decision, service Z is a larger well known provider of Internet services, who offer a SLA, DDoS protection, and amazing uptime; at about 12 times the price.</p>\n<p>At the end of the day, this was a painful lesson to learn. DNS isn’t something to be taken lightly, and is something we really do need to pay a pretty penny for.</p>\n<p>Why don’t we run our own DNS servers? DNS is something that demands a level of maintainability, when something goes wrong fixing the server is difficult due to not being able to resolve the servers domain. This means more downtime, harder to maintain, and generally more expensive to run, and more messes like what happened yesterday.</p>\n","source":"_posts/downtime.md","raw":"title: \"Downtime, DNS, and a reliance on others\"\nid: 226\ncategories:\n  - Uncategorized\ndate: 2014-04-13 05:25:48\ntags:\n---\n\nAt around 4 pm PST tox.im and its subdomains failed to load, along with libtoxcore.so.\n\nAbout 6 hours later it returned, after my late notice and quick action.\n\nAfter a quick investigation I determined that the web server was up and the nameservers were up, all working at 100%. Further investigation determined that the nameservers that powered the domain the nameservers were at went down, and after quickly moving that domains nameservers and a bit of DNS propagation service was restored.\n\nSo, what exactly went wrong? Tox's DNS is provided by service X, behind nameservers on domain b. Domain b once used service X, though for DNSSEC support moved to service Y. Service Y was chosen because DNSSEC DNS providers are rather rare, and these servers provided faster response times. Service Y's 4 nameservers were all taken down as a result of what we suspect was a DDoS attack, rendering queries on the nameservers for Tox useless. DNS glue was designed to prevent this issue, stop that catch-22, done by providing nameserver names and IPs in the whois record itself. This managed to get ignored by every DNS resolver, resulting in no queries going through. I was able to address this issue by fetching the bind file from X for domain b and deploying nameservers with service Z. After a bit of mitigation everything was all fine, with availability all around.\n\nService Y was chosen due to price and limited selection, though this later turned out to be a poor decision, service Z is a larger well known provider of Internet services, who offer a SLA, DDoS protection, and amazing uptime; at about 12 times the price.\n\nAt the end of the day, this was a painful lesson to learn. DNS isn't something to be taken lightly, and is something we really do need to pay a pretty penny for.\n\nWhy don't we run our own DNS servers? DNS is something that demands a level of maintainability, when something goes wrong fixing the server is difficult due to not being able to resolve the servers domain. This means more downtime, harder to maintain, and generally more expensive to run, and more messes like what happened yesterday.","slug":"downtime","updated":1422148791000,"excerpt":"","_id":"i8544msdpg9tbbsb","comments":true,"layout":"post","photos":[],"link":""},{"title":"How the crypto Tox uses works","id":251,"categories":["nlwrm5tlcr1n8dpi"],"date":1398629196000,"tags":[],"content":"<p>Yesterday, I made this: <a href=\"https://gist.github.com/irungentoo/58a8b5da5b2becd09e0f\" target=\"_blank\" rel=\"external\">https://gist.github.com/irungentoo/58a8b5da5b2becd09e0f</a></p>\n<p>If this is the first time you see this puzzle and want to try solving it then stop reading this now.</p>\n<p>I was very disappointed that only one anonymous person seemed to know how to solve it so I’m writing this to educate you on how the crypto Tox uses to encrypt messages works.</p>\n<p>First of all, the flaw in the secure_chat.py program in the puzzle is that nonces are reused for every message. If every message had a different nonce this puzzle would be unsolvable.</p>\n<p>I’ll start by explaining how crypto_box in NaCl works before telling you the solution.</p>\n<p>crypto_box_keypair(pk,sk) generates a Curve25519 public/private keypair for us. crypto_box_beforenm(k,pk,sk) then uses our secret key and the other guys public key to generate a key using ECDH (Elliptic curve Diffie-Hellman)</p>\n<p>The other guy also uses it on his side and gets the same key as us.</p>\n<p>So both now have the same 256bit key that only they know.</p>\n<p>what do they do with that key? they use it to encrypt/decrypt data using xsalsa20: a stream cipher.</p>\n<p>How does a stream cipher work?</p>\n<p>You have a function to generate a stream of pseudorandom bytes based on a nonce and a key: crypto_stream(c,clen,n,k)</p>\n<p>To encrypt a message, just generate a stream as long as the message then XOR the message with the stream.</p>\n<p>Since the stream looks random, the stream xored with the message will also appear to be random.</p>\n<p>To decrypt the message, just use the same nonce and key to generate a stream then xor the stream with the encrypted message to get the message.</p>\n<p>Now, this is nice and all but how do we protect ourselves against someone modifying the message? Or someone trying to send us fake messages?</p>\n<p>That’s where the MAC (message authentication code) Poly1305 comes in.</p>\n<p>MACs are used to authenticate messages, by verifying them, the receiver</p>\n<p>crypto_onetimeauth(a,m,mlen,k) Is used to generate a 16 byte authenticator that is appended to the beginning of each plaintext message encrypted with crypto_box right before being actually encrypted.</p>\n<p>Poly1305 requires that the key given to it is always different so it takes the first 32bytes that comes out of crypto_stream(c,clen,n,k) (clen is always 32 + 16 (the length of the MAC) + msglen) for that key.</p>\n<p>So, it generates an xsalsa20 stream 48 bytes longer than the message, takes the first 32 to generate the 16 byte MAC, appends it to the beginning of the message and encrypts the MAC+Message with the rest of the generated stream bytes.</p>\n<p>So how do we solve the puzzle?</p>\n<p>nonces are reused which means the stream generated by crypto_stream(c,clen,n,k) is the same for all messages.</p>\n<p>The first two packets are obviously the handshake (size checks out).</p>\n<p>This particular python wrapper puts the 24 byte nonce at the beginning of each encrypted message and we know the handshake.</p>\n<p>So we just xor the plaintext handshake with where the message is in the encrypted message to get the stream.</p>\n<p>With the stream we can then decrypt all the packets that use that same nonce by xoring the stream with the encrypted message.</p>\n<p>Repeat that for the packets with the other nonce and we can decrypt everything.</p>\n<p>Easy right?</p>\n<p>This is why every single message must be encrypted with a different nonce, so that a different stream is used for each message.</p>\n<p>Further reading:<br><a href=\"http://nacl.cr.yp.to/box.html\" target=\"_blank\" rel=\"external\">http://nacl.cr.yp.to/box.html</a><br><a href=\"http://nacl.cr.yp.to/stream.html\" target=\"_blank\" rel=\"external\">http://nacl.cr.yp.to/stream.html</a><br><a href=\"http://nacl.cr.yp.to/onetimeauth.html\" target=\"_blank\" rel=\"external\">http://nacl.cr.yp.to/onetimeauth.html</a><br><a href=\"https://en.wikipedia.org/wiki/Curve25519\" target=\"_blank\" rel=\"external\">https://en.wikipedia.org/wiki/Curve25519</a><br><a href=\"https://en.wikipedia.org/wiki/Elliptic_curve_Diffie%E2%80%93Hellman\" target=\"_blank\" rel=\"external\">https://en.wikipedia.org/wiki/Elliptic_curve_Diffie%E2%80%93Hellman</a><br><a href=\"https://en.wikipedia.org/wiki/Poly1305-AES\" target=\"_blank\" rel=\"external\">https://en.wikipedia.org/wiki/Poly1305-AES</a></p>\n<p><a href=\"https://en.wikipedia.org/wiki/Cryptographic_nonce\" target=\"_blank\" rel=\"external\">https://en.wikipedia.org/wiki/Cryptographic_nonce</a></p>\n","source":"_posts/how-the-crypto-tox-uses-works.md","raw":"title: How the crypto Tox uses works\nid: 251\ncategories:\n  - Tox Core\ndate: 2014-04-27 16:06:36\ntags:\n---\n\nYesterday, I made this: https://gist.github.com/irungentoo/58a8b5da5b2becd09e0f\n\nIf this is the first time you see this puzzle and want to try solving it then stop reading this now.\n\nI was very disappointed that only one anonymous person seemed to know how to solve it so I'm writing this to educate you on how the crypto Tox uses to encrypt messages works.\n\nFirst of all, the flaw in the secure_chat.py program in the puzzle is that nonces are reused for every message. If every message had a different nonce this puzzle would be unsolvable.\n\nI'll start by explaining how crypto_box in NaCl works before telling you the solution.\n\ncrypto_box_keypair(pk,sk) generates a Curve25519 public/private keypair for us. crypto_box_beforenm(k,pk,sk) then uses our secret key and the other guys public key to generate a key using ECDH (Elliptic curve Diffie-Hellman)\n\nThe other guy also uses it on his side and gets the same key as us.\n\nSo both now have the same 256bit key that only they know.\n\nwhat do they do with that key? they use it to encrypt/decrypt data using xsalsa20: a stream cipher.\n\nHow does a stream cipher work?\n\nYou have a function to generate a stream of pseudorandom bytes based on a nonce and a key: crypto_stream(c,clen,n,k)\n\nTo encrypt a message, just generate a stream as long as the message then XOR the message with the stream.\n\nSince the stream looks random, the stream xored with the message will also appear to be random.\n\nTo decrypt the message, just use the same nonce and key to generate a stream then xor the stream with the encrypted message to get the message.\n\nNow, this is nice and all but how do we protect ourselves against someone modifying the message? Or someone trying to send us fake messages?\n\nThat's where the MAC (message authentication code) Poly1305 comes in.\n\nMACs are used to authenticate messages, by verifying them, the receiver\n\ncrypto_onetimeauth(a,m,mlen,k) Is used to generate a 16 byte authenticator that is appended to the beginning of each plaintext message encrypted with crypto_box right before being actually encrypted.\n\nPoly1305 requires that the key given to it is always different so it takes the first 32bytes that comes out of crypto_stream(c,clen,n,k) (clen is always 32 + 16 (the length of the MAC) + msglen) for that key.\n\nSo, it generates an xsalsa20 stream 48 bytes longer than the message, takes the first 32 to generate the 16 byte MAC, appends it to the beginning of the message and encrypts the MAC+Message with the rest of the generated stream bytes.\n\nSo how do we solve the puzzle?\n\nnonces are reused which means the stream generated by crypto_stream(c,clen,n,k) is the same for all messages.\n\nThe first two packets are obviously the handshake (size checks out).\n\nThis particular python wrapper puts the 24 byte nonce at the beginning of each encrypted message and we know the handshake.\n\nSo we just xor the plaintext handshake with where the message is in the encrypted message to get the stream.\n\nWith the stream we can then decrypt all the packets that use that same nonce by xoring the stream with the encrypted message.\n\nRepeat that for the packets with the other nonce and we can decrypt everything.\n\nEasy right?\n\nThis is why every single message must be encrypted with a different nonce, so that a different stream is used for each message.\n\nFurther reading:\nhttp://nacl.cr.yp.to/box.html\nhttp://nacl.cr.yp.to/stream.html\nhttp://nacl.cr.yp.to/onetimeauth.html\nhttps://en.wikipedia.org/wiki/Curve25519\nhttps://en.wikipedia.org/wiki/Elliptic_curve_Diffie%E2%80%93Hellman\nhttps://en.wikipedia.org/wiki/Poly1305-AES\n\nhttps://en.wikipedia.org/wiki/Cryptographic_nonce","slug":"how-the-crypto-tox-uses-works","updated":1420586788000,"excerpt":"","_id":"ej9hg7c55lewjeex","comments":true,"layout":"post","photos":[],"link":""},{"title":"Antox Release 0.14.0-alpha","id":462,"categories":["q5mc6700pzozi6gl"],"date":1412373163000,"tags":[],"content":"<p>It didn’t take long for another release to happen but here it is, version 0.14.0. This release mostly brings a lot of changes to under the hood. Namely, the entire code base has been moved from Java to Scala and with it came a new sleek UI with improved animations<br><a id=\"more\"></a></p>\n<img src=\"/images/antox-0-14-0.png\">\n\n<p>Hopefully this transition of language goes smoothly and everything works as well as it did before. Next in the development line is adding avatars and finally finishing off implementing audio calling</p>\n","source":"_posts/antox-release-0-14-0-alpha.md","raw":"title: Antox Release 0.14.0-alpha\nid: 462\ncategories:\n  - Antox\ndate: 2014-10-03 17:52:43\ntags:\n---\n\nIt didn't take long for another release to happen but here it is, version 0.14.0\\. This release mostly brings a lot of changes to under the hood. Namely, the entire code base has been moved from Java to Scala and with it came a new sleek UI with improved animations\n<!-- more -->\n{% limg antox-0-14-0.png %}\n\nHopefully this transition of language goes smoothly and everything works as well as it did before. Next in the development line is adding avatars and finally finishing off implementing audio calling\n","slug":"antox-release-0-14-0-alpha","updated":1422148791000,"excerpt":"<p>It didn’t take long for another release to happen but here it is, version 0.14.0. This release mostly brings a lot of changes to under the hood. Namely, the entire code base has been moved from Java to Scala and with it came a new sleek UI with improved animations<br>","_id":"s30rg7tgrpx2c64m","comments":true,"layout":"post","photos":[],"link":""},{"title":"Introducing STS: The Single Tox Standard","id":182,"categories":["nlwrm5tlcr1n8dpi"],"date":1396308021000,"tags":[],"content":"<p>As Tox grows and more clients are created, we feel it is time to create a Tox standard. Doing so will enable us to promote a single, cohesive brand despite the numerous clients. STS aims to offer a handbook for existing and potential client developers to follow so they can all remain consistent, yet unique in their own way. Terminology such as the <strong>Tox ID</strong> will represent the 76-character string used to identify users, but <strong>Nickname </strong>and <strong>Names</strong> being used to personally recognize friends. This will prevent confusion for users who wish to switch clients, and allow Tox to focus on pushing a single brand. At the moment, we are <strong>strongly recommending</strong> adherence to the STS, as it will foster a more productive environment, but we recognize that it’s the right of the developer to chose. Once the STS has been completed and v1.0.0 has been published, we will no longer offer support or publicity to clients that wish to deviate from the STS. We regret that we must take such a stance, but it is required that we take such measures in order to uphold one of Tox’s foremost goals: to provide a smooth and easy experience for all walks of life.</p>\n<p>Like everything Tox does, the Single Tox Standard is on GitHub where you may open tickets to address concerns, questions, or offer feedback. Your continued support of Tox is appreciated as we draft the first version of STS.</p>\n<p><a href=\"https://github.com/Tox/STS\" target=\"_blank\" rel=\"external\">https://github.com/Tox/STS</a></p>\n","source":"_posts/introducing-sts-single-tox-standard.md","raw":"title: \"Introducing STS: The Single Tox Standard\"\nid: 182\ncategories:\n  - Tox Core\ndate: 2014-03-31 19:20:21\ntags:\n---\n\nAs Tox grows and more clients are created, we feel it is time to create a Tox standard. Doing so will enable us to promote a single, cohesive brand despite the numerous clients. STS aims to offer a handbook for existing and potential client developers to follow so they can all remain consistent, yet unique in their own way. Terminology such as the **Tox ID** will represent the 76-character string used to identify users, but **Nickname **and **Names** being used to personally recognize friends. This will prevent confusion for users who wish to switch clients, and allow Tox to focus on pushing a single brand. At the moment, we are **strongly recommending** adherence to the STS, as it will foster a more productive environment, but we recognize that it's the right of the developer to chose. Once the STS has been completed and v1.0.0 has been published, we will no longer offer support or publicity to clients that wish to deviate from the STS. We regret that we must take such a stance, but it is required that we take such measures in order to uphold one of Tox's foremost goals: to provide a smooth and easy experience for all walks of life.\n\nLike everything Tox does, the Single Tox Standard is on GitHub where you may open tickets to address concerns, questions, or offer feedback. Your continued support of Tox is appreciated as we draft the first version of STS.\n\nhttps://github.com/Tox/STS","slug":"introducing-sts-single-tox-standard","updated":1422148791000,"excerpt":"","_id":"zqmdg3z2wnemu31c","comments":true,"layout":"post","photos":[],"link":""},{"title":"Jenkins CI and signed commits","tags":["v9hgqbmdqj6y7m3c","rl3qvhg1ki1za9dj","4c3qgpjblqf7la9s","sshw3dk4ycgi1vys"],"id":128,"categories":["rpfxl29wpibc9sbf"],"date":1395260551000,"content":"<p>This is the first post in our new Jenkins section. In this section, we will post updates about how we’re building Tox automatically.</p>\n<p>Today we started rolling out a new feature in our builds, Signed git commits. What are signed commits, and why are we using them? Well, the first question is answered quite easily: We use PGP signatures in order to verify the integrity of any commit. If you don’t know what PGP is, you can read about it here: <a href=\"https://en.wikipedia.org/wiki/Pretty_Good_Privacy\" title=\"Pretty Good Privacy\" target=\"_blank\" rel=\"external\">PGP</a>. Now, why are we doing this? This answer is a little more complicated.</p>\n<p>A friend (we’ll call him Bob) of mine recently told me a little story about how something went horribly wrong when using git. In git, you can set your <code>user.email</code> and <code>user.name</code> to arbitrary values. There is no way to check if the email and name you gave are actually YOURS.</p>\n<p>Now, there was another user who had push access to the repository, and they were malicious, as later discovered. Let’s call them Mallory. One day, Mallory decided to push a malicious feature to the git repository. Mallory was smart however, and so they did this before creating the commit: <code>git config user.name Bob</code> and <code>git config user.email bob@example.com</code>.</p>\n<p>You might already see where this is going now. Mallory pushed the malicious code under the name and email of Bob. When the “feature” was discovered, Bob was blamed immediately, and noone even thought about blaming Mallory (who didn’t work at the company anymore at this point) because after all, the email and name stated quite clearly that Bob committed that code. Gladly, Bob wasn’t fired, as he could assure that it was NOT him who committed the code.</p>\n<p>Now, what can we do to prevent this from happening? It’s surprisingly easy. Git has always offered the functionality to sign Tags with PGP, but starting with version 1.7.9, functionality to sign commits was added. It’s very easy to enable, too. First step, locate your PGP key:</p>\n<figure class=\"highlight sh\"><table><tr><td class=\"gutter\"><pre><div class=\"line\">1</div><div class=\"line\">2</div></pre></td><td class=\"code\"><pre><div class=\"line\">$ gpg --list-secret-keys | grep ^sec</div><div class=\"line\">sec <span class=\"number\">2048</span>R/<span class=\"number\">75</span>D697BF <span class=\"number\">2013</span>-<span class=\"number\">07</span>-<span class=\"number\">08</span> [expires: <span class=\"number\">2023</span>-<span class=\"number\">07</span>-<span class=\"number\">06</span>]</div></pre></td></tr></table></figure>\n\n<p>Second step, set up that key to be used with git:</p>\n<figure class=\"highlight sh\"><table><tr><td class=\"gutter\"><pre><div class=\"line\">1</div></pre></td><td class=\"code\"><pre><div class=\"line\">$ git config --global user.signingkey <span class=\"number\">75</span>D697BF</div></pre></td></tr></table></figure>\n\n<p>And now you’re ready to sign your git commits with <code>git commit -S</code>. Now that commit is signed, and everyone that has your PGP public key can confirm that YOU made this commit (or someone stole your private key, but that’s a completely different problem, and you should revoke your key immediately.) You can verify the signatures on commits like this: <code>git log --show-signature</code>. Since the output is very long, I put the output for different scenarios in a <a href=\"https://gist.github.com/sonOfRa/9649586\" title=\"Git commit signatures\" target=\"_blank\" rel=\"external\">gist</a></p>\n<p>Does that mean that every Tox contributor has to set up PGP now? While personally, I think EVERYONE should have PGP, no. You can go on developing and adding Pull Request just as you did before. Only the repository maintainers of core, the bindings, and the clients need to worry about this.</p>\n<p>And what does all this have to do with our Build Server? Currently, our Build Server fetches the latest changes from our different repositories and makes the updated code available to the build jobs, which then create a new binary each time the build is triggered by a change. This results in downloads that are minutes older than the latest commit, at the most.</p>\n<p>Even though malicious commits are very unlikely, a malicious commit would also trigger a build on all clients, and until it is reverted, we would have built malicious binaries. In order to prevent this, we check the signatures of the commits each time the code is checked out. If the verification fails, the checkout will be marked as failed, and no builds using the unsigned commit would be made.</p>\n<p>So what does this mean for the repository maintainers? Not much, except that they have to set up PGP and start signing their commits. There is one small problem, though. It is not possible to sign Pull Request through the Github Web-Interface. Therefore, we have to check out the Pull Request locally. Github has a guide how to do this <a href=\"https://help.github.com/articles/checking-out-pull-requests-locally\" title=\"Local PR\" target=\"_blank\" rel=\"external\">here</a>. Now, after you’ve checked out the Pull Request you want to merge, and it’s in the branch “1234”, this is how you would merge the PR and push the result to master:</p>\n<figure class=\"highlight sh\"><table><tr><td class=\"gutter\"><pre><div class=\"line\">1</div><div class=\"line\">2</div><div class=\"line\">3</div><div class=\"line\">4</div><div class=\"line\">5</div></pre></td><td class=\"code\"><pre><div class=\"line\">$ git checkout master</div><div class=\"line\"><span class=\"comment\"># --no-ff creates a merge commit</span></div><div class=\"line\"><span class=\"comment\"># -S signs the commit</span></div><div class=\"line\">$ git merge --no-ff -S <span class=\"number\">1234</span></div><div class=\"line\">$ git push origin master</div></pre></td></tr></table></figure>\n\n<p>The <code>--no-ff</code> option is vital, because we need a commit on master for which we can check the signature. If the option is ommitted, the commits might simply be added into the master branch, and signing will be problematic.</p>\n<p>Here’s some handy aliases so you don’t forget to sign your commits or merges, and one to view signed commits when using git log:</p>\n<figure class=\"highlight sh\"><table><tr><td class=\"gutter\"><pre><div class=\"line\">1</div><div class=\"line\">2</div><div class=\"line\">3</div><div class=\"line\">4</div><div class=\"line\">5</div><div class=\"line\">6</div></pre></td><td class=\"code\"><pre><div class=\"line\"><span class=\"comment\"># View log with signatures with 'git slog'</span></div><div class=\"line\">$ git config --global alias.slog <span class=\"string\">\"log --show-signature\"</span></div><div class=\"line\"><span class=\"comment\"># Create a signed commit with 'git scommit'</span></div><div class=\"line\">$ git config --global alias.scommit <span class=\"string\">\"commit -S\"</span></div><div class=\"line\"><span class=\"comment\"># Create a signed, non-fast-forward merge</span></div><div class=\"line\">$ git config --global alias.smerge <span class=\"string\">\"merge -S --no-ff\"</span></div></pre></td></tr></table></figure>\n\n","source":"_posts/jenkins-ci-and-signed-commits.md","raw":"title: Jenkins CI and signed commits\ntags:\n  - git\n  - jenkins\n  - jToxcore\n  - pgp\nid: 128\ncategories:\n  - Jenkins\ndate: 2014-03-19 16:22:31\n---\n\nThis is the first post in our new Jenkins section. In this section, we will post updates about how we're building Tox automatically.\n\nToday we started rolling out a new feature in our builds, Signed git commits. What are signed commits, and why are we using them? Well, the first question is answered quite easily: We use PGP signatures in order to verify the integrity of any commit. If you don't know what PGP is, you can read about it here: [PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy \"Pretty Good Privacy\"). Now, why are we doing this? This answer is a little more complicated.\n\nA friend (we'll call him Bob) of mine recently told me a little story about how something went horribly wrong when using git. In git, you can set your `user.email` and `user.name` to arbitrary values. There is no way to check if the email and name you gave are actually YOURS.\n\nNow, there was another user who had push access to the repository, and they were malicious, as later discovered. Let's call them Mallory. One day, Mallory decided to push a malicious feature to the git repository. Mallory was smart however, and so they did this before creating the commit: `git config user.name Bob` and `git config user.email bob@example.com`.\n\nYou might already see where this is going now. Mallory pushed the malicious code under the name and email of Bob. When the \"feature\" was discovered, Bob was blamed immediately, and noone even thought about blaming Mallory (who didn't work at the company anymore at this point) because after all, the email and name stated quite clearly that Bob committed that code. Gladly, Bob wasn't fired, as he could assure that it was NOT him who committed the code.\n\nNow, what can we do to prevent this from happening? It's surprisingly easy. Git has always offered the functionality to sign Tags with PGP, but starting with version 1.7.9, functionality to sign commits was added. It's very easy to enable, too. First step, locate your PGP key:\n``` sh\n$ gpg --list-secret-keys | grep ^sec\nsec 2048R/75D697BF 2013-07-08 [expires: 2023-07-06]\n```\nSecond step, set up that key to be used with git:\n``` sh\n$ git config --global user.signingkey 75D697BF\n```\nAnd now you're ready to sign your git commits with `git commit -S`. Now that commit is signed, and everyone that has your PGP public key can confirm that YOU made this commit (or someone stole your private key, but that's a completely different problem, and you should revoke your key immediately.) You can verify the signatures on commits like this: `git log --show-signature`. Since the output is very long, I put the output for different scenarios in a [gist](https://gist.github.com/sonOfRa/9649586 \"Git commit signatures\")\n\nDoes that mean that every Tox contributor has to set up PGP now? While personally, I think EVERYONE should have PGP, no. You can go on developing and adding Pull Request just as you did before. Only the repository maintainers of core, the bindings, and the clients need to worry about this.\n\nAnd what does all this have to do with our Build Server? Currently, our Build Server fetches the latest changes from our different repositories and makes the updated code available to the build jobs, which then create a new binary each time the build is triggered by a change. This results in downloads that are minutes older than the latest commit, at the most.\n\nEven though malicious commits are very unlikely, a malicious commit would also trigger a build on all clients, and until it is reverted, we would have built malicious binaries. In order to prevent this, we check the signatures of the commits each time the code is checked out. If the verification fails, the checkout will be marked as failed, and no builds using the unsigned commit would be made.\n\nSo what does this mean for the repository maintainers? Not much, except that they have to set up PGP and start signing their commits. There is one small problem, though. It is not possible to sign Pull Request through the Github Web-Interface. Therefore, we have to check out the Pull Request locally. Github has a guide how to do this [here](https://help.github.com/articles/checking-out-pull-requests-locally \"Local PR\"). Now, after you've checked out the Pull Request you want to merge, and it's in the branch \"1234\", this is how you would merge the PR and push the result to master:\n``` sh\n$ git checkout master\n# --no-ff creates a merge commit\n# -S signs the commit\n$ git merge --no-ff -S 1234\n$ git push origin master\n```\nThe `--no-ff` option is vital, because we need a commit on master for which we can check the signature. If the option is ommitted, the commits might simply be added into the master branch, and signing will be problematic.\n\nHere's some handy aliases so you don't forget to sign your commits or merges, and one to view signed commits when using git log:\n``` sh\n# View log with signatures with 'git slog'\n$ git config --global alias.slog \"log --show-signature\"\n# Create a signed commit with 'git scommit'\n$ git config --global alias.scommit \"commit -S\"\n# Create a signed, non-fast-forward merge\n$ git config --global alias.smerge \"merge -S --no-ff\"\n```","slug":"jenkins-ci-and-signed-commits","updated":1422148791000,"excerpt":"","_id":"nlg2cl3jkp72bljh","comments":true,"layout":"post","photos":[],"link":""},{"title":"qTox now in Tox Repositories","id":539,"categories":["n2ucmyxmms5yv6mr","kots9n2e471yrjqu"],"date":1413837460000,"tags":[],"content":"<p>It took awhile, and some may have noticed it was there earlier, but qTox has now hit the Tox Repos. It’s a great addition to the already expansive list of Tox clients users have to choose from, and personally, I think it’s one of the best clients we have to offer.</p>\n<p><a id=\"more\"></a><br>If you haven’t already, <a href=\"https://wiki.tox.im/Binaries#Linux\" target=\"_blank\" rel=\"external\">here are the instructions</a> on how to add the Tox Repo to your packaging software.</p>\n<img src=\"/images/qtox-settings-window.png\">\n","source":"_posts/qtox-now-in-tox-repositories.md","raw":"title: qTox now in Tox Repositories\nid: 539\ncategories:\n  - qTox\n  - Tox Repositories\ndate: 2014-10-20 16:37:40\ntags:\n---\n\nIt took awhile, and some may have noticed it was there earlier, but qTox has now hit the Tox Repos. It's a great addition to the already expansive list of Tox clients users have to choose from, and personally, I think it's one of the best clients we have to offer.\n\n<!-- more -->\nIf you haven't already, [here are the instructions](https://wiki.tox.im/Binaries#Linux) on how to add the Tox Repo to your packaging software.\n\n{% limg qtox-settings-window.png %}\n","slug":"qtox-now-in-tox-repositories","updated":1420586900000,"excerpt":"<p>It took awhile, and some may have noticed it was there earlier, but qTox has now hit the Tox Repos. It’s a great addition to the already expansive list of Tox clients users have to choose from, and personally, I think it’s one of the best clients we have to offer.</p>\n<p>","_id":"xtnxnpx4sx1k8um7","comments":true,"layout":"post","photos":[],"link":""},{"title":"Ratox in Tox Repositories","id":470,"categories":["p8mle97ey5sjnf7j","b1grbwe40a75ur1i"],"date":1412471598000,"tags":[],"content":"<p>Man, we’re on fire lately. Ratox, a relatively new client created by the wonderful people at <a href=\"www.2f30.org\">2f30</a>, can now be found in Tox Repos. Unlike other clients relying on GUIs as an interface to the user, Ratox is developed with the UNIX-philosophy in mind and allows complete interaction through named pipes. For more info, visit the <a href=\"https://wiki.tox.im/Ratox\" target=\"_blank\" rel=\"external\">Ratox article</a> on the Tox Wiki.<br><a id=\"more\"></a><br>If you’re new to Tox, or haven’t added our Tox Repository yet, check out <a href=\"https://wiki.tox.im/Binaries#Repositories\" target=\"_blank\" rel=\"external\">the instructions</a> on how to add the Tox Repo to your software management suite.</p>\n<img src=\"/images/ratox_small.png\">\n","source":"_posts/ratox-in-tox-repositories.md","raw":"title: Ratox in Tox Repositories\nid: 470\ncategories:\n  - Ratox\n  - Tox Repositories\ndate: 2014-10-04 21:13:18\ntags:\n---\n\nMan, we're on fire lately. Ratox, a relatively new client created by the wonderful people at [2f30](www.2f30.org), can now be found in Tox Repos. Unlike other clients relying on GUIs as an interface to the user, Ratox is developed with the UNIX-philosophy in mind and allows complete interaction through named pipes. For more info, visit the [Ratox article](https://wiki.tox.im/Ratox) on the Tox Wiki.\n<!-- more -->\nIf you're new to Tox, or haven't added our Tox Repository yet, check out [the instructions](https://wiki.tox.im/Binaries#Repositories) on how to add the Tox Repo to your software management suite.\n\n{% limg ratox_small.png %}\n","slug":"ratox-in-tox-repositories","updated":1420586900000,"excerpt":"<p>Man, we’re on fire lately. Ratox, a relatively new client created by the wonderful people at <a href=\"www.2f30.org\">2f30</a>, can now be found in Tox Repos. Unlike other clients relying on GUIs as an interface to the user, Ratox is developed with the UNIX-philosophy in mind and allows complete interaction through named pipes. For more info, visit the <a href=\"https://wiki.tox.im/Ratox\" target=\"_blank\" rel=\"external\">Ratox article</a> on the Tox Wiki.<br>","_id":"bnqyaxwvcxeufmpj","comments":true,"layout":"post","photos":[],"link":""},{"title":"The State of the Foundation address, April 2014","id":243,"categories":["i0yjl3tz23qj3npq"],"date":1398578715000,"tags":[],"content":"<p>I’d like to take a moment to keep you folks informed about the status of the foundation behind Tox, something I plan on doing monthly.</p>\n<p>Late December of 2013 Project Tox officially became a ULX Foundation project, this granted Tox developers the ability to attend shows like CES at no charge and participate in Google Summer of Code, all while providing legal a presence for the project.</p>\n<p>For the past two months Tox developers and ULX Foundation folks discussed a rename, ideas were bounced everywhere but nothing was settled on. To deal with this rename an acting board was formed.</p>\n<p>Half way through April the idea to write a technical paper came up, the acting board agreed to form the Tox Technical Reporting working group, who are still working on this.</p>\n<p>On the 24th a decision on the rename was made, the acting board unanimously agreed to adopt the name Tox Foundation. On this same day the acting board agreed to change the title Tox Developer to Tox Engineer, designating between those who do engineering related tasks and those who do other essential tasks.</p>\n<p>On the 25th the paperwork was filed, and the rename was official.</p>\n<p>Next up is adopting a new set of bylaws, adopting a new board, and working out all the financial aspects of everything. We hope that with the Foundation by our sides, the Tox Project and all of our future projects will prosper.</p>\n","source":"_posts/stf-4-14.md","raw":"title: \"The State of the Foundation address, April 2014\"\nid: 243\ncategories:\n  - Tox Foundation\ndate: 2014-04-27 02:05:15\ntags:\n---\n\nI'd like to take a moment to keep you folks informed about the status of the foundation behind Tox, something I plan on doing monthly.\n\nLate December of 2013 Project Tox officially became a ULX Foundation project, this granted Tox developers the ability to attend shows like CES at no charge and participate in Google Summer of Code, all while providing legal a presence for the project.\n\nFor the past two months Tox developers and ULX Foundation folks discussed a rename, ideas were bounced everywhere but nothing was settled on. To deal with this rename an acting board was formed.\n\nHalf way through April the idea to write a technical paper came up, the acting board agreed to form the Tox Technical Reporting working group, who are still working on this.\n\nOn the 24th a decision on the rename was made, the acting board unanimously agreed to adopt the name Tox Foundation. On this same day the acting board agreed to change the title Tox Developer to Tox Engineer, designating between those who do engineering related tasks and those who do other essential tasks.\n\nOn the 25th the paperwork was filed, and the rename was official.\n\nNext up is adopting a new set of bylaws, adopting a new board, and working out all the financial aspects of everything. We hope that with the Foundation by our sides, the Tox Project and all of our future projects will prosper.","slug":"stf-4-14","updated":1422148791000,"excerpt":"","_id":"ekkpozb5wykd8fpw","comments":true,"layout":"post","photos":[],"link":""},{"title":"STS Approaches v0.0.5","id":219,"categories":["n3qafcv6z7xjcsay","zeqsivfrc306kq3p"],"date":1397146925000,"tags":[],"content":"<p>After a little more than week of work, the STS is rapidly approaching a first draft. Standards such as DNS Discovery and the URI standard have been set, and naming schemes of often used protocols such as the Tox Network have been established. We’re always looking for criticism, so all input is welcome—even grammar corrections.</p>\n<p>You can check out the current revision of the STS on our <a href=\"https://github.com/Tox/STS/blob/master/STS.md\" target=\"_blank\" rel=\"external\">Tox/STS GitHub repo</a>.</p>\n","source":"_posts/sts-approaches-v0-0-5.md","raw":"title: STS Approaches v0.0.5\nid: 219\ncategories:\n  - STS\n  - Tox Core\ndate: 2014-04-10 12:22:05\ntags:\n---\n\nAfter a little more than week of work, the STS is rapidly approaching a first draft. Standards such as DNS Discovery and the URI standard have been set, and naming schemes of often used protocols such as the Tox Network have been established. We're always looking for criticism, so all input is welcome—even grammar corrections.\n\nYou can check out the current revision of the STS on our [Tox/STS GitHub repo](https://github.com/Tox/STS/blob/master/STS.md).","slug":"sts-approaches-v0-0-5","updated":1422148791000,"excerpt":"","_id":"q28swfj9bkp2ecax","comments":true,"layout":"post","photos":[],"link":""},{"title":"Audio Calling Implemented in Toxic","id":48,"categories":["ysh4ufalq2ulbpz8"],"date":1394564102000,"tags":[],"content":"<p>Last night, a non-gui client was given audio support: Toxic!</p>\n<p>What does this mean? Well for starters toxic is the CLI client, meaning it’s all done in console, so not that many people will be using it. That said, it’s the first real implementation of the audio/video features worked on by mannol and Martijnvdc, with mannol putting audio functionality inside of Toxic as well.</p>\n<p>It took a while for one client to do it, but after this we expect more clients to add support, with an example to go off of. Be warned though, Toxic is buggy right now, and is subject to crashing. This goes along with a daily reminder that Tox is still pre-alpha, but making strides!</p>\n","source":"_posts/audio.md","raw":"title: Audio Calling Implemented in Toxic\nid: 48\ncategories:\n  - Toxic\ndate: 2014-03-11 14:55:02\ntags:\n---\n\nLast night, a non-gui client was given audio support: Toxic!\n\nWhat does this mean? Well for starters toxic is the CLI client, meaning it's all done in console, so not that many people will be using it. That said, it's the first real implementation of the audio/video features worked on by mannol and Martijnvdc, with mannol putting audio functionality inside of Toxic as well.\n\nIt took a while for one client to do it, but after this we expect more clients to add support, with an example to go off of. Be warned though, Toxic is buggy right now, and is subject to crashing. This goes along with a daily reminder that Tox is still pre-alpha, but making strides!","slug":"audio","updated":1420586788000,"excerpt":"","_id":"lpm02fb0deo1d0ya","comments":true,"layout":"post","photos":[],"link":""},{"title":"TCP Branch Merged with Master","id":266,"categories":["nlwrm5tlcr1n8dpi"],"date":1400457616000,"tags":[],"content":"<p>irungentoo has merged the TCP branch he has been long working on today, which now enabled those behind restrictive NATs access to TCP relays in order to connect with other users. Most of the changes were backend, which means not much is required to update existing clients, but be aware that old clients will no longer work with new clients.</p>\n<p>Expect a detailed post about all the changes soon.</p>\n","source":"_posts/tcp-branch-merged-with-master.md","raw":"title: TCP Branch Merged with Master\nid: 266\ncategories:\n  - Tox Core\ndate: 2014-05-18 20:00:16\ntags:\n---\n\nirungentoo has merged the TCP branch he has been long working on today, which now enabled those behind restrictive NATs access to TCP relays in order to connect with other users. Most of the changes were backend, which means not much is required to update existing clients, but be aware that old clients will no longer work with new clients.\n\nExpect a detailed post about all the changes soon.","slug":"tcp-branch-merged-with-master","updated":1420586899000,"excerpt":"","_id":"dirhuqkxbitdlw6i","comments":true,"layout":"post","photos":[],"link":""},{"title":"New Milestone Reached: Audio Calling on Windows","id":280,"categories":["63k4kifl4fx5xmzk","ae9xsrnb1o32hh4a"],"date":1401565305000,"tags":[],"content":"<p>Yesterday a new milestone was reached, winTox (Windows only GUI) now supports audio calling. winTox is the first non command line client and the first Windows client to support audio calling.</p>\n<p>To try it out just grab one of the latest winTox builds from: <a href=\"https://wiki.tox.im/Binaries\" target=\"_blank\" rel=\"external\">https://wiki.tox.im/Binaries</a></p>\n<p>Make sure your friend has a client that supports audio calling (only toxic and winTox do at the moment) then click on your friend and press the call button near the top right corner or accept the incoming call with the same button.</p>\n<p>The audio calling part of Tox currently uses the opus codec at 64kbs for 1 channel 48khz audio. It is encrypted exactly the same way as everything else (text, files, etc..) with xsalsa20 + poly1305 and a temporary key but unlike text and audio it is sent as a lossy packet for minimum delay and because some packet loss in audio transmissions is acceptable.</p>\n<p>Note that Tox and all its clients are still in alpha state so if you encounter any bugs or issues let us know and we will fix them.</p>\n<p>winTox github repo: <a href=\"https://github.com/notsecure/winTox\" target=\"_blank\" rel=\"external\">https://github.com/notsecure/winTox</a></p>\n","source":"_posts/new-milestone-reached-audio-calling-on-windows.md","raw":"title: \"New Milestone Reached: Audio Calling on Windows\"\nid: 280\ncategories:\n  - Google Summer of Code\n  - Tox Core\ndate: 2014-05-31 15:41:45\ntags:\n---\n\nYesterday a new milestone was reached, winTox (Windows only GUI) now supports audio calling. winTox is the first non command line client and the first Windows client to support audio calling.\n\nTo try it out just grab one of the latest winTox builds from: https://wiki.tox.im/Binaries\n\nMake sure your friend has a client that supports audio calling (only toxic and winTox do at the moment) then click on your friend and press the call button near the top right corner or accept the incoming call with the same button.\n\nThe audio calling part of Tox currently uses the opus codec at 64kbs for 1 channel 48khz audio. It is encrypted exactly the same way as everything else (text, files, etc..) with xsalsa20 + poly1305 and a temporary key but unlike text and audio it is sent as a lossy packet for minimum delay and because some packet loss in audio transmissions is acceptable.\n\nNote that Tox and all its clients are still in alpha state so if you encounter any bugs or issues let us know and we will fix them.\n\nwinTox github repo: https://github.com/notsecure/winTox","slug":"new-milestone-reached-audio-calling-on-windows","updated":1422148791000,"excerpt":"","_id":"4fozimgtgyx4gqcc","comments":true,"layout":"post","photos":[],"link":""},{"title":"The TCP branch: An Explanation","id":270,"categories":["nlwrm5tlcr1n8dpi"],"date":1400613716000,"tags":[],"content":"<p>The TCP branch was merged 2 days ago breaking all compatibility with older clients, yesterday, a major protocol change was introduced, if you run a bootstrap node or a client with a core version older than <a href=\"https://github.com/irungentoo/ProjectTox-Core/commit/e85feb8a3db42a0285b940a090c60102fae50374\" target=\"_blank\" rel=\"external\">https://github.com/irungentoo/ProjectTox-Core/commit/e85feb8a3db42a0285b940a090c60102fae50374</a> then please update it.</p>\n<p>So, what does the TCP branch bring to Tox?</p>\n<p>Tox now supports using TCP relay nodes to connect to friends meaning those behind unpunchable NATs should now be able to connect.</p>\n<p>The protocol has been revamped to be better and safer. Packets are now generally smaller in size and the protocol used to transport the data securely has been redesigned in order to prevent possible evil relays from interfering with the connections between you and your friends. The protocol also now supports padding which can be used to obscure the size of the data transmitted.</p>\n<p>Tox can switch between relayed TCP and direct UDP connections seamlessly meaning if you initially connect to a friend with a TCP relay and then for some reason 5 minutes later the hole punching works and the direct UDP starts working Tox will automatically switch from one to the other without the users noticing anything.</p>\n<p>This also means that Tox can switch between different relays if one used to connect to the other peer goes offline. Again, without the users noticing anything.</p>\n<p>There have also been some fixes and optimizations to increase the initial connection speed meaning you should see your friends come online faster than before.</p>\n<p>I will warn you though that group chats and A/V have not yet been updated to work with the TCP so issues with them right now are perfectly normal.</p>\n<p>If you try Tox but can’t connect to anyone make sure you are using an updated core and bootstrapping into the network with an updated node, (<a href=\"https://wiki.tox.im/Nodes\" target=\"_blank\" rel=\"external\">https://wiki.tox.im/Nodes</a>)</p>\n<p>In other news Google Summer of Code has officially started which means the amount of work done on Tox will increase.</p>\n<p>This update brings us closer to our goal of creating the best skype replacement that works everywhere while being both secure and simple to use.</p>\n","source":"_posts/the-tcp-branch-an-explanation.md","raw":"title: \"The TCP branch: An Explanation\"\nid: 270\ncategories:\n  - Tox Core\ndate: 2014-05-20 15:21:56\ntags:\n---\n\nThe TCP branch was merged 2 days ago breaking all compatibility with older clients, yesterday, a major protocol change was introduced, if you run a bootstrap node or a client with a core version older than https://github.com/irungentoo/ProjectTox-Core/commit/e85feb8a3db42a0285b940a090c60102fae50374 then please update it.\n\nSo, what does the TCP branch bring to Tox?\n\nTox now supports using TCP relay nodes to connect to friends meaning those behind unpunchable NATs should now be able to connect.\n\nThe protocol has been revamped to be better and safer. Packets are now generally smaller in size and the protocol used to transport the data securely has been redesigned in order to prevent possible evil relays from interfering with the connections between you and your friends. The protocol also now supports padding which can be used to obscure the size of the data transmitted.\n\nTox can switch between relayed TCP and direct UDP connections seamlessly meaning if you initially connect to a friend with a TCP relay and then for some reason 5 minutes later the hole punching works and the direct UDP starts working Tox will automatically switch from one to the other without the users noticing anything.\n\nThis also means that Tox can switch between different relays if one used to connect to the other peer goes offline. Again, without the users noticing anything.\n\nThere have also been some fixes and optimizations to increase the initial connection speed meaning you should see your friends come online faster than before.\n\nI will warn you though that group chats and A/V have not yet been updated to work with the TCP so issues with them right now are perfectly normal.\n\nIf you try Tox but can't connect to anyone make sure you are using an updated core and bootstrapping into the network with an updated node, (https://wiki.tox.im/Nodes)\n\nIn other news Google Summer of Code has officially started which means the amount of work done on Tox will increase.\n\nThis update brings us closer to our goal of creating the best skype replacement that works everywhere while being both secure and simple to use.","slug":"the-tcp-branch-an-explanation","updated":1422148791000,"excerpt":"","_id":"hdtpvplt0tk8hhs7","comments":true,"layout":"post","photos":[],"link":""},{"title":"To 5,000 and beyond!","id":334,"categories":["nlwrm5tlcr1n8dpi"],"date":1407172966000,"tags":[],"content":"<img src=\"/images/toxcore-over-5000-commits.jpeg\">\n\n<p>Thank you to everyone who has supported us over the year, here’s to the next 5,000!</p>\n","source":"_posts/to-5000-and-beyond.md","raw":"title: \"To 5,000 and beyond!\"\nid: 334\ncategories:\n  - Tox Core\ndate: 2014-08-04 13:22:46\ntags:\n---\n\n{% limg toxcore-over-5000-commits.jpeg %}\n\nThank you to everyone who has supported us over the year, here's to the next 5,000!","slug":"to-5000-and-beyond","updated":1420586900000,"excerpt":"","_id":"dtb3bcsyoyztlnfi","comments":true,"layout":"post","photos":[],"link":""},{"title":"The day we've all been waiting for","id":292,"categories":["nlwrm5tlcr1n8dpi","upkdnlsjjo67oz6b"],"date":1405194014000,"tags":[],"content":"<p>Now that it’s <del>Friday</del> Saturday it’s finally time to spoil the news that we’ve somehow managed to keep mostly secret.</p>\n<p>Tox is once and for all Alpha. Yes, you heard correctly, Alpha. That’s it, go home.</p>\n<p>Kidding! We’ve got a <em>little bit more to share.</em></p>\n<p>Right now when you want to download Tox you click on a button to a wiki page where you follow a confusing chart to find a bunch of builds for various clients, all squeezed together waiting for a click. You don’t know what’s better, you don’t know what does what, and that’s a serious issue.</p>\n<p>First, we’ve introduced a single easy to use webpage. Those confusing charts? gone, just select your OS and be on your way. Remember all those clients when you went to past download Tox? The official client is now just Tox. We’ve gone ahead and chosen the best client for each OS and made it Tox. If you’re used to using builds of other clients or want to try something new don’t be disheartened, we’ll still be providing builds for all the clients so you can test to your hearts extent.</p>\n<p>Having trouble with Tox? soon you’ll be able to go to our new support site, choose your issue, and have an answer. Still confused? You’ll also be able to punch in a question and get a response from a real live human as soon as we can. Say you find a bug, maybe you have a suggestion. Soon you’ll be able to make bug report for Tox, make a suggestion, or just tell us how you feel, and it’ll be sent to the respective support personnel and developers who’ll do what they can to see to it that your bug is resolved as soon as we can.</p>\n<p>And what you’ve all been waiting for, Tox for Windows, OS X, and Linux all have calling, and Tox for Windows has video! Video should be arriving soon for OS X as it’s currently just broken due to a bug, and Linux is being worked on as we speak.</p>\n","source":"_posts/took-long-enough.md","raw":"title: \"The day we've all been waiting for\"\nid: 292\ncategories:\n  - Tox Core\n  - Tox Foundation\ndate: 2014-07-12 15:40:14\ntags:\n---\n\nNow that it's <del>Friday</del> Saturday it's finally time to spoil the news that we've somehow managed to keep mostly secret.\n\nTox is once and for all Alpha. Yes, you heard correctly, Alpha. That's it, go home.\n\nKidding! We've got a _little bit more to share._\n\nRight now when you want to download Tox you click on a button to a wiki page where you follow a confusing chart to find a bunch of builds for various clients, all squeezed together waiting for a click. You don't know what's better, you don't know what does what, and that's a serious issue.\n\nFirst, we've introduced a single easy to use webpage. Those confusing charts? gone, just select your OS and be on your way. Remember all those clients when you went to past download Tox? The official client is now just Tox. We've gone ahead and chosen the best client for each OS and made it Tox. If you're used to using builds of other clients or want to try something new don't be disheartened, we'll still be providing builds for all the clients so you can test to your hearts extent.\n\nHaving trouble with Tox? soon you'll be able to go to our new support site, choose your issue, and have an answer. Still confused? You'll also be able to punch in a question and get a response from a real live human as soon as we can. Say you find a bug, maybe you have a suggestion. Soon you'll be able to make bug report for Tox, make a suggestion, or just tell us how you feel, and it'll be sent to the respective support personnel and developers who'll do what they can to see to it that your bug is resolved as soon as we can.\n\nAnd what you've all been waiting for, Tox for Windows, OS X, and Linux all have calling, and Tox for Windows has video! Video should be arriving soon for OS X as it's currently just broken due to a bug, and Linux is being worked on as we speak.","slug":"took-long-enough","updated":1422148791000,"excerpt":"","_id":"rglzbd97evl5jzhh","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox Bootstrap Now Packaging for armhf","id":592,"categories":["nlwrm5tlcr1n8dpi","augsl7gp3lhrywul"],"date":1417399702000,"tags":[],"content":"<p>For those who own a Raspberry Pi just sitting there, collecting dust after an impulse buying spree, you finally have a reason to use it.<a id=\"more\"></a> With effort from our packager, Urras, we now have the tox-bootstrapd package available for anyone using an armhf instruction set, and quite possibly armel as well. Simply install the <a href=\"https://wiki.tox.im/Binaries#Apt.2FAptitude_.28Debian.2C_Ubuntu.2C_Mint.2C_etc..29\" target=\"_blank\" rel=\"external\">Tox Repo</a> to your Apt or Yum-based distro and off to the races with ye’.</p>\n<p>For more imformation as to what the Tox Bootstrap package does, and why Tox Nodes are important, visit our Running a Bootstrap Node page.</p>\n","source":"_posts/tox-bootstrap-now-packaging-for-armhf.md","raw":"title: Tox Bootstrap Now Packaging for armhf\nid: 592\ncategories:\n  - Tox Core\n  - Tox Repositories\ndate: 2014-11-30 21:08:22\ntags:\n---\n\nFor those who own a Raspberry Pi just sitting there, collecting dust after an impulse buying spree, you finally have a reason to use it.<!-- more --> With effort from our packager, Urras, we now have the tox-bootstrapd package available for anyone using an armhf instruction set, and quite possibly armel as well. Simply install the [Tox Repo](https://wiki.tox.im/Binaries#Apt.2FAptitude_.28Debian.2C_Ubuntu.2C_Mint.2C_etc..29) to your Apt or Yum-based distro and off to the races with ye'.\n\nFor more imformation as to what the Tox Bootstrap package does, and why Tox Nodes are important, visit our Running a Bootstrap Node page.\n","slug":"tox-bootstrap-now-packaging-for-armhf","updated":1420586899000,"excerpt":"<p>For those who own a Raspberry Pi just sitting there, collecting dust after an impulse buying spree, you finally have a reason to use it.","_id":"ge5fxh8gqg1gknrr","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox: A New Direction","id":193,"categories":["q5mc6700pzozi6gl","bxds5mqaljzaayrm","0n0xmqn8bx51wwkb","z49sqq3vv4kxk3re","hpvfrn75g04b5kk8","ss2kdqby9kb3zb90"],"date":1396310726000,"tags":[],"content":"<p>We realized after many people complained that the way we currently use to develop Tox is wrong. C is the worst language to develop a lightweight skype replacement in. Compared to modern languages like C#, JavaScript and Java, C is an old and deprecated language only used by old men with long beards who refuse to update their old MSDOS machines to the much better and modern Windows 8.1. In order to become a popular application, Tox must be built with modern tools and not languages like C that belong in a museum.</p>\n<p>We have decided to rewrite Tox in JavaScript, this will enable us to make use of advanced web frameworks and base our application on advanced libraries such as WinJS and Node.js in order to create the best user experience possible.</p>\n<p>We have listened to those who say we have been re inventing the wheel and pledge to never do it again. As such we will only use proven libraries for the functionality Tox needs.</p>\n<p>Tox will now use i2p for the peer finding, this will also enable you to connect anonymously to other peers. For the networking we will use the very popular C++ Boost libraries to boost our application to a next level of performance and portability. Instead of NaCl (a relatively unknown crypto library) Tox will use OpenSSL, the standard library for secure communication on the internet. Instead of stupidly using the audio and video encoders and decoders directly, Tox will now use WebRTC for audio and video communications. Because of this, Tox will now be compatible with web browsers. Instead of the relatively new and untested ECC cryptography, Tox will now use good old RSA and AES for encryption. We will now use 512 bit RSA keys that are much stronger than the weak 256 bit ECC keys Tox uses right now. Tox will now use namecoin so that everyone can have a unique username which will increase ease of use by large amounts and solve one of the biggest issues that people have been having with current Tox.</p>\n<p>A huge issue that current Tox has is that it fails to sync conversations across devices, we will solve this by using facebook. Using facebook we can securely store the contents of all conversations and your contacts in a location that can be accessed using an extremely secure https connection from anywhere. This will also prevent murderers, terrorists, racists, pedophiles, privacy activists and other people that could hurt the image of Tox from using it for extended periods of time.</p>\n<p>In order to enhance the user interface, the official Tox clients will include buttons so that users can share the contents of their conversations on free social networking websites such as reddit and twitter.</p>\n<p>A significant amount of resources will be spent to create a Tox client that works entirely in the cloud. Tox will now be usable by anyone with a web browser and a facebook account. We now truly see that the browser is the future and that applications running natively on the desktop will soon disappear completely. We had previously though web clients could not be secure but realized that we were wrong. Encrypting things browser side with JavaScript served from a central web server is much more safe than using unsafe languages like C.</p>\n<p>To finance our operations, some advertisements will be added to every Tox client, the only way to disable them will be to compile Tox manually from source which will be very hard to do because we plan to soon remove the bloated build systems from every client.</p>\n<p>I must also warn you that we will not be using git or github to develop this new version of Tox. Git is a creation of Linus Torvalds, a very backwards man who thinks that object oriented programming is very bad and who hates modern safe languages like C++ and Java. Since we don’t agree with him, we cannot in good faith use anything he is the CEO of. Therefore and also to promote synergy between our many developers, we have also decided to migrate our version control system to CVS. CVS has the advantage of forcing people to talk more about their pull request, thus streamlining our communications. We are sure this paradigm shift will help us push the envelope on Tox development.</p>\n<p>We understand that this is a huge change for Tox however we believe this is for the best.</p>\n<p>Thanks again for your continued support,</p>\n<p>Project Tox.</p>\n<p><strong>NOTE: This was posted on April 1 and as such should not be taken seriously.</strong></p>\n","source":"_posts/tox-a-new-direction.md","raw":"title: \"Tox: A New Direction\"\nid: 193\ncategories:\n  - Antox\n  - Poison\n  - Tox Core\n  - Toxic\n  - Toxicity\n  - Venom\ndate: 2014-03-31 20:05:26\ntags:\n---\n\nWe realized after many people complained that the way we currently use to develop Tox is wrong. C is the worst language to develop a lightweight skype replacement in. Compared to modern languages like C#, JavaScript and Java, C is an old and deprecated language only used by old men with long beards who refuse to update their old MSDOS machines to the much better and modern Windows 8.1\\. In order to become a popular application, Tox must be built with modern tools and not languages like C that belong in a museum.\n\nWe have decided to rewrite Tox in JavaScript, this will enable us to make use of advanced web frameworks and base our application on advanced libraries such as WinJS and Node.js in order to create the best user experience possible.\n\nWe have listened to those who say we have been re inventing the wheel and pledge to never do it again. As such we will only use proven libraries for the functionality Tox needs.\n\nTox will now use i2p for the peer finding, this will also enable you to connect anonymously to other peers. For the networking we will use the very popular C++ Boost libraries to boost our application to a next level of performance and portability. Instead of NaCl (a relatively unknown crypto library) Tox will use OpenSSL, the standard library for secure communication on the internet. Instead of stupidly using the audio and video encoders and decoders directly, Tox will now use WebRTC for audio and video communications. Because of this, Tox will now be compatible with web browsers. Instead of the relatively new and untested ECC cryptography, Tox will now use good old RSA and AES for encryption. We will now use 512 bit RSA keys that are much stronger than the weak 256 bit ECC keys Tox uses right now. Tox will now use namecoin so that everyone can have a unique username which will increase ease of use by large amounts and solve one of the biggest issues that people have been having with current Tox.\n\nA huge issue that current Tox has is that it fails to sync conversations across devices, we will solve this by using facebook. Using facebook we can securely store the contents of all conversations and your contacts in a location that can be accessed using an extremely secure https connection from anywhere. This will also prevent murderers, terrorists, racists, pedophiles, privacy activists and other people that could hurt the image of Tox from using it for extended periods of time.\n\nIn order to enhance the user interface, the official Tox clients will include buttons so that users can share the contents of their conversations on free social networking websites such as reddit and twitter.\n\nA significant amount of resources will be spent to create a Tox client that works entirely in the cloud. Tox will now be usable by anyone with a web browser and a facebook account. We now truly see that the browser is the future and that applications running natively on the desktop will soon disappear completely. We had previously though web clients could not be secure but realized that we were wrong. Encrypting things browser side with JavaScript served from a central web server is much more safe than using unsafe languages like C.\n\nTo finance our operations, some advertisements will be added to every Tox client, the only way to disable them will be to compile Tox manually from source which will be very hard to do because we plan to soon remove the bloated build systems from every client.\n\nI must also warn you that we will not be using git or github to develop this new version of Tox. Git is a creation of Linus Torvalds, a very backwards man who thinks that object oriented programming is very bad and who hates modern safe languages like C++ and Java. Since we don't agree with him, we cannot in good faith use anything he is the CEO of. Therefore and also to promote synergy between our many developers, we have also decided to migrate our version control system to CVS. CVS has the advantage of forcing people to talk more about their pull request, thus streamlining our communications. We are sure this paradigm shift will help us push the envelope on Tox development.\n\nWe understand that this is a huge change for Tox however we believe this is for the best.\n\nThanks again for your continued support,\n\nProject Tox.\n\n**NOTE: This was posted on April 1 and as such should not be taken seriously.**","slug":"tox-a-new-direction","updated":1422148791000,"excerpt":"","_id":"pkk7wr65mftzttap","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox Core and API changes","id":158,"categories":["nlwrm5tlcr1n8dpi"],"date":1395377465000,"tags":[],"content":"<p>Recently pushed was the api-fix branch by irungentoo. Nothing too big was changed, fortunately, but things were changed to keep consistencies and so forth. Included in this merge was:</p>\n<ul>\n<li>No more forcing NULL terminated strings in Tox Core (meaning whatever you send to the core, it won’t chop off the end forcefully)</li>\n<li>Some naming changes like tox_get_friend_id -&gt; tox_get_friend_number to clear some confusions</li>\n<li>Many <code>int</code>s were changed to <code>int32_t</code> for consistency and clarity<br>You can check all the changes <a href=\"https://github.com/irungentoo/ProjectTox-Core/commit/5770a0e29ab35efb1ef656ab81c499635fc5fecf\" target=\"_blank\" rel=\"external\">here</a>, as well.</li>\n</ul>\n<p>All of the clients have been able to update their builds to reflect the API changes as well, amazingly fast. There might be even more changes to come to make the API even better in the future! In other news, more work is being done on TCP in the core. Can’t wait for that to finish.</p>\n","source":"_posts/tox-core-and-api-changes.md","raw":"title: Tox Core and API changes\nid: 158\ncategories:\n  - Tox Core\ndate: 2014-03-21 00:51:05\ntags:\n---\n\nRecently pushed was the api-fix branch by irungentoo. Nothing too big was changed, fortunately, but things were changed to keep consistencies and so forth. Included in this merge was:\n\n*   No more forcing NULL terminated strings in Tox Core (meaning whatever you send to the core, it won't chop off the end forcefully)\n*   Some naming changes like tox_get_friend_id -&gt; tox_get_friend_number to clear some confusions\n*   Many `int`s were changed to `int32_t` for consistency and clarity\nYou can check all the changes [here](https://github.com/irungentoo/ProjectTox-Core/commit/5770a0e29ab35efb1ef656ab81c499635fc5fecf), as well.\n\nAll of the clients have been able to update their builds to reflect the API changes as well, amazingly fast. There might be even more changes to come to make the API even better in the future! In other news, more work is being done on TCP in the core. Can't wait for that to finish.","slug":"tox-core-and-api-changes","updated":1422148791000,"excerpt":"","_id":"o82x6to410zsc7c5","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox now works through Tor (and other proxies)","id":349,"categories":["nlwrm5tlcr1n8dpi"],"date":1408126142000,"tags":[],"content":"<p>Toxcore can now function on TCP only as a fall back when UDP can’t be used.</p>\n<p>There were many people who requested Tor support so I implemented basic SOCKS5 proxy support for toxcore TCP connections.</p>\n<p>To use Tox with Tor, set your Tor proxy address in your Tox client proxy settings and disable UDP (UDP connections bypass the proxy and must be disabled if the proxy is used for privacy and not simply for accessing the internet).</p>\n<p>This will make toxcore use Tor for all connections.</p>\n<p>As of now I’m pretty sure the only possible toxcore leak (if UDP is disabled) would be if a DNS name is passed to the tox_bootstrap_from_address() function it would not be resolved using Tor. (I’m pretty sure all the main clients only pass ip addresses to this function though.)</p>\n<p>Clients are not Tor safe yet and bypass the proxy for any non toxcore related network communications (DNS names for example) which means it should not be used in situations that require serious anonymity yet (unless you use something like iptables to plug the leaks).</p>\n<p>Happy Anonymous Toxing.</p>\n","source":"_posts/tox-now-works-through-tor.md","raw":"title: Tox now works through Tor (and other proxies)\nid: 349\ncategories:\n  - Tox Core\ndate: 2014-08-15 14:09:02\ntags:\n---\n\nToxcore can now function on TCP only as a fall back when UDP can't be used.\n\nThere were many people who requested Tor support so I implemented basic SOCKS5 proxy support for toxcore TCP connections.\n\nTo use Tox with Tor, set your Tor proxy address in your Tox client proxy settings and disable UDP (UDP connections bypass the proxy and must be disabled if the proxy is used for privacy and not simply for accessing the internet).\n\nThis will make toxcore use Tor for all connections.\n\nAs of now I'm pretty sure the only possible toxcore leak (if UDP is disabled) would be if a DNS name is passed to the tox_bootstrap_from_address() function it would not be resolved using Tor. (I'm pretty sure all the main clients only pass ip addresses to this function though.)\n\nClients are not Tor safe yet and bypass the proxy for any non toxcore related network communications (DNS names for example) which means it should not be used in situations that require serious anonymity yet (unless you use something like iptables to plug the leaks).\n\nHappy Anonymous Toxing.","slug":"tox-now-works-through-tor","updated":1420586788000,"excerpt":"","_id":"mw2mkbx3a4tlznud","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox on OSX","id":550,"categories":["n2ucmyxmms5yv6mr","r8wa1580n6ik5nes"],"date":1414010209000,"tags":[],"content":"<p>Hodwy folks,</p>\n<p>After 27 whole days of delay our Tox downloads for OS X work again, and are better than ever!</p>\n<p>We ran them previously, but progress on clients stagnated and we couldn’t justify the extra cost to build binaries that didn’t really work.<br><a id=\"more\"></a><br>Now that qTox works great on OS X we’ve continued our builds for all our OS X users, you can download them <a href=\"https://wiki.tox.im/Binaries#OS_X\" title=\"here\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<p>Happy Toxing!</p>\n","source":"_posts/tox-on-osx.md","raw":"title: Tox on OSX\nid: 550\ncategories:\n  - qTox\n  - Tox Core\ndate: 2014-10-22 16:36:49\ntags:\n---\n\nHodwy folks,\n\nAfter 27 whole days of delay our Tox downloads for OS X work again, and are better than ever!\n\nWe ran them previously, but progress on clients stagnated and we couldn't justify the extra cost to build binaries that didn't really work.\n<!-- more -->\nNow that qTox works great on OS X we've continued our builds for all our OS X users, you can download them [here](https://wiki.tox.im/Binaries#OS_X \"here\").\n\nHappy Toxing!\n","slug":"tox-on-osx","updated":1422148791000,"excerpt":"<p>Hodwy folks,</p>\n<p>After 27 whole days of delay our Tox downloads for OS X work again, and are better than ever!</p>\n<p>We ran them previously, but progress on clients stagnated and we couldn’t justify the extra cost to build binaries that didn’t really work.<br>","_id":"57a990xmw3ju9ba3","comments":true,"layout":"post","photos":[],"link":""},{"title":"Lets Tox, everywhere!","id":552,"categories":["rpfxl29wpibc9sbf","0r4cfoczye4c9gdv","tthwe6ydx6ente4g","03sb46ncmqp9o8ly"],"date":1414011383000,"tags":[],"content":"<p>Howdy folks for the 2nd time today!</p>\n<p>Remember that time you got Linux running on your Wii? When you managed to install Debian to your Raspberry Pi?</p>\n<p>Wouldn’t it be <em>super cool</em> if you could Tox your friends without dealing with a compiler or git?<br><a id=\"more\"></a><br>Thankfully we agree, and we know you have tons of other cases where x86/x86_64 might not be the architecture of your PC. We believe you should be able to Tox no matter where you are or what you use without a bunch of work or hacks, so we’re introducing the Tox Everywhere initiative.</p>\n<p>Be it your PowerPC Mac running Linux or your Wii, the Tox Everywhere initiative was created to give everyone with whatever odd case you may have the same ease of ability to use Tox as our traditional x86 friends</p>\n<p>In the coming weeks expect to see more posts on more architectures and clients, all ready to go directly in our repo so you can install Tox with the same repo instructions we already have on our <a href=\"https://wiki.tox.im/Binaries\" title=\"binaries\" target=\"_blank\" rel=\"external\">binaries</a> page.</p>\n<p>Phase one of this program is targeting the Arm, Armv7, PowerPC, and PowerPC64 architectures and is currently being created as we speak. <a href=\"http://jenkins.libtoxcore.so/job/qTox-Linux-pkg/\" title=\"PowerPC packages for qTox\" target=\"_blank\" rel=\"external\">PowerPC packages for qTox</a> already exist ready for you to install, though they are not yet in the repo.</p>\n<p>For the 2nd time, happy Toxing</p>\n<p>ps: If you have any questions on what we’ll support or when shoot me an email or Tox me, sean [at] tox [.] im</p>\n","source":"_posts/tox-on-your-wii.md","raw":"title: \"Lets Tox, everywhere!\"\nid: 552\ncategories:\n  - Jenkins\n  - Tox Core\n  - Tox Foundation\n  - Tox Repositories\ndate: 2014-10-22 16:56:23\ntags:\n---\n\nHowdy folks for the 2nd time today!\n\nRemember that time you got Linux running on your Wii? When you managed to install Debian to your Raspberry Pi?\n\nWouldn't it be *super cool* if you could Tox your friends without dealing with a compiler or git?\n<!-- more -->\nThankfully we agree, and we know you have tons of other cases where x86/x86_64 might not be the architecture of your PC. We believe you should be able to Tox no matter where you are or what you use without a bunch of work or hacks, so we're introducing the Tox Everywhere initiative.\n\nBe it your PowerPC Mac running Linux or your Wii, the Tox Everywhere initiative was created to give everyone with whatever odd case you may have the same ease of ability to use Tox as our traditional x86 friends\n\nIn the coming weeks expect to see more posts on more architectures and clients, all ready to go directly in our repo so you can install Tox with the same repo instructions we already have on our [binaries](https://wiki.tox.im/Binaries \"binaries\") page.\n\nPhase one of this program is targeting the Arm, Armv7, PowerPC, and PowerPC64 architectures and is currently being created as we speak. [PowerPC packages for qTox](http://jenkins.libtoxcore.so/job/qTox-Linux-pkg/ \"PowerPC packages for qTox\") already exist ready for you to install, though they are not yet in the repo.\n\nFor the 2nd time, happy Toxing\n\nps: If you have any questions on what we'll support or when shoot me an email or Tox me, sean [at] tox [.] im\n","slug":"tox-on-your-wii","updated":1422148791000,"excerpt":"<p>Howdy folks for the 2nd time today!</p>\n<p>Remember that time you got Linux running on your Wii? When you managed to install Debian to your Raspberry Pi?</p>\n<p>Wouldn’t it be <em>super cool</em> if you could Tox your friends without dealing with a compiler or git?<br>","_id":"o78q2cq2e32bsa45","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox, packaging, and versions","id":583,"categories":["nlwrm5tlcr1n8dpi","augsl7gp3lhrywul"],"date":1416795004000,"tags":[],"content":"<p>As many of you know, Tox follows a pretty fun rolling release style alpha development cycle where a lot of code changes and improves very rapidly without any set pace.<br><a id=\"more\"></a><br>Because of the oh so fast pace of this we spent a good deal of time designing a cross-OS compilation system that churns out the latest copy of Tox no more than 5 minutes after a commit was pushed ready to be tested by you, our lovely users.</p>\n<p>Because we churned out builds so fast we knew we needed a way to make sure you always ran the latest version of Tox + your favourite client so you could enjoy all the new features and bug fixes as soon as is possible. As such we statically linked and packaged the Linux clients sitting in a repo we run, designed autoupdaters for our Windows clients, and spent a good deal working on efficient ways to update on OS X seamlessly.</p>\n<p>While this system works out wonderfully for those users who pull the tox clients from this repo or use our autoupdaters, there still exists the group of users who use distribution created packages. The problem with distro packaging is that for rolling release software it reduces and slows our ability to get the latest features or security fixes directly in to your hands.</p>\n<p>Our issue with distro packaging at this stage is simple, we don’t want our users to miss out on features or critical security fixes at the hand of slower packagers or the bureaucratic cycle/freeze model that some Linux distributions implement(looking at you, Debian).</p>\n<p>Why is this post happening now of all times? Lemmie tell you a little story.</p>\n<p>A few days back a user entered our IRC channel asking for help joining group chats, he explained that he just ran apt-get update/upgrade and installed the latest Tox package and he wasn’t getting invites to the chat at all. After a bit of questioning I realised he used an obscure Ubuntu fork aimed at older systems that shipped a copy of utox that was almost a month old. It turns out he was attempting to join the new audio group chats with a super old client. After he added our up to date and current repositories he had no more issues.</p>\n<p>If you don’t think this mess is still an issue, <a href=\"https://github.com/irungentoo/toxcore/compare/master%40%7B30day%7D...master\" target=\"_blank\" rel=\"external\">I encourage you to take a look at all the changes that have happened to toxcore alone.</a></p>\n<p>About versioning, it won’t happen while we’re in our rolling release alpha build cycle.</p>\n<p>&nbsp;</p>\n<p>Happy Toxing, Sean</p>\n","source":"_posts/tox-packaging-and-versions.md","raw":"title: \"Tox, packaging, and versions\"\nid: 583\ncategories:\n  - Tox Core\n  - Tox Repositories\ndate: 2014-11-23 21:10:04\ntags:\n---\n\nAs many of you know, Tox follows a pretty fun rolling release style alpha development cycle where a lot of code changes and improves very rapidly without any set pace.\n<!-- more -->\nBecause of the oh so fast pace of this we spent a good deal of time designing a cross-OS compilation system that churns out the latest copy of Tox no more than 5 minutes after a commit was pushed ready to be tested by you, our lovely users.\n\nBecause we churned out builds so fast we knew we needed a way to make sure you always ran the latest version of Tox + your favourite client so you could enjoy all the new features and bug fixes as soon as is possible. As such we statically linked and packaged the Linux clients sitting in a repo we run, designed autoupdaters for our Windows clients, and spent a good deal working on efficient ways to update on OS X seamlessly.\n\nWhile this system works out wonderfully for those users who pull the tox clients from this repo or use our autoupdaters, there still exists the group of users who use distribution created packages. The problem with distro packaging is that for rolling release software it reduces and slows our ability to get the latest features or security fixes directly in to your hands.\n\nOur issue with distro packaging at this stage is simple, we don’t want our users to miss out on features or critical security fixes at the hand of slower packagers or the bureaucratic cycle/freeze model that some Linux distributions implement(looking at you, Debian).\n\nWhy is this post happening now of all times? Lemmie tell you a little story.\n\nA few days back a user entered our IRC channel asking for help joining group chats, he explained that he just ran apt-get update/upgrade and installed the latest Tox package and he wasn’t getting invites to the chat at all. After a bit of questioning I realised he used an obscure Ubuntu fork aimed at older systems that shipped a copy of utox that was almost a month old. It turns out he was attempting to join the new audio group chats with a super old client. After he added our up to date and current repositories he had no more issues.\n\nIf you don't think this mess is still an issue, [I encourage you to take a look at all the changes that have happened to toxcore alone.](https://github.com/irungentoo/toxcore/compare/master%40%7B30day%7D...master)\n\nAbout versioning, it won't happen while we're in our rolling release alpha build cycle.\n\n&nbsp;\n\nHappy Toxing, Sean\n","slug":"tox-packaging-and-versions","updated":1422148791000,"excerpt":"<p>As many of you know, Tox follows a pretty fun rolling release style alpha development cycle where a lot of code changes and improves very rapidly without any set pace.<br>","_id":"pdytut5vf1p1xv6n","comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox Updates! Kinda","id":287,"categories":["nlwrm5tlcr1n8dpi"],"date":1404803016000,"tags":[],"content":"<p>Well folks, here we are, a blog post in what seems like forever.</p>\n<p>Now, if you’re following the project off our blog and twitter, don’t get discouraged, we’re still alive and well, busily working away.</p>\n<p>So, if you haven’t heard we introduced a site called <a href=\"https://toxme.se\" title=\"https://toxme.se\" target=\"_blank\" rel=\"external\">https://toxme.se</a>, a fast and easy way to share your ID with your friends. It’s as simple as punching in an ID, selecting a name, and getting a name like joe@toxme.se. Now I know what you may be wondering, isn’t this controlling in some sense? To correctly answer that we’ll have to look at how it works. The website is an extension of the DNS Discovery standard, a method for storing keys in DNS records, usually encrypted to prevent spoofing and mitm attacks. The way this works is that you can take your domain like cats.com and make your own sarah user, so all your friends can add you by adding sarah@cats.com, we’ve just gone ahead and setup a site to make it easy.</p>\n<p>Now, toxme isn’t new, we introduced it a few weeks back, but never formally announced its arrival. If you signed up back then keep in mind, a few weeks back we did wipe all the records as we moved to an encrypted format, so your entry may no longer exist.</p>\n<p>Now, I know what you’re thinking, that can’t be all they’ve done, right?</p>\n<p>Right!, but we want to keep a good bit of it a surprise, so hold on to your horses for a few more days, this is going to be big.</p>\n<p>Happy Toxxing,</p>\n<p>Sean</p>\n","source":"_posts/tox-updates-kinda.md","raw":"title: \"Tox Updates! Kinda\"\nid: 287\ncategories:\n  - Tox Core\ndate: 2014-07-08 03:03:36\ntags:\n---\n\nWell folks, here we are, a blog post in what seems like forever.\n\nNow, if you're following the project off our blog and twitter, don't get discouraged, we're still alive and well, busily working away.\n\nSo, if you haven't heard we introduced a site called [https://toxme.se](https://toxme.se \"https://toxme.se\"), a fast and easy way to share your ID with your friends. It's as simple as punching in an ID, selecting a name, and getting a name like joe@toxme.se. Now I know what you may be wondering, isn't this controlling in some sense? To correctly answer that we'll have to look at how it works. The website is an extension of the DNS Discovery standard, a method for storing keys in DNS records, usually encrypted to prevent spoofing and mitm attacks. The way this works is that you can take your domain like cats.com and make your own sarah user, so all your friends can add you by adding sarah@cats.com, we've just gone ahead and setup a site to make it easy.\n\nNow, toxme isn't new, we introduced it a few weeks back, but never formally announced its arrival. If you signed up back then keep in mind, a few weeks back we did wipe all the records as we moved to an encrypted format, so your entry may no longer exist.\n\nNow, I know what you're thinking, that can't be all they've done, right?\n\nRight!, but we want to keep a good bit of it a surprise, so hold on to your horses for a few more days, this is going to be big.\n\nHappy Toxxing,\n\nSean","slug":"tox-updates-kinda","updated":1420586788000,"excerpt":"","_id":"8risgqer3wnxllzx","comments":true,"layout":"post","photos":[],"link":""},{"title":"Toxic added to Tox Repositories","id":483,"categories":["jhq3nve14qq04ygg","ubz8ogw0dlh8pv9k"],"date":1412580959000,"tags":[],"content":"<p>One of our oldest, but feature-rich clients, <a href=\"https://wiki.tox.im/Toxic\" target=\"_blank\" rel=\"external\">Toxic</a>, has been added to the Tox Repos. Toxic uses an ncurses interface, and is written in C. All Unix-like operating systems are currently supported (e.g. Linux, OSX, FreeBSD).</p>\n<p><a id=\"more\"></a><br>If you haven’t added our repository yet, you can follow <a href=\"https://wiki.tox.im/Binaries#Repositories\" target=\"_blank\" rel=\"external\">these instructions.</a> You can also download the packages directly <a href=\"https://jenkins.libtoxcore.so/job/toxic-linux-pkg/\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<img src=\"/images/toxic-0-5-1.png\">\n","source":"_posts/toxic-added-to-tox-repositories.md","raw":"title: Toxic added to Tox Repositories\nid: 483\ncategories:\n  - Tox Repositories\n  - Toxic\ndate: 2014-10-06 03:35:59\ntags:\n---\n\nOne of our oldest, but feature-rich clients, [Toxic](https://wiki.tox.im/Toxic), has been added to the Tox Repos. Toxic uses an ncurses interface, and is written in C. All Unix-like operating systems are currently supported (e.g. Linux, OSX, FreeBSD).\n\n<!-- more -->\nIf you haven't added our repository yet, you can follow [these instructions.](https://wiki.tox.im/Binaries#Repositories) You can also download the packages directly [here](https://jenkins.libtoxcore.so/job/toxic-linux-pkg/).\n\n{% limg toxic-0-5-1.png %}\n","slug":"toxic-added-to-tox-repositories","updated":1420586900000,"excerpt":"<p>One of our oldest, but feature-rich clients, <a href=\"https://wiki.tox.im/Toxic\" target=\"_blank\" rel=\"external\">Toxic</a>, has been added to the Tox Repos. Toxic uses an ncurses interface, and is written in C. All Unix-like operating systems are currently supported (e.g. Linux, OSX, FreeBSD).</p>\n<p>","_id":"8za5rho1j52vrt7c","comments":true,"layout":"post","photos":[],"link":""},{"title":"Toxic release v.0.5.2 (and groupchat issues)","id":459,"categories":["ysh4ufalq2ulbpz8"],"date":1412315363000,"tags":[],"content":"<p>Major changes include:</p>\n<ul>\n<li>Ability to set an avatar. You can set it in the config file (see the <a href=\"https://github.com/Tox/toxic/blob/master/misc/toxic.conf.example\" target=\"_blank\" rel=\"external\">example config file</a>) or with the command ‘/avatar &lt;path&gt;’ (Note: This command will only set it temporarily until you restart your client).</li>\n<li>Previous chat history is now loaded when you open a chat window.</li>\n<li>Chat log files are now renamed when a contact changes their name instead of creating a new log file and leaving the old one.</li>\n<li>Resolved a performance issue where idle CPU usage was unacceptably high when compiled with sound notifications.</li>\n<li>Some small UI changes that need no explanation.</li>\n<li>Lots of important bug fixes<br>The currently ongoing toxcore groupchat rewrite broke Toxic’s implementation of groupchats. Any version of Toxic older than <strong>c56c6cc2</strong> will behave very strangely with the new groupchats (this may be temporary).</li>\n</ul>\n<p>Also, as of writing this GroupBot is up to date with the latest core, so if you can’t get an invite from him then you need to update your toxcore.</p>\n<p>tldr; update everything</p>\n","source":"_posts/toxic-release-v-0-5-2-and-groupchat-issues.md","raw":"title: Toxic release v.0.5.2 (and groupchat issues)\nid: 459\ncategories:\n  - Toxic\ndate: 2014-10-03 01:49:23\ntags:\n---\n\nMajor changes include:\n\n*   Ability to set an avatar. You can set it in the config file (see the [example config file](https://github.com/Tox/toxic/blob/master/misc/toxic.conf.example)) or with the command '/avatar &lt;path&gt;' (Note: This command will only set it temporarily until you restart your client).\n*   Previous chat history is now loaded when you open a chat window.\n*   Chat log files are now renamed when a contact changes their name instead of creating a new log file and leaving the old one.\n*   Resolved a performance issue where idle CPU usage was unacceptably high when compiled with sound notifications.\n*   Some small UI changes that need no explanation.\n*   Lots of important bug fixes\nThe currently ongoing toxcore groupchat rewrite broke Toxic's implementation of groupchats. Any version of Toxic older than **c56c6cc2** will behave very strangely with the new groupchats (this may be temporary).\n\nAlso, as of writing this GroupBot is up to date with the latest core, so if you can't get an invite from him then you need to update your toxcore.\n\ntldr; update everything\n","slug":"toxic-release-v-0-5-2-and-groupchat-issues","updated":1422148791000,"excerpt":"","_id":"47apcdc7jj0le6x4","comments":true,"layout":"post","photos":[],"link":""},{"title":"Toxicity and background and notifications","id":179,"categories":["jmr06mopc1cr2ep1"],"date":1395805313000,"tags":[],"content":"<p>A lot of work is being done on Toxicity recently, one of which is <a href=\"https://blog.libtoxcore.so/128/jenkins-ci-and-signed-commits\" target=\"_blank\" rel=\"external\">signed commits</a>! There was a small hiccup in getting used to it, but from now on everything should be nice and trustable. There’s also a lot of under-the-hood refactoring happening, cleaning up messy code and such, better for developers.</p>\n<p>The reason for this post, though, is the addition of background running and notifications. Currently Toxicity is using a max 10 minute timer (by iOS) to allow apps to utilize background threads while the app isn’t running in the foreground. This allows the app to not completely shutdown and restart Tox core every time you switch out of the app! Right now tox_do has a bit of a bigger interval in-between, but users should still be warned about battery drainage.</p>\n<p>As a result of this background servicing, notifications were possible to add, using simple UILocalNotifications, for incoming messages. It shows the sender, and which groupchat it came from provided it wasn’t a friend’s message. There’s a bit of work to be done still. This mainly includes switching to appropriate chat windows once the user opens the app via notification.</p>\n","source":"_posts/toxicity-and-background-and-notifications.md","raw":"title: Toxicity and background and notifications\nid: 179\ncategories:\n  - Toxicity\ndate: 2014-03-25 23:41:53\ntags:\n---\n\nA lot of work is being done on Toxicity recently, one of which is [signed commits](https://blog.libtoxcore.so/128/jenkins-ci-and-signed-commits)! There was a small hiccup in getting used to it, but from now on everything should be nice and trustable. There's also a lot of under-the-hood refactoring happening, cleaning up messy code and such, better for developers.\n\nThe reason for this post, though, is the addition of background running and notifications. Currently Toxicity is using a max 10 minute timer (by iOS) to allow apps to utilize background threads while the app isn't running in the foreground. This allows the app to not completely shutdown and restart Tox core every time you switch out of the app! Right now tox_do has a bit of a bigger interval in-between, but users should still be warned about battery drainage.\n\nAs a result of this background servicing, notifications were possible to add, using simple UILocalNotifications, for incoming messages. It shows the sender, and which groupchat it came from provided it wasn't a friend's message. There's a bit of work to be done still. This mainly includes switching to appropriate chat windows once the user opens the app via notification.","slug":"toxicity-and-background-and-notifications","updated":1420586899000,"excerpt":"","_id":"5bvei27mm7kola0s","comments":true,"layout":"post","photos":[],"link":""},{"title":"Toxicity and Jenkins","id":156,"categories":["jmr06mopc1cr2ep1"],"date":1395376816000,"tags":[],"content":"<p>The main Toxicity dev has finally finished with some personal stuff and is back to working on Toxicity, rather than merging a bunch of pull requests! Along with that the Jenkins build for Toxicity is working perfectly, thanks to stqism (Sean) and stal for their work on that.</p>\n<p>Along with some recent commits, a few big issues were resolved, including updating core and fixing some PR bugs. Hopefully there’ll be more in the future. A little bird hinted to me something about background threading…</p>\n","source":"_posts/toxicity-and-jenkins.md","raw":"title: Toxicity and Jenkins\nid: 156\ncategories:\n  - Toxicity\ndate: 2014-03-21 00:40:16\ntags:\n---\n\nThe main Toxicity dev has finally finished with some personal stuff and is back to working on Toxicity, rather than merging a bunch of pull requests! Along with that the Jenkins build for Toxicity is working perfectly, thanks to stqism (Sean) and stal for their work on that.\n\nAlong with some recent commits, a few big issues were resolved, including updating core and fixing some PR bugs. Hopefully there'll be more in the future. A little bird hinted to me something about background threading...","slug":"toxicity-and-jenkins","updated":1420586899000,"excerpt":"","_id":"80c22x83tfu33s35","comments":true,"layout":"post","photos":[],"link":""},{"title":"uTox now has Audio Filtering (Noise cancellation, etc..).","id":577,"categories":["8mjo8a20yy8ruzwh"],"date":1416787618000,"tags":[],"content":"<p>To turn it on, the dropdown is right beside the audio input settings in uTox. You can preview your filtered (or not) audio by clicking on the preview button.</p>\n<p>Currently noise reduction and gain control are properly implemented.<br><a id=\"more\"></a><br>This is what it uses to filter the audio: <a href=\"https://github.com/irungentoo/filter_audio\" title=\"filter_audio\" target=\"_blank\" rel=\"external\">github repo here</a> I put it in its own repo so other clients can easily add it too.</p>\n<p>I really would like to know how well it performs so please try it out and tell us.</p>\n","source":"_posts/utox-now-has-audio-filtering-noise-cancellation-etc.md","raw":"title: \"uTox now has Audio Filtering (Noise cancellation, etc..).\"\nid: 577\ncategories:\n  - μTox\ndate: 2014-11-23 19:06:58\ntags:\n---\n\nTo turn it on, the dropdown is right beside the audio input settings in uTox. You can preview your filtered (or not) audio by clicking on the preview button.\n\nCurrently noise reduction and gain control are properly implemented.\n<!-- more -->\nThis is what it uses to filter the audio: [github repo here](https://github.com/irungentoo/filter_audio \"filter_audio\") I put it in its own repo so other clients can easily add it too.\n\nI really would like to know how well it performs so please try it out and tell us.\n","slug":"utox-now-has-audio-filtering-noise-cancellation-etc","updated":1420586788000,"excerpt":"<p>To turn it on, the dropdown is right beside the audio input settings in uTox. You can preview your filtered (or not) audio by clicking on the preview button.</p>\n<p>Currently noise reduction and gain control are properly implemented.<br>","_id":"tl9mecwlyh0llmyo","comments":true,"layout":"post","photos":[],"link":""},{"title":"uTox now in Apt & Yum Repos","id":437,"categories":["jhq3nve14qq04ygg","79izstuei0zdeqwv"],"date":1411941379000,"tags":[],"content":"<p>uTox is now the second Tox client to be hosted on the Tox Repositories, second to Venom.<br>If you haven’t already, add our Tox repo to Apt or Yum by following <a href=\"https://wiki.tox.im/Binaries#Repositories\" target=\"_blank\" rel=\"external\">these instructions.</a> It’s a great way to get the latest changes to Tox clients in a quick and easy fashion.</p>\n<p>32 and 64bit instructions supported; more to come in the upcoming week! (We’re in the process of getting Toxic and qTox on the repo as well!)</p>\n<img src=\"/images/utox-small.png\">","source":"_posts/utox-now-in-apt-yum-repos.md","raw":"title: \"uTox now in Apt & Yum Repos\"\nid: 437\ncategories:\n  - Tox Repositories\n  - μTox\ndate: 2014-09-28 17:56:19\ntags:\n---\n\nuTox is now the second Tox client to be hosted on the Tox Repositories, second to Venom.\nIf you haven't already, add our Tox repo to Apt or Yum by following [these instructions.](https://wiki.tox.im/Binaries#Repositories) It's a great way to get the latest changes to Tox clients in a quick and easy fashion.\n\n32 and 64bit instructions supported; more to come in the upcoming week! (We're in the process of getting Toxic and qTox on the repo as well!)\n\n{% limg utox-small.png %}","slug":"utox-now-in-apt-yum-repos","updated":1420586900000,"excerpt":"","_id":"gk9jjem57bx5aw1l","comments":true,"layout":"post","photos":[],"link":""},{"title":"uTox updates 0.1.8","id":410,"categories":["8mjo8a20yy8ruzwh"],"date":1411588168000,"tags":[],"content":"<p>What’s new: Save file location changed, bug fixes, bug fixes, new translations and some small features like the icon on Windows changing colour when a message is received.</p>\n<p>For credits and a detailed list of all changes: <a href=\"https://github.com/notsecure/uTox/commits/master\" title=\"https://github.com/notsecure/uTox/commits/master\" target=\"_blank\" rel=\"external\">https://github.com/notsecure/uTox/commits/master</a></p>\n<p>The main change in this update and why I made this post is that uTox now saves to roaming appdata instead of local appdata which should lead to less people losing their saves. uTox should automatically load the save from its previous location meaning you don’t have to move it there yourself. What you should do that uTox doesn’t do is remove the old location.</p>\n<p>Also, if anyone isn’t aware of this yet, I will be the one maintaining uTox from now on until notsecure is less busy.</p>\n<p>Expect something bigger next week.</p>\n","source":"_posts/utox-updates-0-1-8.md","raw":"title: uTox updates 0.1.8\nid: 410\ncategories:\n  - μTox\ndate: 2014-09-24 15:49:28\ntags:\n---\n\nWhat's new: Save file location changed, bug fixes, bug fixes, new translations and some small features like the icon on Windows changing colour when a message is received.\n\nFor credits and a detailed list of all changes: [https://github.com/notsecure/uTox/commits/master](https://github.com/notsecure/uTox/commits/master \"https://github.com/notsecure/uTox/commits/master\")\n\nThe main change in this update and why I made this post is that uTox now saves to roaming appdata instead of local appdata which should lead to less people losing their saves. uTox should automatically load the save from its previous location meaning you don't have to move it there yourself. What you should do that uTox doesn't do is remove the old location.\n\nAlso, if anyone isn't aware of this yet, I will be the one maintaining uTox from now on until notsecure is less busy.\n\nExpect something bigger next week.","slug":"utox-updates-0-1-8","updated":1422148791000,"excerpt":"","_id":"wb9ublewc3t5aac6","comments":true,"layout":"post","photos":[],"link":""},{"title":"uTox updates 0.1.a","id":452,"categories":["8mjo8a20yy8ruzwh"],"date":1412290733000,"tags":[],"content":"<p>The major update this week is the new groupchats that should work much better (connection wise) than the old ones. Note that as of now they are still missing important features like usernames but the base of them (joining/quitting/sending messages) should already work well.</p>\n<p>As for uTox, mainly bug/translation fixes.</p>\n<p>Also, I will be pushing updates in a more regular manner until group chats work well.</p>\n","source":"_posts/utox-updates-0-1-a.md","raw":"title: uTox updates 0.1.a\nid: 452\ncategories:\n  - μTox\ndate: 2014-10-02 18:58:53\ntags:\n---\n\nThe major update this week is the new groupchats that should work much better (connection wise) than the old ones. Note that as of now they are still missing important features like usernames but the base of them (joining/quitting/sending messages) should already work well.\n\nAs for uTox, mainly bug/translation fixes.\n\nAlso, I will be pushing updates in a more regular manner until group chats work well.","slug":"utox-updates-0-1-a","updated":1420586788000,"excerpt":"","_id":"7nxuuurzrvn9rud6","comments":true,"layout":"post","photos":[],"link":""},{"title":"Venom Changes for March 12th, 2014","id":68,"categories":["xyv47d59cscxjvsj"],"date":1394633870000,"tags":[],"content":"<p>Lots of small changes lately that all add up to a great user experience. Here are the changes for March 12th, 2014:</p>\n<ul>\n<li>ToxSession function names were changed to better reflect the Tox Core function names</li>\n<li>Username and status messages are now set via signals</li>\n<li>A tooltip has been added to each contact in the contact list, which includes a last seen message.</li>\n<li>Name highlighting has been implemented</li>\n<li>URI support for launching a certain conversation has been added.</li>\n</ul>\n","source":"_posts/venom-changes-for-march-12th-2014.md","raw":"title: \"Venom Changes for March 12th, 2014\"\nid: 68\ncategories:\n  - Venom\ndate: 2014-03-12 10:17:50\ntags:\n---\n\nLots of small changes lately that all add up to a great user experience. Here are the changes for March 12th, 2014:\n\n*   ToxSession function names were changed to better reflect the Tox Core function names\n*   Username and status messages are now set via signals\n*   A tooltip has been added to each contact in the contact list, which includes a last seen message.\n*   Name highlighting has been implemented\n*   URI support for launching a certain conversation has been added.","slug":"venom-changes-for-march-12th-2014","updated":1420586899000,"excerpt":"","_id":"2ae9uyn50tdnxzjs","comments":true,"layout":"post","photos":[],"link":""},{"title":"Warrant Canary Changes","id":346,"categories":["i0yjl3tz23qj3npq"],"date":1407954684000,"tags":[],"content":"<p>While moving the wiki frontend a week ago we managed to forget to move it after changing the IP. This resulted in it being down for around a week.</p>\n<p>We apologize for making this mistake, and have not been contacted by {3 letter agency}.</p>\n<p>In addition to this, the canary is now located at <a href=\"https://wiki.tox.im/canary.html\" target=\"_blank\" rel=\"external\">https://wiki.tox.im/canary.html</a></p>\n<p>It is also pgp signed with the build system key at <a href=\"https://wiki.tox.im/canary.html\" target=\"_blank\" rel=\"external\">https://wiki.tox.im/canary.asc</a></p>\n","source":"_posts/warrant-canary-changes.md","raw":"title: Warrant Canary Changes\nid: 346\ncategories:\n  - Tox Foundation\ndate: 2014-08-13 14:31:24\ntags:\n---\n\nWhile moving the wiki frontend a week ago we managed to forget to move it after changing the IP. This resulted in it being down for around a week.\n\nWe apologize for making this mistake, and have not been contacted by {3 letter agency}.\n\nIn addition to this, the canary is now located at [https://wiki.tox.im/canary.html](https://wiki.tox.im/canary.html)\n\nIt is also pgp signed with the build system key at [https://wiki.tox.im/canary.asc](https://wiki.tox.im/canary.html)","slug":"warrant-canary-changes","updated":1422148791000,"excerpt":"","_id":"ln6dmfe83nffr51c","comments":true,"layout":"post","photos":[],"link":""},{"title":"Warrant Canary Updated & Changes","id":397,"categories":["i0yjl3tz23qj3npq"],"date":1410120598000,"tags":[],"content":"<p>To show a more serious commitment to the warrant canary, we will now be updating it every two weeks. The canary itself will now contain news headlines as well to mitigate automatic signing and updating.</p>\n<p>You can visit the canary at <a href=\"https://wiki.tox.im/canary.html\" target=\"_blank\" rel=\"external\">https://wiki.tox.im/canary.html</a></p>\n","source":"_posts/warrant-canary-updated-changes.md","raw":"title: \"Warrant Canary Updated & Changes\"\nid: 397\ncategories:\n  - Tox Foundation\ndate: 2014-09-07 16:09:58\ntags:\n---\n\nTo show a more serious commitment to the warrant canary, we will now be updating it every two weeks. The canary itself will now contain news headlines as well to mitigate automatic signing and updating.\n\nYou can visit the canary at [https://wiki.tox.im/canary.html](https://wiki.tox.im/canary.html)\n","slug":"warrant-canary-updated-changes","updated":1422148791000,"excerpt":"","_id":"ulim1sdfdxhwdyjq","comments":true,"layout":"post","photos":[],"link":""},{"title":"We're Not Dead; Just Working on TCP","id":261,"categories":["nlwrm5tlcr1n8dpi"],"date":1399241358000,"tags":[],"content":"<p>Just for those who may be worried that there haven’t been any commits to the master branch in a few days, irungentoo and others are all making commits to the TCP branch of the GitHub repository. You can view our progress <a href=\"https://github.com/irungentoo/ProjectTox-Core/tree/TCP\" target=\"_blank\" rel=\"external\">here.</a></p>\n","source":"_posts/were-not-dead-just-working-on-tcp.md","raw":"title: \"We're Not Dead; Just Working on TCP\"\nid: 261\ncategories:\n  - Tox Core\ndate: 2014-05-04 18:09:18\ntags:\n---\n\nJust for those who may be worried that there haven't been any commits to the master branch in a few days, irungentoo and others are all making commits to the TCP branch of the GitHub repository. You can view our progress [here.](https://github.com/irungentoo/ProjectTox-Core/tree/TCP)","slug":"were-not-dead-just-working-on-tcp","updated":1420586899000,"excerpt":"","_id":"nvyau2liy545vx3n","comments":true,"layout":"post","photos":[],"link":""},{"title":"TCP Relay Work Begun in Tox Core","id":77,"categories":["nlwrm5tlcr1n8dpi"],"date":1394725611000,"tags":[],"content":"<p>irungentoo, our glorious leader, has begun writing the code for the TCP relay servers that will help those who are behind strict NATs and/or poor UDP handling, like those on mobile networks. You can view the commit <a href=\"https://github.com/irungentoo/ProjectTox-Core/commit/2bb5e2c08488d4f43c964fcb92629dca2d294e7a\" target=\"_blank\" rel=\"external\">here</a>, but as the commit name suggests, it’s a work in progress.</p>\n<p>To those who have unable to connect to other users, this commit is the beginning of your saving grace. With TCP relay servers, you’ll be able to connect to the Tox DHT network without having to mess with port forwarding, or anything else. Stay tuned!</p>\n","source":"_posts/tcp-relay-work-begun.md","raw":"title: TCP Relay Work Begun in Tox Core\nid: 77\ncategories:\n  - Tox Core\ndate: 2014-03-13 11:46:51\ntags:\n---\n\nirungentoo, our glorious leader, has begun writing the code for the TCP relay servers that will help those who are behind strict NATs and/or poor UDP handling, like those on mobile networks. You can view the commit [here](https://github.com/irungentoo/ProjectTox-Core/commit/2bb5e2c08488d4f43c964fcb92629dca2d294e7a), but as the commit name suggests, it's a work in progress.\n\nTo those who have unable to connect to other users, this commit is the beginning of your saving grace. With TCP relay servers, you'll be able to connect to the Tox DHT network without having to mess with port forwarding, or anything else. Stay tuned!","slug":"tcp-relay-work-begun","updated":1420586899000,"excerpt":"","_id":"hd0jl08eqsk7mil5","comments":true,"layout":"post","photos":[],"link":""},{"title":"Toxic and Threads","id":82,"categories":["ysh4ufalq2ulbpz8"],"date":1394735916000,"tags":[],"content":"<p>Everybody’s favorite CLI client now utilizes threads for both Audio and the separation of Curses and Tox. This means that file transfers will be quicker, CPU usages should go down (after some optimizations), and everything should run smoother.</p>\n<p>Before, Curses and Tox were refreshed on every cycle, which was a bit too much for curses. Drawing to the screen takes quite a bit of time, and doesn’t need to happen as often as possible.</p>\n","source":"_posts/toxic-and-threads.md","raw":"title: Toxic and Threads\nid: 82\ncategories:\n  - Toxic\ndate: 2014-03-13 14:38:36\ntags:\n---\n\nEverybody's favorite CLI client now utilizes threads for both Audio and the separation of Curses and Tox. This means that file transfers will be quicker, CPU usages should go down (after some optimizations), and everything should run smoother.\n\nBefore, Curses and Tox were refreshed on every cycle, which was a bit too much for curses. Drawing to the screen takes quite a bit of time, and doesn't need to happen as often as possible.","slug":"toxic-and-threads","updated":1420586788000,"excerpt":"","_id":"s81rdqqwpxj4foc6","comments":true,"layout":"post","photos":[],"link":""},{"title":"No Antox GPlay Release for March 13th","id":84,"categories":["q5mc6700pzozi6gl"],"date":1394799180000,"tags":[],"content":"<p>I apologize for those who await for the daily build of Antox in the Alpha Testing Group, but timing constraints left me away from the computer the entire day. There will be a release pushed to GPlay later today, and will include all the changes made yesterday as well.</p>\n","source":"_posts/no-antox-gplay-release-for-march-13th.md","raw":"title: No Antox GPlay Release for March 13th\nid: 84\ncategories:\n  - Antox\ndate: 2014-03-14 08:13:00\ntags:\n---\n\nI apologize for those who await for the daily build of Antox in the Alpha Testing Group, but timing constraints left me away from the computer the entire day. There will be a release pushed to GPlay later today, and will include all the changes made yesterday as well.","slug":"no-antox-gplay-release-for-march-13th","updated":1420586899000,"excerpt":"","_id":"wm1d8ekx8b3zpzud","comments":true,"layout":"post","photos":[],"link":""},{"title":"Hello World","id":7,"author":null,"categories":["nlwrm5tlcr1n8dpi"],"date":1394493690000,"tags":[],"content":"<p>After about 2 dead devblogs, let’s keep this one running. Something to note about this devblog is that we will be also posting about the other clients as well, whereas previously we just mentioned the Tox Core. Hopefully that will drum up a bit more activity here so there’s actually something to be interested in.</p>\n","source":"_posts/hello-world-2.md","raw":"title: Hello World\nid: 7\nauthor: \ncategories:\n  - Tox Core\ndate: 2014-03-10 19:21:30\ntags:\n---\n\nAfter about 2 dead devblogs, let's keep this one running. Something to note about this devblog is that we will be also posting about the other clients as well, whereas previously we just mentioned the Tox Core. Hopefully that will drum up a bit more activity here so there's actually something to be interested in.\n","slug":"hello-world-2","updated":1420586900000,"excerpt":"","_id":"l1osrt9lyciveqc4","comments":true,"layout":"post","photos":[],"link":""},{"title":"Update on the state of Tox","date":1424285351000,"author":"Dubslow, co. Sean","tags":[],"content":"<p>Hello everyone. We realize it’s been a while since the last post, but a lot has happened and Tox continues to progress, so there’s a lot to talk about.<br><a id=\"more\"></a></p>\n<h2 id=\"Tox_core\">Tox core</h2>\n<h4 id=\"Core\">Core</h4>\n<p><a href=\"https://github.com/irungentoo/toxcore\" target=\"_blank\" rel=\"external\">toxcore</a> has been largely in maintenance mode, with memory leaks, logic errors and other bugs being fixed every day. Recently work has begun on implementing a <a href=\"https://github.com/irungentoo/toxcore/tree/new_api\" target=\"_blank\" rel=\"external\">new, cleaner API</a> written by the <a href=\"https://github.com/sonOfRa/tox4j\" target=\"_blank\" rel=\"external\">Tox4j</a> developers.</p>\n<h4 id=\"Bootstrap_daemon\">Bootstrap daemon</h4>\n<p>As a small treat, the <a href=\"https://github.com/irungentoo/toxcore/tree/master/other/bootstrap_daemon\" target=\"_blank\" rel=\"external\">boostrap daemon</a> now has systemd support, thanks to contributor <a href=\"https://github.com/ray65536\" target=\"_blank\" rel=\"external\">ray65536</a>. It is also available as the package <code>tox-bootstrapd</code> from our Linux repositories.</p>\n<h4 id=\"New_groupchats\">New groupchats</h4>\n<p>Additionally, work is progressing on the complete <a href=\"https://github.com/JFreegman/toxcore\" target=\"_blank\" rel=\"external\">groupchat re-design</a> and overhaul, started by <a href=\"https://github.com/alnf\" target=\"_blank\" rel=\"external\">alnf</a> and currently being led primarily by <a href=\"https://github.com/JFreegman\" target=\"_blank\" rel=\"external\">JFreegman</a>. Features include moderation abilities and group chat persistence (!). These group chats are a long way from being ready to merge into master; however, there is now a properly <a href=\"https://jenkins.libtoxcore.so/job/toxic_linux_beta/lastSuccessfulBuild/artifact/toxic\" target=\"_blank\" rel=\"external\">modified build of Toxic</a> for Linux available with the changes.</p>\n<p>You can also download the modified Toxic by installing <code>toxic-beta</code> from our Apt and Yum repos and running <code>toxic-beta</code>. Keep in mind that this copy is totally isolated from your existing Toxic install to prevent issues.</p>\n<p>Please be aware that this is experimental testing code that will not work with the regular Tox network until we’ve finished it and merged it with master. You can follow development on the #tox-groupchats IRC channel on Freenode.</p>\n<h1 id=\"Audio_filtering_and_echo_cancellation\">Audio filtering and echo cancellation</h1>\n<p>It’s been around for a few months now, but <a href=\"https://github.com/notsecure/uTox\" target=\"_blank\" rel=\"external\">uTox</a> has had audio filtering, provided by <a href=\"https://github.com/irungentoo/filter_audio\" target=\"_blank\" rel=\"external\">code</a> from <a href=\"https://code.google.com/p/webrtc/\" target=\"_blank\" rel=\"external\">WebRTC</a>. <a href=\"https://github.com/tux3/qTox\" target=\"_blank\" rel=\"external\">qTox</a> now supports it as well.</p>\n<h4 id=\"Experimental_echo_cancellation\">Experimental echo cancellation</h4>\n<p>Recently though, <a href=\"https://github.com/irungentoo\" target=\"_blank\" rel=\"external\">irungentoo</a> (project founder and lead developer, in case you needed reminding :) ) has created <a href=\"https://github.com/irungentoo/openal-soft-tox\" target=\"_blank\" rel=\"external\">some patches for OpenAL</a> that allow for cancelling speaker echoes from your microphone’s sound input, a necessary feature for using a microphone without headphones or earbuds. uTox quickly put that to use, and qTox gained the same ability yesterday. Note that, if you compile these clients yourself, you will need to link against the patched version of OpenAL to enjoy echo cancellation. The official builds of both qTox and uTox are both built that way, and if you need to you can try using the <a href=\"https://jenkins.libtoxcore.so/search/?q=openal\" target=\"_blank\" rel=\"external\">OpenAL builds</a> on <a href=\"https://jenkins.libtoxcore.so/\" target=\"_blank\" rel=\"external\">Jenkins</a> used for qTox and uTox.</p>\n<p>Currently echo cancellation is considered experimental, and Tox is seeking testing and feedback from users (on IRC or <a href=\"https://reddit.com/r/projecttox\" target=\"_blank\" rel=\"external\">reddit</a>, for example) about how effective it is. If testing demonstrates that it is working properly, the patches will be submitted to the <a href=\"https://github.com/kcat/openal-soft\" target=\"_blank\" rel=\"external\">OpenAL upstream</a> for merging.</p>\n<h2 id=\"qTox_progress\">qTox progress</h2>\n<p>Besides continual minor improvements, qTox has gained the following major features.</p>\n<h4 id=\"New_chatform\">New chatform</h4>\n<p>Over the last several months, <a href=\"https://github.com/krepa098\" target=\"_blank\" rel=\"external\">krepa098</a> had been working on a complete rewrite of qTox’s chat form, and we’re happy to say that it was finally merged into master in the last week (over 4000 new lines of code!). Users should see significant reductions in memory and CPU usage (though some problems still exist), as well as being much prettier and easier to use. Copy and pasting in particular had been a big issue that should be pretty much solved, and there are some nice little animations (such as the typing notification).</p>\n<h4 id=\"Local_file_encryption\">Local file encryption</h4>\n<p>Additionally, a fair bit of work (no where near as much as the new chat form required) was put into fixing the local file encryption and its interface in qTox, and that work was merged roughly two weeks ago. Users can now password protect their profile to safely transfer their profile to other computers, or even public computers. (Be sure to delete your profile when you leave a public computer!)</p>\n<h4 id=\"Compact_contact_list\">Compact contact list</h4>\n<p>Finally, a lot of people probably love (or perhaps are unaware of) the new <a href=\"http://i.imgur.com/tmX8z9s.png\" target=\"_blank\" rel=\"external\">compact contact list</a> option that qTox has, thanks to <a href=\"https://github.com/lumirayz\" target=\"_blank\" rel=\"external\">lumirayz</a>.</p>\n<h4 id=\"OS_X\">OS X</h4>\n<p>A note for Mac OS X users: We pushed a number of major changes that totally reworked how the app works. Because of this, many improvements like Qt 5.3 -&gt; 5.4 mean updating it normally will break. Please be aware that this update includes a new icon that you may not be used to, and has many visual improvements.</p>\n<p>In order to update cleanly you’ll need to re-download qTox and drag the app in to your applications folder like usual. Your profiles won’t be harmed or modified in any way.</p>\n<h2 id=\"uTox_progress\">uTox progress</h2>\n<p>uTox has been slowly receiving incremental improvements, primarily in the interface. For more details, you can check out the <a href=\"https://github.com/notsecure/uTox/commits/master\" target=\"_blank\" rel=\"external\">commit log</a> or <a href=\"https://twitter.com/irungentoo\" target=\"_blank\" rel=\"external\">irungentoo’s Twitter</a>.</p>\n<h2 id=\"Google_Summer_of_Code\">Google Summer of Code</h2>\n<p>Like last year, Tox is applying to be a participating organization in the Google Summer of Code. Check back soon for updates.</p>\n<h2 id=\"Android\">Android</h2>\n<p>As mentioned above, work continues on Tox4j, the replacement Java wrapper for core, and when that’s complete a new Android client will be developed from scratch on top of it. Another vague possibility is that qTox can be ported to Android, since it’s written in Qt 5; <a href=\"https://github.com/tux3\" target=\"_blank\" rel=\"external\">tux3</a> (qTox’s primary author) has recently started the very basic framework of such a port, but it is currently significantly less useful than the old Antox.</p>\n<p>A fork of the old Antox is currently being maintained against the Tox4j work in progress. You can download it by joining the Google Play beta or adding our F-Droid repo. Details on this are <a href=\"https://wiki.tox.im/Binaries\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<h2 id=\"Website_improvements\">Website improvements</h2>\n<p>We’ve been continuously working to improve and refine the experience for new users by making things simpler and more straightforward. With this, we’re currently working on a new site for tox.im and a new downloads page until the site is complete.</p>\n<p>You can check out progress on the new site <a href=\"https://beta.tox.im\" target=\"_blank\" rel=\"external\">here</a> and check out the progress on the new temporary downloads page <a href=\"https://download.tox.im\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<h3 id=\"ToxMe_improvements\">ToxMe improvements</h3>\n<p>By popular demand we’ve added a reverse lookup API to ToxMe. This allows people to look up DNS Discovery names using just a Tox ID as long as the ID they want to lookup isn’t marked private. It is documented <a href=\"https://github.com/Tox/toxme.se/blob/master/api.md\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<h2 id=\"Repository_improvements\">Repository improvements</h2>\n<p>If you use our RPM repo you may have suffered some issues downloading Tox due to an old revoked PGP key getting stuck in the signing process. We’ve gone ahead and fixed all the issues associated with that and ensured that it works perfectly.</p>\n<p>Supporting our new downloads page, we’ve gone ahead and made the qTox packages automatically configure and setup the repo on your system by just installing the deb. This means for normal users all you’ll have to do is click download and Ubuntu software center will pop up to automatically set everything up and ensure you always have the latest and greatest copy of qTox. If you had the repo installed before it may cause conflicts in apt. Please remove it by running <code>rm /etc/apt/sources.list.d/toxrepo.list</code> and it’ll take care of itself automatically.</p>\n","source":"_posts/Update-on-the-state-of-Tox.md","raw":"title: Update on the state of Tox\ndate: 2015-02-18 13:49:11\nauthor: Dubslow, co. Sean\ntags:\n---\n\nHello everyone. We realize it's been a while since the last post, but a lot has happened and Tox continues to progress, so there's a lot to talk about.\n<!-- more -->\n\n##Tox core\n\n####Core\n[toxcore](https://github.com/irungentoo/toxcore) has been largely in maintenance mode, with memory leaks, logic errors and other bugs being fixed every day. Recently work has begun on implementing a [new, cleaner API](https://github.com/irungentoo/toxcore/tree/new_api) written by the [Tox4j](https://github.com/sonOfRa/tox4j) developers.\n\n####Bootstrap daemon\nAs a small treat, the [boostrap daemon](https://github.com/irungentoo/toxcore/tree/master/other/bootstrap_daemon) now has systemd support, thanks to contributor [ray65536](https://github.com/ray65536). It is also available as the package `tox-bootstrapd` from our Linux repositories.\n\n####New groupchats\nAdditionally, work is progressing on the complete [groupchat re-design](https://github.com/JFreegman/toxcore) and overhaul, started by [alnf](https://github.com/alnf) and currently being led primarily by [JFreegman](https://github.com/JFreegman). Features include moderation abilities and group chat persistence (!). These group chats are a long way from being ready to merge into master; however, there is now a properly [modified build of Toxic](https://jenkins.libtoxcore.so/job/toxic_linux_beta/lastSuccessfulBuild/artifact/toxic) for Linux available with the changes.\n\nYou can also download the modified Toxic by installing `toxic-beta` from our Apt and Yum repos and running ``toxic-beta``. Keep in mind that this copy is totally isolated from your existing Toxic install to prevent issues.\n\nPlease be aware that this is experimental testing code that will not work with the regular Tox network until we've finished it and merged it with master. You can follow development on the #tox-groupchats IRC channel on Freenode.\n\n#Audio filtering and echo cancellation\n\nIt's been around for a few months now, but [uTox](https://github.com/notsecure/uTox) has had audio filtering, provided by [code](https://github.com/irungentoo/filter_audio) from [WebRTC](https://code.google.com/p/webrtc/). [qTox](https://github.com/tux3/qTox) now supports it as well.\n\n####Experimental echo cancellation\nRecently though, [irungentoo](https://github.com/irungentoo) (project founder and lead developer, in case you needed reminding :) ) has created [some patches for OpenAL](https://github.com/irungentoo/openal-soft-tox) that allow for cancelling speaker echoes from your microphone's sound input, a necessary feature for using a microphone without headphones or earbuds. uTox quickly put that to use, and qTox gained the same ability yesterday. Note that, if you compile these clients yourself, you will need to link against the patched version of OpenAL to enjoy echo cancellation. The official builds of both qTox and uTox are both built that way, and if you need to you can try using the [OpenAL builds](https://jenkins.libtoxcore.so/search/?q=openal) on [Jenkins](https://jenkins.libtoxcore.so/) used for qTox and uTox.\n\nCurrently echo cancellation is considered experimental, and Tox is seeking testing and feedback from users (on IRC or [reddit](https://reddit.com/r/projecttox), for example) about how effective it is. If testing demonstrates that it is working properly, the patches will be submitted to the [OpenAL upstream](https://github.com/kcat/openal-soft) for merging.\n\n##qTox progress\nBesides continual minor improvements, qTox has gained the following major features.\n\n####New chatform\nOver the last several months, [krepa098](https://github.com/krepa098) had been working on a complete rewrite of qTox's chat form, and we're happy to say that it was finally merged into master in the last week (over 4000 new lines of code!). Users should see significant reductions in memory and CPU usage (though some problems still exist), as well as being much prettier and easier to use. Copy and pasting in particular had been a big issue that should be pretty much solved, and there are some nice little animations (such as the typing notification).\n\n####Local file encryption\nAdditionally, a fair bit of work (no where near as much as the new chat form required) was put into fixing the local file encryption and its interface in qTox, and that work was merged roughly two weeks ago. Users can now password protect their profile to safely transfer their profile to other computers, or even public computers. (Be sure to delete your profile when you leave a public computer!)\n\n####Compact contact list\nFinally, a lot of people probably love (or perhaps are unaware of) the new [compact contact list](http://i.imgur.com/tmX8z9s.png) option that qTox has, thanks to [lumirayz](https://github.com/lumirayz).\n\n####OS X\nA note for Mac OS X users: We pushed a number of major changes that totally reworked how the app works. Because of this, many improvements like Qt 5.3 -> 5.4 mean updating it normally will break. Please be aware that this update includes a new icon that you may not be used to, and has many visual improvements.\n\nIn order to update cleanly you'll need to re-download qTox and drag the app in to your applications folder like usual. Your profiles won't be harmed or modified in any way.\n\n##uTox progress\nuTox has been slowly receiving incremental improvements, primarily in the interface. For more details, you can check out the [commit log](https://github.com/notsecure/uTox/commits/master) or [irungentoo's Twitter](https://twitter.com/irungentoo).\n\n##Google Summer of Code\n\nLike last year, Tox is applying to be a participating organization in the Google Summer of Code. Check back soon for updates.\n\n##Android\n\nAs mentioned above, work continues on Tox4j, the replacement Java wrapper for core, and when that's complete a new Android client will be developed from scratch on top of it. Another vague possibility is that qTox can be ported to Android, since it's written in Qt 5; [tux3](https://github.com/tux3) (qTox's primary author) has recently started the very basic framework of such a port, but it is currently significantly less useful than the old Antox.\n\nA fork of the old Antox is currently being maintained against the Tox4j work in progress. You can download it by joining the Google Play beta or adding our F-Droid repo. Details on this are [here](https://wiki.tox.im/Binaries).\n\n\n##Website improvements\n\nWe've been continuously working to improve and refine the experience for new users by making things simpler and more straightforward. With this, we're currently working on a new site for tox.im and a new downloads page until the site is complete.\n\nYou can check out progress on the new site [here](https://beta.tox.im) and check out the progress on the new temporary downloads page [here](https://download.tox.im).\n\n###ToxMe improvements\n\nBy popular demand we've added a reverse lookup API to ToxMe. This allows people to look up DNS Discovery names using just a Tox ID as long as the ID they want to lookup isn't marked private. It is documented [here](https://github.com/Tox/toxme.se/blob/master/api.md).\n\n##Repository improvements\n\nIf you use our RPM repo you may have suffered some issues downloading Tox due to an old revoked PGP key getting stuck in the signing process. We've gone ahead and fixed all the issues associated with that and ensured that it works perfectly.\n\nSupporting our new downloads page, we've gone ahead and made the qTox packages automatically configure and setup the repo on your system by just installing the deb. This means for normal users all you'll have to do is click download and Ubuntu software center will pop up to automatically set everything up and ensure you always have the latest and greatest copy of qTox. If you had the repo installed before it may cause conflicts in apt. Please remove it by running ``rm /etc/apt/sources.list.d/toxrepo.list`` and it'll take care of itself automatically.\n\n\n\n\n","slug":"Update-on-the-state-of-Tox","updated":1424725059000,"excerpt":"<p>Hello everyone. We realize it’s been a while since the last post, but a lot has happened and Tox continues to progress, so there’s a lot to talk about.<br>","_id":"mwgy7ale6a2m480h","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"GSoC, languages, and more","date":1426715351000,"author":"Sean","tags":[],"content":"<p>Howdy folks, I feel like it’s a good time to get you all up to speed with Tox development.<br><a id=\"more\"></a></p>\n<h2 id=\"GSoC\">GSoC</h2>\n<p>For the 2nd year in a row, <a href=\"https://www.google-melange.com/gsoc/org2/google/gsoc2015/tox\" target=\"_blank\" rel=\"external\">Tox got accepted in to GSoC</a>. This is great news and will both help new students learn about and start contributing to open source, and help Tox developers improve our projects and advance our goals of making security mainstream.</p>\n<p>Want to contribute to Tox in GSoC but you’re not a C/C++ developer? Tox has plenty of projects like ToxMe improvements in Python, Tox for Windows in C#, iOS and Android clients in Java/Objective C that you might enjoy. You can checkout our full list of ideas <a href=\"http://wiki.tox.im/GSoC/2015/Ideas\" target=\"_blank\" rel=\"external\">here</a>.</p>\n<p>Ready to jump in and contribute to Tox? The deadline to write and submit a proposal for GSoC ends in a week but we encourage you to run it by us in <a href=\"https://webchat.freenode.net/?channels=%23tox-gsoc-students\" target=\"_blank\" rel=\"external\">#tox-gsoc-students</a> for review so we can help you improve it.</p>\n<h2 id=\"Translations\">Translations</h2>\n<p>Want to contribute to Tox and speak another language? Localization and being able to ensure Tox is accessible to as many people as possible is something we pride in, but not something we can do alone. Localization in Tox and our sites depends on our community and bilingual Toxers like you taking the time to submit and review translations, and is something we greatly appreciate.</p>\n<p>If you want to spend a few minutes becoming a translator or reviewer for our new site signup <a href=\"https://www.transifex.com/projects/p/tox-website-next\" target=\"_blank\" rel=\"external\">here</a>, if you want we can also let you know of other things needing translations too.</p>\n<h2 id=\"Toxcore\">Toxcore</h2>\n<p>The new API for toxcore mentioned in our last post is almost complete and almost ready to be merged, if you work on a client/wrapper/tool over Tox we encourage you to start porting your applications now. The new API is <a href=\"https://github.com/irungentoo/toxcore/blob/new_api/toxcore/tox.h\" target=\"_blank\" rel=\"external\">here</a></p>\n<h2 id=\"Git_mirror\">Git mirror</h2>\n<p>We now maintain a Git mirror of popular Tox repositories for archive reasons, located at <a href=\"https://git.tox.im\" target=\"_blank\" rel=\"external\">git.tox.im</a>. The mirror is powered by our fork of <a href=\"http://gogs.io\" target=\"_blank\" rel=\"external\">Gogs</a> and can be used as a personal code host if you’d like. Being a personal/non Github host isn’t our main goal, but we don’t prohibit it and a couple users/contributors have started using it as such.</p>\n","source":"_posts/gsoc-translations-more.md","raw":"title: GSoC, languages, and more\ndate: 2015-03-18 17:49:11\nauthor: Sean\ntags:\n---\n\nHowdy folks, I feel like it's a good time to get you all up to speed with Tox development.\n<!-- more -->\n\n##GSoC\n\nFor the 2nd year in a row, [Tox got accepted in to GSoC](https://www.google-melange.com/gsoc/org2/google/gsoc2015/tox). This is great news and will both help new students learn about and start contributing to open source, and help Tox developers improve our projects and advance our goals of making security mainstream.\n\nWant to contribute to Tox in GSoC but you're not a C/C++ developer? Tox has plenty of projects like ToxMe improvements in Python, Tox for Windows in C#, iOS and Android clients in Java/Objective C that you might enjoy. You can checkout our full list of ideas [here](http://wiki.tox.im/GSoC/2015/Ideas).\n\nReady to jump in and contribute to Tox? The deadline to write and submit a proposal for GSoC ends in a week but we encourage you to run it by us in [#tox-gsoc-students](https://webchat.freenode.net/?channels=%23tox-gsoc-students) for review so we can help you improve it.\n\n##Translations\n\nWant to contribute to Tox and speak another language? Localization and being able to ensure Tox is accessible to as many people as possible is something we pride in, but not something we can do alone. Localization in Tox and our sites depends on our community and bilingual Toxers like you taking the time to submit and review translations, and is something we greatly appreciate.\n\nIf you want to spend a few minutes becoming a translator or reviewer for our new site signup [here](https://www.transifex.com/projects/p/tox-website-next), if you want we can also let you know of other things needing translations too.\n\n##Toxcore\n\nThe new API for toxcore mentioned in our last post is almost complete and almost ready to be merged, if you work on a client/wrapper/tool over Tox we encourage you to start porting your applications now. The new API is [here](https://github.com/irungentoo/toxcore/blob/new_api/toxcore/tox.h)\n\n##Git mirror\n\nWe now maintain a Git mirror of popular Tox repositories for archive reasons, located at [git.tox.im](https://git.tox.im). The mirror is powered by our fork of [Gogs](http://gogs.io) and can be used as a personal code host if you'd like. Being a personal/non Github host isn't our main goal, but we don't prohibit it and a couple users/contributors have started using it as such.\n","slug":"gsoc-translations-more","updated":1426728659000,"excerpt":"<p>Howdy folks, I feel like it’s a good time to get you all up to speed with Tox development.<br>","_id":"jd62ryto5ejehyxb","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Introducing Toxcoin","date":1427860801000,"author":"irungentoo, Sean","tags":[],"content":"<p>A new cryptocurrency to solve the issues tox has.</p>\n<a id=\"more\"></a>\n\n<p>The main issues Tox face are that since we do not have central servers things<br>like making multiple devices have the same “account” and offline messaging is<br>very difficult. For this reason we have searched long and hard for a real<br>decentralized solution to these problems. We are proud to announce today that<br>we have found such a solution. This solution also has far reaching applications<br>and could also for example enable the creation of more efficient crypto<br>currencies and solve world hunger.</p>\n<p>So how does it work? First we define proof of trust as the amount of trust that<br>can be proven a node has in a distributed peer to peer network. The trust a<br>node has in the system is defined as the inverse of the non trust a node has in<br>the system. Trusted nodes are assumed to always behave correctly meaning<br>untrusted nodes will not behave correctly. By making each node look for nodes<br>that do not behave correctly non trusted nodes can therefore be identified and<br>disposed of by the network. This leaves a network that only contains trusted<br>nodes. Once a network is certain to contain only trusted nodes any system which<br>requires such a system can easily be implemented on top meaning it is possible<br>to implement every centralized system in an efficient decentralized manner.</p>\n<p>Creating a decentralized internet will therefore be possible. The possibilities<br>are endless. With this revolutionary new technology anybody will be capable of<br>having their own website.</p>\n<p>Why name this technology toxcoin? The best way to get this technology up and<br>running fast and to fund development is to make it its own crypto currency.<br>Toxcoin will also be used to fund development of Tox. Tox developers will be<br>payed in Toxcoins which will increase in value as more and more people used<br>Tox. If we assume a total market cap of 1 million toxcoin and assume each tox<br>user is worth 10$. When Tox reaches 1 billion users each toxcoin will be worth<br>10000$. Toxcoins are clearly an investment that will only grow in value.<br>Investing in this con will truly increase your money.</p>\n<p>Is this an altcoin? No, toxcoin will be implemented using the bitcoin<br>blockchain as a base.</p>\n<p>There is already some proof of concept code in the github repo but it is still<br>in very early stages.</p>\n<p>See the whitepaper: <a href=\"https://coin.tox.im/whitepaper.pdf\" target=\"_blank\" rel=\"external\">coin.tox.im/whitepaper.pdf</a></p>\n<p>Github repo: <a href=\"https://github.com/irungentoo/toxcoin\" target=\"_blank\" rel=\"external\">github.com/irungentoo/toxcoin</a></p>\n<p>Join the revolution: <a href=\"https://webchat.freenode.net/?channels=%23toxcoin\" target=\"_blank\" rel=\"external\">#toxcoin</a> on Freenode.</p>\n","source":"_posts/introducing-toxcoin.md","raw":"title: Introducing Toxcoin\ndate: 2015-04-1 00:00:01\nauthor: irungentoo, Sean\ntags:\n---\n\nA new cryptocurrency to solve the issues tox has.\n\n<!-- more -->\n\nThe main issues Tox face are that since we do not have central servers things \nlike making multiple devices have the same \"account\" and offline messaging is \nvery difficult. For this reason we have searched long and hard for a real \ndecentralized solution to these problems. We are proud to announce today that \nwe have found such a solution. This solution also has far reaching applications \nand could also for example enable the creation of more efficient crypto \ncurrencies and solve world hunger.\n\nSo how does it work? First we define proof of trust as the amount of trust that \ncan be proven a node has in a distributed peer to peer network. The trust a \nnode has in the system is defined as the inverse of the non trust a node has in \nthe system. Trusted nodes are assumed to always behave correctly meaning \nuntrusted nodes will not behave correctly. By making each node look for nodes \nthat do not behave correctly non trusted nodes can therefore be identified and \ndisposed of by the network. This leaves a network that only contains trusted \nnodes. Once a network is certain to contain only trusted nodes any system which \nrequires such a system can easily be implemented on top meaning it is possible \nto implement every centralized system in an efficient decentralized manner.\n\nCreating a decentralized internet will therefore be possible. The possibilities \nare endless. With this revolutionary new technology anybody will be capable of \nhaving their own website.\n\nWhy name this technology toxcoin? The best way to get this technology up and \nrunning fast and to fund development is to make it its own crypto currency.\nToxcoin will also be used to fund development of Tox. Tox developers will be \npayed in Toxcoins which will increase in value as more and more people used \nTox. If we assume a total market cap of 1 million toxcoin and assume each tox \nuser is worth 10$. When Tox reaches 1 billion users each toxcoin will be worth \n10000$. Toxcoins are clearly an investment that will only grow in value. \nInvesting in this con will truly increase your money.\n\nIs this an altcoin? No, toxcoin will be implemented using the bitcoin \nblockchain as a base.\n\nThere is already some proof of concept code in the github repo but it is still\nin very early stages.\n\nSee the whitepaper: [coin.tox.im/whitepaper.pdf](https://coin.tox.im/whitepaper.pdf)\n\nGithub repo: [github.com/irungentoo/toxcoin](https://github.com/irungentoo/toxcoin)\n\nJoin the revolution: [#toxcoin](https://webchat.freenode.net/?channels=%23toxcoin) on Freenode.\n","slug":"introducing-toxcoin","updated":1427824269000,"excerpt":"<p>A new cryptocurrency to solve the issues tox has.</p>\n","_id":"559bfpqo1446os0n","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox, bringing your friends closer","date":1427860802000,"author":"Sean","tags":[],"content":"<p>While PC usage is on the decline, mobile usage has skyrocketed</p>\n<a id=\"more\"></a>\n\n<p>and will continue to skyrocket in the future. We’ve come to realize<br>that because of this we need to start working to support mobile<br>and mobile device users as best we can.</p>\n<p>With <a href=\"https://blog.tox.im/2015/04/01/introducing-toxcoin/\" target=\"_blank\" rel=\"external\">ToxCOIN</a> support having been recently<br>announced we realized progress was being made in the right direction,<br>but it wasn’t enough. We realized that some people might still<br>want to use traditional Tox IDs and use mobile devices at the<br>same time so we decided to take a step back from what we’re used<br>to and look at what much of our mobile using audience is already doing.</p>\n<p>We saw typical mobile users send short video clips, talk in groups,<br>message automatically without setup, but nothing would work for Tox.<br>That was, until we noticed someone send a cute little heart icon to<br>her friend to express a complex feeling.</p>\n<p>We realized that if one little character could express a whole emotion,<br>a couple of them could express a Tox ID, and so emoji support was born.</p>\n<p>Starting today, most of our clients now support fun and friendly emoji<br>in place of existing scary and frightening Tox IDs, be it uTox or Toxy<br>with more clients in the works.</p>\n<p>Ready to try it out? lean back, open uTox Android, and punch in<br><code>🌔💡⭩⬃⚿🚧⟛⋏⩮🚍🛱💖🖭⚏⋻😇∁⤔ℐ⋜↷⚑⍕👫≧ℇ😇</code> to join our always<br>popular groupchat in style.</p>\n<p>Want to make your own emoji ID? Checkout the tools <a href=\"https://github.com/irungentoo/base_emoji\" target=\"_blank\" rel=\"external\">here</a>.</p>\n","source":"_posts/tox-friends-2015.md","raw":"title: Tox, bringing your friends closer\ndate: 2015-04-1 00:00:02\nauthor:  Sean\ntags:\n---\n\nWhile PC usage is on the decline, mobile usage has skyrocketed\n\n<!-- more -->\n\nand will continue to skyrocket in the future. We've come to realize\nthat because of this we need to start working to support mobile\nand mobile device users as best we can.\n\nWith [ToxCOIN](https://blog.tox.im/2015/04/01/introducing-toxcoin/) support having been recently\nannounced we realized progress was being made in the right direction,\nbut it wasn't enough. We realized that some people might still\nwant to use traditional Tox IDs and use mobile devices at the \nsame time so we decided to take a step back from what we're used\nto and look at what much of our mobile using audience is already doing.\n\nWe saw typical mobile users send short video clips, talk in groups,\nmessage automatically without setup, but nothing would work for Tox.\nThat was, until we noticed someone send a cute little heart icon to\nher friend to express a complex feeling.\n\nWe realized that if one little character could express a whole emotion,\na couple of them could express a Tox ID, and so emoji support was born.\n\nStarting today, most of our clients now support fun and friendly emoji\nin place of existing scary and frightening Tox IDs, be it uTox or Toxy\nwith more clients in the works.\n\n\nReady to try it out? lean back, open uTox Android, and punch in \n``🌔💡⭩⬃⚿🚧⟛⋏⩮🚍🛱💖🖭⚏⋻😇∁⤔ℐ⋜↷⚑⍕👫≧ℇ😇`` to join our always \npopular groupchat in style.\n\n\n\nWant to make your own emoji ID? Checkout the tools [here](https://github.com/irungentoo/base_emoji).\n","slug":"tox-friends-2015","updated":1427839160000,"excerpt":"<p>While PC usage is on the decline, mobile usage has skyrocketed</p>\n","_id":"lrfb4wh58z1pvmng","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox for Chrome OS preview","date":1427865023000,"author":"Sean","tags":[],"content":"<p>Tox development preview for Chrome OS</p>\n<a id=\"more\"></a>\n\n<p>With the advent of the Chromebook, the face of modern computing<br>changed in a number of drastic ways. Super low cost but fully<br>usable machines with browsers, chat programs, and full office<br>suites became available to even the lowest income students.</p>\n<p>These devices let users shift from low budget bottom of the<br>barrel laptops often times filled to the brim in spyware and<br>adware to light and responsive machines boasting great battery<br>life and access to services they already use, something that<br>can only be looked at as a win for consumers.</p>\n<p>With the announcement of even cheaper Chromebooks and sticks,<br>we realize the value in providing secure messaging with friends<br>and families to this ever expanding market more than ever.</p>\n<p>As such, we’d like to announce the Tox for Chrome OS technical<br>preview. You’ll be one of the very first testers to this so<br>tons of bugs and issues are to be expected. While these clients<br>work, we do not encourage you to use them as your daily drivers.<br>You may experience data loss or other bugs that could prevent<br>you from using it correctly in some cases because of how early<br>this preview is.</p>\n<h1 id=\"Getting_started\">Getting started</h1>\n<ul>\n<li>To test Antox for Chrome OS please click <a href=\"https://chrome.google.com/webstore/detail/antox/mblkomdgjiaclkhabhmhnkmkfbbclgdi\" target=\"_blank\" rel=\"external\">here</a></li>\n<li>To test uTox for Chrome OS please click <a href=\"https://chrome.google.com/webstore/detail/%CE%BCtox/cpbcplbgcffgmhagekhlifhpaihcgokf\" target=\"_blank\" rel=\"external\">here</a></li>\n</ul>\n<h1 id=\"Reporting_issues\">Reporting issues</h1>\n<ul>\n<li>To report Antox issues please visit the issue tracker <a href=\"https://github.com/subliun/Antox/issues\" target=\"_blank\" rel=\"external\">here</a></li>\n<li>To report uTox issues please visit the issue tracker <a href=\"https://github.com/notsecure/wintox/issues\" target=\"_blank\" rel=\"external\">here</a></li>\n</ul>\n","source":"_posts/tox-chromeos.md","raw":"title: Tox for Chrome OS preview\ndate: 2015-04-1 01:10:23\nauthor:  Sean\ntags:\n---\n\nTox development preview for Chrome OS\n\n<!-- more -->\n\nWith the advent of the Chromebook, the face of modern computing\nchanged in a number of drastic ways. Super low cost but fully \nusable machines with browsers, chat programs, and full office\nsuites became available to even the lowest income students.\n\nThese devices let users shift from low budget bottom of the\nbarrel laptops often times filled to the brim in spyware and\nadware to light and responsive machines boasting great battery\nlife and access to services they already use, something that\ncan only be looked at as a win for consumers.\n\nWith the announcement of even cheaper Chromebooks and sticks,\nwe realize the value in providing secure messaging with friends\nand families to this ever expanding market more than ever.\n\nAs such, we'd like to announce the Tox for Chrome OS technical\npreview. You'll be one of the very first testers to this so\ntons of bugs and issues are to be expected. While these clients\nwork, we do not encourage you to use them as your daily drivers.\nYou may experience data loss or other bugs that could prevent\nyou from using it correctly in some cases because of how early\nthis preview is.\n\n#Getting started\n\n* To test Antox for Chrome OS please click [here](https://chrome.google.com/webstore/detail/antox/mblkomdgjiaclkhabhmhnkmkfbbclgdi)\n* To test uTox for Chrome OS please click [here](https://chrome.google.com/webstore/detail/%CE%BCtox/cpbcplbgcffgmhagekhlifhpaihcgokf)\n\n#Reporting issues\n\n* To report Antox issues please visit the issue tracker [here](https://github.com/subliun/Antox/issues)\n* To report uTox issues please visit the issue tracker [here](https://github.com/notsecure/wintox/issues)\n","slug":"tox-chromeos","updated":1427879203000,"excerpt":"<p>Tox development preview for Chrome OS</p>\n","_id":"vihbcdk11fc3bm67","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Major Discovery by the Tox Foundation","date":1427886623000,"author":"irungentoo","tags":[],"content":"<p>The Tox Foundation has made an important discovery today that might change the world forever.</p>\n<a id=\"more\"></a>\n\n<p>Our research team at the Tox foundation has made an important discovery today. Data packets travel at the speed of light meaning finding a way to make them travel slightly faster is not that hard. The trick is to make the wire itself go fast in order to transmit the data inside at faster than light speeds. The following diagram should explain very well how it works.</p>\n<img src=\"/images/Tox_ftl.png\">\n\n<p>Faster than light information travel allows us to send information back and forward in time by tweaking the packet parameters.</p>\n<p>I managed to communicate with myself from the future and this is what I managed to understand. The connection was very flaky because of the dimensional noise created when someone interferes with his past. Here is the news from the future:</p>\n<p><a href=\"https://blog.tox.im/2015/04/01/introducing-toxcoin\" target=\"_blank\" rel=\"external\">Toxcoin</a> died a slow death after not a single developer was found that wanted to develop it.</p>\n<p>qTox is doing very well competing with other web browsers.</p>\n<p>uTox was rewritten in javascript and became a web client.</p>\n<p>Toxic was acquired by Microsoft and ported to Windows, it will soon be replacing Skype.</p>\n<p>Antox was slowly replaced by uTox for android.</p>\n<p>nTox is still alive.</p>\n<p>I also received this image but can’t make sense of it.</p>\n<img src=\"/images/Tox_ftl_message.jpg\">\n\n\n<p>The connection was then cut suddenly. I will try to find out why the connection cut and why I can’t seem to be able to contact the future anymore.</p>\n<p>Happy Future Toxing.</p>\n<p>In other news it has been reported to us that Tox works from a helicopter.</p>\n","source":"_posts/tox-ftl.md","raw":"title: Major Discovery by the Tox Foundation\ndate: 2015-04-1 07:10:23\nauthor:  irungentoo\ntags:\n---\n\nThe Tox Foundation has made an important discovery today that might change the world forever.\n\n<!-- more -->\n\nOur research team at the Tox foundation has made an important discovery today. Data packets travel at the speed of light meaning finding a way to make them travel slightly faster is not that hard. The trick is to make the wire itself go fast in order to transmit the data inside at faster than light speeds. The following diagram should explain very well how it works.\n\n{% limg Tox_ftl.png %}\n\nFaster than light information travel allows us to send information back and forward in time by tweaking the packet parameters.\n\nI managed to communicate with myself from the future and this is what I managed to understand. The connection was very flaky because of the dimensional noise created when someone interferes with his past. Here is the news from the future:\n\n[Toxcoin](https://blog.tox.im/2015/04/01/introducing-toxcoin) died a slow death after not a single developer was found that wanted to develop it.\n\nqTox is doing very well competing with other web browsers.\n\nuTox was rewritten in javascript and became a web client.\n\nToxic was acquired by Microsoft and ported to Windows, it will soon be replacing Skype.\n\nAntox was slowly replaced by uTox for android.\n\nnTox is still alive.\n\n\nI also received this image but can't make sense of it.\n\n{% limg Tox_ftl_message.jpg %}\n\n\nThe connection was then cut suddenly. I will try to find out why the connection cut and why I can't seem to be able to contact the future anymore.\n\nHappy Future Toxing.\n\nIn other news it has been reported to us that Tox works from a helicopter.\n","slug":"tox-ftl","updated":1427888844000,"excerpt":"<p>The Tox Foundation has made an important discovery today that might change the world forever.</p>\n","_id":"biladxo3ycojf78w","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox updates and GSoC 2015","date":1430132400000,"author":"Sean","tags":[],"content":"<p>As you may have noticed, your Tox client received an update.</p>\n<a id=\"more\"></a>\n\n<h2 id=\"New_API\">New API</h2>\n<p>After almost a month of blocking updates we finally pushed a major change that might have caused some issues with your friends. The new API was a major refactor and improvement in the protocol and the public API, resulting in issues with old API clients.</p>\n<p>To transition smoothly we blocked most updates so clients and other software could be updated to work with our changes, and when we felt this was done the flood gates were re-opened.</p>\n<p>If you haven’t already, please update your client and instruct your friends to do the same and you should be back to Toxing without interruption.</p>\n<h2 id=\"GSoC\">GSoC</h2>\n<p>After over a month of work reading proposals, talking to students, and debating on the best of the best we’ve come to a conclusion and decided on the 9 best students we could.</p>\n<p>Students were evaluated on proposals, how much they fit with what we’re trying to accomplish with Tox, and how much we thought they had a genuine interest in helping open source.</p>\n<p>With over 90 proposals from many amazing students from a wide variety of backgrounds, choosing 9 special few for this year’s GSoC was one of the most difficult decisions we’ve had to make all year and we hope we chose well.</p>\n<p>Want to know who got selected? This is published on the <a href=\"https://www.google-melange.com/gsoc/org2/google/gsoc2015/tox\" target=\"_blank\" rel=\"external\">Melange</a>.</p>\n<p>Did you get selected? Join us in <a href=\"https://webchat.freenode.net/?channels=%23tox-gsoc-students\" target=\"_blank\" rel=\"external\">#tox-gsoc-students</a> and get to meet your mentors if you haven’t already.</p>\n<p>Did you not get selected? Many of you submitted amazing proposals that we wish we could have selected but didn’t have the mentors or resources to do so. We’d greatly appreciate it if you’d continue to contribute to Tox or any other open source project that you find interesting.</p>\n","source":"_posts/new-api-gsoc-2015.md","raw":"title: Tox updates and GSoC 2015\ndate: 2015-04-27 07:00:00\nauthor: Sean\ntags:\n---\n\nAs you may have noticed, your Tox client received an update.\n\n<!-- more -->\n\n##New API\nAfter almost a month of blocking updates we finally pushed a major change that might have caused some issues with your friends. The new API was a major refactor and improvement in the protocol and the public API, resulting in issues with old API clients.\n\nTo transition smoothly we blocked most updates so clients and other software could be updated to work with our changes, and when we felt this was done the flood gates were re-opened.\n\nIf you haven’t already, please update your client and instruct your friends to do the same and you should be back to Toxing without interruption.\n\n##GSoC\nAfter over a month of work reading proposals, talking to students, and debating on the best of the best we’ve come to a conclusion and decided on the 9 best students we could.\n\nStudents were evaluated on proposals, how much they fit with what we’re trying to accomplish with Tox, and how much we thought they had a genuine interest in helping open source.\n\nWith over 90 proposals from many amazing students from a wide variety of backgrounds, choosing 9 special few for this year’s GSoC was one of the most difficult decisions we’ve had to make all year and we hope we chose well.\n\nWant to know who got selected? This is published on the [Melange](https://www.google-melange.com/gsoc/org2/google/gsoc2015/tox).\n\nDid you get selected? Join us in [#tox-gsoc-students](https://webchat.freenode.net/?channels=%23tox-gsoc-students) and get to meet your mentors if you haven’t already.\n\nDid you not get selected? Many of you submitted amazing proposals that we wish we could have selected but didn’t have the mentors or resources to do so. We’d greatly appreciate it if you’d continue to contribute to Tox or any other open source project that you find interesting.\n","slug":"new-api-gsoc-2015","updated":1435184252000,"excerpt":"<p>As you may have noticed, your Tox client received an update.</p>\n","_id":"5pq6dk48bv06lav8","categories":[],"comments":true,"layout":"post","photos":[],"link":""},{"title":"Tox infastructure and various changes","date":1436439600000,"author":"Sean","tags":[],"content":"<p>With all the drama going on, I think we should talk</p>\n<a id=\"more\"></a>\n\n<p>About a month back the Tox Foundation attempted to peacefully transition and move everything to the project itself. This included various domains and assets renewed and set in place for years.</p>\n<p>We wanted to peacefully transition things and share data, working together to move things from 1 owner to the next while ensuring everything continued to work and operate without issue.</p>\n<p>Unfortunately rather than work together to move everything and its data when I tried to discuss how to do so I was told to fuck off.</p>\n<p>Going forward, the Tox Foundation has decided that rather than let them break everything and since they don’t want to work together, that we’ll distance<br>ourselves from the main of the project, running infrastructure and some external programs totally separate from the project itself.</p>\n<p>We’ve decided on the following course of action: Maintaining the site and build infrastructure until 2017, placing the wiki and mailing list in read only mode, maintaining and supporting ToxMe indefinitely, transitioning our DNS infrastructure to HE, making libtoxcore static fully, making tox.horse static, and migrating ToxMail offsite for about a year.<br>Be advised that until the end of our support deadline things like the repo will continue to run and build packages successfully.</p>\n<p>If you have a @tox.im email and you’d like your emails archived and sent to you or transitioned to the new system please send an email to noc@tox.im</p>\n<p>At the end of the ~2 year extended support period we’ll evaluate either continuing to run everything or search for a new operator, suspending all further operations.</p>\n<p>While we have monitoring systems in place, if you notice an issue or something go wrong shoot an email to noc@tox.im ASAP.</p>\n","source":"_posts/tox-infa-update.md","raw":"title: Tox infastructure and various changes\ndate: 2015-07-09 07:00:00\nauthor: Sean\ntags:\n---\n\nWith all the drama going on, I think we should talk\n\n<!-- more -->\n\nAbout a month back the Tox Foundation attempted to peacefully transition and move everything to the project itself. This included various domains and assets renewed and set in place for years.\n\nWe wanted to peacefully transition things and share data, working together to move things from 1 owner to the next while ensuring everything continued to work and operate without issue.\n\nUnfortunately rather than work together to move everything and its data when I tried to discuss how to do so I was told to fuck off.\n\nGoing forward, the Tox Foundation has decided that rather than let them break everything and since they don't want to work together, that we'll distance \nourselves from the main of the project, running infrastructure and some external programs totally separate from the project itself.\n\nWe've decided on the following course of action: Maintaining the site and build infrastructure until 2017, placing the wiki and mailing list in read only mode, maintaining and supporting ToxMe indefinitely, transitioning our DNS infrastructure to HE, making libtoxcore static fully, making tox.horse static, and migrating ToxMail offsite for about a year.\nBe advised that until the end of our support deadline things like the repo will continue to run and build packages successfully.\n\nIf you have a @tox.im email and you'd like your emails archived and sent to you or transitioned to the new system please send an email to noc@tox.im\n\nAt the end of the ~2 year extended support period we'll evaluate either continuing to run everything or search for a new operator, suspending all further operations.\n\nWhile we have monitoring systems in place, if you notice an issue or something go wrong shoot an email to noc@tox.im ASAP.\n","slug":"tox-infa-update","updated":1436469764000,"excerpt":"<p>With all the drama going on, I think we should talk</p>\n","_id":"tdwn64ngglutcoz8","categories":[],"comments":true,"layout":"post","photos":[],"link":""}],"Tag":[{"name":"git","_id":"v9hgqbmdqj6y7m3c","posts":["nlg2cl3jkp72bljh"]},{"name":"jenkins","_id":"rl3qvhg1ki1za9dj","posts":["nlg2cl3jkp72bljh"]},{"name":"jToxcore","_id":"4c3qgpjblqf7la9s","posts":["nlg2cl3jkp72bljh"]},{"name":"pgp","_id":"sshw3dk4ycgi1vys","posts":["nlg2cl3jkp72bljh"]}]}