Moved to https://wiki.tox.chat/users/nodes
1. Founder has all permissions. | |
2. Everyone in the chatroom can verify that public key X is indeed founder's key, it's a property of the chatroom and no peer stores it i.e. the chatroom itself contains that information somewhere, presumably in its ID (we don't rely on chatroom peers storing that data because they can came up with whatever they want i.e. say that the key X is not founder's key; we want that verification to be 100% exact and to work with even 1 peer in the chatroom). | |
3. To give permissions to user A, founder gives user A data which tells what permission level does A have (if we are going to have permission levels in tox at all). The data is signed by founder's private key. | |
4. Now A can show anyone that signed by founder data from the step (3) as a proof of her having permissions (anyone can verify that it was indeed signed by founder by (2)), so A can exercise her rights over everyone in the chatroom. | |
5. If A gives permissions to B, 1) A sends her founder-signed data to B to show that she i |
#------------------------------------------------- | |
# | |
# Project created by QtCreator 2014-04-01T02:11:23 | |
# | |
#------------------------------------------------- | |
QT += widgets network | |
TARGET = ToxDNSRecordResolver | |
TEMPLATE = app |
#!/usr/bin/env python | |
""" | |
Copyright (c) 2014 by nurupo <nurupo.contributions@gmail.com> | |
Permission is hereby granted, free of charge, to any person obtaining a copy | |
of this software and associated documentation files (the "Software"), to deal | |
in the Software without restriction, including without limitation the rights | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is | |
furnished to do so, subject to the following conditions: |
// "License": Public Domain | |
// I, Mathias Panzenböck, place this file hereby into the public domain. Use it at your own risk for whatever you like. | |
#ifndef PORTABLE_ENDIAN_H__ | |
#define PORTABLE_ENDIAN_H__ | |
#if (defined(_WIN16) || defined(_WIN32) || defined(_WIN64)) && !defined(__WINDOWS__) | |
# define __WINDOWS__ |
template<typename Func, Func func> struct thunk; | |
template<typename Class, typename R, typename ...Args, R(Class::*func)(Args...)> | |
struct thunk<R(Class::*)(Args...), func> | |
{ | |
static R call(Tox *tox, Args ...args, void *userData) | |
{ | |
return ((*static_cast<Class *>(userData)).*func)(args...); | |
} | |
}; |
#Tox Echo Bot Example
##Getting started
This example is aimed at introducing people to basics of using toxcore C API. It's assumed that the reader is familiar with the C programming language.
Before jumping to coding, we need to install toxcore library, which can be done by following installation instructions from toxcore's git repository.
For the sake of simplicity, we will use a couple of helper functions from the sodium library, which is a dependency of toxcore, so it should be installed along with it.
########## | |
# Tweaked Win10 Initial Setup Script | |
# Primary Author: Disassembler <disassembler@dasm.cz> | |
# Original Version: 1.4, 2016-01-16 | |
# Tweaked based on personal preferences for @alirobe 2016-03-23 - v1.4.1 | |
# NOTE: MAKE SURE YOU READ THIS SCRIPT CAREFULLY BEFORE RUNNING IT + ADJUST COMMENTING AS APPROPRIATE | |
# This script will reboot your machine when completed. | |
########## | |
# Ask for elevated permissions if required |
I hereby claim:
- I am nurupo on github.
- I am nurupo (https://keybase.io/nurupo) on keybase.
- I have a public key whose fingerprint is 1D4E 9375 AD9B D50F 80FF 55AC 6F55 0977 4B1E F0C2
To claim this, I am signing this object:
This year's ToxCon was super fun, thanks to everyone who attended it!
If you have missed the event, list of talks, talk slides and some photos from the event are available online. No videos are available as it was decided not to record the talks.
We are planning to hold another ToxCon the next year, so keep an eye for announcements. If you are working on anything fun with Tox and want to share it with the world, consider giving a talk at the next ToxCon -- we would be happy to host your talk.