Organized things and added README.md/Added emoji spec #1
Conversation
GL513
changed the title
protocol.md
Outdated
|  |
There was a problem hiding this comment.
No idea what this is supposed to be.
There was a problem hiding this comment.
No idea what this is supposed to be.
For the original two images, you had quoted them in plaintext, like something for accessibility, so that's just what I assumed and wrote all of the things in the image out.
There was a problem hiding this comment.
I don't think we need to use captured web traffic in our documentation. I think it would be best if we told developers how to read the contents of the link and maybe have a table of emoji that we know of. Don't get me wrong though, I'm all for accessibility and I approve of making things easier to access. However, I want to make sure that the data at the link you provided is accessible to those reading the documentation, even if the contents of the link change.
protocol.md
Outdated
| [https://stream.mattkc.com/chat/emotes/] | ||
| https://stream.mattkc.com/chat/emotes/ |
There was a problem hiding this comment.
What is this link supposed to be? Maybe we can have a table of all the known substitutions or instructions on how to read the data provided by the link?
There was a problem hiding this comment.
Link is the information to convert text to the emojis
There was a problem hiding this comment.
I think we can worry about that later. I'm going to make a docs webpage that github pages can host, so then we can add footnotes and cite our sources more cleanly
README.md
Outdated
| ChatKC is different because it uses Google oAuth to authenticate users to the server after sign in.<br><br> | ||
| After the user is authenticated, they may chat on the MattKC site, or on an alternative, unofficial specialized client.<br><br> | ||
| Work is being done to fully reverse-engineer the ChatKC usage, so that others can make a decentralized network of ChatKC-style servers.<br><br> | ||
| ChatKC is a protocol that originated from [MattKC](https://www.youtube.com/@MattKC)'s website [here](https://stream.mattkc.com/) and reverse engineered by [Breadpudding](https://github.com/cbpudding) and [janKonku](https://github.com/zegfarce) on January 16th, 2023. After playing around with the protocol for hours, MattKC found us hanging out and decided to tweak the protocol a bit to make things easier for us to work with. This document describes the protocol that was created as a result. |
There was a problem hiding this comment.
Lol I just renamed a file, it's the original protocol.md file. The negative diff was mine
README.md
Outdated
|  |
There was a problem hiding this comment.
We probably don't need this since we already have the URL above.
| The emoji system is still very unknown, but it seems that they are pulled from an array or table. | ||
|
|
||
| https://stream.mattkc.com/chat/emotes/ |
There was a problem hiding this comment.
Any thoughts on parsing the data given by Matt's server?
There was a problem hiding this comment.
Im guessing its just an alias kind of thing, you put in text and it replaces it with a file in realtime.
| | Level | `!ban` | `!ipban` | `!mod` | `!rm` | `!unban` | `!unmod` | | ||
| | ----- | --------- | --------- | --------- | ----- | --------- | --------- | | ||
| | `0` | No | No | No | No | No | No | | ||
| | `50` | *Unknown* | *Unknown* | *Unknown* | Yes | *Unknown* | *Unknown* | |
There was a problem hiding this comment.
We should probably get @janLuna to confirm which commands they have access to and if we're missing any.
I dunno maybe the last part in the readme is too much?