Miranda NG Official Community Forum

Forum for English speaking Miranda NG users => Development => Topic started by: watcher on 17 08 2014, 17:42:31

Title: Tox protocol
Post by: watcher on 17 08 2014, 17:42:31
This topic is dedicated to Tox (https://uvarov.pw/tox.html) protocol development and beta-testing.

When creating new Tox account you can use Tox profile from another Tox client (see the screenshot) to import your existing friend list:

(http://i.imgur.com/hzyf6FF.png)

If you choose not to import old Tox profile - press "Create" button to create a new one.

Current state of Tox protocol in Miranda (http://forum.miranda-ng.org/index.php?topic=2502.0)
Title: Re: Tox
Post by: Vulpix on 17 08 2014, 18:38:51
Testing!

Is there a Visual C++ Redist requirement for this? (looks like the 2010 one)

I cannot load the plugin, it says (when starting miranda):
Title: Re: Tox
Post by: Black Sniper on 17 08 2014, 18:43:42
Similarly. Please share a file. Or can you say that you need to reinstall?
---
Аналогично. Поделитесь пожалуйста файликом.
Или может, скажете что нужно переустановить?
Win7 x64
Title: Re: Tox
Post by: watcher on 17 08 2014, 18:56:26
It's just a debug builds, i will rebuild it as release in a short while.
Title: Re: Tox
Post by: watcher on 17 08 2014, 19:02:31
Done, please re-download.
Title: Re: Tox
Post by: Ищезаяц on 17 08 2014, 19:55:18
блин, айдишка сменилась :) а так круто. только ника нету, хоть в настройки и вписал.
Title: Re: Tox
Post by: Vulpix on 17 08 2014, 20:06:07
Done, please re-download.

It works! And sends messages too!

I have a question. For users who did not import their profile - where in Miranda can they check their own Tox ID so I can add them? (I got my Tox ID from uTox as I have been using it previously).

I think it should be easily visible somewhere, like in my details or on the account page - to make it possible for the user to link it to another user.

Otherwise, stellar! Didn't take long to make this!

All I need now is file transfer and we're golden :D

Much <3 to unsane/watcher/everyone.
Title: Re: Tox
Post by: watcher on 17 08 2014, 20:10:12
I have a question. For users who did not import their profile - where in Miranda can they check their own Tox ID so I can add them?

In search section enter the ID and press "Add to list" without pressing "Search" button. It supposed to work this way, although I'm not sure that it works at all yet. But you can try anyway.
Title: Re: Tox
Post by: Vulpix on 17 08 2014, 20:18:09
Well, no; my question was, how do I know my own Tox ID (as a miranda user). I cannot put it in search if I don't know it x3

And a second question:

After running the dbchecked, it said there were some duplicate items (skipping). After launch, I checked history and found that the check garbled some of the history.

I used the "mark events as read" option, because all events were shown every time I opened the chat window (and I know that marking all events as read fixes this).

Sample of garbled text:

Vulpix, 17.8.2014 22:00:22:
Hi!

Vulpix, 22:00:23:
:3

<party b>, 22:00:39:
汐慥敳愠瑵潨楲敺洠⁹敲畱獥⁴湡⁤摡⁤敭琠潹牵挠湯慴瑣氠獩⹴Ā

<party b>, 22:00:43:
祭爠煥敵瑳愠摮愠摤洠⁥潴礠畯⁲潣瑮捡⁴楬瑳.

Vulpix, 22:00:51:
You see yourself as Unknown contact? |3


I noticed the same behavior with Steam history so I assume this is some sort of a bug - but I don't know which plugin this relates to. DB checker? History storing itself?

Version info:

Sorry but you are not allowed to view spoiler contents.


Seems to be a reoccurence of: http://forum.miranda-ng.org/index.php?topic=1222.msg5836#msg5836
Title: Re: Tox
Post by: watcher on 17 08 2014, 20:22:01
my question was, how do I know my own Tox ID (as a miranda user)

I think it's not implemented yet.

I noticed the same behavior with Steam history so I assume this is some sort of a bug - but I don't know which plugin this relates to. DB checker? History storing itself?

I hope unsane will answer it tomorrow.
Title: Re: Tox
Post by: dartraiden on 18 08 2014, 10:40:09
Windows XP: account creation lead to crash

crashlog (http://pastebin.com/gbkXsw6K)
Title: Re: Tox
Post by: unsane on 18 08 2014, 13:08:12
Vulpix, thanks for report. I'll fix it at this evening or a bit later)
Title: Re: Tox
Post by: watcher on 18 08 2014, 21:20:20
Binaries updated to r10234 (http://trac.miranda-ng.org/changeset/10234). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 18 08 2014, 21:51:02
Vulpix, thanks for report. I'll fix it at this evening or a bit later)

Hello! Great, now I can see my Tox ID in the accounts pane! However, it would be nice if I could somehow copy it (or see it somewhere from where it can be copied) to share with a friend.

Added in the latest binary.

Another thing is - the issue with the database; is this related to tox/steam protocol or is this something else? Because (as I said a few posts above), these two seem to be showing the same kind of issue. Do you want some more reports about that?

Thank you for your continuous effort to improve Tox support in miranda!

Post Merge: 19 08 2014, 07:31:45
Binaries updated to r10234 (http://trac.miranda-ng.org/changeset/10234). Please update manually from attachments in the first post.

It's better now!

However, every time I restart miranda, my "nickname" is lost (and I become the "tox ID" instead, so it looks very weird in the chat window). Also, setting nickname only affects my miranda - others don't actually see the change.

Update:

I "fixed" this by simply loading the tox profile in uTox, changing the necessary things, saving it, quitting tox and then moving the profile back to where miranda expects it. Nickname etc is now stored correctly :3 this should be fixed, hehe.
Title: Re: Tox
Post by: Vulpix on 20 08 2014, 14:56:16
Issue (minor):

UTF-8 / unicode characters (stuff like: "š ř ž" etc.. ) set as status message in uTox (or other tox clients) are not properly recognized by Miranda - ( uTox is able to display them, however - so the information is properly stored in the stream.). In miranda, they become random garbled characters.


Fixed in the latest binary.
Title: Re: Tox
Post by: watcher on 20 08 2014, 20:01:05
Binaries updated to r10245 (http://trac.miranda-ng.org/changeset/10245). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 20 08 2014, 21:25:47

Great job!

Title: Re: Tox
Post by: watcher on 21 08 2014, 06:33:59
Binaries updated to r10249 (http://trac.miranda-ng.org/changeset/10249). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 21 08 2014, 08:53:04
Latest binaries break buddy-adding. Previous binaries work just fine.

Issue:
Entering Tox ID (or toxme.se) returns "No results" in the add-buddy dialogue window.

Being added still works, so it's just the "search" that's broken.

Tested with both toxme and regular tox id on the latest binary (and obviously only tox id on the previous binary since it didn't have toxme).
Title: Re: Tox
Post by: unsane on 21 08 2014, 10:57:19
I broke searching by tox id specially.
It's not good if you can "find" invalid tox id.
Searching via toxme.se worked a few hours earlier (
Title: Re: Tox
Post by: Vulpix on 21 08 2014, 11:03:44
I see about the tox IDs. I assume it will be turned on when you have a mechanism to make sure you are searching by correct tox ID~

Retesting toxme.se:


Searching by toxme id works - however, only if you omit the @toxme.se component.

I.e. searching for user abcd@toxme.se returns nothing. Searching for user abcd returns user abcd@toxme.se (i.e. his tox ID, which you can then add)

If this is working "as intended", then it may need to be clarified in the search box - instead of "e-mail", it should say something different so that the user who is searching omits the @toxme.se part.
Title: Re: Tox
Post by: watcher on 22 08 2014, 06:36:20
Binaries updated to r10268 (http://trac.miranda-ng.org/changeset/10268). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 22 08 2014, 07:17:40
The other option to "add to friend list" is currently being worked on so it actually lets you add anything (even a completely random string, not just a tox ID). I assume this will be modified in a later fix.

As a sidenote, I can see that changing my status (i.e. online, away, DND) works - but for some reason, when you check the status of the protocol in Miranda, the "online" option is always highlighted, regardless of your choice - so it looks like you are Online (even though you have switched to Away, for example). Other clients see the protocol change, so it is just the local view that does not reflect the change.

Current state of tox updated @ sticky.

Post Merge: 22 08 2014, 08:13:10
Whilst looking for a reproduction scenario for a different bug, I found another one.

If you "spam"-send messages from miranda (not to miranda, that doesn't break anything), miranda crashes. Windows-ish freeze. No crash dump even with crashdumper installed and enabled.

To reproduce, simply open a tox chat and for example very quickly send "1" (1 enter 1 enter 1 enter). The window will freeze and miranda will stop responding. On the other party's message window, you can see that miranda has disconnected.
Title: Re: Tox
Post by: watcher on 22 08 2014, 12:44:46
Binaries updated to r10288 (http://trac.miranda-ng.org/changeset/10288). Protocol icons added. Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 22 08 2014, 13:12:36
Protocol icons work and show properly for contacts in the contact list as well.  :THUMBS UP: Feature listed in the state of tox protocol sticky in "quality of life" section.

Issue with the local protocol status being "stuck" in "online" (even though the actual status can be changed) still prevails.
Title: Re: Tox
Post by: watcher on 22 08 2014, 13:26:03
Issue with the local protocol status being "stuck" in "online" (even though the actual status can be changed) still prevails.

Yes - this is pretty annoying.
Title: Re: Tox
Post by: Robyer on 22 08 2014, 13:34:22
I think that "spam" problem is because toxlibrary isn't thread safe (as I understand from their TODO list, they're working on it). So unsane could fix it in plugin (use thread locks and send one message at once) and/or wait for tox devs to fix it too.
Title: Re: Tox
Post by: watcher on 22 08 2014, 20:58:22
Binaries updated to r10308 (http://trac.miranda-ng.org/changeset/10308). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 23 08 2014, 06:04:53
Changing status now reflects on the local protocol icon in miranda  :THUMBS UP:
Thread-safety workaround seems to be working, I was unable to make miranda crash where I was previously able to make it happen 100% Nope, still broken :< guess we'll have to wait for a fix in toxcore.

Searching/adding buddies is still broken:

trunk/protocols/Tox/src/tox_proto.cpp
Line 168: regex = "^\\s*([A-Za-z]+)(@toxme.se)?\\s*$";


This causes toxme usernames that have other characters in them to be unsearchable. For example, tox username abcd-efgh@toxme.se cannot be found. abcdefgh@toxme.se works, however.

Adding by tox ID causes weird behavior where no matter which tox id you add, it will (after adding) always say "this tox ID is already in your contact list", regardless of whether that's actually true or not.
Being added by tox ID doesn't actually send out add request so the adding is still not functioning.

Looking up a toxme user with regular username abcdef works - but adding doesn't do anything (I assume the add-by-id broke this as well?) Contact request is never sent.
Being added "from the other party" does work and authentication is properly accepted.
Title: Re: Tox
Post by: watcher on 23 08 2014, 20:25:46
Binaries updated to r10315 (http://trac.miranda-ng.org/changeset/10315). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 23 08 2014, 20:40:24
Searching via toxme-se is now working even for names with weird characters.  :THUMBS UP:

Clicking "add contact" on the add contact dialogue of the found contact doesn't do anything.

Weirdly enough, clicking "user details" in the right-mouse-button menu of the search results shows the user details of the local miranda user - nothing related to the search result.

Searching via tox ID simply says "contact is already in your list" (even though it is not) and you cannot add the user.
Title: Re: Tox
Post by: watcher on 23 08 2014, 20:54:19
Binaries updated to r10316 (http://trac.miranda-ng.org/changeset/10316). Please update manually from attachments in the first post. (message sending fix).
Title: Odp: Tox
Post by: Vulpix on 24 08 2014, 08:56:41
Contact adding is still broken
Netlog/debug log:
[10:49:14 0B3C] CToxProto::AddToList: you cannot add yourself to friend list
[10:49:15 0B3C] CToxProto::AddToList: you cannot add yourself to friend list
[10:49:15 0B3C] CToxProto::AddToList: you cannot add yourself to friend list
[10:49:16 0B3C] CToxProto::AddToList: you cannot add yourself to friend list

I think that the search result (when right-clicking) returns the user's own tox protocol ID. This is also why right-clicking and selecting "user details" shows my own details; not the person I'm trying to add.

This happens with both tox ID and toxme.se search result because the "add contact" dialogue is in the end the same kind of dialogue.


Additionally:

I noticed a strange behavior with Tox after the last changes (though it may have nothing to do with them).

If I go online with Tox, sometimes it gets stuck in the "connecting" phase. I.e. netlog says this:

[10:50:36 0E0C] Setting protocol/module name to 'Toxanda'
[10:50:47 0E0C] CToxProto::SetStatus: changing status from 40071 to 40072
[10:50:47 1704] CToxProto::PollingThread: entering


And nothing will happen even if you leave it up for several minutes.

However, if you switch to offline and online again, the protocol reconnects immediately (or very quickly):

Not sure what this is related to, but my connection is stable, 240/20Mbit optics, so it's not the connection.
Title: Re: Tox
Post by: watcher on 25 08 2014, 19:03:40
Binaries updated to r10320 (http://trac.miranda-ng.org/changeset/10320). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 25 08 2014, 19:21:57
And nothing will happen even if you leave it up for several minutes.

However, if you switch to offline and online again, the protocol reconnects immediately (or very quickly):

For me it's quick only if i restart Miranda, otherwise it takes pretty long tim until i see contacts online if i played with on\off status (it may be as well libtox initialization behavior).
Title: Re: Tox
Post by: Vulpix on 25 08 2014, 20:26:15
Hmm, it's not so much about seeing contacts online. It's literally about the protocol taking a long time to show as "connected" - sometimes it never happens.

Anyway, latest binary:

Contact adding by tox id - fixed!  :THUMBS UP:
Contact adding by toxme.se - fixed!  :THUMBS UP:
Title: Re: Tox
Post by: watcher on 25 08 2014, 21:02:54
Hmm, it's not so much about seeing contacts online. It's literally about the protocol taking a long time to show as "connected" - sometimes it never happens.

Protocol itself - for me it's a matter of seconds to re-connect.
Title: Re: Tox
Post by: Vulpix on 25 08 2014, 21:13:02
I see... well anyway! I'm very excited about file transfers :D I saw that some initial stuff was being put in! <3
Title: Re: Tox
Post by: watcher on 28 08 2014, 20:33:47
Binaries updated to r10334 (http://trac.miranda-ng.org/changeset/10334). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 28 08 2014, 21:31:48
 the /me actions work, but I didn't see that anywhere for the other clients (like in uTox). I assume this is a miranda-only client-side thing? It does work though!  This is a Tox feature ( https://libtoxcore.so/api/tox_8h.html#a446bfa17062465c7f18674e9ff559f8c ), miranda now supports it. :THUMBS UP:

*wink wink file transfers next wink* :D

Chat direction from Miranda to uTox or qTox=>
Interestingly, using /me while chatting with someone using utox appears like a regular message, the "/me" is stripped.
Using /me while chatting with someone using qtox causes the message to not be shown at all!

This is a client issue though, not a miranda issue.
Title: Re: Tox
Post by: unsane on 29 08 2014, 07:56:22
uTox support actions, but shows them in log like a message (and it's his own troubles).
Miranda is not possible to send the action otherwise, other than as a message with the prefix / me.
So, before the action event will be saved in database, miranda cuts /me prefix
and change the type of event (action should be shown not like a message in log, i suppose).
Title: Re: Tox
Post by: watcher on 29 08 2014, 08:36:30
action should be shown not like a message in log, i suppose

I checked in History++, it appears like a different type of event.
Title: Re: Tox
Post by: Vulpix on 29 08 2014, 08:40:01
I use ieview and the /me action appears exactly like a contact status change text - this is good and I am used to it.

I was just stating that the /me doesn't work with most tox-only clients (utox/qtox), but this is actually their issue; not miranda's.
Title: Re: Tox
Post by: watcher on 30 08 2014, 12:32:22
Binaries updated to r10340 (http://trac.miranda-ng.org/changeset/10340). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 30 08 2014, 12:33:08
I see... well anyway! I'm very excited about file transfers :D I saw that some initial stuff was being put in! <3

Now you can start testing it :)
Title: Re: Tox
Post by: Vulpix on 30 08 2014, 13:23:37
Now you can start testing it :)


So I did!

Test: Sending a 4.4MB text file.

Miranda to Miranda:

Sender:
Sees: "Unable to initiate file transfer" until the recipient accepts

Recipient:
Sees regular file transfer request. Upon choosing location, the file is partially stored. (Usually sub-20KBytes of the file) Both receive "Filetransfer was successful" message.

Received file:
- Sub-20KBytes of the source file
- One byte (00) is appended to the beginning of the file.
- File is closed() - can be deleted etc.

Miranda to uTox:

Sender:
Sees: "Unable to initiate file transfer" until the recipient accepts

Recipient:
Sees regular file transfer request. Upon choosing location, the file is partially stored. (Usually sub-20KBytes of the file) Both receive "Filetransfer was successful" message.

Received file:
- Sub-20KBytes of the source file
- Up to the point where the file is cut off, there are no differences between the received and the source file.
- File is closed() - can be deleted etc.

uTox to Miranda:

Sender:
Sees regular file send request.

Recipient:
Sees regular file transfer request. Upon choosing location, the file is stored completely. Progressbar is properly displayed throughout the entire transfer.

Received file:

- Complete
- An empty byte (00) is appended to the beginning of the file. Rest of the file is unchanged (md5 is valid after removing the first byte of the received file)
- File is closed() - can be deleted etc.


Fixed! The above case now works properly!


BONUS:

uTox to Miranda, pausing and resuming transfer mid-transfer:

Sender:
Everything is normal here

Recipient:
- Complete
- An empty byte (00) is appended to the beginning of the file. Rest of the file is unchanged (md5 is valid after removing the first byte of the received file)
- File cannot be deleted ("remains opened in miranda NG") when you attempt to remove it.


Fixed! The above case now works properly!



uTox to Miranda, cancelling mid-transfer:

Sender:
Everything is normal here

Recipient:
Doesn't receive the notification that the transfer was cancelled - leaves filetransfer open. Can be cancelled manually and the file can then be deleted.


Fixed! The above case now works properly!

Sending 2GB+ files (from 64bit utox to 64bit miranda):

Sender:
Everything is normal here

Recipient:
Sees regular file transfer request. Upon choosing location, the file is partially stored. (Usually sub-2KBytes of the file) Both receive "Filetransfer was successful" message.


Sending multiple files at once from uTox to Miranda:

Sender:
Queues up multiple files just fine

Recipient:
Receives a filetransfer popup for each file queued up.

Files:
Saved successfully, each with an empty byte appended to the beginning of it.


Fixed! The above case now works properly!
Title: Re: Tox
Post by: watcher on 07 09 2014, 06:31:19
Binaries updated to r10383 (http://trac.miranda-ng.org/changeset/10383). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 07 09 2014, 08:07:00
Test cases with results updated in my previous post.

TL;DR - asides from sending a 2+GB file, everything else works, for uTox=> miranda transfer! :)

Issue:
When logging in, other clients sometimes see me as "away", even though my status is definitely online in miranda. I am yet to find a clear reproduction scenario.

To "fix" that, what I need to do is change my status to "away" and then back to "online"; this will show me as online with the other clients. I tried it with the second client being offline too, to make sure this is actually something that's internally exposed to them; and indeed. Shutting down the "party B" client, changing from online to away and then back to online and then starting the "party b" client again correctly shows me as online; i.e. "internally", in miranda, the tox protocol tells others I'm "away" whilst showing me as "online" in miranda. Weird!

Post Merge: 08 09 2014, 07:48:05
Tox protocol ignores proxy settings in "Network" section of Miranda, i.e. it always connects directly. (Even with IPv6 / UDP disabled.)
Title: Re: Tox
Post by: watcher on 09 09 2014, 20:21:10
Binaries updated to r10412-10414 (http://trac.miranda-ng.org/changeset/10412).
Title: Re: Tox
Post by: Vulpix on 09 09 2014, 21:34:25
Hello Watcher/Unsane,

I can see that this is a big change in the storing of database data for Tox (in miranda); however, this also means I would lose all of the histories with my tox contacts.

I tried exporting/importing user history into a new contact, but it doesn't work as intended.

I have downgraded back to my previous version of Tox and restored miranda from backup.

Please implement a way to use the new version without losing all user data. I already have significant history stored under these contacts.

Thanks!
Title: Re: Tox
Post by: watcher on 10 09 2014, 06:28:11
Unsane wrote the converter - testing now.

Post Merge: 10 09 2014, 06:52:25
Not working for now, we will try and fix it at evening.
Title: Re: Tox
Post by: Vulpix on 10 09 2014, 07:16:14
Thank you!

I'm sorry if I'm adding more work, but I already have ~10 tox contacts, some with a lot of history (miranda x64).

Thank you very much for the effort with the converter! I'll wait until it is ready.
Title: Re: Tox
Post by: watcher on 10 09 2014, 20:46:27
Binaries updated to r10423 (http://trac.miranda-ng.org/changeset/10423). Please update manually from attachments in the first post.

Post Merge: 10 09 2014, 20:46:54
Vulpix,  converter should work, you can try it.
Title: Re: Tox
Post by: Vulpix on 10 09 2014, 21:24:17
Thanks!

It's working :) No duplicate contacts and histories stayed the same.

Thanks~!
Title: Re: Tox
Post by: watcher on 11 09 2014, 06:24:03
Binaries updated to r10426 (http://trac.miranda-ng.org/changeset/10426). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 11 09 2014, 15:13:31
Updated, everything seems good now. Thanks for the extra work with the converter~ I'm sure those who use it in miranda will appreciate it :)

Pending issues:

File sending is not enabled
Tox ignores "network" settings, i.e. you cannot set up a proxy for it
Title: Re: Tox
Post by: santa on 11 09 2014, 16:14:43
Miranda crashed on MenuItemEx while building menu, then I click on Tox contact in contact list or click on menu button in chat window.
Miranda is a latest nightly build from Plugin Updater, tox plugin is a latest from first topic message.
Tox profile was created with ToxID and attached to uTox tox_save profile.

Crash report attached to tracker issue #787.
Title: Re: Tox
Post by: watcher on 11 09 2014, 16:25:43
santa, confirmed. here is the crash log from me also:

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox
Post by: santa on 11 09 2014, 16:34:57
Yet another issue is that in chat window (TabSRMM) contact ID shown in place of protocol name and contact name is empty.
May be it is related to the same.
Title: Re: Tox
Post by: Wishmaster on 11 09 2014, 16:46:56
Yet another issue is that in chat window (TabSRMM) contact ID shown in place of protocol name and contact name is empty.
May be it is related to the same.
Yes, there was a change in the way the contact tox ID is stored. As for Menuitemex it will help to disable "Copy ID" item in options.
Title: Odp: Tox
Post by: santa on 11 09 2014, 16:55:26
Yes, thanks. After disabling Copy ID in MenuItemEx settings crash gone.

Post Merge: 11 09 2014, 17:36:41
May be it's not a Tox issue, but after renaming Tox protocol in Accounts dialog (protocol name in list) from very long name to simple 'Tox', have garbage in TabSRMM window in Contact Protocol name filed. All OK after Miranda restart.
Title: Re: Tox
Post by: unsane on 11 09 2014, 17:49:45
santa, MenuItemEx fixed in r10432 (http://trac.miranda-ng.org/changeset/10432).
Title: Re: Tox
Post by: watcher on 11 09 2014, 18:02:56
Binaries updated to r10431 (http://trac.miranda-ng.org/changeset/10431). Please update manually from attachments in the first post.

Post Merge: 11 09 2014, 18:03:50
Vulpix,  please test file sending.
Title: Re: Tox
Post by: Vulpix on 11 09 2014, 18:49:22
Miranda => uTox:

Works! File is transferred just fine.  :THUMBS UP:

Miranda => uTox:
Pausing transfer in uTox and resuming:


This causes the transfer to restart from the beginning and the progressbar + numbers in miranda become very strange (4651658465135168kb/s for example). The progress bar is also jumping around.

The resulting file is malformed; as the "already-transferred part" is preserved, and the "restarted from beginning" part is appended to it, i.e. you end up with file bigger than the one you are sending.

Miranda => uTox:
Start transfer but then cancel it midway:


Everything works fine here, miranda shows "File transfer denied".


Miranda => Miranda
uTox=>Miranda


The receiving miranda crashes.

File receiving is now broken!

I tried it with the previous build as well and it's broken there too. Does this have something to do with the blob database conversion? I noticed that I cannot use %userid% variable anymore, but miranda crashes even when I select the save dir manually.

I think a fix similar to r10432 (http://trac.miranda-ng.org/changeset/10432) is necessary for this variable?
Title: Re: Tox
Post by: santa on 11 09 2014, 18:52:41
r10431

Miranda => uTox
Fine

uTox => Miranda
Crashed on receive dialog.

Subfolder with macro name '%userid%' created in 'Received Files' folder

Post Merge: 11 09 2014, 19:00:39
And after account renaming in Accounts three are two *.tox files in my profile directory, with old and new account names and different contents. Is it by intent?
Title: Re: Tox
Post by: watcher on 11 09 2014, 19:29:35
Binaries updated to r10433 (http://trac.miranda-ng.org/changeset/10433). Please update manually from attachments in the first post.  Crash on file receiving fixed!
Title: Re: Tox
Post by: Wishmaster on 11 09 2014, 19:35:52
And after account renaming in Accounts three are two *.tox files in my profile directory, with old and new account names and different contents. Is it by intent?
I can confirm that. In my opinion, Tox should use szModuleName instead of tszAccountName. szModuleName is constant and cannot be changed by the user after an account has been created.
Title: Re: Tox
Post by: santa on 11 09 2014, 19:48:45
uTox => Miranda fixed, but suggest folder named %userid% in save dialog.
Miranda receives notification, if uTox sender canceled upload, but does not receives if connection was lost or one of users goes offline.
Title: Re: Tox
Post by: Vulpix on 11 09 2014, 19:58:03
Sending a bigger (50MB+) file from miranda to miranda causes it to desynchronize; you will randomly lose a part of the file (tried using local file transfer from miranda to miranda).

I was also trying to send a bigger file to a friend (not locally) and his miranda crashed. I was unable to reproduce it myself using a remote computer.

Using %nick% for now as a workaround for the missing IDs.

Filetransfer works but is currently unreliable.

In one case, I was able to start a filetransfer where I selected the save folder correctly, everything went fine and then the transfer started.

On the sending miranda, everything looked normal.
On the receiving miranda, the file transfer dialog was stuck on "waiting for connection" - it never started showing the progress and no file was being received. I was able to cancel it on the remote end (the one stuck in "waiting for connection") and that correctly stopped it on the already-sending miranda.

I tried this by using uTox on the remote end, and utox was able to receive the file just fine. A thing to note is that the remote end is behind a firewall. The transfer was pretty slow using miranda to utox as well - but at least it did work.

Do you know what the reason for this could be?

Title: Re: Tox
Post by: watcher on 12 09 2014, 20:29:07
Binaries updated to r10440 (http://trac.miranda-ng.org/changeset/10440). Please update manually from attachments in the first post.
Title: Odp: Tox
Post by: santa on 12 09 2014, 21:06:17
Account file renaming works fine, thanks
But issue with account name in TabSRMM window still there.
First time my tox account name was eqaul to my ToxID (by mistake).

After account renaming there is something strange in account name filed in TadSRMM.
May be it reads already freed memory.

And after miranda restart correct account name is in place.
Title: Re: Tox
Post by: Vulpix on 14 09 2014, 04:56:23
https://github.com/irungentoo/toxcore/pull/1043 big change in toxcore - user data is now encrypted! Also some minor tcp tweaks, but yay! :3
Title: Odp: Tox
Post by: watcher on 14 09 2014, 18:53:16
Binaries updated to r10447 (http://trac.miranda-ng.org/changeset/10447). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: ISquishWorms on 20 09 2014, 14:43:00
This is crashing on Windows XP x86.  :(

I can include a crash report if that is of any help.

I have a fresh install of Miranda NG 0.95.2 Build #9966 and just downloaded the Tox binarys from first post.  On trying to create an account it is crashing on my Windows XP machine.  It works on my Windows 7 x86 machine although if move the copy over to my Windows XP x86 machine it will crash Miranda NG before it even gets to  load the GUI.

I have no other accounts other than the Tox account and just the standard plugins that come with a fresh install of Miranda NG.

I apologise if Miranda no longer supports Windows XP as I do realise that this OS is now considered old and no longer supported by MS.
Title: Re: Tox
Post by: Wishmaster on 20 09 2014, 15:01:08
Well, Windows XP should supported with Service Pack 3. Please read this (http://wiki.miranda-ng.org/index.php?title=Crash_reports) and provide a crash report.
Title: Re: Tox
Post by: Vulpix on 20 09 2014, 15:17:50
This is crashing on Windows XP x86.  :(

I can include a crash report if that is of any help.

I have a fresh install of Miranda NG 0.95.2 Build #9966 and just downloaded the Tox binarys from first post.  On trying to create an account it is crashing on my Windows XP machine.  It works on my Windows 7 x86 machine although if move the copy over to my Windows XP x86 machine it will crash Miranda NG before it even gets to  load the GUI.

I have no other accounts other than the Tox account and just the standard plugins that come with a fresh install of Miranda NG.

I apologise if Miranda no longer supports Windows XP as I do realise that this OS is now considered old and no longer supported by MS.

in light of

This topic is dedicated to Tox (https://uvarov.pw/tox.html) protocol development and alpha-testing.

Latest binaries can be obtained here. (for use with nightly builds only).


Can you get the latest miranda alpha and see if it still happens?
Title: Re: Tox
Post by: ISquishWorms on 20 09 2014, 15:33:16
Well, Windows XP should supported with Service Pack 3. Please read this (http://wiki.miranda-ng.org/index.php?title=Crash_reports) and provide a crash report.

Thanks.

I hope the following  below is of some assistance. 

I am actually a programmer so I guess I should stop being lazy and investigate it myself.  ;D  Only I do not currently have the space to install a copy of Visual Studio at home.  ::)

Sorry but you are not allowed to view spoiler contents.


Sorry but you are not allowed to view spoiler contents.

Title: Re: Tox
Post by: Vulpix on 20 09 2014, 15:34:57
Again:

Miranda NG Version: 0.95.2 build #9966

This plugin is meant for a nightly (dev) version of Miranda.

You can switch to it by going to options->Services->Plugin Updater->Files Source-> "Development Version"

Current version is Miranda NG version: 0.95.3 alpha build #10535
Title: Re: Tox
Post by: ISquishWorms on 20 09 2014, 15:40:01
Again:

Miranda NG Version: 0.95.2 build #9966

This plugin is meant for a nightly (dev) version of Miranda.

You can switch to it by going to options->Services->Plugin Updater->Files Source-> "Development Version"

Current version is Miranda NG version: 0.95.3 alpha build #10535

Sorry that will teach me for not reading my only excuse is that I am new to Miranda NG I decided to give it a try once I saw that a Tox plugin for it was under development (not sure that this is really a valid excuse for not reading though).  Anyway I will give the nightly (dev) build a try thanks.

**EDIT** Still crashing having updated to the nightly (dev) build.

Sorry but you are not allowed to view spoiler contents.


Sorry but you are not allowed to view spoiler contents.

Title: Re: Tox
Post by: watcher on 20 09 2014, 16:00:03
This is crashing on Windows XP x86.  :(

Crash on creating Tox account on Windows XP - plugin author knows about it, i showed it to him some time ago, so just wait for a fix :)
Title: Re: Tox
Post by: ISquishWorms on 20 09 2014, 16:07:42
Crash on creating Tox account on Windows XP - plugin author knows about it, i showed it to him some time ago, so just wait for a fix :)

Ok thanks for confirming that this is being looked into.

I am enjoying using and finding my way around Miranda NG and very much looking forward to using it with Tox.

I will wait for the fix.  :THUMBS UP:
Title: Re: Tox
Post by: watcher on 20 09 2014, 19:56:41
Vulpix,  can you please test the latest version of Tox? It has a converter - ID went back to string, for me on my main Tox Miranda Set-up conversion went bad and contacts got duplicated and those with history were not those in use anymore. But I did not have any backup :( And on newly created and other profiles i could not repeat that at all - it got converted. Can you please make backup and try it? Maybe you will be able to repeat that, than we'll try and fix this. If you can - i will PM it to you.
Title: Re: Tox
Post by: Vulpix on 20 09 2014, 20:07:03
Will check; gimme a minute. Also, you should try the autobackup plugin! It's helped me many times, hehe.

Post Merge: 20 09 2014, 20:13:08
One contact got duplicated; the contact I had the most chat history with. The "active" one is the one without any chat history. Also, that contact was online at the time. However, there was another contact also online and that one did not get duplicated, so I don't know what causes this. It is definitely buggy though; I'm restoring my backup now.

Out of curiosity, why was the tox id converted to blob in the first place; and why is it string again now?

I was able to reproduce this every time. I even tried running a db check before doing this and it still happened.
Title: Re: Tox
Post by: watcher on 20 09 2014, 20:21:32
Also, you should try the autobackup plugin! It's helped me many times, hehe.

I have next to 12 test set-ups (as a main Miranda NG tester), so they are not so important, also i keep them in dropbox, so i have full month of backups for every part of every set-up, by chance this one wasn't in dropbox folder, just a bad luck

Post Merge: 20 09 2014, 20:23:45
Out of curiosity, why was the tox id converted to blob in the first place; and why is it string again now?

Unsane tried to work with blob, it was more convenient to him, but then as it was converted - it brought many compatibility problems. so it had to be changed back.
Title: Re: Tox
Post by: Vulpix on 20 09 2014, 20:24:50
So yup. Was able to reproduce this. Anything else I need to do?
Title: Re: Tox
Post by: watcher on 20 09 2014, 20:25:08
Vulpix, this is good that you've got one contact duplicated, thanks! Unsane will contact you :)
Title: Re: Tox
Post by: watcher on 21 09 2014, 18:52:12
Binaries updated to r10544 (http://trac.miranda-ng.org/changeset/10544). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 21 09 2014, 21:17:29
Everything is working, no duplications etc. By the way, it looks like avatars will be implemented in toxcore pretty soon! https://github.com/irungentoo/toxcore/pull/1029
Title: Re: Tox
Post by: watcher on 21 09 2014, 21:33:48
By the way, it looks like avatars will be implemented in toxcore pretty soon!

Cool stuff!
Title: Re: Tox
Post by: Vulpix on 22 09 2014, 19:18:27
https://github.com/irungentoo/toxcore/pull/1029 merged! Avatars are now in!
Title: Re: Tox
Post by: Mataes on 23 09 2014, 04:44:26
They add nodes on 443 port. So now we can connect on tcp 443 :)
Title: Re: Tox
Post by: Vulpix on 25 09 2014, 07:38:14
Quick reminder:

Current (main) issue are the filetransfers.

Very unreliable at the moment, unfortunately :( They work for files around 1-2MB in size. Anything bigger (or if one of the parties has a slower connection) and the filetransfer will either:

1) stall (stop transfering) and then fail
2) become corrupted (file has less / more data when transfer is finished)
3) recipient's miranda will crash (though I also think this might be something with thread-safety - as this usually happens when they are typing while receiving a file)

The speed is pretty good. It's really just the reliability.

A sidenote is that if you choose "resume" a previously-failed filetransfer, the file will be appended in its entirety, i.e. if you had 50% of the file, you will end up with a file that's 1.5x the size of the original (and obviously corrupted).

Current medium-importance issues:

Current minor-importance issues:
Title: Re: Tox
Post by: watcher on 26 09 2014, 18:33:50
Binaries updated to r10594 (http://trac.miranda-ng.org/changeset/10594). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 28 09 2014, 20:13:08
Binaries updated to r10615 (http://trac.miranda-ng.org/changeset/10615). Please update manually from attachments in the first post. Added avatar support.
Title: Re: Tox
Post by: Vulpix on 28 09 2014, 21:21:44
Avatars are working!  :THUMBS UP: (Updated AVS is required for it though, the one on dist crashes it at the moment).
Title: Re: Tox
Post by: watcher on 28 09 2014, 21:53:23
Updated AVS is required for it though, the one on dist crashes it at the moment

Tomorrow's nightly build will fix it.
Title: Re: Tox
Post by: Vulpix on 29 09 2014, 08:11:15
The 32bit build of tox protocol damages miranda!

Do not use the latest plugin if you have a 32bit miranda.

EDIT: some new info. It looks like this happens on 64/32bit regardless - the trigger is that you must not have updated your tox plugin for some time. There was a string->blob and then blob->string conversion at one point, and this is the reason for the below behavior; if your miranda profile is running the old version of tox plugin which still uses blob, chances are this will happen when you update the plugin. Devs will take a look at this and figure out what to do, but until then, if you really want to update and try the new avatar support, make sure to have a backup of (preferrably) the entire miranda folder, so that you can just go back to the previous version in case this happens.

It truncates the *.tox profile to 0 bytes, causing you to be unable to connect. You cannot remove the tox profile to re-create a new one because miranda crashes whenever you open the account manager and select the tox profile. If you delete the tox plugin, it is possible; but of course you lose all of your histories etc. Best wait for some better solution and a fix to the 32bit tox.

No issues with the 64bit miranda.


With this I'd like to ask; was this tested before it was pushed live? I know it's alpha but at least launch miranda with it :< now there is some damage I cannot repair on my friend's profile.

EDIT:

I checked it on my own profile, and the same thing happened. But next time it didn't happen anymore, so I couldn't reproduce it. Seems this only happens to some 32bit mirandas... :/
Title: Re: Tox
Post by: watcher on 29 09 2014, 10:14:49
With this I'd like to ask; was this tested before it was pushed live? I know it's alpha but at least launch miranda with it :< now there is some damage I cannot repair on my friend's profile.

No - it was not, coder loads it on his profile, it works ok, i test it - it's ok, i upload it then. This is an alpha version and this is a topic for testing, we do test it ourself after compiling once. In testing branch anything can happen - this is not new. This is why plugin is not in official repo and updated only manually. Regression can happen at any moment and whole protocol might be rewritten, history lost and so on. And it's all ok in alpha branch.
Title: Re: Tox
Post by: Vulpix on 29 09 2014, 10:18:43
I used importtxt to export history, get a new tox profile set up by removing the tox dll and then removing the tox account; and then putting it back and re-creating one, so no data was lost pretty much. Still potentially annoying.

I do understand the point of alpha; and I was just curious how well tested these are before they're released :3
Title: Odp: Tox
Post by: watcher on 29 09 2014, 10:20:16
Do not use the latest plugin if you have a 32bit miranda.

Or better - find for us the way to repeat this, all of us are on 32-bit Miranda and with working Tox profile.
Title: Odp: Tox
Post by: watcher on 29 09 2014, 10:26:19
I do understand the point of alpha; and I was just curious how well tested these are before they're released :3

I can't test it well - i load it, doesn't crash, users online - it goes to the site. I can stop compiling and leave testing to users who can compile, debug, report and send a patch.

1 - there will be not enough testing this way.
2 - i think using alpha protocol and counting on any stability at all - is a huge mistake. This binaries are for testing purposes only, until it stabilizes and we put it to a regular repo, until then - anything might happen, not on purpose, it is just too raw and it's too much changes in code to stabilize. You write new feature, regression might kill working state.
Title: Re: Tox
Post by: Vulpix on 29 09 2014, 10:54:58
Or better - find for us the way to repeat this, all of us are on 32-bit Miranda and with working Tox profile.

I have a way to reproduce it
Title: Re: Tox
Post by: Mataes on 29 09 2014, 10:55:27
write it here please
Title: Re:Tox
Post by: Vulpix on 29 09 2014, 11:07:04
Heya Mataes!

I have a full profile from a test miranda where it happens every time.

I sent the profile to Watched and unsane. Watcher had a look at it and said that it's because the id is still blob (the profile wasn't updated until today, so probably the converter didn't convert it before some id check happened).

Watcher/unsane have the profile if you want more details

Post Merge: 29 09 2014, 13:29:07
Summary for people who want to update:

This happens on 64/32bit regardless - the trigger is that you must not have updated your tox plugin for some time. There was a string->blob and then blob->string conversion at one point, and this is the reason for the below behavior; if your miranda profile is running the old version of tox plugin which still uses blob, chances are this will happen when you update the plugin. Devs will take a look at this and figure out what to do, but until then, if you really want to update and try the new avatar support, make sure to have a backup of (preferrably) the entire miranda folder, so that you can just go back to the previous version in case this happens.

My previous post updated.
Title: Re: Tox
Post by: watcher on 29 09 2014, 18:07:26
Binaries updated to r10635 (http://trac.miranda-ng.org/changeset/10635). Please update manually from attachments in the first post. Tox profile corruption when updating from old versions must be fixed now.
Title: Re: Tox
Post by: santa on 29 09 2014, 20:31:40
There is an issue with copying contact's ID with context menu. It was truncated from 76 to 64 chars.
TabSRMM header shows truncated ID too.
Title: Re: Tox
Post by: Vulpix on 29 09 2014, 20:41:34
From what I understand, this is how Tox works by design. You can never copy the contact's ID because the nospam+checksum part will never be in it, as it is possible to change this in most of the clients. The full ID is only required for the initial authentication (adding a contact) and no longer for the actual communication; so changing your nospam value doesn't make you unable to chat with your friends; but this also means that you cannot "share a contact" with anyone else, unless the contact themselves tells you the current, full ID.

See:

https://github.com/notsecure/uTox/issues/325

https://github.com/tux3/qTox/issues/235

https://github.com/notsecure/uTox/issues/250
Title: Re: Tox
Post by: santa on 29 09 2014, 20:46:36
So it's a feature by protocol design. Thanks, I do not know about it)

Trying to add contact form Miranda list to antox by copying ID and writing it on phone, but have an Invalid ToxID message. May be, simpler way is to copy tox_save on phone.
Title: Re: Tox
Post by: Vulpix on 29 09 2014, 20:50:42
Hehe, yep, I tried something similar too :D And found out that copying the tox profile is the best idea. Since they are all compatible - as they all use toxcore :3 Though, you can't be online on both at the same time. Again, a tox issue (though they said they may make this possible at some point - online on multiple devices at the same time on the same profile)

Post Merge: 30 09 2014, 08:18:14
Avatars are working, however there are 2 issues:

1) Avatars for my contacts don't update unless I relog, i.e. they won't see my avatar unless I go offline and online.
2) clicking "offline" on tox protocol and then clicking "online" makes tox sign back in within 0.1 seconds (too fast, in other words), and what happens then is that all of the tox contacts show as offline. Even if they are online. And you can chat with them too! I.e. the protocol does, in fact, reconnect - but miranda doesn't show the contacts as online. Something is wrong there.
Title: Re: Tox
Post by: watcher on 30 09 2014, 19:34:57
Binaries updated to r10654 (http://trac.miranda-ng.org/changeset/10654). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 30 09 2014, 19:37:32
) clicking "offline" on tox protocol and then clicking "online" makes tox sign back in within 0.1 seconds (too fast, in other words), and what happens then is that all of the tox contacts show as offline. Even if they are online. And you can chat with them too! I.e. the protocol does, in fact, reconnect - but miranda doesn't show the contacts as online. Something is wrong there.

Confirming - quick off and then on does not return contacts online.
Title: Re: Tox
Post by: watcher on 02 10 2014, 20:17:47
Binaries updated to r10669 (http://trac.miranda-ng.org/changeset/10669). Please update manually from attachments in the first post.

Post Merge: 02 10 2014, 21:17:03
Binaries updated to r10672 (http://trac.miranda-ng.org/changeset/10672). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 04 10 2014, 12:43:58
Binaries updated to r10681 (http://trac.miranda-ng.org/changeset/10681). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 04 10 2014, 14:24:38
Tox now works through a proxy (i.e. with tor/vidalia)! (It respects the network settings). :THUMBS UP: (tox protocol state sticky updated)

However, tox will disrespect these settings if IPv6 / UDP is enabled (which is the default state).

Would it be possible to make it so that when you set proxy for Tox connection, it would prompt you that you have to set tox to not use ipv6 + UDP; or perhaps just notify the user and do so automatically?

Otherwise, great stuff~!
Title: Re: Tox
Post by: watcher on 04 10 2014, 18:25:21
Binaries updated to r10688 (http://trac.miranda-ng.org/changeset/10688). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 05 10 2014, 13:30:33
When sending files to a remote target, even after the transfer finishes (successfully!), the source files become locked, i.e. you cannot delete or edit them. Miranda has to be turned off first.
Title: Re: Tox
Post by: Vulpix on 10 10 2014, 11:55:41
Latest tox -  r10688(and I am not sure, but it might be a build before that as well, or maybe several :X I don't have them anymore to test this) is corrupting the <profile>.tox tox-save file.

Every miranda restart, the file grows by 50-250kb. Changes made (for example added contacts) are not saved when you log off. I assume something is wrong with writing the tox profile back to the tox save file, because when miranda is running, there are no issues.

This can manifest itself as contacts being offline forever (because miranda still sees the contact as it's in its contact database) but tox doesn't - since the tox contact is not in the tox profile.

My tox profile was now 5MB big - it should not be more than several dozen or hundred kilobytes at best.

Loading the tox profile in utox will fix this corruption - and revert the file to its normal state. As a workaround, I have re-added the people I previously added on miranda via tox - and this caused the changes to be saved in the tox profile, and upon copying it back to miranda's profile folder, I was finally able to see those people online again.

I hope this gets fixed soon, because I'm afraid my tox profile will become completely corrupted.
Title: Re: Tox
Post by: Alberto on 20 10 2014, 14:12:03
Every miranda restart, the file grows by 50-250kb.
I can confirm this here.

Another thing is handling of avatar files. At the moment Miranda will always create a folder AvatarCache\Tox in my database folder. So support for folders plugin would be nice.
Title: Re: Tox
Post by: Vulpix on 10 11 2014, 10:22:49
Development of Tox plugin is on hold and the latest versions are somewhat unusable. Awaiting Unsane's return and/or someone else's effort into the plugin.
Title: Re: Tox
Post by: Vulpix on 22 11 2014, 11:25:45
Vulpix-sponsored bounty:

$500 if you fix tox plugin to work properly:

- latest tox binaries
- everything has to work - filetransfers (this means they work regardless of filesize, even on big files), regular chat (+ /me actions), adding/removing contacts, proper storing in tox savefile, avatars.

$800 if it doesn't take longer than 2 months.

$100 up-front if you at least make the latest plugin not corrupt the savefile (bloats/grows everytime you restart miranda).

I am willing to betatest and bug-check, I am a heavy miranda tox user.

Payment via paypal.

I know you guys don't accept donations, so I'm putting up a bounty. I love miranda and I love tox, and currently it's just not working at all with the latest versions.
Title: Re: Tox
Post by: calabar on 31 12 2014, 15:15:25
Tox is very promising and I hope that the protocol will be released soon as stable.
Here I read that at the moment the development has been stopped, is there any news about the resumption of work?
Title: Re: Tox
Post by: watcher on 05 01 2015, 10:17:11
Binaries updated to r11730 (http://trac.miranda-ng.org/changeset/11730). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: Vulpix on 05 01 2015, 10:20:10
I tested/used this on x86 / x64 miranda and I can confirm that this no longer corrupts the tox profile. Rejoice!

What was broken is still broken though (avatars / file transfers / sending messages fast / sending messages while transferring files), but this is at least using the latest tox dll. I noticed that I was not able to see some people online sometimes with the old tox dll, but the new one is fine. Very strange.

I'll wait until another update is pushed to tox before I re-activate the tox progression sticky again, but this is pretty good!


Also:

Vulpix-sponsored bounty:

$500 if you fix tox plugin to work properly:

- latest tox binaries
- everything has to work - filetransfers (this means they work regardless of filesize, even on big files), regular chat (+ /me actions), adding/removing contacts, proper storing in tox savefile, avatars.

$800 if it doesn't take longer than 2 months.

$100 up-front if you at least make the latest plugin not corrupt the savefile (bloats/grows everytime you restart miranda).

I am willing to betatest and bug-check, I am a heavy miranda tox user.

Payment via paypal.

I know you guys don't accept donations, so I'm putting up a bounty. I love miranda and I love tox, and currently it's just not working at all with the latest versions.

I will stand by my word. Can someone tell Unsane, if he's interested? :P
Title: Re: Tox
Post by: watcher on 06 01 2015, 13:47:34
Binaries updated to r11778-11779 (http://trac.miranda-ng.org/changeset/11779). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 06 01 2015, 19:41:54
Binaries updated to r11781 (http://trac.miranda-ng.org/changeset/11781). Please update manually from attachments in the first post.
Title: Re: Tox
Post by: watcher on 07 01 2015, 21:50:25
Binaries updated to r11790 (http://trac.miranda-ng.org/changeset/11790). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 12 01 2015, 20:46:17
Binaries updated to r11845 (http://trac.miranda-ng.org/changeset/11845). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 13 01 2015, 10:40:54
A friend of mine had issues when updating to this latest tox. What we had to do was load his tox profile in utox, then close utox and then load that tox profile in miranda. That fixed the problem; otherwise miranda was saying (in netlog) "unable to load tox profile".

Additionally, multiple filetransfer at once resulted in mismatching md5 checksums; I'm now replicating the issue.

EDIT: Testing transfers shows that even to uTox, the transfer is terminated/cancelled midway (at seemingly random points).

EDIT2: Seems to be a tox issue as this happens with uTox->uTox transfer as well. The difference is however that uTox resumes from where it left off whereas Miranda gives up.

The updated toxcore however helps as my friend was previously unable to use the updated toxcore and stay online - and now he can! :)
Title: Re: Tox
Post by: Dimsok on 14 01 2015, 10:22:31
Doesn't work for me. Icon just blink once and i don't see if it tries to connect. Rolled down to the old
Title: Re: Tox
Post by: Vulpix on 14 01 2015, 20:45:21
That means your tox profile is corrupted. Load it in uTox and then close utox and put it back into miranda and it'll work.
Title: Re: Tox
Post by: Vulpix on 17 01 2015, 10:05:01
http://forum.miranda-ng.org/index.php?topic=2502 Current state of Tox protocol in miranda updated with latest state

Changelogs:

Filetransfers improved - everything but multiple filetransfers / resuming a filetransfer is working
Avatars fixed - You can set your own and see the contact's avatar without issues
Changing status message - You can set your own and see the contact's status message without issues
Title: Re: Tox
Post by: watcher on 18 01 2015, 22:57:14
Binaries updated to r11875 (http://trac.miranda-ng.org/changeset/11875). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 18 01 2015, 23:50:45
Hmm I see that support for resuming was added (and pausing). How do I do this with Miranda? There doesn't seem to be a pause button.
Title: Odp: Tox
Post by: unsane on 19 01 2015, 18:16:08
Pausing. If recipient pause(on client that support pause) the transmission, Miranda stops sending as long as the recipient does not resume reception.
Resuming. If the connection breaks during sending/receiving you can resume broken transfer after you (or your frend) will be reconnected.
Title: Re: Tox
Post by: watcher on 19 01 2015, 19:21:07
Binaries updated to r11876 (http://trac.miranda-ng.org/changeset/11876). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 19 01 2015, 20:25:51
Filetransfers are somewhat broken, wait for a fixed release, don't update to r11876, it crashes miranda on transfer. :) Unsane has the log, he'll look at it when he has time! :)
Title: Re: Tox
Post by: watcher on 20 01 2015, 00:27:33
Binaries updated to r11880 (http://trac.miranda-ng.org/changeset/11880). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 20 01 2015, 08:45:21
Filetransfers still broken with the latest build. Unsane has logs, will look at it when he has time again :)
Title: Re: Tox
Post by: watcher on 02 02 2015, 08:24:11
Binaries updated to r11977 (http://trac.miranda-ng.org/changeset/11977). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 02 02 2015, 08:54:04
File transfers over fast lines are still broken; the transfer goes too fast, then makes the protocol disconnect, and upon reconnecting, miranda is unable to resume correctly:

[9:47:27 0FAC] CToxProto::SendFileAsync: start sending file (0)
[9:48:00 1EC0] CToxProto::OnFileRequest: change file position from 38707443 to 17373312 of file (0)
[9:48:00 1EC0] CToxProto::OnFileRequest: resumption of sending at 17373312 of 64177790 of file (0)
[9:48:29 1EC0] CToxProto::OnFileRequest: change file position from 64177790 to 28253568 of file (0)
[9:48:29 1EC0] CToxProto::OnFileRequest: resumption of sending at 28253568 of 64177790 of file (0)

The resulting file should be 61.2MB, but it ends up being 26.2MB and the final transfer progress bar never disappears.

The "disconnect on sending" happens with uTox as well, but uTox is able to resume correctly.
Title: Re: Tox
Post by: Vulpix on 04 02 2015, 12:31:17
Filetransfers seem to be a lot better now with r11998; some more fixes for chat and so that transfers don't constantly kill connection, but tox is getting a lot better now.

Thanks Unsane/Watcher~!
Title: Re: Tox
Post by: watcher on 04 02 2015, 19:40:00
Binaries updated to r12003 (http://trac.miranda-ng.org/changeset/12003). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 09 02 2015, 19:33:34
Binaries updated to r12071 (http://trac.miranda-ng.org/changeset/12071). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 10 02 2015, 13:47:57
Latest build:

- Sending of single file _vastly_ improved; chat not impaired by file sending + sending is pretty fast.
- Sending of multiple files at once can sometimes cause some files to be declined. Logs have been shared with Unsane.

Generic remark

- it is not possible to utilize the 64bit aspect of tox; support for files bigger than 2GB is not in; unsane knows about this and will try to look at it soon.

Otherwise, really good job on improving that file send :3 it's almost ready now!
Title: Re: Tox
Post by: watcher on 10 02 2015, 19:53:18
Binaries updated to r12083 (http://trac.miranda-ng.org/changeset/12083). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 12 02 2015, 18:03:25
- The 64bit-ness of the file sending was fixed, it is now possible to send very large files (tested with a 4.1GB file, transferred over 20Mbit line at 1.5MB/s without issues).  :THUMBS UP:

Not much remains to be fixed in the protocol. When I have time I'll quickly check the problem with overwriting/resuming on already-present files.

Furthermore, irungentoo (toxcore maintainer) looked briefly at miranda code for the transfers and said it will help him fix toxcore issue with the filetransfers killing toxcore :D so that could also happen :)


- CRASH (still present, not new).

Reproduction scenario:

1) send a file (download dialog appears on miranda recipient side)
2) cancel the file send BEFORE the transfer starts on sender side
3) accept the file @ recipient side
4) Miranda crashes.

Crashlog:

Sorry but you are not allowed to view spoiler contents.

Title: Re: Tox
Post by: unsane on 13 02 2015, 20:19:21
- CRASH (still present, not new).
Reproduction scenario:

1) send a file (download dialog appears on miranda recipient side)
2) cancel the file send BEFORE the transfer starts on sender side
3) accept the file @ recipient side
4) Miranda crashes.

Should be fixed in r12102 (http://trac.miranda-ng.org/changeset/12102)
Title: Re: Tox
Post by: Vulpix on 14 02 2015, 12:00:53
Indeed, the transfer window disappears. This could however be somewhat confusing as there is no evidence of what happened. Is it possible to instead make the dialogue button (to accept the transfer) gray and say "Transfer cancelled by sender" or something like that? :o

Either way, thanks for the quick fix :)
Title: Re: Tox
Post by: Robyer on 14 02 2015, 13:44:18
Or immediatelly after accepting it in Miranda show error that sender canceled it. I think graying out isn't possible.
Title: Re: Tox
Post by: Vulpix on 14 02 2015, 20:52:27
Actually, now I have a different problem - any transfer gets denied as soon as I click start transfer on the recipient side :D

And then my miranda crashed O_o (windows freeze, no crashlog).
Title: Re: Tox
Post by: unsane on 14 02 2015, 21:44:28
It should be fixed in next nightly build i hope.
Title: Re: Tox
Post by: watcher on 15 02 2015, 20:19:42
Binaries updated to r12132 (http://trac.miranda-ng.org/changeset/12132). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 16 02 2015, 14:18:11
After updating to the latest build, I've started getting disconnected. Other protocols stay up and my connection is stable.

What has changed? I noticed some major change to how tox nodes work and also a new "tox node" option section in the "Network" menu.

EDIT:

+ another strange issue. I started sending one file to 2 people. Very small file, ~54kb. Both of them accepted it (not at the same time though), and both got no file being sent.

Then I cancelled the second transfer, which caused the first transfer to show "file transfer denied" in the miranda transfer window.

Then I re-sent the file to both, and both were able to accept it and save it without problems. What happened there?

The log looked like this:

17:16:49 18D4] CToxProto::OnFileRequest: start the transfer of file (0) <--- starting the file transfer to contact 1
[17:17:07 18D4] CToxProto::OnFileRequest: start the transfer of file (0) <--- starting the file transfer to contact 2
[17:17:27 18D4] CToxProto::OnFileRequest: start the transfer of file (0) <--- contact 1 complains no file transferred. Cancelling transfer for contact 2. Not shown anywhere in the log?! Starting transfer for contact 2
[17:17:27 18D4] CToxProto::SendFileAsync: finish the transfer of file (0) <--- contact 2 gets the file instantly
[17:17:37 18D4] CToxProto::OnFileRequest: start the transfer of file (1) <--- starting transfer for contact 1
[17:17:37 18D4] CToxProto::SendFileAsync: finish the transfer of file (1) <--- contact 1 gets the file instantly


Title: Re: Tox
Post by: watcher on 16 02 2015, 22:57:53
Binaries updated to r12152 (http://trac.miranda-ng.org/changeset/12152). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 16 02 2015, 23:00:41
Tox nodes autoexec file - http://svn.miranda-ng.org/main/trunk/protocols/Tox/docs/
Title: Re: Tox
Post by: Vulpix on 16 02 2015, 23:10:43
Can you please describe what the autoexec is and why is it needed? I can see it has a list of all the nodes but I don't understand why that's necessary; it used to be hardcoded in toxcore, right?
Title: Re: Tox
Post by: watcher on 17 02 2015, 07:36:59
Binaries updated to r12157 (http://trac.miranda-ng.org/changeset/12157). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: unsane on 17 02 2015, 08:09:59
In r12157 fixed bug when old profiles are not loaded by plugin, but loaded by uTox.

Can you please describe what the autoexec is and why is it needed? I can see it has a list of all the nodes but I don't understand why that's necessary; it used to be hardcoded in toxcore, right?
Two node is hardcoded and uses when node list is empty. That's enough to login in most cases.
But in some cases you may need other nodes (on 443 port for example), or hardcoded nodes are not available. Now you can add node manually.
Autoexec contains list of all official nodes. If you add them all, may be you login faster, or your friends will appear online faster or may be not  ;D
Title: Re: Tox
Post by: unsane on 17 02 2015, 21:26:42
+ another strange issue. I started sending one file to 2 people. Very small file, ~54kb. Both of them accepted it (not at the same time though), and both got no file being sent.
Fixed in r12171.
Title: Re: Tox
Post by: watcher on 17 02 2015, 23:01:49
Binaries updated to r12172 (http://trac.miranda-ng.org/changeset/12172). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re:Tox
Post by: Vulpix on 17 02 2015, 23:22:23
After updating to the latest version, the netlog is spammed with:

Sorry but you are not allowed to view spoiler contents.



It's growing very rapidly. Is this supposed to be the case?
Title: Re: Tox
Post by: unsane on 18 02 2015, 05:29:49
Ooups, my bet. Will be fixed in next build.
Title: Re: Tox
Post by: Vulpix on 18 02 2015, 07:57:00
I got disconnected again,

This is the log prior to DC. As you can see, I get lots of the "restored connection with DHT" every second, but then nothing for about 5 seconds and after that I get disconnected:

[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:43 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:44 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:45 1E2C] CToxProto::CheckConnection: restored connection with DHT
[2:43:50 1E2C] CToxProto::CheckConnection: disconnected from DHT

[2:43:50 1E2C] CToxProto::SetStatus: changing status from 40073 to 40071
[2:43:50 1E2C] CToxProto::PollingThread: leaving
Title: Re: Tox
Post by: watcher on 18 02 2015, 08:03:25
Binaries updated to r12178 (http://trac.miranda-ng.org/changeset/12178). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: unsane on 18 02 2015, 08:08:30
hmm. somthing was lock the poll thread.
did you do anything before dc (messaging, transfers, or smth else)?
Title: Re: Tox
Post by: Vulpix on 18 02 2015, 08:10:40
Nope, it was 2:43am :D I was sleeping, I only noticed I DCd in the morning when I turned on my monitor.
Title: Re: Tox
Post by: unsane on 18 02 2015, 19:26:55
Experement (http://trac.miranda-ng.org/changeset/12183) with disconnect suppression in next build.
Title: Re: Tox
Post by: watcher on 18 02 2015, 20:50:39
Binaries updated to r12188 (http://trac.miranda-ng.org/changeset/12188). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 19 02 2015, 07:11:41
Binaries updated to r12192 (http://trac.miranda-ng.org/changeset/12192). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 19 02 2015, 08:57:30
Alrighty!

Out of curiosity, why is the "Tox nodes" option in the "Network" submenu, instead of being a tab on the "Tox" network menu? It makes little sense I think. Additionally, the "Tox nodes" submenu should have a "remove" button, if it has an "add" button. I know you can click the cross next to every entry but it feels counterintuitive.

Additionally, what is going on in the log below? Why the "double" bootstrap?

Sorry but you are not allowed to view spoiler contents.


Title: Re: Tox
Post by: Mataes on 19 02 2015, 09:15:44
1) coz list of nodes one for all tox accounts
2) diagree with you. for what we need button if we already have way to delete node?
Title: Re: Tox
Post by: unsane on 19 02 2015, 09:33:29
Additionally, what is going on in the log below? Why the "double" bootstrap?
Danger, wild logs :D I'll fix "lost connection" duplication later.
I don't now how to avoid disconnect. It's just experiment.
When tox considers that it is disconnected from DHT it tries to rebootstrap DHT.
If you will get dc then the experiment will be failed.
Title: Re: Tox
Post by: Vulpix on 19 02 2015, 09:59:23
1) coz list of nodes one for all tox accounts
2) diagree with you. for what we need button if we already have way to delete node?

1) Ohh. Fair enough. I only use one so I didn't think of that.
2) I guess for completeness' sake. It feels weird to only have a button for "add" because when you highlight a node you expect to be able to hit DEL or click "remove" to delete it. It's just user/usability tweak, quality of life thing. Not game-breaking, hehe.

@unsane, so far, no DC :D
Title: Re: Tox
Post by: Mataes on 19 02 2015, 10:01:14
about delete button on keyboard i agree. i ll add this function
Title: Re: Tox
Post by: watcher on 19 02 2015, 22:10:05
Binaries updated to r12202 (http://trac.miranda-ng.org/changeset/12202). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 07:00:23
Updated, but after update, all of the tox nodes in the GUI are gone. It also failed to connect 1x before connecting:

[7:50:09 1ADC] CToxProto::PollingThread: entering
[7:50:09 1ADC] CToxProto::InitToxCore: initializing tox core
[7:50:09 1ADC] CToxProto::InitToxCore: loading tox profile
[7:50:09 1ADC] CToxProto::InitToxCore: tox profile load successfully
[7:50:09 1ADC] CToxProto::BootstrapDht: bootstraping DHT
[7:50:19 1ADC] CToxProto::SetStatus: changing status from 202 to 40071
[7:50:19 1ADC] CToxProto::PollingThread: failed to connect to DHT
[7:50:19 1ADC] CToxProto::PollingThread: leaving
[7:50:30 0F60] CToxProto::SetStatus: changing status from 40071 to 40072
[7:50:30 1AEC] CToxProto::PollingThread: entering
[7:50:30 1AEC] CToxProto::InitToxCore: initializing tox core
[7:50:30 1AEC] CToxProto::InitToxCore: loading tox profile
[7:50:30 1AEC] CToxProto::InitToxCore: tox profile load successfully
[7:50:30 1AEC] CToxProto::BootstrapDht: bootstraping DHT
[7:50:40 1AEC] CToxProto::PollingThread: successfuly connected to DHT
[7:50:40 1AEC] CToxProto::PollingThread: changing status from 1 to 40072

but it worked ever since, so maybe it was just some temporary error.

Also I see the log is fixed since there is no spam of "lost connection" like before.
Title: Re: Tox
Post by: unsane on 20 02 2015, 07:37:39
all of the tox nodes in the GUI are gone
It's because key TOX\NodeCount was renamed into TOX\Node_Count.
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 08:14:37
I see... is there something I should do in miranda DB so I can see all the nodes I've added?

Also, I asked irungentoo about nodes and he said it literally doesn't matter which node you connect to to bootstrap, in the sense that "as long as you can connect, it can be the US node or node from NL and the connect bootstrap speed will be the same".
Title: Re: Tox
Post by: Wishmaster on 20 02 2015, 10:55:36
Vulpix, you can remane that key as unsane said.

unsane, I wonder why that key is needed at all? Can't you just loop through all settings until you find one that doesn't exist?

Smth like that:
Code: [Select]
for (lvi.iItem = 0; ; lvi.iItem++)
{
mir_snprintf(setting, SIZEOF(setting), TOX_SETTINGS_NODE_IPV4, lvi.iItem);
                                char *szIPv4 = db_get_sa(NULL, MODULE, setting);
                                if (szIPv4 == NULL) break; // break if setting doesn't exist

mir_snprintf(setting, SIZEOF(setting), TOX_SETTINGS_NODE_IPV6, lvi.iItem);
                                char *szIPv6 = db_get_sa(NULL, MODULE, setting);
                                if (szIPv6 == NULL) {
                                       mir_free(szIPv4);
                                       break; // break if setting doesn't exist
                                 }

mir_snprintf(setting, SIZEOF(setting), TOX_SETTINGS_NODE_PKEY, lvi.iItem);
                                char *szKey = db_get_sa(NULL, MODULE, setting);
                                if (szKey == NULL) {
                                       mir_free(szIPv4);
                                       mir_free(szIPv6);
                                       break; // break if setting doesn't exist
                                 }

lvi.iImage = -1;
lvi.mask = LVIF_TEXT | LVIF_IMAGE;

lvi.iSubItem = 0;
lvi.pszText = szIPv4;
SendMessage(hwndList, LVM_INSERTITEMA, 0, (LPARAM)&lvi);

lvi.iSubItem = 1;
lvi.pszText = szIPv6;
SendMessage(hwndList, LVM_SETITEMA, 0, (LPARAM)&lvi);

mir_snprintf(setting, SIZEOF(setting), TOX_SETTINGS_NODE_PORT, lvi.iItem);
int port = db_get_w(NULL, MODULE, setting, 0);
if (port > 0)
{
char portNum[10];
itoa(port, portNum, 10);
lvi.pszText = mir_strdup(portNum);
}
lvi.iSubItem = 2;
SendMessage(hwndList, LVM_SETITEMA, 0, (LPARAM)&lvi);

lvi.iSubItem = 3;
lvi.pszText = szKey;
SendMessage(hwndList, LVM_SETITEMA, 0, (LPARAM)&lvi);

lvi.mask = LVIF_IMAGE;
lvi.iSubItem = 4;
lvi.iImage = 0;
ListView_SetItem(hwndList, &lvi);

lvi.iSubItem = 5;
lvi.iImage = 1;
ListView_SetItem(hwndList, &lvi);
}
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 11:00:05
Wishmaster - Thanks! That helped.

My friend had another tox DC (other protocols were just fine and he was online at the time. Not messaging or sending anything; tox just went offline):


[9:16:45 1488] CToxProto::PollingThread: successfuly connected to DHT
[9:16:45 1488] CToxProto::PollingThread: changing status from 1 to 40072
[12:23:07 1488] CToxProto::CheckConnection: lost connection with DHT
[12:23:07 1488] CToxProto::BootstrapDht: bootstraping DHT
[12:23:11 1488] CToxProto::CheckConnection: disconnected from DHT
[12:23:11 1488] CToxProto::SetStatus: changing status from 40072 to 40071
[12:23:11 1488] CToxProto::PollingThread: leaving

What happened there?
Title: Re: Tox
Post by: unsane on 20 02 2015, 12:48:56
Wishmaster, good idea. it will be implemented in next build.

Vulpix, Did you have nodes in node list?
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 13:09:40
unsane - Well, yes, but they were not showing in the GUI (I have not modded his db yet). It's my friend's miranda. We also only left two nodes in the node list. Is it required to keep more nodes in the node list?
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 17:08:49
I'm a little confused on what's happening with the plugin right now, hehe.

If I change NodeCount to Node_Count, then I see all the nodes, except... (and I think this is because the numbering changed from 1 to 0 or something?) one of the nodes remains stuck in the DB. I've deleted it.

If you delete all the nodes, Tox still connects. Which nodes is it using? Some hardcoded ones? Which are those? Do the settings from the node list have any effect right now?

Furthermore, the "tox.ini" file, how is it being loaded? My friend put it in the plugins folder but got no nodes into the db from it.

:o looks a bit mixed up right now.
Title: Re: Tox
Post by: Mataes on 20 02 2015, 17:52:29
there are 2 ways of loading nodes: from db and from ini. They both work. tox.ini should be in Plugins folder
Title: Re: Tox
Post by: unsane on 20 02 2015, 17:58:42
I'm a little confused on what's happening with the plugin right now, hehe.
It's under construction right now. But as Mataes said both variants are working.
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 18:07:37
there are 2 ways of loading nodes: from db and from ini. They both work. tox.ini should be in Plugins folder

The tox.ini in Plugins folder is not working for me. I just tried it; nothing is loaded. I checked the database to make sure and DB is empty too.

EDIT:
Wait I think I'm misunderstanding. Loading nodes from the ini doesn't actually put them in the tox nodes options section (i.e. they are not displayed there). Right? It just uses them to connect, that's all. If that is so, then it probably works, but how do I know it does if I can't see any log or anything that indicates the nodes have been loaded?
Title: Re: Tox
Post by: Mataes on 20 02 2015, 18:32:50

Yes plugin don't add nodes from ini to db.you don't need know what nodes plugin use. For you main thing: it works.

Title: Re: Tox
Post by: Wishmaster on 20 02 2015, 18:48:28
Yes plugin don't add nodes from ini to db.
Well, why not? It might make sense to save them to use them later after ini file has been deleted?
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 18:59:43
The reason I use miranda and not some stupid skype etc ... is because I hate how those applications think they "know better". Maybe so; but I like to know what's going on underneath. Those applications are all like - no changelogs, no info, it works, so accept it!

If it's not super difficult to do, would it be possible to at least display the nodes that are currently loaded from the INI, even if you don't plan on storing them in the DB?
Title: Re: Tox
Post by: Mataes on 20 02 2015, 19:03:44
for what? this information useless for you. Actually you don't know what node uses now. Storing nodes in ini file is better for managering.
in db stores your personal nodes and they uses first
Title: Re: Tox
Post by: Mataes on 20 02 2015, 19:05:56
You can't use this information and take benefit from it
Title: Re: Tox
Post by: Vulpix on 20 02 2015, 19:11:00
I suppose the idea was to make it better to debug if I'm getting disconnected. At least put it in log that node X was used to bootstrap from or something?

But if it's too much trouble then forget it.
Title: Re: Tox
Post by: Mataes on 20 02 2015, 19:11:55
no, this function created not for you :)
Title: Re: Tox
Post by: watcher on 21 02 2015, 19:41:08
Binaries updated to r12226 (http://trac.miranda-ng.org/changeset/12226).Tox.ini with additional nodes is now supplied with plugin archive, please unpack it to Plugins folder with Tox.dll. Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox
Post by: watcher on 22 02 2015, 08:44:03
Binaries updated to r12253 (http://trac.miranda-ng.org/changeset/12253). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 01 03 2015, 12:31:49
Binaries updated to r12281 (http://trac.miranda-ng.org/changeset/12281). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 03 03 2015, 20:44:07
Binaries updated to r12308 (http://trac.miranda-ng.org/changeset/12308). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 05 03 2015, 20:05:16
Binaries updated to r12331-13341 (http://trac.miranda-ng.org/changeset/12331). Please update manually from attachments in the first post. Please backup Tox profile before updating to this revision! It may become corrupted!
Title: Re: Tox
Post by: watcher on 05 03 2015, 20:43:59
Tox now will not work without tox.ini next to tox.dll or nodes, added to database. So make sure that you unpack provided tox.ini when you update plugin!
Title: Re: Tox
Post by: Raileath on 08 03 2015, 07:25:38
Hello, internets! I noticed a crash on Windows XP SP3 when the plugin tries to connect to Tox. It does work in Windows 7, but my main computer is still XP so this is a fair bother for me. If anyone would like to look into how to fix it, I would very much appreciate it! Quoted below is the crash report, in case that will help any.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox
Post by: watcher on 08 03 2015, 07:58:34
Quote
Miranda NG Version: 0.95.3 build #11706

First of all - you should use this plugin with nightly builds only, just cause one day it might crash your Miranda, Miranda NG is compatible with plugins within one build (not sure it will solve your XP crash problem though).

Latest binaries can be obtained here. (for use with nightly builds only).
Title: Re: Tox
Post by: Robyer on 08 03 2015, 08:35:06
It's crash inside tox library, not this plugin. Does it work for you with other Tox client (e.g. uTox)?
Title: Re: Tox
Post by: watcher on 08 03 2015, 08:56:09
Robyer, it's not the first time that toxcore crashes on XP, it would be interesting to catch it with a longer stack.
Title: Re: Tox
Post by: Raileath on 08 03 2015, 16:33:45
uTox seems to run just fine, so at the very least there is some version of the Tox library that runs on XP. I am using the latest dev build available on the site, is there somewhere else to look for nightlies?
Title: Re: Tox
Post by: Vulpix on 08 03 2015, 17:59:27
uTox seems to run just fine, so at the very least there is some version of the Tox library that runs on XP. I am using the latest dev build available on the site, is there somewhere else to look for nightlies?

The best (or rather easiest) way to ensure your miranda is always up to date is to use the pluginupdater plugin and set it up like this:
(http://i.imgur.com/c34XOst.png)
Title: Re: Tox
Post by: Robyer on 08 03 2015, 20:21:17
The best (or rather easiest) way to ensure your miranda is always up to date is to use the pluginupdater plugin and set it up like this:

Not for Tox though, as it's still in alpha stage and available only for manual download (without plugin updater).

But probably unsane need to answer Raileath about used tox library in plugin :)
Title: Re: Tox
Post by: Vulpix on 08 03 2015, 23:56:27
Well yeah, hehe. I meant just the core + other plugins, to make sure that the miranda itself is nightly.

Post Merge: 10 03 2015, 15:10:37
So I got myself a windows XP virtual machine and indeed, tox (on fully updated miranda) won't log in. I.e. it starts and works fine as long as you keep tox offline. The moment you try logging in, you get this:

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 13 03 2015, 09:02:31
As a sidenote, today, the bounty for Tox has been paid

I hope that support for Tox will remain strong though :P it's an awesome protocol.

Vulpix-sponsored bounty:

$500 if you fix tox plugin to work properly:

- latest tox binaries
- everything has to work - filetransfers (this means they work regardless of filesize, even on big files), regular chat (+ /me actions), adding/removing contacts, proper storing in tox savefile, avatars.

$800 if it doesn't take longer than 2 months.

$100 up-front if you at least make the latest plugin not corrupt the savefile (bloats/grows everytime you restart miranda).

I am willing to betatest and bug-check, I am a heavy miranda tox user.

Payment via paypal.

I know you guys don't accept donations, so I'm putting up a bounty. I love miranda and I love tox, and currently it's just not working at all with the latest versions.
Title: Re: Tox protocol
Post by: Alberto on 13 03 2015, 14:03:28
Good to know there are still people who keep their word. :)
Title: Re: Tox protocol
Post by: Vulpix on 08 04 2015, 14:35:04
BIG CHANGES INCOMING:

Toxcore is switching to a so-called "new api"
(something that has been in the works for quite some time, but has been finalized recently and most of the clients (utox/qtox) are starting to migrate over. This new api was made by the devs of toxcore in an attempt to unify the way things are coded for toxcore and make further development more structured.

Communication of an old toxcore and new toxcore causes major disruption to the chat, so for example messages sent from old toxcore to the new toxcore will have weird symbols in them, and you will not receive a "message sent successfully" echo. Likewise, messages sent from the new toxcore to the old toxcore will actually have missing characters. Old toxcore will also attempt to download a random file from the new toxcore - but this file doesn't exist, it's just an issue caused by the interoperability.

Unsane is currently working (and has been working for a while now - thanks!) on the new api migration, but expect random bugs and issues to occur. As always, make a backup of your tox profile before you do anything.

For now, I some of my linux-using friends who use uTox are already reporting that it has been updated to the latest version which includes the new api (version 0.2.p). Windows version is still using 0.2.o (old toxcore), unless you download the nightly build.

tl;dr:

- new internal workings of toxcore
- miranda plugin must be reworked
- once done no real difference for end-user
- until done, talking inbetween old and new toxcore will be almost impossible

I'm mentioning this so that people who use tox aren't suddenly cut from their friends. Best spread the word to make sure they know, or have your tox profile at the ready to copy it to utox with new toxcore until miranda's implementation gets updated, just so you can talk to people for the time being :)


Edit: Tox plugin for miranda has been reworked; we are simply currently waiting for the official switch to new api; it must be done by people @toxcore (irungentoo on github). Expected switch is end of April.
Title: Re: Tox protocol
Post by: Vulpix on 25 04 2015, 15:04:09
qTox has been ported to new api (which was the last thing hindering the migration to new api for all of the other clients). Testing is currently underway and if all goes well, it will be merged to master on Monday. This means that tox will officially migrate to new api on Monday. Remember to update your plugins folks! :)
Title: Re: Tox protocol
Post by: Vulpix on 26 04 2015, 22:17:44
New api released for utox,qtox and everything. Y'all can happily update from the stickied post above! :D remember to tell your friends to update as well.




Everything below this line (i.e. new posts) must be on the new tox api!
Title: Re: Tox protocol
Post by: Vulpix on 27 04 2015, 18:40:52
Testing:

1) File transfers are broken; sending a file causes the recipient to receive it but it shows for sender as "failed", furthermore miranda tries to retransfer it all the time:

Sorry but you are not allowed to view spoiler contents.


2) Avatars aren't being sent. Cached avatars will be shown, but no new ones. When a contact changes avatar, old avatar (if cached) remains visible to the other person.


Title: Odp: Tox protocol
Post by: BantonioAnderas on 03 05 2015, 08:58:29
My friend showed me a screenshot. When I'm getting online miranda is trying to send 4GB file for him ;D
(https://i.imgur.com/SNWvIWB.png)
I'm using Miranda x86 and the newest tox plugin
Title: Re: Tox protocol
Post by: Vulpix on 03 05 2015, 09:33:10
Tell your friend to update to the latest qtox, he is using the old version with old api which causes these issues.
Title: Re: Tox protocol
Post by: Vulpix on 05 05 2015, 12:28:49
Tox crashed my miranda just now:

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 06 05 2015, 06:24:20
Another crash just now:

Sorry but you are not allowed to view spoiler contents.


And netlog:

Sorry but you are not allowed to view spoiler contents.


Title: Re: Tox protocol
Post by: Vulpix on 06 05 2015, 21:54:14
Thank to Unsane for the quick hotfix! r13472 (http://trac.miranda-ng.org/changeset/13472/)

Miranda no longer crashes, and also you can now receive new avatars from users. Setting own avatar doesn't work (or rather it doesn't show yet), I tell a lie, it's working, but only miranda-to-miranda. Miranda-to-utox doesn't work. They cannot see your avatar. But you can see theirs and no crashes.

State of tox updated. @ http://forum.miranda-ng.org/index.php?topic=2502.msg6093
Title: Re: Tox protocol
Post by: Vulpix on 12 05 2015, 08:15:04
Filetransfers:

When miranda is RECEIVING:
Everything seems to work. You see a progress bar, it is possible to queue up multiple files. Works for miranda->miranda and utox->miranda.

When miranda is SENDING:
Receiving side sees a progress bar like normal and will generally receive the file just fine.
Sending side sees "request sent, waiting for acceptance" during transfer; no progress bar. At the end, sending side sees "file transfer failed", but the receiving side has the complete file.

Title: Re: Tox protocol
Post by: Vulpix on 12 05 2015, 19:14:07
Just had a miranda crash due to tox. Tox went offline while I was chatting with a friend and about 5 seconds later, miranda crashed.

Netlog:
Sorry but you are not allowed to view spoiler contents.


Stack trace:
Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: watcher on 15 05 2015, 21:20:35
Significant update - http://trac.miranda-ng.org/changeset/13610
Title: Re: Tox protocol
Post by: Vulpix on 15 05 2015, 22:25:07
Retested, avatars work, file transfers work! Great work to unsane and thanks to watcher for compiling and helping me test it!  :THUMBS UP:
Title: Re: Tox protocol
Post by: watcher on 15 05 2015, 22:48:07
Protocol was added to PluginUpdater, so no need to update manually anymore.
Title: Re: Tox protocol
Post by: EagleXK on 24 05 2015, 22:41:08
Creahed when trying to select Tox protocol (just installed, no account created)

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: watcher on 25 05 2015, 06:19:27
Code: [Select]
Tox.dll v.0.11.1.6 [23 May 2015 23:59:53] - Tox protocol
Don't install it on stable version that 1 month older than plugin - then it won't crash. Read here (http://wiki.miranda-ng.org/index.php?title=Main_Page) the message on red background.
Title: Re: Tox protocol
Post by: lx on 25 05 2015, 07:54:14
After recent updates can`t  set online.

Code: [Select]
[spoiler=VersionInfo][quote]CPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz [Intel64 Family 6 Model 69 Stepping 1] [DEP Enabled] [4 CPUs]
Installed RAM: 7633 MBytes
Operating System: Microsoft Windows 8.1 Professional Edition, 64-bit (build 9600)
Internet Explorer: 9.11.9600.17801 (build 99600)
Administrator privileges: Yes
OS Languages: (UI | Locale (User/System)) : Russian/Russian | Russian/Russian
Free disk space on Miranda partition: 34318 MBytes

Miranda NG Version: 0.95.5 alpha build #13823 x64
Build time: 25 May 2015 5:42:16
Profile: C:\Users\lx\Documents\Miranda NG\Profiles\lx\lx.dat
Profile size: 589824 Bytes
Profile creation date: 18 May 2015 11:01:08
Language pack: Russian (RU) [0419]
Service Mode: No

[b]Active Plugins (13):[/b]
  AdvaImg.dll v.[b]0.11.0.2[/b] [25 May 2015 5:43:22] - Miranda image services
  AVS.dll v.[b]0.95.3.4[/b] [25 May 2015 5:42:26] - Avatar service
  Clist_modern.dll v.[b]0.9.1.3[/b] [24 May 2015 14:11:34] - Modern contact list
  CrashDumper.dll v.[b]0.0.5.2[/b] [24 May 2015 14:12:46] - Crash dumper
  Dbx_mmap.dll v.[b]0.95.3.1[/b] [25 May 2015 5:42:30] - Miranda NG mmap database driver
  ICQ.dll v.[b]0.11.3.4[/b] [25 May 2015 5:43:10] - IcqOscarJ protocol
  Import.dll v.[b]0.95.4.2[/b] [25 May 2015 5:42:26] - Import contacts and messages
  IRC.dll v.[b]0.11.0.3[/b] [24 May 2015 14:08:36] - IRC protocol
  Jabber.dll v.[b]0.11.0.4[/b] [24 May 2015 14:09:18] - Jabber protocol
  PluginUpdater.dll v.[b]0.1.2.4[/b] [24 May 2015 14:13:16] - Plugin updater
  Scriver.dll v.[b]2.12.1.2[/b] [25 May 2015 5:42:36] - Scriver
  TopToolBar.dll v.[b]0.8.0.4[/b] [24 May 2015 14:11:14] - TopToolBar
  Tox.dll v.[b]0.11.1.6[/b] [24 May 2015 14:17:32] - Tox protocol

[b]Unloadable Plugins (2):[/b]
  DbChecker.dll v.[b]0.0.0.0[/b] [25 May 2015 5:46:38] - <unknown>

  libtox.dll v.[b]0.0.0.0[/b] [19 May 2015 11:18:25] - <unknown>
    This dll is not a Miranda plugin and should be removed from plugins directory


[b]Protocols and Accounts:[/b]
-------------------------------------------------------------------------------
ICQ                      2 - Enabled 0 - Disabled  Loaded
IRC                      1 - Enabled 0 - Disabled  Loaded
JABBER                   0 - Enabled 1 - Disabled  Loaded
TOX                      1 - Enabled 0 - Disabled  Loaded
MetaContacts             1 - Enabled 0 - Disabled  Loaded

[b]Icon Packs:[/b]
-------------------------------------------------------------------------------
 Proto_ICQ.dll [25 May 2015 5:45:08]
 Proto_IRC.dll [24 May 2015 14:11:16]
 Proto_Jabber.dll [24 May 2015 14:11:16]
 Proto_MetaContacts.dll [25 May 2015 5:49:46]
 Proto_Tox.dll [24 May 2015 14:17:22]
 Toolbar_icons.dll [24 May 2015 14:11:18]
 xStatus_ICQ.dll [25 May 2015 5:43:30]
 xStatus_Jabber.dll [24 May 2015 14:09:28]
[/quote][/spoiler]
Title: Re: Tox protocol
Post by: Robyer on 25 05 2015, 08:04:26
lx, folders structure in download archives are prepared just for extraction into Miranda's root folder.

So, libtox.dll should be in Miranda's root folder, not in plugins folder.

If this won't help, then provide network log, as usual.
Title: Re: Tox protocol
Post by: lx on 25 05 2015, 08:29:10
Robyer, it has always been there)
But thanx for tip to look into the options, I turned on UDP and IP6 and somehow Tox took online status.
What is for logs - I have enabled it as described in wiki and reproduced error, but catalog c:\Users\lx\Documents\Miranda NG\Profiles\lx\Logs\ is empty.
Anyway, Tox plugin is working, many thanx!
Title: Re: Tox protocol
Post by: Vulpix on 25 05 2015, 10:36:17
Hello lx,

You are actually correct, I just tested it; tox is unable to connect in TCP-only mode right now (on miranda). @unsane
Title: Re: Tox protocol
Post by: Vulpix on 27 05 2015, 12:20:34
When transferring files to/from people with slower connection, miranda causes the other contact to disconnect and upon reconnection, it is unable to resume the file.

This makes sending/receiving files from people with slower/less reliable connections (=most of the world) almost impossible.

Would it be possible to re-implement the file resuming? More importantly, when I use uTox (v0.3.0) with my friend for the same file transfer, it is transferred without issues. The speed is very erratic but there are no disconnects or issues during the transfer. Miranda transfer fails after 10-40 seconds (randomly). Filesize was 6MB. Then I restarted my miranda and tried to get him to send me the file again, but it was impossible to get it. It always just never started.

My netlog:

[14:03:48 1E40] CToxProto::SetStatus: changing status from 40071 to 40072
[14:03:48 63BC] CToxProto::PollingThread: entering
[14:03:48 63BC] CToxProto::InitToxCore: initializing tox core
[14:03:48 63BC] CToxProto::InitToxCore: loading tox profile
[14:03:48 63BC] CToxProto::LoadToxProfile: loading tox profile
[14:03:48 63BC] CToxProto::LoadToxProfile: tox profile load successfully
[14:03:48 63BC] CToxProto::BootstrapNodes: bootstraping DHT
[14:03:55 63BC] CToxProto::TryConnect: successfuly connected to DHT
[14:03:55 63BC] CToxProto::TryConnect: changing status from 1 to 40072
[14:03:56 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:03:57 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:04:06 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:04:08 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:04:09 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:04:10 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:04:10 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:04:11 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:04:12 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:04:13 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:04:16 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:04:17 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:06:25 1E40] CToxProto::OnFileResume: start receiving file (65536) to (8)
[14:06:33 1E40] CToxProto::OnFileResume: start receiving file (65536) to (8)
[14:06:55 63BC] CToxProto::OnConnectionStatusChanged: sending ask to resume the transfer of file (65536)
[14:06:55 63BC] CToxProto::OnConnectionStatusChanged: failed to resume the transfer (3)
[14:06:56 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:06:57 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)
[14:07:18 1E40] CToxProto::OnFileResume: start receiving file (65536) to (8)
[14:07:18 1E40] CToxProto::OnFileResume: failed to start the transfer of file(65536) to (8): (3)
[14:07:44 63BC] CToxProto::OnFileRequest: start/resume the transfer of file (0)
[14:07:45 63BC] CToxProto::OnFileSendData: finised the transfer of file (0)

then he tried to send the screenshot:

[14:10:34 1E40] CToxProto::OnFileResume: start receiving file (65536) to (8)
[14:10:55 63BC] CToxProto::OnConnectionStatusChanged: sending ask to resume the transfer of file (65536)
[14:10:55 63BC] CToxProto::OnConnectionStatusChanged: failed to resume the transfer (3)


Friend is using uTox, his screen looked like this (attachment).

Thanks!



Title: Re: Tox protocol
Post by: Vulpix on 03 06 2015, 07:41:21
Robyer, it has always been there)
But thanx for tip to look into the options, I turned on UDP and IP6 and somehow Tox took online status.
What is for logs - I have enabled it as described in wiki and reproduced error, but catalog c:\Users\lx\Documents\Miranda NG\Profiles\lx\Logs\ is empty.
Anyway, Tox plugin is working, many thanx!

@lx
, the tcp-only mode is working now again.
Title: Re: Tox protocol
Post by: Vulpix on 04 06 2015, 21:38:39
Tox causes disconnection of the target of transfer. This is a toxcore issue and should be fixed in toxcore (happens even on uTox). However, utox is able to resume the transfer; miranda is not.

Below is the log from my attempt to send a file to a friend (34):


[23:25:59 0F24] CToxProto::OnSendFile: start sending file (0) to (24)
[23:26:47 341C] CToxProto::OnFileSendData: finised the transfer of file (0) to (24)
[23:29:53 0F24] CToxProto::OnSendFile: start sending file (0) to (34)
[23:30:47 341C] CToxProto::PauseOutgoingTransfers: sending ask to pause the transfer of file (0) to (34)
[23:30:47 341C] CToxProto::PauseOutgoingTransfers: failed to pause the transfer (0) to (34) cause(2)
[23:30:49 0F24] CToxProto::OnSendMessage: failed to send message (3)
[23:32:58 341C] CToxProto::OnFriendFile: incoming file (65536) from (24)
[23:33:03 0F24] CToxProto::OnFileResume: start receiving file (65536) from (24)
[23:33:05 341C] CToxProto::OnTransferCompleted: finised the transfer of file (65536) from (24)
[23:33:08 341C] CToxProto::OnFriendFile: incoming avatar (65536) from (34)
[23:33:08 341C] CToxProto::OnFileCancel: Transfer (65536) is canceled

After about 1MB of the file is sent, the friend disconnects. Comes back ~2 minutes later but the transfer shows up as "File transfer denied" and does not resume.
Title: Re: Tox protocol
Post by: Vulpix on 07 06 2015, 11:02:42
More strange logs - I have no idea what is happening in miranda during this time.

Entire log up for download as an attachment, too long to paste in.
Title: Re: Tox protocol
Post by: Vulpix on 18 06 2015, 10:36:04
File transfers are just broken and unreliable right now. Even small files <64 kB can get stuck, not sent, etc.

I.e.:

12:31:25 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:25 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:25 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:25 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:33 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:33 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:33 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:33 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:41 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:41 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:41 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:41 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:49 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:49 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:49 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:31:49 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:31:53 241C] CToxProto::OnSendFile: start sending file (0) to (0)
[12:32:05 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:05 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:32:05 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:05 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:32:09 241C] CToxProto::OnSendFile: start sending file (0) to (0)
[12:32:21 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:21 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:32:21 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:21 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:32:53 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:53 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:32:53 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:32:53 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:09 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:09 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:09 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:09 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:17 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:17 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:17 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:17 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:25 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:25 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:25 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:25 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:33 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:33 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:33 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:33 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:41 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:41 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
[12:33:41 39C0] CToxProto::OnFriendFile: incoming avatar (65536) from (0)
[12:33:41 39C0] CToxProto::OnFileCancel: Transfer (65536) is canceled
Title: Re: Tox protocol
Post by: Vulpix on 15 07 2015, 17:42:16
File transfers are working, however, sometimes (usually after being online for some time), the first time you try to transfer something, it won't work.

The recipient will see the prompt and will be able to start saving the file, but the file sending gets stuck on 1% and never finishes.

If you then try to cancel and resend the file again, it will not be possible due to file locks.

The transfer is from miranda to miranda, both always on latest dev version of miranda.

Below is the sender log for this:

18:11 -> I tried to send a file, but it got stuck at 1% and did nothing. So I didn't do anything, and I was just chatting with the contact.
19:37 -> I tried to send a file, no problem. Seems that something happened that timed out the transfer from what I can see in the log.

[18:11:01 2588] CToxProto::OnSendFile: start sending file (0) to (0)
[18:21:32 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[18:21:33 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[18:28:59 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[18:29:21 1E38] CToxProto::PauseOutgoingTransfers: sending ask to pause the transfer of file (0) to (2)
[18:29:21 1E38] CToxProto::PauseOutgoingTransfers: failed to pause the transfer (0) to (2) cause(2)
[18:29:22 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[18:29:25 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[18:29:25 1E38] CToxProto::OnFileSendData: file (0) is not completely transferred to (2)
[18:53:47 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[18:53:48 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[19:00:17 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[19:00:18 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[19:00:40 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[19:00:42 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[19:33:13 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[19:33:15 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[19:33:44 1E38] CToxProto::OnFriendFile: incoming avatar (65536) from (2)
[19:33:47 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (2)
[19:37:34 2588] CToxProto::OnSendFile: start sending file (0) to (0)
[19:38:05 1E38] CToxProto::OnFileSendData: finised the transfer of file (0) to (0)


This happens constantly and it's really annoying because miranda creates 0byte files in the recipient's miranda file download directory, and you cannot overwrite it, you have to use rename when you try to send something again, and then it still doesn't work sometimes.

Can provide more logs if required. Both using TCP-only mode.

Otherwise the plugin is okay.
Title: Re: Tox protocol
Post by: unsane on 15 07 2015, 21:15:31
Vulpix, it should be fixed at version 0.11.1.11  ::)
Title: Re: Tox protocol
Post by: Vulpix on 16 07 2015, 22:52:56
:D nice version number!

Anyway, it seems to be fixed, it didn't happen today! Thanks! I'll let you know if there is anything else.

Oh right.

Do you know what this means?


[0:51:01 1704] CToxProto::SetAwayMsg: failed to set status status message F (0)
[0:51:01 1704] CToxProto::SetAwayMsg: failed to set status status message F (0)
[0:51:07 1704] CToxProto::SetAwayMsg: failed to set status status message F (0)
[0:51:07 1704] CToxProto::SetStatus: changing status from 40072 to 40073
[0:51:08 1704] CToxProto::SetAwayMsg: failed to set status status message A (0)
[0:51:12 1704] CToxProto::SetAwayMsg: failed to set status status message A (0)
[0:51:12 1704] CToxProto::SetStatus: changing status from 40073 to 40072
[0:51:14 1704] CToxProto::SetAwayMsg: failed to set status status message F (0)


My statuses at that time were "Awaypix" and "Fivetail", so it's clearly that 'A' and 'F'. Maybe one of those encoding changes that happened with the miranda changes recently. Is something broken?
Title: Re: Tox protocol
Post by: Vulpix on 20 07 2015, 08:31:27
So it happened again today:

There is NOTHING useful in the log. At all.

Sender side only has this:
[10:23:04 27D8] CToxProto::OnSendFile: start sending file (0) to (0)


Recipient side:
[10:23:01 1044] CToxProto::OnFriendFile: incoming file (65536) from (0) <- me sending the file
[10:23:18 1398] CToxProto::OnFileResume: start receiving file (65536) from (0) <- my contact accepted it, it started, went to a progress bar but no progress has been filled
[10:23:48 1398] CToxProto::OnFileCancel: Transfer (65536) is canceled <- he cancelled the transfer when he realized that it's the bug again.


I am using tcp-only mode, my contact is using udp as well. We both have latest dev version of miranda as always.

This only happens after I (sender) have been online for a very long time (since yesterday). Is it possible that something in there times out or whatever?

It's very frustrating :<
Title: Re: Tox protocol
Post by: unsane on 06 08 2015, 07:55:59
Irungentoo (the main developer of Toxcore) started fundraising for tox development.
If someone interesting https://www.indiegogo.com/projects/toxcore-development.
Title: Re: Tox protocol
Post by: Vulpix on 12 08 2015, 07:44:00
Right-clicking a contact and selecting "read online message" or "copy online message" shows "failed to read online message". It's a bit annoying if I want to copy a link someone uses as their status; I always have to re-type it.
Title: Re: Tox protocol
Post by: unsane on 12 08 2015, 18:57:22
Vulpix, try r14926 (http://trac.miranda-ng.org/changeset/14926)
Title: Re: Tox protocol
Post by: Vulpix on 13 08 2015, 07:14:22
@unsane, thanks! That worked. I also see you put in a new toxcore and changed some stuff regarding transfers. I was having some transfer issues before where a transfer would just never start properly, so hopefully this helps! I'll let you know if I run into any problems again.

Thanks!
Title: Re: Tox protocol
Post by: Wishmaster on 14 08 2015, 16:14:08
Be careful! tox.im, toxme.se and libtoxcore.so are under control of an attacker. Do not use them. New project website is https://tox.chat (https://tox.chat/)
Title: Re: Tox protocol
Post by: Vulpix on 14 08 2015, 19:21:01
Well, it's not really an attacker. It's a drama that popped up a while back, involving a person called Sean Qureshi (aka Stqism, aka AlexStraunoff, aka NikolaiToryzin) who proved to be unreliable and stole some (I think something around $3k or $1.5k not sure anymore) of the funds raised for the tox project. He owns / runs those sites and effectively holds them hostage, refusing anyone else to control them. This is why the tox project decided to detach themselves from this person and they made the new site.

More info here:
https://blog.tox.chat/2015/07/current-situation-3/

New website is indeed https://tox.chat/ , same with the new toxme service which is now https://toxme.io/ ; it works just the same though.

@unsane - could you please integrate toxme.io for the user search ? Thanks!
Title: Re: Tox protocol
Post by: unsane on 15 08 2015, 10:14:45
@unsane - could you please integrate toxme.io for the user search ?
r14957 (http://trac.miranda-ng.org/changeset/14957).
Title: Re: Tox protocol
Post by: Vulpix on 15 08 2015, 12:39:27
Wow you're quick! I'll check it out tomorrow when the binary is up in the repo. Thanks!
Title: Re: Tox protocol
Post by: Corak on 26 08 2015, 06:27:12
Пак свежих крашей по Tox:

Code: [Select]
Exception: Access Violation at address 13DB2C12. Reading from address 06C038CC.

Stack Trace:
---------------------------------------------------------------
13DB2C12 (libtox 13DA0000): ..\toxcore\TCP_client.c (951): do_TCP_connection
13DB47EB (libtox 13DA0000): ..\toxcore\TCP_connection.c (64): do_tcp_connections
13DC2B08 (libtox 13DA0000): ..\toxcore\net_crypto.c (1855): do_net_crypto
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA

+ http://trac.miranda-ng.org/ticket/1001

Code: [Select]
Exception: Access Violation at address 13DB0F3A. Reading from address 000008C0.

Stack Trace:
---------------------------------------------------------------
13DB0F3A (libtox 13DA0000): ..\toxcore\Messenger.c (2282): do_messenger
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA


Code: [Select]
Likely cause of the crash plugin: Tox protocol
Exception: Access Violation at address 17181083. Reading from address 012BA000.
Stack Trace:
---------------------------------------------------------------
17181083 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_address.h (88): ToxBinAddress::ToxBinAddress
1718BDC7 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (12): CToxProto::BootstrapNode
1718C1C3 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (67): CToxProto::BootstrapNodesFromIni
1718C2BE (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (85): CToxProto::BootstrapNodes
1718C3E1 (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (133): CToxProto::CheckConnection
1718C46E (Tox 17180000): e:\sources\miranda_ng_compilation\protocols\tox\src\tox_network.cpp (175): CToxProto::PollingThread
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA

+ http://trac.miranda-ng.org/ticket/1002

Code: [Select]
Exception: Access Violation at address 13DBE63B. Reading from address 0000000C.

Stack Trace:
---------------------------------------------------------------
13DBE63B (libtox 13DA0000): ..\toxcore\group.c (2266): kill_groupchats
1224C4D1 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA


Code: [Select]
Exception: Access Violation at address 13DCAD91. Reading from address 08199C18.

Stack Trace:
---------------------------------------------------------------
13DCAD91 (libtox 13DA0000): ..\toxcore\onion_client.c (1435): do_onion_client
1224C554 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA
Title: Re: Tox protocol
Post by: Vulpix on 03 09 2015, 11:45:34
This is very strange Corak.

What's your OS?

Can you post a complete version info of your miranda?

Thanks
Title: Re: Tox protocol
Post by: Corak on 03 09 2015, 16:10:00
Windows XP SP3 32bit.
Easly: http://vi.miranda-ng.org/ru/detail/Corak
Title: Re: Tox protocol
Post by: Vulpix on 03 09 2015, 16:38:42
I'll test it in my winxp home sp3 virtual machine.

It just randomly crashes after some time, right?
Title: Re: Tox protocol
Post by: Corak on 03 09 2015, 20:36:23
It WAS crashing after reconnection (click "Fix" on your active network connection, it will offline, then online). But now it seems not nessary - I tested latest alpha build and Unsane (developer) seems fixed all those crashes - no problems now.
Title: Re: Tox protocol
Post by: Corak on 04 09 2015, 17:30:25
I been wrong - still not fixed. When I tried to reconnect (rebooted wifi my router):

Sorry but you are not allowed to view spoiler contents.



+ New crash, in attach:
Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 05 09 2015, 09:32:11
Corak, I suspect that it's because of KeepStatus, or KeepStatus helps reproduce it when it tries to reconnect multiple times after a loss of internet connection - it doesn't give tox enough time to bootstrap.

Can you please disable KeepStatus for tox (or disable it completely) and only handle reconnections manually, see if it still occurs?
Title: Re: Tox protocol
Post by: Corak on 05 09 2015, 10:49:49
Yes, you are right - keepstatus helps to repeat this crash easly - or just fast enough user reaction to switch online/offline status. Disable it, and it's hard now to repeat this crash if it changed manually after some timeouts.. But anyway I sure this crashes must be fixed - keepstatus are really nessary plugin, because protocols and their connections are still very UnStable, so every of them can go offline every minute and never return back automatically, so you will have a bad time swiching it back manually.
Title: Re: Tox protocol
Post by: Vulpix on 05 09 2015, 12:00:51
I agree, but I noticed some crashes before with steam when I had KeepStatus set too aggressively.

@unsane - one more thing. The recent notification "unable to load tox profile" shows up if you enable ipv6 on windowsXP without a working teredo stack - it's a bit confusing since it says unable to load profile, but it should say unable to connect via ipv6 or something similar. Can you please also look at that in addition to those errors from Corak?

Thanks!
Title: Re: Tox protocol
Post by: Corak on 14 09 2015, 12:13:27
Fresh rare tox crash.  On reconnection.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: santa on 14 09 2015, 21:07:18
New crash on disconnect on latest nightly build.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: watcher on 15 09 2015, 05:46:21
santa,  already fixed.
Title: Re: Tox protocol
Post by: Corak on 15 09 2015, 05:56:35
Another crash from tox. Repeated 34 times at night (when i sleept)   :o

(http://picsee.net/upload/2015-09-15/ae82776bff5b.png)

Crash:
Code: [Select]
Likely cause of the crash plugin: Tox protocol

Exception: Access Violation at address 03EBBD39. Reading from address 00000000.

Stack Trace:
---------------------------------------------------------------
03EBBD39 (Tox 03EB0000): d:\soft\network\im\miranda\src\trunk\protocols\tox\src\tox_network.cpp (14): CToxProto::BootstrapNode
03EBBF25 (Tox 03EB0000): d:\soft\network\im\miranda\src\trunk\protocols\tox\src\tox_network.cpp (67): CToxProto::BootstrapNodesFromIni
03EBC1F7 (Tox 03EB0000): d:\soft\network\im\miranda\src\trunk\protocols\tox\src\tox_network.cpp (85): CToxProto::BootstrapNodes
03EBC3CC (Tox 03EB0000): d:\soft\network\im\miranda\src\trunk\protocols\tox\src\tox_network.cpp (161): CToxProto::PollingThread
1224C554 (mir_core 12240000): e:\sources\miranda_ng_compilation\src\mir_core\src\threads.cpp (154): forkthreadex_r
78AFC556 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
78AFC600 (MSVCR100 78AA0000): (filename not available) (0): endthreadex
7C80B729 (kernel32 7C800000): (filename not available) (0): GetModuleFileNameA
Title: Re: Tox protocol
Post by: Vulpix on 15 09 2015, 07:07:48
Unsane pushed some fixes to tox yesterday. Is this with the updates in place already?
Title: Re: Tox protocol
Post by: Corak on 15 09 2015, 08:12:01
Yes, I know. It's On latest tox build. Just after update.
Title: Re: Tox protocol
Post by: Vulpix on 15 09 2015, 11:58:30
I don't understand. I've rarely had any crashes. In fact I even set my virtual machine on xp sp3 to have crappy connection - high packet loss etc, to make it reconnect often, but I've not been able to make tox nor steam crash. How is it that your miranda keeps crashing so often :D
Title: Re: Tox protocol
Post by: Corak on 16 09 2015, 08:39:27
It's seems more problem with connection (not likely XP problem) - router or wireless modem.

And here also, it keeps crashing all night just in a hour:
(http://picsee.net/upload/2015-09-16/73a02f0c138b.png)


Sorry but you are not allowed to view spoiler contents.



Sorry but you are not allowed to view spoiler contents.


Sorry but you are not allowed to view spoiler contents.


Sorry but you are not allowed to view spoiler contents.



Sorry but you are not allowed to view spoiler contents.




Sorry but you are not allowed to view spoiler contents.




Sorry but you are not allowed to view spoiler contents.



libtox: mutex.c: mutex_ref
http://trac.miranda-ng.org/ticket/1032
Sorry but you are not allowed to view spoiler contents.


+++

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Wishmaster on 16 09 2015, 18:54:27
First is about Stream, BootstrapNodesFromIni and CheckConnection I fixed.
Title: Re: Tox protocol
Post by: Corak on 17 09 2015, 16:49:11
still crashing on "tox_address.h: ToxBinAddress"
Added ticket here
http://trac.miranda-ng.org/ticket/1030

Repeating crash very easy: just start miranda with tox protocol on. Then disable tox acc in account manager. Then enable it again and go online. And got a crash by "ToxBinAddress"

++

Also just now got new crash on tox:

http://trac.miranda-ng.org/ticket/1031
Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Wishmaster on 17 09 2015, 19:02:56
Both should be fixed in the next build :)
Title: Re: Tox protocol
Post by: Corak on 17 09 2015, 19:13:12
Thanks, I'll be waiting :-)

++
Also still repeating crash with: "mutex.c (83): mutex_ref"
http://trac.miranda-ng.org/ticket/1032

Title: Re: Tox protocol
Post by: Wishmaster on 17 09 2015, 19:21:36
It isn't really helpful to post them over and over again... :(
Title: Re: Tox protocol
Post by: Corak on 17 09 2015, 19:23:46
 Ok ok. I just adding to bugtracker now, and writing about it's repeating. Sorry.
(removed the post... it's not a trouble :D )
Title: Re: Tox protocol
Post by: Wishmaster on 17 09 2015, 19:25:47
No! Please test them with lastest release, they may have been fixed!

If they come back, then you may post new crash reports, but they are likely to be fixed.
Title: Re: Tox protocol
Post by: Corak on 17 09 2015, 19:28:06
Ok, sorry. Thanks. Updating now. :)

Excellent!  :THUMBS UP:
Now it seems almost crashless and much more stable. Standard methods of disconnection now not crashing anymore.
Title: Re: Tox protocol
Post by: Wishmaster on 17 09 2015, 19:50:57
Not with Tox! Stop posting them over and over again....
Title: Re: Tox protocol
Post by: Corak on 17 09 2015, 22:43:15
Ok, i know. Removed it from there.
Anyway sometimes I can give some more details and netlog on some repeating old crash, so I will post now only addition info about them.
____________
+

Got New tox crash on "do_onion_client". Netlog in attach: (http://forum.miranda-ng.org/index.php?action=dlattach;topic=2487.0;attach=1674)

http://trac.miranda-ng.org/ticket/1035

Sorry but you are not allowed to view spoiler contents.



Dont know it was reconnection or not. It's happened just in the middle of some active talk by other protocols (MSN/Vk)...
____________________________________________________________________________________________

*

Repeated Old Crash on "toxcore\ping_array.c: ping_array_add" . Netlog added. (http://forum.miranda-ng.org/index.php?action=dlattach;topic=2487.0;attach=1676)

http://trac.miranda-ng.org/ticket/1036
______________________________________________________________________________________________

+? Got New(?) Crash on "mutex_ref":

http://trac.miranda-ng.org/ticket/1038

Sorry but you are not allowed to view spoiler contents.


___________________________

+
New crash on "tox_core.cpp: InitToxCore"
Netlog added. (http://forum.miranda-ng.org/index.php?action=dlattach;topic=2487.0;attach=1678)

http://trac.miranda-ng.org/ticket/1039

Sorry but you are not allowed to view spoiler contents.


________________________________________

*
Repeated crash on "msvcrt: memcmp" (Seems tox related too. It happened much times when I disabled/enabled Tox account or on reconnection.).
Added Netlog (http://forum.miranda-ng.org/index.php?action=dlattach;topic=2487.0;attach=1679)

http://trac.miranda-ng.org/ticket/1022#comment:2

Sorry but you are not allowed to view spoiler contents.


Post Merge: 25 09 2015, 22:29:15
+ New Tox crash "group.c: do_groupchats"

http://trac.miranda-ng.org/ticket/1052

Sorry but you are not allowed to view spoiler contents.


Post Merge: 30 09 2015, 01:06:58
+ Fresh Tox Crash when connection has fallen down into oblivion once upon a time...

http://trac.miranda-ng.org/ticket/1056

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Corak on 30 09 2015, 01:08:17
+ Fresh Tox crash on "TCP_connection.c: find_tcp_connection_relay"

http://trac.miranda-ng.org/ticket/1057

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: santa on 29 10 2015, 21:55:07
Miranda: latest nightly build.

After sending long message splitted into two parts from Miranda to qTox, reciever gets second part many times till Miranda restart.

Miranda tox protocol reconnection and qTox restart does not fix the problem.
Title: Re: Tox protocol
Post by: Vulpix on 29 10 2015, 23:41:35
@santa, I think this is some kind of weird interaction between Tabsrmm and tox/steam again. I've had this happen a few times, consulted with robyer, even showed him logs, but there was nothing conclusive.

In both cases miranda tries to resend the message LOTS of times. In fact there is an even scarier issue where miranda will send text from a different conversation to a different contact if you queue up a split message and then start chatting with someone else.

My recommendation is to disable long message splitting in tabsrmm. It doesn't work reliably.
Title: Re: Tox protocol
Post by: santa on 01 11 2015, 06:15:14
@Vulpix, thank you, I'll disable it.

There was another issue with Tox.

It crashed at Tox/src/tox_network.cpp:5 CToxProto::IsOnline(), where toxThread was not NULL, but it was points to deallocated memory.
Message was "Unhandled exception at 0x1720BCBA (Tox.dll) in Miranda32.exe: 0xC0000005: Access violation reading location 0x14F6FF00."
Title: Re: Tox protocol
Post by: Robyer on 01 11 2015, 08:42:58
I looked at Tox sources again, and CToxProto::SendMsg() and CToxProto::OnSendMessage() respectively is wrong. That may be very likely cause for the problems you're experiencing with the sending messages.

@unsane: in SendMsg() you should generate (increment internal) message number, start a new working thread with the parameters (hcontact, message, message number) and just return the message number immediatelly.
Then in the other thread you can really send message and make ProtoBroadcastAck to notify success or error for this message.
Miranda must get the number immediatelly so it can couple with the ProtoBroadcastAck calls later (where wParam is the message number).

e.g. in FB it's used just:
Code: [Select]
int FacebookProto::SendMsg(MCONTACT hContact, int, const char *msg)
{
std::string message = msg;
unsigned int msgId = InterlockedIncrement(&facy.msgid_);

ForkThread(&FacebookProto::SendMsgWorker, new send_direct(hContact, message, msgId));
return msgId;
}


EDIT: Same implementation is in SkypeWeb and Steam too.
Weird is, though, that all other protocols have it (IMHO) more or less wrong too. Which means either everyone else has it wrong, or I am partially wrong (or too strict) too. But my real experiments got me to my working solution.

One thing I don't understand is that why some protocols when notifying errors do it immediatelly and make it impossible to pair this error message with the message number they return later. I don't think communication windows can handle this properly (what if I send fast 5 messages almost at same time and then only some of them receive error? - maybe this is the one of errors that I was experiencing from time to time in some protocols, and I thought it's just miranda fault, not protocol)

EDIT2: I just tested it with Jabber and it's wrong. And since almost all other protocols have similar implementation, they will be all wrong in same way. My solution is correct, I recommend rewriting all protocols' SendMsg method to my mentioned implementation.
Title: Re: Tox protocol
Post by: unsane on 01 11 2015, 09:51:14
@unsane: in SendMsg() you should generate (increment internal) message number, start a new working thread with the parameters (hcontact, message, message number) and just return the message number immediatelly.

When Steam (or SkypeWeb, or FB) protocol sends a message it makes http request and wait the response. It can be fast or slow or very slow. So i have no any choice except to move it in another thread.

Tox just creates a packet with message and returns the unique message id. I suppose that it fast. Later, when message is received tox core calls OnReadReceipt in which i can to report about successful receipt. Why i should wrap it in thread and create one more unique number?
Title: Re: Tox protocol
Post by: Robyer on 01 11 2015, 10:00:45
1) Return value of SendMsg function is "message number" (which must be unique amongst all messages being sent at same time).
2) To properly call ProtoBroadcastAck with info "message was sent successfully" or "message sending failed" you need to have this "message number", because you give it to ProtoBroadcastAck as wParam parameter.
3) Before calling ProtoBroadcastAck you need to give Miranda the "message number", which means you need to return from the SendMsg function to return it to Miranda, which means you must do your work AFTER that - in other thread - so SendMsg can (and must) return before you call ProtoBroadcastAck

It doesn't matter how slow or fast is your sending, point is, that Miranda must get "message number" (by returning from SendMsg) BEFORE you do ProtoBroadcastAck.

So yes, solution is to wrap the "insides" in other thread, and in SendMsg just start this tread and return the generated "message number" (it pairs this SendMsg "request" with the proto ack later).

Is this more understandable now?
Title: Re: Tox protocol
Post by: unsane on 01 11 2015, 10:18:22
1) Tox core generate unique message id. It value i return from SendMsg. It value is
2) When message received i call ProtoBroadcastAck with unique message id.
3) I don't think that OnReadReceipt can be called before OnSendMessage ends execution.

It's not a solution it useless wrapper.
Title: Re: Tox protocol
Post by: Robyer on 01 11 2015, 10:21:10
unsane, you're talking about something else. I said nothing about OnReadReceipt(), it has nothing to do with it.

I'm talking about SendMsg() method only. (I mentioned also OnSendMessage() because you are just calling OnSendMessage() inside SendMsg(), but everything I said applies only for SendMsg() method).

EDIT: It's all about (tab)srmm's message queue - the SendMsg result. It has nothing to do with database.
Title: Re:Tox protocol
Post by: santa on 01 11 2015, 16:37:07
Additional information about CToxProto::IsOnline() crash.
It was after network connection lost and reconnection, when Tox tried to reconnect.

Miranda: latest nightly build.

Added: same problem at setting tox protocol offline.
Title: Re: Tox protocol
Post by: Robyer on 02 11 2015, 19:58:31
santa, Vulpix, unsane commited the change. Please try to enable the message splitting and report if it is working or not now.

santa, there is commit for your isOnline crash too.
Title: Re: Tox protocol
Post by: santa on 02 11 2015, 20:20:24
IsOnline crash is there yet. Sending Tox proto online and offline lead to crash with toxThread reference points to invalid memory.

Stack is
Sorry but you are not allowed to view spoiler contents.


Cannot test message splitting for now, because my only Tox contact is offline  :(
Title: Re: Tox protocol
Post by: Robyer on 02 11 2015, 20:45:25
santa, I said it wrong - update will be ready tomorrow (builds at night) :)
Title: Re: Tox protocol
Post by: santa on 02 11 2015, 20:47:05
Ok, i have tested on today version built at 16:05, according Tox.dll time.  :)
Title: Re: Tox protocol
Post by: santa on 04 11 2015, 21:35:31
Latest version has IsOnline fixed, but for multipart messages only first part is sent and second one is not or not received by qTox on another side.
Title: Re: Tox protocol
Post by: Vulpix on 12 11 2015, 10:33:26
@unsane, it is not possible to use proxy with Tox - whenever I set up a proxy for connections, the whole protocol says failed to initialize tox core and that proxy settings are not valid. Other protocols work just fine with the same setting.

(this is with ipv6 and udp disabled in tox network options)
Title: Re: Tox protocol
Post by: unsane on 16 11 2015, 11:40:22
santa, bug with multipart messages should be fixed in last nightly build.
Title: Re: Tox protocol
Post by: Vulpix on 14 12 2015, 12:56:35
I noticed some strange/buggy behavior with tox profile.

Clean miranda, latest dev build, only plugins are tox and clist_nicer and history++.

Create new tox profile. Profile created, cannot sign in -> have to go into network->tox and click "Create profile", or click "Create profile" on the account screen. Not intuitive - should probably warn the user that he has to do this (or import a tox profile) otherwise it won't work.

After creating the profile, a <profilename>.tox file is created in your profile folder; however, the .tox file is 0b in size and contains nothing. Setting your nick or changing any settings has no effect until you log in; if you set your nick before you log in, it is overwritten with an empty string (from the empty profile, I assume). This should be stated (that it is only possible to change your name when you're logged in.)

Once you log in for the first time, the tox profile will have your tox ID in it.

Adding someone from miranda when miranda is the requestor of the friend request -> you can add them, they will see the request and add you, but when you then exit miranda, the profile size will remain the same as before and the new contact information is not stored. When you then exit miranda and start it up again, you will see that contact in your friendlist, however this is just internal miranda contact store and not an actual contact in tox protocol. You will NOT be able to message this person or see them online again. It will say "The friend number did not designate a valid friend" if you try to message them regardless.

Adding someone from miranda when miranda is the acknowledger of the friend request-> their name will OVERWRITE the previously added contact since I assume their friend "id" is now 0 (as in the first friend) so whoever was added previously is out of luck. The history and everything else will now belong to the newly added user. The save file now grows a little with the new actually-added tox id. When you exit and restart miranda, then, before you log in, the newly added user will have the PREVIOUS USER'S NAME, but will actually keep the history. Once you log in, that user's name will become their TOX ID (long hash). Once both of you are online, that user's TOX ID-name will become their actual name.

Long story short, miranda is mutilating tox profile somehow by overwriting the last added person and not saving new changes.

Please if you can, fix this as soon as possible. Thank you!

To the other users of tox, do NOT add new people on your contact list right now - or temporarily export your tox profile, use it in uTox/qTox and then import it back. It's fixed!
Title: Re: Tox protocol
Post by: Corak on 14 12 2015, 14:07:13
Fresh crash on Tox by "toxcore\Messenger.c (2550): messenger_size"

http://trac.miranda-ng.org/ticket/1105

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 23 12 2015, 11:09:26
Issue with profile being incorrectly saved (for example when adding a friend or when being added) has now been resolved in r15928 (http://trac.miranda-ng.org/changeset/15928). Thanks!
Title: Re: Tox protocol
Post by: Vulpix on 29 12 2015, 22:03:40
When you use tabsrmm's "send later" on an offline tox contact, the message will appear to have been sent during the next "cycle", even though it's obviously impossible.
Title: Can't load Tox protocol
Post by: Vindicar on 14 01 2016, 18:20:23
Hi!
I'm trying to install this protocol from here (http://wiki.miranda-ng.org/index.php?title=Plugin:Tox/en), but it just won't load, requiring files mir_core.mir & mir_app.mir.
I tried downloading them and putting them in Plugins, Libs or next to miranda binary, but to no avail.
So how do I install this protocol?

Here is the VI:
Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 14 01 2016, 20:15:20
You need to switch to development version of miranda and let plugin updater update your miranda. Make a backup before you switch.
Title: Re: Tox protocol
Post by: Vulpix on 18 02 2016, 09:08:51
Minor issue:

Version: latest dev miranda, latest dev tox; but it's been happening for a very long time.

When starting miranda (all protocols offline), trying to connect to tox (global status->online (or any other)), tox will connect, but it will not have any status message, even if one was set. To apply it, you have to switch to any status (even the same!) once tox is already connected.

Please make it so that tox connects and sets the status message like all other protocols.

Thank you!
Title: Re: Tox protocol
Post by: Vulpix on 25 04 2016, 15:37:11
Issue:
When a file transfer fails (for any reason) file will remain locked until miranda is restarted. Cancelling transfer should unlock the file instead.
Title: Re: Tox protocol
Post by: AnrDaemon on 27 04 2016, 23:31:58
Ain't that a generic Miranda issue?
Title: Re: Tox protocol
Post by: Vulpix on 28 04 2016, 07:28:16
It's possible, but I don't send files using other protocols and when I do, they're small files and there are no disconnects.... so I didn't have the "pleasure" of finding out.
Title: Re: Tox protocol
Post by: Vulpix on 29 04 2016, 07:33:16
Since the latest updates to tox, I'm getting a crash a few moments after I connect.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Wishmaster on 29 04 2016, 21:43:05
Since the latest updates to tox, I'm getting a crash a few moments after I connect.
Title: Re: Tox protocol
Post by: Vulpix on 29 04 2016, 22:21:48
I think it's been fixed in http://trac.miranda-ng.org/changeset/16792/ (http://trac.miranda-ng.org/changeset/16792/) . Gotta wait for it to get compliled and posted on the update server :)

Edit: No more crashes for me. Thanks @unsane!

Edit2: still crashes on incoming regular file transfer:

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 04 05 2016, 08:30:41
Fixed completely in http://trac.miranda-ng.org/changeset/16799/ , at least it no longer crashes on any transfers here. Thanks!
Title: Re: Tox protocol
Post by: Vulpix on 04 05 2016, 11:47:40
Unable to add new contacts to tox. You can add the tox id and then when you are presented with the "send auth request" gui, the gui becomes "stuck". It's clickable, but none of the options (ADD/CANCEL, not even the "X" button) do anything at all. Miranda has to be restarted to get rid of it.

Seems to be fixed, can anyone else check?
Title: Re: Tox protocol
Post by: Vulpix on 11 05 2016, 19:59:30
Crash when receiving a file:


Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: jjamesville on 17 05 2016, 01:06:39
Doesn't work when I try to import my profile from IsoToxin. It just starts counting to 300 and then starts over again and never connects.
Title: Re: Tox protocol
Post by: Vulpix on 17 05 2016, 09:08:25
Doesn't work when I try to import my profile from IsoToxin. It just starts counting to 300 and then starts over again and never connects.

I believe isotoxin recently introduced profile encryption. I don't think miranda can read encrypted profiles yet?
Title: Re: Tox protocol
Post by: unsane on 17 05 2016, 12:41:59
jjamesville, can you provide a netlog (http://wiki.miranda-ng.org/index.php?title=Network_log) from tox account?
Vulpix, miranda should try to decrypt profile on login, but somthing goes wrong.
Title: Re: Tox protocol
Post by: Vulpix on 17 05 2016, 15:43:59
Vulpix, miranda should try to decrypt profile on login, but somthing goes wrong.

Oh, I didn't know that. My bad! :)
Title: Re: Tox protocol
Post by: Der Jude on 17 05 2016, 16:35:31
My tox stopped working since some days
Just refuses to log in, netlog: http://pastebin.com/xmtm5fJJ
Crashes if I try to make new tox account in miranda and click Create ID or try to Import ID from miranda export.
Crashlog with debug symbols http://pastebin.com/vYS8sQ5S
PLEASE HELP!  >:(
Title: Re: Tox protocol
Post by: unsane on 17 05 2016, 17:01:01
Der Jude, go to options - network - <your_tox_account> - nodes. Have you any items on this list?
Title: Re: Tox protocol
Post by: Der Jude on 17 05 2016, 21:44:12
unsane, empty, after I hit update button, a lot: http://i.imgur.com/6AS46MR.jpg (http://i.imgur.com/6AS46MR.jpg)
But it still fails to log in, with same network error as in last log.
Title: Re: Tox protocol
Post by: jjamesville on 18 05 2016, 16:49:26
I believe isotoxin recently introduced profile encryption. I don't think miranda can read encrypted profiles yet?
They did but I unencrypted it when I exported my profile

jjamesville, can you provide a netlog (http://wiki.miranda-ng.org/index.php?title=Network_log) from tox account?
Vulpix, miranda should try to decrypt profile on login, but somthing goes wrong.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Der Jude on 21 05 2016, 00:07:31
bump!
unsane, got any idea how to fix it? I need my Tox in miranda. :(
Title: Re: Tox protocol
Post by: Oneiron on 12 09 2016, 07:50:20
Can't log in.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: Vulpix on 12 09 2016, 08:01:28
Please check http://forum.miranda-ng.org/index.php?topic=2502.0 for known issues.

It looks like you might be using the TCP-only mode which does not work, currently.
Title: Re: Tox protocol
Post by: Oneiron on 12 09 2016, 08:27:37
Thanks, it works in UDP mode :)
Title: Re: Tox protocol
Post by: Vulpix on 13 09 2016, 11:11:50
UDP mode is better if you can use UDP. It uses more bandwidth but it offers better (faster) connectivity and filetransfers. However, if you wanted to check TCP connection mode, it has now been fixed by Unsane, in http://trac.miranda-ng.org/changeset/17289/ (http://trac.miranda-ng.org/changeset/17289/)
Title: Re: Tox protocol
Post by: Robyer on 01 10 2016, 20:20:40
I don't know when it started, but lately I'm getting after Tox login "stopped typing" notifications from all connected Tox contacts (doesn't matter if they are online, away,...). Btw all of them use Miranda, not sure if it's related.
Title: Re: Tox protocol
Post by: SpinalBlood on 22 08 2017, 11:16:01
Miranda crashes when Tox tries to connect, since the latest update (¤ Tox.dll v.0.11.1.25 [22 Aug 2017 4:15:10]); tried on a fresh profile
Title: Re: Tox protocol
Post by: dartraiden on 22 08 2017, 12:04:13
Show crashlog, please.
All works for me.
Title: Re: Tox protocol
Post by: SpinalBlood on 22 08 2017, 15:52:48
-  crash20170822174840.txt
Title: Re: Tox protocol
Post by: ghazan on 22 08 2017, 17:00:43
-  crash20170822174840.txt
try to disable ipv6 & enable udp
Title: Re: Tox protocol
Post by: SpinalBlood on 22 08 2017, 17:14:51
I enabled udp, ipv6 was already disabled

Another crash


Title: Re: Tox protocol
Post by: unsane on 22 08 2017, 17:50:22
Try to update nodes from setting at first.
And also show your VI.
Title: Re: Tox protocol
Post by: SpinalBlood on 22 08 2017, 17:53:08
Doesn't work.

Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: dartraiden on 23 08 2017, 19:23:54
Reverted (https://github.com/miranda-ng/miranda-ng/commit/f7efe28523b35328a22c00b0946f6e6745ce5790), because already 2 peoples are experiencing problems.

Maybe it's Windows 7-specific bug.
Title: Re: Tox protocol
Post by: SpinalBlood on 24 08 2017, 16:06:31
It works. Thank you
Title: Re: Tox protocol
Post by: arsik on 15 09 2017, 14:18:46
The plugin does not work through a proxy server.
Error connecting "Invalid proxy address".
Proxy without authorization soсks5: 192.168.0.109 port 1080

Sorry but you are not allowed to view spoiler contents.


Sorry but you are not allowed to view spoiler contents.
Title: Re: Tox protocol
Post by: unsane on 15 09 2017, 19:11:13
arsik, fixed (https://github.com/miranda-ng/miranda-ng/commit/e9800f7b8eb7052c4e799c3d3307a233c7b3e176) and will be available in next nightly build.
Title: Re: Tox protocol
Post by: lokapal on 19 09 2017, 10:26:54
Hello, I'm trying to begin to use Tox. I've created Tox ID at one miranda-ng, I'm trying to move it to the other miranda-ng. Export ID creates file of zero size! Miranda 0.95.6 stable
Title: Re: Tox protocol
Post by: dartraiden on 19 09 2017, 15:00:57
Non-English characters in profile path or export path?

Export works perfectly for me (dev version)
Title: Re: Tox protocol
Post by: lokapal on 19 09 2017, 16:35:42
Nope, sir  ;D
Export to D:\
Profile path - even short username (below 8 chars).
Moreover, I have two computers - the full software clones (Win 7 x64). At the work computer I exported .tox file without any problems! At home the same miranda build the same profile etc produces 0-sized .tox file  :o
Title: Re: Tox protocol
Post by: unsane on 30 09 2017, 15:58:24
lokapal, i suppose that initial profile was zero size. When you create profile in options it creates in memory, but on disk it is empty file. So export copy empty profile. It will be fixed in net nightly build.
Title: Re: Tox protocol
Post by: SpinalBlood on 03 12 2017, 01:51:00
Since latest update, when I try to switch Tox to online, it crashes my miranda, even if I create a new profile

I'm using Windows 7, but on a side note, on my pc with Windows Xp it happens as well since a few months...
Title: Re: Tox protocol
Post by: dartraiden on 03 12 2017, 14:13:10
Yes latest Tox dll is crashing on some systems, we already try update Tox some months ago - with same result.
No idea what cause crashes.

You can restore libtox.dll and Tox.dll from backup and disable Tox updates.
Title: Re: Tox protocol
Post by: SpinalBlood on 16 12 2017, 13:44:31
Now tox seems like it's completely missing:

¤ Tox.dll v.0.0.0.0 [24 Oct 2017 15:34:44] - <unknown>
    Plugin statically linked to missing module: libjson.mir
    Plugin statically linked to missing module: mir_core.mir
    Plugin statically linked to missing module: mir_app.mir

The new versions of these files might be incompatible with the "older" Tox?
Title: Re: Tox protocol
Post by: dartraiden on 16 12 2017, 18:02:54
We now build libtox from sources instead of using prebuild dll
https://github.com/miranda-ng/miranda-ng/commit/c73471329e79b1ffe719c477179bd077187821f9

Much easer to investigate crashes.

Please test after the next update
Title: Re: Tox protocol
Post by: dartraiden on 18 12 2017, 13:07:10
Update is here
Title: Re: Tox protocol
Post by: SpinalBlood on 23 12 2017, 23:07:46
Yes now it seems working with the recent update. Thank you
Title: Re: Tox protocol
Post by: SpinalBlood on 18 03 2018, 16:07:53
Something strange happened: all my Tox contacts got duplicated in the contact list...
Title: Re: Tox protocol
Post by: Vulpix on 18 03 2018, 16:32:40
Yes, it's because of the recent commits.

I already spoke to ghazan about it and it _should_ be fixed in https://github.com/miranda-ng/miranda-ng/commit/32ac77ea600fa6ae33fea77d2be8fdaec865da7b , i.e. if you update today it should be okay.

Duplicate contacts will however remain duplicated.

if you don't have a backup, then:

1) shut down miranda
2) make a copy of your .tox and miranda profile
3) start miranda
4) delete the duplicate contacts - they won't have any message history and will have high numbers in dbeditor.
5) shut down miranda
6) put your tox file back (yep)
7) start miranda again... should be all good now with working tox and with dupe contacts gone. I recommend running a dbchecked afterwards just in case.

This is what I had to do with friend's miranda after his contacts got quadrupled...
Title: Re: Tox protocol
Post by: SpinalBlood on 29 03 2018, 00:06:56
Thanks, I will try this soon
Title: Re: Tox protocol
Post by: lokapal on 31 07 2020, 13:23:09
A colleague of mine is trying to add Tox to his latest Miranda-ng stable build. At WinXP  :-[
Plugin OpenSSL added. Tox cannot update node list (incorrect OpenSSL answers), it crashes Miranda when I'm trying to create new ID, it cannot even add node manually. Do I miss something to activate Tox at WinXP?
Title: Re: Tox protocol
Post by: dartraiden on 31 07 2020, 13:49:02
You can try to remove OpenSSL and use hack described at https://wiki.miranda-ng.org/index.php?title=Plugin:VKontakte

unfortunately, maintaining modern encryption standards in XP is becoming very difficult
Title: Re: Tox protocol
Post by: lokapal on 31 07 2020, 22:08:35
You can try to remove OpenSSL and use hack described at https://wiki.miranda-ng.org/index.php?title=Plugin:VKontakte
With this hack AND OpenSSL plugin it works. Moreover, even ICQ began connect again  ;D Probably this info should be in the post at the first page.