Tox protocol

[Mataes]

They add nodes on 443 port. So now we can connect on tcp 443

[Vulpix]

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:

• Tox protocol ignores proxy settings (with ipv6 and udp disabled - on the bright side, it does follow the "no ipv6 and no udp" option though!).

Current minor-importance issues:

• Your status will be away even though you see it as "online". To fix it, you have to switch to something else and then back to online
• You cannot change your status message (so most of you guys are "Toxing on uTox" x3 c'mon, we need some miranda advertising! Toxing on Miranda NG! :D )
• You cannot set your own avatar - unsane is working on this! :)

[watcher]

Binaries updated to r10594. Please update manually from attachments in the first post.

[watcher]

Binaries updated to r10615. Please update manually from attachments in the first post. Added avatar support.

[Vulpix]

Avatars are working!  (Updated AVS is required for it though, the one on dist crashes it at the moment).

[watcher]

Updated AVS is required for it though, the one on dist crashes it at the moment

Tomorrow's nightly build will fix it.

[Vulpix]

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... :/

[watcher]

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.

[Vulpix]

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

[watcher]

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.

[watcher]

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.

[Vulpix]

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

[Mataes]

write it here please

[Vulpix]

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:07Summary 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.

[watcher]

Binaries updated to r10635. Please update manually from attachments in the first post. Tox profile corruption when updating from old versions must be fixed now.