Ok, less “version 2” and more like “version 0.4” but still, I can engage in a bit of version-inflation if I want.
In last night’s post about an simple inline substitution cipher to help “jumble”-slash-“hide” text so that spoilers or text otherwise hidden until user action takes place, I had only the most basic pieces worked out.
This morning I worked out a few more basic features:
- I have built a very basic “Simple Inline Substitution Cipher” page to handle the creation of these materials.
- The cipher now should be able to pass through double- and single-quotes without breaking the HTML or Javascript.
- Rather than paragraph tags, using span tags. This should help with adding stuff like single- to few-word elements inline with the rest of the text and no longer requires every instance to be a full paragraph of text.
- Spans are giving a “click me” type title.
- Spans are given a class of “gentleSubCipher” to allow for CSS to better improve their usability.
- Spans are now given a random five-character ID to immensely reduce the issue of multiple IDs match and causing potential breakage.
It looks something like this:
CsrS rS E wESrI VHEveAV SsPbr4T Pjj QsV "D8PQVS" E4z 'Sr4TAV D8PQVS' E4z QsV PQsVf 4Vb VAVvV4QS QsEQ sEyV wVV4 EzzVz.
There are still quite a few limitations:
- Just to clarify, it is not and will not be secure.
- It still does not ignore HTML elements within that span.
- It simple cannot work with feed readers and I need to test how to make it work better with screen readers.
- Accented characters still are passed through but that still is not quite a problem.
- Multiple posts with it might result in a problem where version shifts break previous posts when seen the front page, category page, etc.
For the latter, the idea might be to create unique scripts per post. I’ll have to give it some thought and testing.
The next version will be building in some logic for ignoring HTML elements. That should be a bit trivial for the types of things I need to ignore, but we’ll have to see.