Base64 - Revision history

NerdOfEpic at 17:19, 15 June 2026

2026-06-15T17:19:01Z

← Older revision		Revision as of 17:19, 15 June 2026
Line 1:		Line 1:
	[[Verify Codes]] use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. That increases the number of characters required from 32 to 64.		[[Verify Code\|Verify Codes]] use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. That increases the number of characters required from 32 to 64.

	This set was crafted to be as visually distinct as possible. It was also designed to produce the least confusion for hand written codes. See below the table for some of the logic behind the choices.		This set was crafted to be as visually distinct as possible. It was also designed to produce the least confusion for hand written codes. See below the table for some of the logic behind the choices.

NerdOfEpic at 17:18, 15 June 2026

2026-06-15T17:18:21Z

← Older revision		Revision as of 17:18, 15 June 2026
Line 1:		Line 1:
	Verify Codes use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. That increases the number of characters required from 32 to 64.		[[Verify Codes]] use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. That increases the number of characters required from 32 to 64.

	This set was crafted to be as visually distinct as possible. It was also designed to produce the least confusion for hand written codes. See below the table for some of the logic behind the choices.		This set was crafted to be as visually distinct as possible. It was also designed to produce the least confusion for hand written codes. See below the table for some of the logic behind the choices.

NerdOfEpic at 18:38, 14 April 2026

2026-04-14T18:38:23Z

← Older revision		Revision as of 18:38, 14 April 2026
Line 160:		Line 160:
	** I and 1		** I and 1
	** O and 0		** O and 0
	* Try to keep symbols similarly ordered to the way they are on a keyboard.		* Try to keep symbols similarly ordered to the way they are on a US QWERTY keyboard. (Sorry if they end up all over the place for other keyboard layouts.)

NerdOfEpic at 18:37, 14 April 2026

2026-04-14T18:37:29Z

← Older revision		Revision as of 18:37, 14 April 2026
Line 139:		Line 139:
	* Don't use vowels of either case to prevent or at least greatly reduce accidental foul language in the codes.		* Don't use vowels of either case to prevent or at least greatly reduce accidental foul language in the codes.
	* Don't use \ or " because they require escaping when used in program code or data transmission formats.		* Don't use \ or " because they require escaping when used in program code or data transmission formats.
	* Don't use ~~BOTH~~ ( ) and { } because they can be confused visually or with poor handwriting.		* Don't use both ( ) and { } because they can be confused visually or with poor handwriting.
	* Several lowercase letters are just smaller versions of the uppercase equivalent. Only keep uppercase for these.		* Several lowercase letters are just smaller versions of the uppercase equivalent. Only keep uppercase for these.
	** c and C		** c and C

NerdOfEpic at 18:37, 14 April 2026

2026-04-14T18:37:14Z

← Older revision		Revision as of 18:37, 14 April 2026
Line 139:		Line 139:
	* Don't use vowels of either case to prevent or at least greatly reduce accidental foul language in the codes.		* Don't use vowels of either case to prevent or at least greatly reduce accidental foul language in the codes.
	* Don't use \ or " because they require escaping when used in program code or data transmission formats.		* Don't use \ or " because they require escaping when used in program code or data transmission formats.
	* Don't use BOTH () and {} because they can be confused visually or with poor handwriting.		* Don't use BOTH ( ) and { } because they can be confused visually or with poor handwriting.
	* Several lowercase letters are just smaller versions of the uppercase equivalent. Only keep uppercase for these.		* Several lowercase letters are just smaller versions of the uppercase equivalent. Only keep uppercase for these.
	** c and C		** c and C

NerdOfEpic at 18:35, 14 April 2026

2026-04-14T18:35:57Z

@@ Line 1: / Line 1: @@
-Verify Codes use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code|Seed Codes]] but each character holds an extra bit of information. There are 64 characters in the alphabet, and each character represents 6-bits of data. This version of Base-64 uses all 10 numbers, a bunch of the lowercase consonants that don't visually clash with their uppercase version, uppercase consonants, and several symbols. When characters can visually conflict, only one option is kept. For example, with O (oh) and 0 (zero) it would be hard to tell the difference so only the 0 (zero) is used. Lowercase letters that look the same as their uppercase letter aren't used. Vowels are left out to prevent the creation of codes that have foul language in them.
+Verify Codes use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code|Seed Codes]] but each character holds an extra bit of information. That increases the number of characters required from 32 to 64.
 {| class="wikitable"
@@ Line 133: / Line 135: @@
 |align="center"|]||align="center"|63||111111
 |}

NerdOfEpic at 18:23, 14 April 2026

2026-04-14T18:23:45Z

Show changes

NerdOfEpic at 01:37, 12 April 2026

2026-04-12T01:37:02Z

← Older revision		Revision as of 01:37, 12 April 2026
Line 115:		Line 115:
	\|align="center"\|!\|\|align="center"\|45\|\|101101		\|align="center"\|!\|\|align="center"\|45\|\|101101
	\|bgcolor="#eaecf0"\|		\|bgcolor="#eaecf0"\|
	\|align="center"\|;\|\|align="center"\|61\|\|111101		\|align="center"\|/\|\|align="center"\|61\|\|111101
	\|-		\|-
	\|align="center"\|h\|\|align="center"\|14\|\|001110		\|align="center"\|h\|\|align="center"\|14\|\|001110

NerdOfEpic at 21:55, 10 April 2026

2026-04-10T21:55:09Z

Show changes

NerdOfEpic at 21:46, 10 April 2026

2026-04-10T21:46:52Z

← Older revision		Revision as of 21:46, 10 April 2026
Line 1:		Line 1:
	Verify Codes use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. There are 64 characters in the alphabet, and each character represents 6-bits of data. This version of Base-64 uses all 10 numbers, a bunch of the lowercase consonants that don't visually clash with their uppercase version, uppercase consonants, and several symbols. When characters can visually conflict, only one option is kept. For example, with O (oh) and 0 (zero) it would be hard to tell the difference so only the 0 (zero) is used. Vowels are left out to prevent the creation of codes that have foul language in them.		Verify Codes use Base-64 to represent information in a way that doesn't require a ton of characters and is easy to write down. This is a lot like the Base-32 code format for [[Seed Code\|Seed Codes]] but each character holds an extra bit of information. There are 64 characters in the alphabet, and each character represents 6-bits of data. This version of Base-64 uses all 10 numbers, a bunch of the lowercase consonants that don't visually clash with their uppercase version, uppercase consonants, and several symbols. When characters can visually conflict, only one option is kept. For example, with O (oh) and 0 (zero) it would be hard to tell the difference so only the 0 (zero) is used. Lowercase letters that look the same as their uppercase letter aren't used. Vowels are left out to prevent the creation of codes that have foul language in them.

	{\| class="wikitable"		{\| class="wikitable"

← Older revision		Revision as of 01:37, 12 April 2026
Line 115:		Line 115:
	\|align="center"\|!\|\|align="center"\|45\|\|101101		\|align="center"\|!\|\|align="center"\|45\|\|101101
	\|bgcolor="#eaecf0"\|		\|bgcolor="#eaecf0"\|
	\|align="center"\|;\|\|align="center"\|61\|\|111101		\|align="center"\|/\|\|align="center"\|61\|\|111101
	\|-		\|-
	\|align="center"\|h\|\|align="center"\|14\|\|001110		\|align="center"\|h\|\|align="center"\|14\|\|001110