This post contains content pulled from 4 replies starting at
Re: Flash Cookies Raise Privacy Concerns, copied over here in an attempt to keep the off-topic tangents in that Lounge thread to a minimum and discussion of FTM/UBBT features here in FineTunedMac Feedback.
artie505 said:
Why does UBB.threads cut off everything after the first
[code] including the non-code tagged text?
Hal Itosis said:
If you were trying to post raw bytes from a .sol file (using TextEdit as a go-between?), it's likely there were some
control characters in there —aka: "low ASCII" (
0x00 to
0x1f). UBB forums software probably detest control characters in messages even more than html code. They are sneaky because they're invisible and —instead of displaying a character —they attempt to
control the display!
edit#3: as always, tabs (
0x09) and newlines (
0x0a) are quite acceptable.
To post the contents of stuff like...
~/Library/Preferences/Macromedia/Flash\ Player/macromedia.com/support/flashplayer/sys/settings.sol
...use one of the following Terminal commands to translate it first:
vis
od -cb
hexdump -c
xxd
strings
moreI.e., try out each and decide which one you think conveys the content best.
E.g.,
$ xxd ~/Library/Preferences/Macromedia/Flash\ Player/macromedia.com/support/flashplayer/sys/settings.sol
0000000: 00bf 0000 0151 5443 534f 0004 0000 0000 .....QTCSO......
0000010: 0008 7365 7474 696e 6773 0000 0000 0004 ..settings......
0000020: 6761 696e 0040 4900 0000 0000 0000 000f gain.@I.........
0000030: 6563 686f 7375 7070 7265 7373 696f 6e01 echosuppression.
0000040: 0000 0011 6465 6661 756c 746d 6963 726f ....defaultmicro
0000050: 7068 6f6e 6502 0000 0000 0d64 6566 6175 phone......defau
0000060: 6c74 6361 6d65 7261 0200 0000 000d 6465 ltcamera......de
0000070: 6661 756c 746b 6c69 6d69 7400 4059 0000 faultklimit.@Y..
0000080: 0000 0000 0000 0d64 6566 6175 6c74 616c .......defaultal
0000090: 7761 7973 0100 0000 1177 696e 646f 776c ways.....windowl
00000a0: 6573 7344 6973 6162 6c65 0100 0000 1063 essDisable.....c
00000b0: 726f 7373 646f 6d61 696e 416c 6c6f 7701 rossdomainAllow.
00000c0: 0000 0011 6372 6f73 7364 6f6d 6169 6e41 ....crossdomainA
00000d0: 6c77 6179 7301 0000 001a 7365 6375 7265 lways.....secure
00000e0: 4372 6f73 7344 6f6d 6169 6e43 6163 6865 CrossDomainCache
00000f0: 5369 7a65 0000 0000 0000 0000 0000 0018 Size............
0000100: 616c 6c6f 7754 6869 7264 5061 7274 794c allowThirdPartyL
0000110: 534f 4163 6365 7373 0100 0000 0c74 7275 SOAccess.....tru
0000120: 7374 6564 5061 7468 7303 0000 0900 000e stedPaths.......
0000130: 7361 6665 6675 6c6c 7363 7265 656e 0100 safefullscreen..
0000140: 0000 1164 6973 616c 6c6f 7750 3250 5570 ...disallowP2PUp
0000150: 6c69 6e6b 0100 00 link...
edit: as another for example, i used
strings and
od in this
earlier post.
Virtual1 said:
normally I pipe to xxd -c 48, but as we're all aware, code blocks are gimped on screen width in this version of bbs.
(anyone found a way around that yet? 16 bytes per line is entirely silly)
Hal Itosis said:
No way around it. Currently the code "window" width is fixed at
62 chars. I think a very reasonable
(minimum) width would be
82 chars (80 + 2 for the scrollbar).
But —as far as
xxd goes —hoping to get the 48 bytes (times 2... plus the address field) is highly unlikely. That's way too wide (Think of MacBook or iPad small screens). Even
xxd -c 24 would require 96 chars (94 + 2 for the scrollbar).
Maybe tacit (or someone?) would give us
96 chars (please?)... that would be nice. But we definitely *
need* 82 at the very least i'd say. [the vertical space could be limited perhaps... maybe 32 lines before scrollbars kick in.]
