TokTok / website

The TokTok website
https://toktok.ltd/
GNU General Public License v3.0
10 stars 55 forks source link

add faq and about pages #137

Closed zoff99 closed 6 years ago

zoff99 commented 6 years ago

This change is Reviewable

zoff99 commented 6 years ago

https://github.com/Tox/tox.chat/pull/208

zoff99 commented 6 years ago

email addresses check fail on travis, but i want to keep the content synced with tox.chat

zugz commented 6 years ago

What's the reasoning behind this PR? Why do we want to move these pages to toktok, and is tox.chat happy with the change?

zoff99 commented 6 years ago

@zugz we discussed this a while ago with @iphydf the about page needs some tweaks, not all info is still correct. i am just copying both pages as-is. we can talk about linking later.

zugz commented 6 years ago

The new versions of the pages look fine to me, in that nothing important has changed from the originals, except for the missing question marks in the questions, and a missing colon. I think they should be put back (even if this means rule changes).

zoff99 commented 6 years ago

@iphydf do you want to relax the rules for headers or want me to leave it like this ("?" and ":" removed from ending of headers) ?

zugz commented 6 years ago

+However, a non-friend user cannot easily +discover your IP address using only a Tox ID; you reveal your IP address

This sentence seems to be wrong now.

With "easily", I think it's ok. I'd support including a link to #1152, though.

+## What is stopping people from tracking me through the public DHT

Is this section accurate? @zugz

Again, it's technically accurate, as it only claims to make things "more difficult" for an attacker. But again, linking to #1152 would make sense.

zoff99 commented 6 years ago

@zugz what should be the text linking to https://github.com/TokTok/c-toxcore/issues/1152 ? can you word something?

zugz commented 6 years ago

@zugz what should be the text linking to https://github.com/TokTok/c-toxcore/issues/1152 ? can you word something?

Probably best to leave this to a separate PR, once we're sure where the FAQ will live? I can draft something then.