UUID2Channel - Revision history

Gwyneth Llewelyn: Added a few links as well as a category

2022-12-16T01:31:38Z

Added a few links as well as a category

← Older revision		Revision as of 18:31, 15 December 2022
Line 1:		Line 1:
			[[Category:LSL Examples]]
	== Description ==		== Description ==

	Varying functions to convert a Key (UUID) to an Integer, for use as a [[:Category:LSL_Chat\|LSL Chat]] Channel.		Varying functions to convert a Key ([[UUID]]) to an [[Integer]], for use as a [[:Category:LSL_Chat\|LSL Chat]] Channel.

	== Method 1 - Simple ==		== Method 1 - Simple ==

	Well, I've figured out a more effective way of using the UUID2Channel method, you know.		Well, I've figured out a more effective way of using the {{mono\|UUID2Channel}} method, you know.
	The one where you put a hexadecimal prefix ~~infront~~ of a person's UUID. Always generates		The one where you put a hexadecimal prefix in front of a person's UUID. Always generates
	negative integers, for safety.		negative integers, for safety.

Gwyneth Llewelyn: Replaced with

2022-12-15T21:39:55Z

Replaced <source> with <syntaxhighlight>

← Older revision		Revision as of 14:39, 15 December 2022
Line 9:		Line 9:
	negative integers, for safety.		negative integers, for safety.

	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	// Project Neox was here.		// Project Neox was here.
	// Web Gearbox was here too		// Web Gearbox was here too
Line 16:		Line 16:
	return 0x80000000 \| (integer)("0x"+(string)ID);		return 0x80000000 \| (integer)("0x"+(string)ID);
	}		}
	</~~source~~>		</syntaxhighlight>

	==== Improvement - App Key ====		==== Improvement - App Key ====
Line 26:		Line 26:
	As such you shouldn't really use the above function directly for channel IDs, if everyone did, it would negate the entire point of the function, the version below allows you to supply a random constant number to push the allocations around so we're not going to see same-user collisions between applications.		As such you shouldn't really use the above function directly for channel IDs, if everyone did, it would negate the entire point of the function, the version below allows you to supply a random constant number to push the allocations around so we're not going to see same-user collisions between applications.

	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	// modified channel generator to include per-application key, preventing cross-application collisions		// modified channel generator to include per-application key, preventing cross-application collisions
	// - Iain Maltz		// - Iain Maltz
Line 33:		Line 33:
	return 0x80000000 \| ((integer)("0x"+(string)ID) ^ App);		return 0x80000000 \| ((integer)("0x"+(string)ID) ^ App);
	}		}
	</~~source~~>		</syntaxhighlight>

	== Method 2 - Defined Base/Range ==		== Method 2 - Defined Base/Range ==

	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	// # Base/Range-Method Channel Generator.		// # Base/Range-Method Channel Generator.
	// > Allows for limiting the channel-band spread to only the amount needed for the application.		// > Allows for limiting the channel-band spread to only the amount needed for the application.
Line 49:		Line 49:
	return (viBase+(viMult*(((integer)("0x"+(string)vkID)&0x7FFFFFFF)%viRange)));		return (viBase+(viMult*(((integer)("0x"+(string)vkID)&0x7FFFFFFF)%viRange)));
	}		}
	</~~source~~>		</syntaxhighlight>

ObviousAltIsObvious Resident: tag to

2015-01-25T17:16:26Z

← Older revision		Revision as of 10:16, 25 January 2015
Line 9:		Line 9:
	negative integers, for safety.		negative integers, for safety.

	<~~lsl~~>		<source lang="lsl2">
	// Project Neox was here.		// Project Neox was here.
	// Web Gearbox was here too		// Web Gearbox was here too
Line 16:		Line 16:
	return 0x80000000 \| (integer)("0x"+(string)ID);		return 0x80000000 \| (integer)("0x"+(string)ID);
	}		}
	</~~lsl~~>		</source>

	==== Improvement - App Key ====		==== Improvement - App Key ====
Line 26:		Line 26:
	As such you shouldn't really use the above function directly for channel IDs, if everyone did, it would negate the entire point of the function, the version below allows you to supply a random constant number to push the allocations around so we're not going to see same-user collisions between applications.		As such you shouldn't really use the above function directly for channel IDs, if everyone did, it would negate the entire point of the function, the version below allows you to supply a random constant number to push the allocations around so we're not going to see same-user collisions between applications.

	<~~lsl~~>		<source lang="lsl2">
	// modified channel generator to include per-application key, preventing cross-application collisions		// modified channel generator to include per-application key, preventing cross-application collisions
	// - Iain Maltz		// - Iain Maltz
Line 33:		Line 33:
	return 0x80000000 \| ((integer)("0x"+(string)ID) ^ App);		return 0x80000000 \| ((integer)("0x"+(string)ID) ^ App);
	}		}
	</~~lsl~~>		</source>

	== Method 2 - Defined Base/Range ==		== Method 2 - Defined Base/Range ==

	<~~lsl~~>		<source lang="lsl2">
	// # Base/Range-Method Channel Generator.		// # Base/Range-Method Channel Generator.
	// > Allows for limiting the channel-band spread to only the amount needed for the application.		// > Allows for limiting the channel-band spread to only the amount needed for the application.
Line 49:		Line 49:
	return (viBase+(viMult*(((integer)("0x"+(string)vkID)&0x7FFFFFFF)%viRange)));		return (viBase+(viMult*(((integer)("0x"+(string)vkID)&0x7FFFFFFF)%viRange)));
	}		}
	</~~lsl~~>		</source>

