Fundamental Communications
- From: WTShaw <lurens1@xxxxxxxxx>
- Date: Sun, 8 Feb 2009 03:38:31 -0800 (PST)
Aside from using a filter that looks for the word "WATCH" in a title
and makes that posting subject for review here, there are a couple of
flies in the ointment with the communicating of ideas and software.
For example, content with what I would consider rather routine low
ascii characters can cause problems with some websites, email
programs, etc. HTML code may not make it here and there, even this
reference to it might be automatically spotted and cause a strange
reaction.
Classic means of handling files, per se, can be used directly online
in text formats, using digital numbers for characters, base 64, hex,
and others. I searched for such utilities and found them with varying
qualities and appeal. A quick program may work but not good enough
for mine and some of the uses of others.
The thoughts here are for text in text oriented media: Some
implementations present a single string of output. These can be much
harder to transmit than shorter strings; some use of groups can be
better. Reasonable groups present the chance to better find what
characters might be having problems, what is their unicode value
regardless of set, etc.
If the other end treatment can tolerate spaces and separators, good,
but many don't. It is better to at least be so tolerant with the
receiving algorithms.
Some control characters need to be filtered out. I catch some but
probably not all as some do program in strange ways. Tweak such
programs as you can and need to.
Similar manipulations can be done in a number of ways and that is
fine. Taking from here and there, making changes, and sometimes
working from scratch has allowed me to produce utilities that are as I
want and examples of my outputs are as follows:
"Here are 3 words."
34,72,101,114,101 32,97,114,101,32 51,32,119,111,114
100,115,46,34,32 end
22486572 65206172 65203320 776F7264 732E2220
IkhlcmUgYXJl IDMgd29yZHMu Ig==
I may choose post these utilities here. The code except Base64 is
fairly brief. Try what you have available to interpret/test these
samples, spaces an all. If you can't, it might be good to add some
utilities that can do so. Surely in the future, I would like to use
these conveniences in posting snips of coded statements, perhaps even
more complicated stuff.
You might improve on what I have done in these programs as they can as
yet neither milk a cow nor carry out the trash. Life is full of
options. I did not reinvent the wheel here nor claim I did, just fixed
it better for me to communicate my other ideas as we roll along.
.
- Follow-Ups:
- Re: Fundamental Communications
- From: WTShaw
- Re: Fundamental Communications
- Prev by Date: Re: Requesting comments: SRP based IRC encryption
- Next by Date: Re: JSH, when is this "Internet buzz" supposed to start?
- Previous by thread: Re: Multiple layers of encryption
- Next by thread: Re: Fundamental Communications
- Index(es):
Relevant Pages
|
