| #!/bin/sh | |
| # Taken from http://blog.encomiabile.it/2011/02/03/prune-quassel-database/ | |
| # Taken from https://gist.github.com/Und3rf10w/36a2034cb2c8eafbfb801c1a89e1f8bc | |
| BAK_PATH="${HOME}/.config/quassel-irc.org/quassel-storage.sqlite.bak" | |
| CURRENT_PATH="${HOME}/.config/quassel-irc.org/quassel-storage.sqlite" | |
| # first day of data that will be maintained | |
| # -7 day means that *every* chatline stored before 8 days ago and so on are going to be eliminated. | |
| # only the last 7 days are keeped. | |
| DATE_TO_PRUNE='-7 day' |
| === 2021-05-23 === | |
| /cs info #toktok | |
| [06:38:26] [ChanServ] Information on #toktok: | |
| [06:38:26] [ChanServ] Founder : iphy | |
| [06:38:26] [ChanServ] Registered : Nov 02 12:23:24 2009 (11y 29w 1d ago) | |
| [06:38:26] [ChanServ] Mode lock : +ntcg | |
| [06:38:26] [ChanServ] URL : https://toktok.ltd | |
| [06:38:26] [ChanServ] Flags : KEEPTOPIC GUARD | |
| [06:38:26] [ChanServ] The #toktok namespace is registered to the toktok project |
Run /msg NickServ LISTCHANS to see what permissions you have in what channels.
For each channel you have +s, +R and either +o or +O or +t permissions in, run:
/msg ChanServ OP #channel
/msg ChanServ SET #channel TOPICLOCK OFF
/msg ChanServ TOPIC #channel We have moved to irc.libera.chat
This October the Tox developer community will be holding its third annual conference in the @metalabvie in the heart of Vienna, Austria.
The event will be 3 full days, from Friday, October 11th to Sunday, October 13th.
We will talk about Tox, and other security related and interesting topics.
If you would like to attend, meet the Tox devs, do some live hacking, or just socialize, get your
free ticket (and reserve a T-shirt) here:
https://pretix.eu/ZMetalab/ToxCon2019/
You can find the exact address on your ticket!
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.
I hereby claim:
To claim this, I am signing this object:
| ########## | |
| # Tweaked Win10 Initial Setup Script | |
| # Primary Author: Disassembler <[email protected]> | |
| # 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 |
#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.
| 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...); | |
| } | |
| }; |