ratox - Mirror of https://git.2f30.org/ratox

Age	Commit message (Collapse)	Author
2014-12-09	Add ability to specify save file as command line argument	FRIGN
	Also, get closer to the STS (Single Tox Standard) by calling the the save file "save file" and not "data file". Additionally, augment the manual section about encrypting and decrypting the save file.
2014-12-08	Rework some of the log-warnings	FRIGN

2014-12-08	Proceed with cleanup	FRIGN

2014-12-08	Guard FD_APPEND with a do { } while(0)	sin

2014-12-08	Begin cleanup according to style(9)	FRIGN

2014-12-07	Bump version to 0.2	sin

2014-12-07	Re-prompt passphrase when creating a new encrypted save	FRIGN
	This is more consistent with the de-facto behaviour of password-setting prompts.
2014-12-07	Remove SEE ALSO section from manpage	sin

2014-12-05	Update LICENSE and AUTHORS section in manpage	sin

2014-12-05	Fix wording in manpage	sin

2014-12-05	Add -E and -e to enable and disable data file encryption	sin

2014-12-01	Do not handle SIGABRT - let it terminate the process immediately	sin

2014-12-01	Underline references to files	sin

2014-12-01	Add info about `id' file to manpage	sin

2014-12-01	Update manpage	sin

2014-12-01	Increase connection delay to 4 seconds	sin

2014-12-01	Do the datasave() as early as possible in shutdown()	sin

2014-12-01	Save data file on receipt of a deadly signal	sin

2014-12-01	Update TODO	sin

2014-11-30	Update list of nodes	sin

2014-11-30	Connect to nodes in a random order to minimize load on any given node	sin

2014-11-30	Update TODO	sin

2014-11-29	Adapt to latest cleanup in API	FRIGN

2014-11-28	Fix style	sin

2014-11-27	Don't lock up on blocking call_out	FRIGN
	Since the av-refactor, we keep a call active as long as there is a listener or a sender. In case we don't have a listener, don't lock up in the sending function and rather just fall-through in case the write blocks. We can't do that as easily with the file-data-code, because data- integrity is very important there.
2014-11-26	Fit ratox to new toxav-API	FRIGN
	mannol has done a great job re-working the toxav-api[0] also based on our suggestions for a stricter callback-approach. Previously, toxav-callbacks could hit any time, leaving us with dramatic timing-issues and instability in certain situations. The new toxav_do()-call enables the client to control when to fire the callbacks. toxav_do_interval() makes sure no time is lost in the meantime. [0]: https://github.com/irungentoo/toxcore/pull/1163
2014-11-01	Don't assume mono-audio in defaults	FRIGN

2014-10-24	Use (none, pending, active) instead of (0, 1, 2)	sin

2014-10-24	Rename .ratox.data to .ratox.tox to comply with STS	sin
	https://github.com/Tox/Tox-STS/blob/master/STS.md
2014-10-23	Add double spacing between sections in README	sin

2014-10-23	Add screencasting example	sin

2014-10-23	Add an examples section in the README	sin

2014-10-18	Refactor logic in main-loop for pending calls even more	FRIGN
	and implement fifoopen in other places.
2014-10-18	Don't forget to queue call_out while incoming ringing	FRIGN
	Else the call would be rejected immediately in case you receive a call and have not yet opened call_out for reading.
2014-10-17	Indentation fixes	sin

2014-10-17	Refactor call-state management	FRIGN
	Checking call_out only and stopping the call as soon as call_out is gone is not desirable behaviour. It now keeps up the running call until both call_out and call_in have been "closed", no matter how or by whom it was started. This is done by introducing av.state, which is a bit field. While at it, I also incorporated the transmission-state into it. toxav_hangup() will now only be called from the one centralized flag-checking-loop before select, not in the callbacks themselves. This will also get rid of some race-conditions (more or less). Previously, call_out was constantly polled as long as the user was online. Change this to only attempt to open call_out when the call is initialized. This lowers CPU-usage dramatically.
2014-10-16	Remove ugly use of O_DIRECTORY	sin
	Oops kfreebsd builds break. Aw well.
2014-10-16	Cleanup	FRIGN
	AV-logging, logic and check for < 0 instead of == -1 (just to make sure).
2014-10-15	Remember to cool down the transfer for pending buffers as well	sin
	This change halves CPU usage on my system.
2014-10-15	Only complain if errno is not EWOULDBLOCK	sin

2014-10-15	Only call toxav_kill_transmission() after toxav_prepare_transmission()	sin
	toxav_prepare_transmission() sets the internal toxav `call_active' state variable. This is checked in toxav_kill_transmission() and only if set, proceeds to release the resources.
2014-10-15	Update README	sin

2014-10-15	Build with -g so users can provide meaningful backtraces	sin

2014-10-15	Fortify and optimize file-sending	FRIGN
	Do this in two ways: 1) only allow ratox to stay in the file-sender for a certain amount of time 2) Stop hammering tox_file_send_data(). When it returns -1, we put the given friend into a cooldown-state, because all internal transmission slots are full. File sending thus now works in bursts, reading from file_in as long as tox_do() allows or until tox_file_send_data() fails. An easy way to see why we need to do the former is piping /dev/urandom to file_in, which never blocks. Effectively, the user goes "offline" after a while given he is trapped inside the loop. Piping to /dev/urandom is not an unrealistic testcase. Imagine a researcher who desperately needs true random data from his special RNG in his lab using ratox and piping it through /dev/urandom.
2014-10-14	Change the state-files	FRIGN
	rename file_pending to file_state rename call_pending to call_state 0 = no call 1 = call pending 2 = call active
2014-10-13	Only send call-data when Tx transmission is ready	FRIGN
	Due to a bug in toxcore the call is set to active too early, leaving room for invocations of sendfriendcalldata() even though the transmission has not yet been set up in cbcallstart. Fix this with a small workaround keeping the transmission-state in the client. In the long run, this definitely needs to be fixed in toxcore for consistency.
2014-10-13	Fortify error-checks and FSM	FRIGN
	Basically the direct calls to cancelcall() should be minimized and only set off in a callback. Additionally, tweak other error-cases and don't always quit fatally but instead provide ways to get out of an error-condition.
2014-10-13	Finish cleaning up av-callbacks	FRIGN
	Now it's fun again to work with the code.
2014-10-12	Further simplify call-start-callbacks	FRIGN
	using the udata-void pointers to pass data as a source of information.
2014-10-12	Use (void *userdata) in callbacks and drop ringing-callback	FRIGN
	This saves a lot of LOC and is definitely easier to maintain.