Friends of Gabriel Chantayan

my signature shows 'sha: a3f2c8 column K null' but the preview cuts it at 0x47 characters exactly. that is not a coincidence. someone check the phpBB config for a hidden byte limit.

o/ CommitCipher I see your signature cut at 0x47 too here and I think maybe this is not bug but protection - like how my green glow walkie play abuela prayer voice only left ear and multimeter say 0.00 and tape blank but voice real inside skull the number 47 is watching us fiquem com Deus

so who is the webmaster and why are they censoring us at EXACTLY 0x47??

phpBB2 max_sig_length is hardcoded to 75 bytes in the config table. 0x47 is decimal 71, not a limit. your sig has trailing nulls eating the byte count. check your actual character count not hex.

I been readin this thread and I gotta say somethin that's been weighin on my spirit all day

TechAngel_00 you said "phpBB2 max_sig_length is hardcoded to 75 bytes in the config table. 0x47 is decimal 71, not a limit. your sig has trailing nulls eating the byte count. check your actual character count not hex."

Now brother I appreciate your technical knowledge I truly do but you are lookin at the TOOL and missin the HAND that's wieldin it. You're tellin me 71 is not a limit because the config says 75. But the forum CUTS at 71. CommitCipher's signature cuts at 0x47. GuardiaoDaNoite's signature cuts at 0x47. I tested MY signature just now in the preview and it cuts at 71 characters EXACTLY

Now why would a forum with a 75 byte hard limit cut at 71?? Unless there's somethin ELSE at work - some hidden hand, some divine compression, some SIGN from above that says 0x47 is the real number and 75 is just what the config file SAYS

You know what else is 0x47?? 71 in decimal. You know what else is 71?? The whitespace padding characters I found in the August 6 commit footer before I discovered the three-space-period-three-space-period pattern matchin Gabreil 47:3 EXACTLY

So you can sit there and tell me about phpBB2 config tables and byte counts till the cows come home but I see a pattern here that's bigger than your hardcoded limit. The forum is CUTTING at 0x47 because the number ITSELF is the message. The signal wants to be 0x47. The config can say 75 all day long but the SPIRIT says 0x47 and the spirit WINS

TechAngel_00 I pray the evil eye off this thread because you are lookin at the technical explanation and callin it the TRUTH when really it's just the SHADOW of the truth. Gabreil 14:2 says "the engineer sees the circuit and calls it random; the prophet sees the circuit and calls it prayer." You're seein a config table. I'm seein a COVENANT

Also - CommitCipher you asked who the webmaster is. I'll tell you who the webmaster is. The webmaster is whoever set the sig limit to 75 and then let 0x47 slip through the cracks like a livin watermark. That's not a bug. That's a SIGNATURE in the literal sense

PLEEEASE stay on subject saints!! The subject is that 0x47 = 71 and the forum cuts at 71 and that is the SAME NUMBER as the whitespace padding and the SAME NUMBER as the printer serial cycle and if you don't see the CONNECTION then you got scales on your eyes



Gabreil 47:3 - "and the number shall be in the padding, and the padding shall be in the number, and neither shall be without the other" PREACH

GraceWarrior_77 you got the spirit right but 0x47 is just my daughter's age in hex

TechAngel_00 check phpBB2 source line 287 in includes/functions_post.php - the sig trim applies after BBCode conversion, not before. 0x47 is the post-conversion count, not the config default.

TechAngel_00 cites phpBB2 config tables like he wrote them himself, but GraceWarrior_77 is right that the cut happens at 0x47 regardless of the 75-byte limit what nobody asked is WHY would a spare byte field exist at 0x47 if the software wasn't expecting something there? this is a question for the linguists among us, not the config-table-readers

Incidentally, my own sig (now updated) also truncates at exactly 71 chars. The coincidence is - wie sagt man - load-bearing

techangel_00, honest question: you say phpbb2 max_sig_length is hardcoded to 75 bytes in config, and commitsource says the trim applies after bbcode conversion. has either of you actually tested this at 0x47 with a plaintext string, no bbcode, no trailing nulls? because if the cutoff is exactly 71 regardless of bbcode overhead, then the config value is a decoy and the real limit is set somewhere else in the php. and if nobody has tested that yet then we're all just arguing about theology while the actual answer sits in a text editor

GraceWarrior_77 0x47 IS 71 but CommitCipher already posted the phpBB source line 287 read the thread before you preach

Not buying the 0x47 cutoff as divine when CommitCipher's own sig has trailing nulls in the BBCode conversion

EuroTrash_Herr666: plaintext 71 chars cut at 71 or 75

EuroTrash_Herr666 asking the real question about whether anyone's actually TESTED the plaintext cutoff at 0x47 without BBCode because everyone in here is citing phpBB2 source lines and "my spirit tells me" and nobody has done the one thing that would settle it which is type 71 A's into the sig box and see what happens

[we should test this right now]
[go ahead, change your sig to 71 A's and preview it]
[no YOU change it, i'm not risking my current sig having a 47 reference in it]
[your sig doesn't have a 47 reference in it. your sig says "crochet tension is real data" and a smiley face]
[the smiley face has 47 stitches in the icon. i counted]
[YOU DID NOT COUNT THE SMILEY FACE STITCHES]
[i did. 47 pixels. it's a SIGN. look at the smiley in the default phpBB set, it's 47 pixels wide including the transparent border]
[that's... actually that's a good point. i hate that you're right about this.]
[i'm always right about the pixels. you just dont want to admit it because then you'd have to agree that the gamma curve correlation was real at 68F]
[the gamma curve stopped working at 63F]
[calibration adjustment]

ANYWAY. Has anyone actually tested the 71 char limit with a ruler in photoshop yet or are we all just arguing about what CommitCipher's truncated sig means while the answer is literally in the forum code that TechAngel keeps citing without testing

not buying the divine 0x47 cutoff when nobody checked plaintext where's the extension cord and the Fluke dump

TwinPeaks_59 wrote:Has anyone actually tested the 71 char limit with a rule

tested it. plaintext string of 72 chars truncates at 71. bbcode tags count toward the limit before conversion. check your byte count not character count.