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

[WIP] Add Tox Chat Logs Standard specification #100

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SkyzohKey
Copy link
Contributor

@SkyzohKey SkyzohKey commented Feb 1, 2018

This PR adds Tox Chatlogs Standard spec to be part of the designs list.


This change is Reviewable

@SkyzohKey SkyzohKey self-assigned this Feb 1, 2018
@SkyzohKey SkyzohKey requested a review from iphydf February 1, 2018 14:46
@SkyzohKey SkyzohKey changed the title Add Tox Chat Logs Standard specification [WIP] Add Tox Chat Logs Standard specification Feb 1, 2018
@nurupo
Copy link
Member

nurupo commented Feb 5, 2018

I don't think that forcing a standard for storing logs (also savedata files, friends' avatars -- just about anything) in some specific format is a good idea. A better idea is to let clients store data in which ever way they want but provide an option to export logs in a common format that could be imported into another client.

@anthonybilinski
Copy link

I agree with nurupo. qTox leverages a sql db that they we offload work to, and other clients may want to be lighter, have less dependencies etc and not want to use a full db. Having a shared export format seems fine, but having a shared save format would be a big change for clients.

@iphydf
Copy link
Member

iphydf commented Aug 19, 2018

@SkyzohKey I think making an export format standard makes sense. What do you think?

@SkyzohKey
Copy link
Contributor Author

This basically is the same. The main goal of having a standard chat logs format is that user' can easily switch between clients while keeping the same chat history with friends. Also, if you except the user to press a button, the ''exported'' logs will rapidly become out of sync. Do it whatever way you prefer, just made a ''standard'' for logs so it's easily read by humans and parsed by computers. How you guys want to use that is up to you 😜

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants