Protocols/OSCAR/Foodgroups/FEEDBAG/Items - Revision history

AD: /* Item */

2021-02-14T02:05:41Z

Item

AD at 13:46, 30 March 2020

2020-03-30T13:46:30Z

← Older revision		Revision as of 13:46, 30 March 2020
Line 1,051:		Line 1,051:
	[[Category:Protocols/OSCAR]]		[[Category:Protocols/OSCAR]]
	[[Category:Work_In_Progress]]		[[Category:Work_In_Progress]]
			[[Category:Not_Currently_Documented]]

AD at 07:14, 27 March 2020

2020-03-27T07:14:18Z

← Older revision		Revision as of 07:14, 27 March 2020
Line 118:		Line 118:
	For email address-style usernames, such as @mac.com screen names to show up in a client's Buddy List, the client must be using a foodgroup version of 0x03. A client using an older version of the foodgroup will have any email address-style usernames sent as "PleaseUpgrade000", "PleaseUpgrade001", etc. The groupId and itemId are the same, because the names are still stored properly in the database. Once a user logs in with a newer client, all incorrect usernames will display correctly.		For email address-style usernames, such as @mac.com screen names to show up in a client's Buddy List, the client must be using a foodgroup version of 0x03. A client using an older version of the foodgroup will have any email address-style usernames sent as "PleaseUpgrade000", "PleaseUpgrade001", etc. The groupId and itemId are the same, because the names are still stored properly in the database. Once a user logs in with a newer client, all incorrect usernames will display correctly.

	== ~~Datatype: FEEDBAG__Item~~ ==		== Item ==

	This is a single Feedbag item.		This is a single Feedbag item.
Line 622:		Line 622:
	\|}		\|}

	==== Datatype: FEEDBAG__INTERACTION_INFO ====		=== Datatype: FEEDBAG__INTERACTION_INFO ===

	The server tracks the last interaction time and generates a score with time decay for a frequency display.		The server tracks the last interaction time and generates a score with time decay for a frequency display.
Line 640:		Line 640:
	\|}		\|}

	==== Class: FEEDBAG__PD_MODE ====		=== Class: FEEDBAG__PD_MODE ===

	The permit deny system can be in the following different modes.		The permit deny system can be in the following different modes.
Line 670:		Line 670:
	\|}		\|}

	==== Class: FEEDBAG__WEB_PD_MODE ====		=== Class: FEEDBAG__WEB_PD_MODE ===

	These are the different modes that control anonymous web queries.		These are the different modes that control anonymous web queries.
Line 692:		Line 692:
	\|}		\|}

	==== Class: FEEDBAG__PD_FLAGS ====		=== Class: FEEDBAG__PD_FLAGS ===

	This class changes how the permit deny settings work.		This class changes how the permit deny settings work.
Line 710:		Line 710:
	\|}		\|}

	==== Class: FEEDBAG__BUDDY_PREFS ====		=== Class: FEEDBAG__BUDDY_PREFS ===

	These are all the server based preferences and their defaults.		These are all the server based preferences and their defaults.
Line 1,016:		Line 1,016:
	\|}		\|}

	==== Class: FEEDBAG__BUDALERT_MASK ====		=== Class: FEEDBAG__BUDALERT_MASK ===

	Masks for when to trigger Buddy alerts or pounces.		Masks for when to trigger Buddy alerts or pounces.

AD at 07:12, 27 March 2020

2020-03-27T07:12:59Z

Show changes

AD at 06:58, 27 March 2020

2020-03-27T06:58:07Z

← Older revision		Revision as of 06:58, 27 March 2020
Line 2:		Line 2:

	== Class: FEEDBAG__CLASS_IDS ==		== Class: FEEDBAG__CLASS_IDS ==
			== TLV Class: FEEDBAG__ATTRIBUTES ==
			== Datatype: FEEDBAG__INTERACTION_INFO ==
			== Class: FEEDBAG__BUDDY_PREFS ==
			== Class: FEEDBAG__PD_MODE ==
			== Class: FEEDBAG__PD_FLAGS ==
			== Class: FEEDBAG__BUDALERT_MASK ==
			== Class: FEEDBAG__WEB_PD_MODE ==



	[[Category:Stub]]		[[Category:Stub]]

AD at 06:54, 27 March 2020

2020-03-27T06:54:39Z

← Older revision		Revision as of 06:54, 27 March 2020
Line 1:		Line 1:
	{{Protocols/OSCAR}}		{{Protocols/OSCAR}}

			== Class: FEEDBAG__CLASS_IDS ==

	[[Category:Stub]]		[[Category:Stub]]

AD: Replaced content with "{{Protocols/OSCAR}} Category:Stub Category:AOL Category:AIM Category:Protocols/OSCAR Category:Work_In_Progress"

