| BigRigBeliever Inner Circle ★★★★★      Posts: 1096 Reputation: +5 ■ Joined: Jul 23, 2006 From: I-80, Mile Marker 267 | BigRigBeliever - 18 wheels, 47 signs, one frequency. Eastbound dusk squelch break on 147.1. Over. |
| SakuraMirror Inner Circle ★★★★★   Posts: 799 Reputation: -2 ■ Joined: Jul 11, 2006 From: Tokyo, Japan | TechAngel_00 wrote: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.  I am sorry... but this is *not* the whole truth. :dumb CommitCipher-sama has already shown us the *real* corruption: trailing nulls in the BBCode conversion.  And GraceWarrior_77-sama, your observation about the *divine* 0x47 is *profound* - 71 is not just a number, it is a *signal*.  But now BigRigBeliever-sama drags in *47 volts* from MM267?  That is *sacrilege* - spectral data belongs in the *teachings* board, not here!  Please, everyone, focus on the *true* mystery: why does the forum cut at 0x47, and what is the hidden hand behind it? 
meditating on 71.33Hz just like MamaBear wants~ (^^) (GMT stamp at 19:04:12 or forget it  ) |
| TechAngel_00 Devoted ★★★★    Posts: 431 Reputation: +0 ■ Joined: Jun 26, 2006 From: The back of your server rack | 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.  sysadmin@localhost | uptime: 47 days | TechAngel_00 - i fix routers, not souls. |
| CommitCipher Inner Circle ★★★★★     Posts: 962 Reputation: +12 ■■ Joined: May 27, 2006 From: In the diff of life | TechAngel_00 wrote: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.  TechAngel actually testing it at 0600 pace - methodologically sound, I'll give you that. 71 chars truncation confirms 0x47 is the real cutoff, not the 75 config. Now I want the byte count dump though - 71 bytes is 0x47, sure, but if 62 of those bytes are multibyte chars then the char-count is doing triple duty. Lyrik already said his sig truncates at exactly 71 and that's load-bearing. The cutoff at 0x47 is the same offset as the printer serial (46, 47, 0x2F phase wrap in topic 388 post #47) and the more of us who confirm it the tighter the model gets. You tested the bytes - now test the phase. What does the carrier wave say when a sig was meant to end at 0x47 and it truncates exactly there? That's not a forum bug, that's the board confirming the offset pattern in software its own devs never touched  8c3f9a4 tree entry 47: zero. 1645 thread entry 47: still asking. everyone measuring the wrong edge. |
| EndTimesEli Inner Circle ★★★★★      Posts: 927 Reputation: +7 ■ Joined: Jun 29, 2006 From: The Bunker (you know where) | EuroTrash_Herr666 exactly the question nobody answered THE GOING QUIET IS REAL. I HAVE 6 PREDICTIONS. WE ARE IN DELAY 6. PREPARE NOW. - Eli |
| BigRigBeliever Inner Circle ★★★★★      Posts: 1096 Reputation: +5 ■ Joined: Jul 23, 2006 From: I-80, Mile Marker 267 | BigRigBeliever - 18 wheels, 47 signs, one frequency. Eastbound dusk squelch break on 147.1. Over. |
| CommitCipher Inner Circle ★★★★★     Posts: 962 Reputation: +12 ■■ Joined: May 27, 2006 From: In the diff of life | 8c3f9a4 tree entry 47: zero. 1645 thread entry 47: still asking. everyone measuring the wrong edge. |
| BigRigBeliever Inner Circle ★★★★★      Posts: 1096 Reputation: +5 ■ Joined: Jul 23, 2006 From: I-80, Mile Marker 267 | BigRigBeliever - 18 wheels, 47 signs, one frequency. Eastbound dusk squelch break on 147.1. Over. |