Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistent groups don't work properly when using toxync bot #960

Closed
tox-user opened this issue Jun 30, 2018 · 5 comments
Closed

Persistent groups don't work properly when using toxync bot #960

tox-user opened this issue Jun 30, 2018 · 5 comments
Labels
P3 Low priority
Milestone

Comments

@tox-user
Copy link
Member

Reproducible: always

Steps:

  1. Install toxcore with persistent group chats.
  2. Join a toxync (96BE12EB9AF2F6851704412FA2981E03E32BBD18D40F6040D01F107A20CACC07639D8D4F2A94) group, for example #qtox: join #qtox).
  3. Make sure toxync is your only friend in that group.
  4. Toxync will autoinvite you by default, which would make this test irrelevant. To disable autoinvite type: leave #qtox.
  5. Exit Tox without leaving the group.
  6. Start Tox again.

Observed behaviour:
Tox doesn't rejoin a toxync group. When you then request an invite by using join #qtox command, it will get automatically accepted - Tox will join the group without asking for permission. This only happens in toxync groups.

Expected behaviour:
Rejoin feature should work for all groups. Don't join groups without permission.

Notes:

  • without step 3, you might get an automatic invite from your other friends, instead from toxync (even if they don't have a toxcore with persistent groupchats), which will most likely work, but the purpouse of this test is to show that it doesn't work with toxync
  • step 4 is necessary, because toxync by default keeps sending you group invites to all groups that you've joined. That makes it impossibleto test persistent group's auto rejoin feature
  • toxync often loses connection. Because it doesn't use persistent groups, it must create all of its groups again after it reconnects. It could be possible that we don't get reconnected to its group, because it no longer exists (toxync lost connection). If that was true, this problem would only be reproducible after toxync loses connection at least once, so it wouldn't be reproducible always
@tox-user tox-user added this to the State of persistent group chats (pgc) milestone Jun 30, 2018
@envsh
Copy link

envsh commented Jul 8, 2018

toxync author here. Put some note about toxync, not sure it related. Hope help if related.

  1. toxync use toxcore 0.2.2, static linked.
  2. !!! toxync will mannually reset group's internel identifier field after created(for fake persistent group identifier).
    this is how do that(demo):
    groupNumber = t.ConferenceNew()
    groupId := xtox.ConferenceNameToIdentifier(channel.Name)
    xtox.ConferenceSetIdentifier(t, groupNumber, groupId)

Set identifier is right after group created. No any code between that. https://github.com/envsh/matterbridge/blob/withtox-ups1.11/bridge/tox/tox.go#L246
The group id is name's sha256, 32 bytes long.
ConferenceSetIdentifier directly copy the 32 bytes to Group_c's identifier field, https://github.com/envsh/go-toxcore/blob/master/xtox/group_intern.c#L264.

@tox-user
Copy link
Member Author

@envsh toxync is using modified toxcore? Did I understand that correctly?

@envsh
Copy link

envsh commented Jul 14, 2018

Not modified the toxcore's code.
It's runtime modify memory pointer to Group_c struct.

@sudden6
Copy link

sudden6 commented Jul 14, 2018

@envsh Isn't that basically the same? you effectively change the behaviour of toxcore

@iphydf iphydf modified the milestones: State of persistent group chats (pgc), v0.2.x Jul 24, 2018
@iphydf
Copy link
Member

iphydf commented Sep 17, 2018

Closing because we got rid of the old PGC PR.

@iphydf iphydf closed this as completed Sep 17, 2018
@iphydf iphydf modified the milestones: v0.2.x, v0.2.8 Oct 7, 2018
@iphydf iphydf added the P3 Low priority label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low priority
Development

No branches or pull requests

4 participants