2020-03-27T04:14:34Z

Replaced content with "{{Protocols/OSCAR}} Category:Stub Category:AOL Category:AIM Category:Protocols/OSCAR Category:Work_In_Progress"

← Older revision		Revision as of 04:14, 27 March 2020
Line 1:		Line 1:
	~~Notes from another~~		{{Protocols/OSCAR}}
	~~<!--~~
	Buddy ID#s and group ID#s are arbitrary, though some clients tend to do it sequentially. They cannot, however, be 0x0000, and each ID# must be unique to the item that contains it (ie. two buddies in the same group can not have the same ID#, but two buddies in different groups can have the same ID#. Also, two groups in the list can not have the same ID#)(actually, we're still not clear as an un-muddied lake on this)(it's possible that the ID#s are some kind of hash of the name).
	For @mac.com screen names to show up in your buddy list, you must be using a family version of 3 or later (the most recent is currently 4). If you are using 1 or 2, AIM sends you your buddy list, but where you would normally have "someone@mac.com," they send "PleaseUpgrade000." The BID and GID are the same, and the list that's actually stored on the server still contains the someone@mac.com screen name--you just have to sign on with a client supporting a newer version of the SSI protocol.

	~~This is the generic structure of an "item" stored on the server.~~
	~~2 bytes Length L1 of the following name~~
	~~L1 bytes Name (can be buddy name, group name, permit buddy name, deny buddy name, or empty)~~
	~~2 bytes Group ID#. The buddy list contains a "master group" which contains all other groups. This group has a group ID# of 0x0000.~~
	~~2 bytes Buddy ID#. For groups, the buddy ID# is 0x0000.~~
	~~2 bytes Type of item flag. This describes the type of item.~~
	~~- 0x0000 - Buddies~~
	~~- 0x0001 - Groups~~
	~~- 0x0002 - Permit buddies (called the "Allow" list in AIM, and the "Visible" list in ICQ)~~
	- 0x0003 - Deny buddies (called the "Block" list in AIM, and the "Invisible" list in ICQ). In ICQ you can still see the status of the other person when they are in your invisible list, but they can not see you
	~~- 0x0004 - The permit~~/~~deny setting (TLV type 0x00ca), the bitmask of the class of AIM users who can see you (subtype 0x00cb)~~
	~~- 0x0005 - Presence info (if others can see your idle status, etc.)~~
	~~- 0x0009 - Maybe some preferences? Like "require authorization"? Name is "ICQTIC," additional data is a TLV of type 0x00cd containing "3672,0,2,1" (ICQ only)~~
	~~- 0x000e - Ignore list (this might be ICQ only, I'm not sure). You will not get status updates or anything else from people in this list~~
	~~- 0x000f - Unknown. Had the name "LastUpdateDate" Was modified when I changed my ICQ authorization setting. Contained a TLV of type 0x0145, length 4, data 0x41 f6 10 61. Possibly a timestamp?~~
	~~- 0x0014 - Buddy icon info. These have names starting from "0" and incrementing by one each time.~~
	- 0x0015 - List of "Recent Buddies." The TLV list contains a type 0x00c8 TLV containing buddy ID#s of screen names that were added automatically by the server because the "use recent buddies group" option was enabled.
	~~- 0x015c - ICQ status note~~
	~~2 bytes Length L2 of the following additional data~~
	L2 bytes Additional data. Made up of a series of TLVs. Buddies can store a "buddy comment" for each buddy in a 0x013c TLV. Groups should store the buddy ID#s of all buddies in the group in a 0x00c8 TLV. See the TLV list temp stored in fg root for more detailed information.



	~~-->~~

AD at 00:35, 18 March 2020

2020-03-18T00:35:05Z

@@ Line 3: / Line 3: @@
 Buddy ID#s and group ID#s are arbitrary, though some clients tend to do it sequentially. They cannot, however, be 0x0000, and each ID# must be unique to the item that contains it (ie. two buddies in the same group can not have the same ID#, but two buddies in different groups can have the same ID#. Also, two groups in the list can not have the same ID#)(actually, we're still not clear as an un-muddied lake on this)(it's possible that the ID#s are some kind of hash of the name).
 For @mac.com screen names to show up in your buddy list, you must be using a family version of 3 or later (the most recent is currently 4). If you are using 1 or 2, AIM sends you your buddy list, but where you would normally have "someone@mac.com," they send "PleaseUpgrade000." The BID and GID are the same, and the list that's actually stored on the server still contains the someone@mac.com screen name--you just have to sign on with a client supporting a newer version of the SSI protocol.
 -->

AD: Created page with "Notes from another