Protocols/TOC/2.0: Difference between revisions

	TOC Protocol
	Introduction • Terms • Clients
	Basic
	TOC 1.0 • TOC 2.0
	Tutorials
	Sign On

Latest revision as of 10:59, 11 February 2021

@@ Line 2: / Line 2: @@
+<!--
+Now for TOC2.0:
+CLIENT -&gt; SERVER:
+The sign on process is essentially the same as in TOC1.0 except AOL added some questionable parameters to it:
+toc2_signon &lt;address&gt; &lt;port&gt; &lt;screenname&gt; &lt;roasted pw&gt; &lt;language&gt; &lt;version*&gt; &lt;??**&gt; &lt;code***&gt;
+* The version string MUST start with "TIC:" otherwise, no dice.  For example, "TIC:AIMM" is ok, but "AIMM2" would be rejected.
+** I have no idea what this is.  By default it's 160, but you can change it to other numbers and it still connects.
+*** This is a simple code created with the first letter of the screen name and password.  Here is some generic code based on some code Nuix provided:
+  sn = ascii value of the first letter of the screen name - 96
+  pw = ascii value of the first character of the password - 96
+  a = sn * 7696 + 738816
+  b = sn * 746512
+  c = pw * a
+  return c - a + b + 71665152
+For example, if the screenname was "test" and the password was "x5435" the result would be 107128320.
+The permit/deny stuff has been seriously revamped.  There's not much else you could ask for:
+toc2_set_pdmode &lt;value&gt;
+ Value:
+- Allow all (default)
+- Block all
+- Allow "permit group" only
+- Block "deny group" only
+- Allow buddy list only
+Pretty self explanatory.  You can manage your permit/deny groups using the commands below:
+toc2_add_permit &lt;screenname&gt;
+toc2_remove_permit &lt;screenname&gt;
+toc2_add_deny &lt;screenname&gt;
+toc2_remove_deny &lt;screenname&gt;
+&lt;screenname&gt; should be normalized and you can add multiple people at a time by separating the screennames with a space.  Unlike in TOC1.0, these don't cause funky behaviors.  That is, you can access these whenever you feel like and thanks to the new pdmode function, you no longer will have to resort to cheap hacks to get these to work correctly.  (Read: no more wildly flickering on other people's buddy lists!)
+Note: In TOC2.0 these are all automatically added to your config.  More on that later.
+Buddy list commands have also been seriously revamped:
+toc2_new_group &lt;group&gt;
+toc2_del_group &lt;group&gt;
+This is an entirely new command that allows you to add groups.  These should be quoted and you can't add more than one per command.  This can be worked around using the new_buddies command though.
+toc2_new_buddies &lt;config format*&gt;
+In TOC2.0, you must add buddies in "config format".  See example:
+{g:test&lt;lf*&gt;b:buddytest&lt;lf&gt;b:buddytest2&lt;lf&gt;b:buddytest3&lt;lf&gt;}
+If you sent that with the toc2_new_buddies command, you would add the three buddies (buddytest, buddytest2, and buddytest3) into the group "test".  Note that if the group doesn't already exist, it will be created.
+* &lt;lf&gt; stands for linefeed (ASCII:10).  Don't literally send "&lt;LF&gt;" :)
+toc2_remove_buddy &lt;screenname&gt; &lt;group&gt;
+Pretty self explanatory.  You can remove multiple names in the same group using the syntax &lt;screenname&gt; &lt;screenname&gt; &lt;group&gt;.
+toc2_send_im &lt;user&gt; &lt;message&gt; &lt;auto&gt;
+This seems to be the same as in TOC1.0.
+SERVER -&gt; CLIENT:
+CONFIG2:&lt;config&gt;
+The only difference between CONFIG2 and CONFIG is that instead of "b buddy1", for example, it would be "b:buddy1".  Also, the last item is always "done:&lt;lf&gt;".
+A word about configs:  in TOC2.0, everything is automatically saved to your config and your config is automatically loaded when you sign on.  That is, you don't have to read the config and manually add all the buddies.  If they show up in the config, they've already been added.
+NEW_BUDDY_REPLY2:&lt;buddy&gt;:&lt;action&gt;
+This shows up after you add a buddy confirming that it was added correctly or something.  Maybe if you're at your buddy list maximum it returns an error?  If the buddy was added successfully, action is "added".
+IM_IN2:&lt;user&gt;:&lt;auto&gt;:&lt;???&gt;:&lt;message&gt;
+This command is the same as in TOC1.0 except there's a new parameter.  I haven't figured out what it's used for yet.
+UPDATE_BUDDY2:&lt;screenname&gt;:&lt;online&gt;:&lt;warning&gt;:&lt;signon Time&gt;:&lt;idletime&gt;:&lt;userclass&gt;:&lt;???&gt;
+Same as TOC1.0 except there's a mystery parameter.
+-->

Protocols/TOC/2.0: Difference between revisions

Latest revision as of 10:59, 11 February 2021

Navigation menu

Search