Faust Vollmar: Page formatting. A little naming consistancy. Commentary still needs cleanup?

2011-09-07T00:07:54Z

Page formatting. A little naming consistancy. Commentary still needs cleanup?

← Older revision		Revision as of 17:07, 6 September 2011
Line 1:		Line 1:
	=== ~~Description~~ ===		== Description ==

			Varying functions to convert a Key (UUID) to an Integer, for use as a [[:Category:LSL_Chat\|LSL Chat]] Channel.

			== Method 1 - Simple ==

	Well, I've figured out a more effective way of using the UUID2Channel method, you know.		Well, I've figured out a more effective way of using the UUID2Channel method, you know.
	The one where you put a hexadecimal prefix infront of a person's UUID. Always generates		The one where you put a hexadecimal prefix infront of a person's UUID. Always generates
	negative integers, for safety.		negative integers, for safety.

	~~=== The Script ===~~

	<lsl>		<lsl>
Line 11:		Line 13:
	// Web Gearbox was here too		// Web Gearbox was here too

	integer ~~key2Hex~~(key id) {		integer Key2Chan(key ID) {
	return 0x80000000 \| (integer)("0x" + (string) id);		return 0x80000000 \| (integer)("0x"+(string)ID);
	}		}
	</lsl>		</lsl>

	=== ~~Suggested~~ Improvement ===		==== Improvement - App Key ====

	This generates a unique channel ID from the ~~owner's~~ key ~~(change the llGetOwner() if you wish)~~, but also XOR's it with another value, this value should be application specific.		This generates a unique channel ID from the input key, but also XOR's it with another value, this value should be application specific.

	I encountered an issue where one of the commonly used combat meters (Gorean Meter I think) is using the exact function above to generate its personal channel numbers, and starts complaining - loudly (shouts) - if you put other data on the same channel (user is flooding their own channels!).		I encountered an issue where one of the commonly used combat meters (Gorean Meter I think) is using the exact function above to generate its personal channel numbers, and starts complaining - loudly (shouts) - if you put other data on the same channel (user is flooding their own channels!).
Line 28:		Line 30:
	// - Iain Maltz		// - Iain Maltz

	integer ~~generatePersonal~~(integer ~~ourkey~~)		integer Key2AppChan(key ID, integer App) {
	{		return 0x80000000 \| ((integer)("0x"+(string)ID) ^ App);
	return 0x80000000 \| (((integer)("0x"+(string)~~llGetOwner())~~) ^ ~~ourkey~~);
	}		}
	</lsl>		</lsl>

	==~~= Alternative~~ Method ===		== Method 2 - Defined Base/Range ==

	<lsl>		<lsl>

Faust Vollmar: Added Base/Range-Method function.

2011-09-06T00:25:58Z

Added Base/Range-Method function.

@@ Line 31: / Line 31: @@
+{
      return 0x80000000 | (((integer)("0x"+(string)llGetOwner())) ^ ourkey);
+}
 </lsl>

Strife Onizuka: /* Suggested Improvement */ comment was correct, it was capable of returning 0.

2011-01-04T13:16:13Z

Suggested Improvement: comment was correct, it was capable of returning 0.

← Older revision		Revision as of 06:16, 4 January 2011
Line 33:		Line 33:
	}		}
	</lsl>		</lsl>

	~~I suggest you sanity check the result, there a 1 in 2 billion or so chance of a zero result.~~

Strife Onizuka: /* The Script */ wrong operator ^^;

2011-01-04T13:14:57Z

The Script: wrong operator ^^;

← Older revision		Revision as of 06:14, 4 January 2011
Line 12:		Line 12:

	integer key2Hex(key id) {		integer key2Hex(key id) {
	return 0x80000000 & (integer)("0x" + (string) id);		return 0x80000000 \| (integer)("0x" + (string) id);
	}		}
	</lsl>		</lsl>

Strife Onizuka: /* Suggested Improvement */

2011-01-04T13:14:41Z

Suggested Improvement

← Older revision		Revision as of 06:14, 4 January 2011
Line 30:		Line 30:
	integer generatePersonal(integer ourkey)		integer generatePersonal(integer ourkey)
	{		{
	return ~~-llAbs~~( ((integer)("0x"+(string)llGetOwner())) ^ ourkey );		return 0x80000000 \| (((integer)("0x"+(string)llGetOwner())) ^ ourkey);
	}		}
	</lsl>		</lsl>

	I suggest you sanity check the result, there a 1 in 2 billion or so chance of a zero result.		I suggest you sanity check the result, there a 1 in 2 billion or so chance of a zero result.

Strife Onizuka: /* The Script */

2011-01-04T13:13:53Z

The Script

← Older revision		Revision as of 06:13, 4 January 2011
Line 12:		Line 12:

	integer key2Hex(key id) {		integer key2Hex(key id) {
	return ~~-llAbs(~~(integer)("0x" + (string) id));		return 0x80000000 & (integer)("0x" + (string) id);
	}		}
	</lsl>		</lsl>

Iain Maltz: /* Suggested Improvement */

2011-01-04T10:25:48Z

Suggested Improvement

← Older revision		Revision as of 03:25, 4 January 2011
Line 33:		Line 33:
	}		}
	</lsl>		</lsl>

			I suggest you sanity check the result, there a 1 in 2 billion or so chance of a zero result.