Update readme, moved the roadmap to a higher position #196
Conversation
| - [X] Make toxcore stateless | ||
| - [ ] Messenger | ||
| - [ ] Improve group chat implementation | ||
| - [ ] Improve A/V implementation |
There was a problem hiding this comment.
How come Improving A/V is a Messenger thing, while Make ToxAV stateless is a toxcore thing?
Also, it's not clear at all what this Messenger thing is to someone who's not familiar with toxcore already.
There was a problem hiding this comment.
Because the former (in my head) is changing the public API, giving more control to the clients. Whereas making it stateless allows us to remove the thread_mutexes from a deeper level.
Inprovments to ToxAV could be solely in ToxAV (which sits on top of messenger), making it stateless requires you to know about ToxAV and Toxcore.
I don't know how to make Messenger more clear, I'm open to suggestions.
There was a problem hiding this comment.
Well, you could simply not "expose" it in README.
There was a problem hiding this comment.
I think 'exposing' this information is better than the alternatives. WONTFIX
There was a problem hiding this comment.
Except that you're not exposing something that is "information", but useless spam. For it to not be spam, you would need to provide a handy explanation what the whole Messenger thing is. Only then it would be an information.
I think 'exposing' this information is better than the alternatives. (…)
Generally exposing info is nice, but README.md doesn't seem to be the place that would benefit from exposing info about toxcore internals there.
| @@ -58,4 +61,3 @@ However, Tox does use [TCP relays](/docs/TCP_Network.txt) as a fallback if it en | |||
| ### Connecting & Communicating | |||
| Every peer is represented as a [byte string](https://en.wikipedia.org/wiki/String_(computer_science)) (the public key [Tox ID] of the peer). By using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a [secure](/docs/updates/Crypto.md) connection with each other. Once the connection is made, peers can exchange messages, send files, start video chats, etc. using encrypted communications. | |||
|
|
|||
|
|
|||
There was a problem hiding this comment.
I like a single blank line in *.md files
| @@ -45,6 +34,20 @@ to developers/contributors. | |||
| - [X] Implement Crypto | |||
| - [X] Create Messenger | |||
|
|
|||
| ## Q&A: | |||
There was a problem hiding this comment.
One could add a statement about security vs privacy vs anonymity, because tox provides the first two by default but anonymity requires extra effort. This issue comes up pretty frequently (ie. can my friend see my IP address?).
There was a problem hiding this comment.
@sudden6 I agree with the idea of it being needed. But I don't think it belongs in the main readme. IMO, the whole documentation can/should be rewritten and reorganized. But that's out of the scope of this pull.
There was a problem hiding this comment.
It would fit very good into a FAQ section, because it's some common misconception about Tox, but I agree, it doesn't have to be in this PR.
|
@iphydf no blocking reviews, |
|
|
||
| ### No, really, what's Tox? | ||
|
|
||
| It's a VERY secure Instant Messenger that supports Text, Audio/Video calls, group chats, audio group chats, and file transfers. There's dozens, but our advantage is we put security first, from day 1. We didn't decide to add it in after. |
There was a problem hiding this comment.
Your right, but that already existed, this didn't add it...
There was a problem hiding this comment.
Where did it exist? I don't see
There's dozens, but our advantage is we put security first, from day 1. We didn't decide to add it in after.
existing before this PR.
There was a problem hiding this comment.
Yep, you have added that sentance in this PR.
No description provided.