| Age | Commit message (Collapse) | Author |
|---|
|
Renamed tox_file_send_seek to tox_file_seek.
|
|
A couple of minor reasons, combined warrant a PR imo:
a) fileChunkRequested is a better signal name than fileRequestChunkReceived, and I don't want to break consistency by reordering words for just this signal
b) "request chunk" is parsed by English speakers as a verb-object combination,
implying sending the request, not receiving, whereas "chunk requested" is
parsed (more correctly) as an adjective-noun combo (in particular, request is
a noun not a verb), and thus reads far more like "hey heads up we just got a request"
For instance some tests/testing code had some callbacks to *receive* chunk requests, and they were called "tox_file_request_chunk"... to receive a chunk, not request it. Now they're called "tox_file_chunk_request".
So yeah...
|
|
|
|
new_api
|
|
messaging function.
This removes code duplication and allows us to easily add new message
types to the api without having to add new functions.
|
|
friend_get_connection_status
|
|
This is now documented in the API.
Ported programs in testing/ to this behaviour.
|
|
receive to recv in file receive functions.
Added TOX_MAX_FILENAME_LENGTH define.
|
|
|
|
file_id is a 32byte identifier that can be used by users to identify
file tranfers across core/client restarts in order to resume broken
file tranfers.
In avatar tranfers it corresponds to the hash of the avatar.
Added tox_file_get_file_id() function to api to obtain the file_id
of an ongoing file transfer.
If not set, core will generate a random one.
|
|
|
|
|
|
|
|
|
|
|
|
This is done so that the function now has the same parameters as the
request chunk callback.
|
|
|
|
|
|
|
|
|
|
|
|
Add missing function and fixes some typos and formatting.
|
|
Commit b8d530c9e0bbce331f22cbff7f818e49673d5bd7 and some of its
parents changed the public name of "client id" to "public key".
Update the avatar documentation to follow the idea.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change location of the user avatar from "<data dir>/avatar.png" to
"<data dir>/avatars/<user id>.png", as proposed by commit
6f4ab49f5c2a33aab00bdb9e80dfe51624089899
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes building on OS X and other systems whose limits.hs have PATH_MAX.
|
|
|
|
Support for other formats was deemed unnecessary in the code review
and therefore removed. The value for the constant TOX_AVATARFORMAT_PNG
is now set in stone; if the other formats become needed again in the
future, this commit shall be reverted and the enum values reordered to
keep compatibility.
|
|
Add a protocol and the APIs to straightforwardly support user avatars
in client applications. The protocol is designed to transfer avatars
in background, between friends only, and minimize network load by
providing a lightweight avatar notification for local cache validation.
Strict safeguards are imposed to avoid damage from non-cooperative or
malicious users and to limit network usage.
The complete documentation is available in docs/Avatars.md and sample
code is available in testing/test_avatars.c.
Code and documentation are released under the GNU GPLv3 or later, as
described in the file COPYING.
|
|
|
|
Patch also fixes NetBSD and OpenBSD, but I can't test that.
<pty.h> is <util.h> on some BSDs.
|
|
tox_shell is a basic secure shell that can be used to control a
computer from any Tox client.
Just run tox_shell and make it add your Tox id.
It's very basic but it works.
|
|
PORT IS NO LONGER PASSED IN NETWORK BYTE ORDER.
Removed useless ipv6enabled parameter.
|
|
tox_new() now takes a Tox_Options struct as argument.
If a NULL pointer is passed to that struct, defaults are used.
|
|
new_messenger() now takes an options struct as an argument.
|
|
|
