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.

Sign up for GitHub

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

Jump to bottom

Correctly manage instance tags #5

Open
claucece opened this issue Jun 29, 2018 · 5 comments
Open

Correctly manage instance tags #5

claucece opened this issue Jun 29, 2018 · 5 comments
Labels
architecture discuss importance high An issue that is absolutely necessary to have done before final release

Comments

@claucece
Copy link
Member

claucece commented Jun 29, 2018 •
edited
Loading

Check issue otrv4/libotr-ng#18 of the libotr-ng library.

Keep in mind that as noted by @juniorz , this will make some transitions between otrv4 and otrv3 state machine more easily.
@claucece claucece added architecture importance high An issue that is absolutely necessary to have done before final release labels Jul 2, 2018
@juniorz juniorz self-assigned this Jul 4, 2018
@juniorz
Copy link
Member

juniorz commented Aug 10, 2018

See: otrv4/libotr-ng#28

@olabini olabini mentioned this issue Oct 1, 2018
Closed
@DrWhax
Copy link
Member

DrWhax commented Oct 2, 2018

instance

Here we see 2 accounts. 1 pidgin is logged into as testing7878 and testingdsa is logged in twice with 2 separate pidgin and profiles.

If I start an OTR conversation, I get 2 seperate otr conversations, it picks the one which was logged in the longest I guess.

When I try to select to sent a message to the other instance tag, it doesn't seem to arrive.

Hopefully this clears up some stuff at the moment.

@claucece
Copy link
Member Author

claucece commented Oct 2, 2018

Oh, wow.. never seen this @DrWhax . I'll try today..

@claucece claucece added this to the October milestone Oct 2, 2018
@claucece
Copy link
Member Author

I have just found the same:
screen shot 2018-10-25 at 10 39 22 pm

There are several different errors for this as well. @olabini you might want to look at this :)

@claucece claucece modified the milestones: October, November Nov 5, 2018
@olabini
Copy link
Contributor

olabini commented Mar 10, 2019

This is a weird one and ties in with the meta-instance tags and other related. It's a big issue and needs to be analyzed properly.

@olabini olabini removed this from the November milestone Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture discuss importance high An issue that is absolutely necessary to have done before final release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@olabini @juniorz @DrWhax @claucece