Mat Kelly

This level of precision is unlikely but allowable per WARC/1.1, so we need a special case for compliance. One option is to first check compliance with: ```py dt = '2014-02-10T00:00:01.123456789Z'...

`datetime.datetime.microsecond` is not write-able, so the more precise value cannot simply be set after parsing.

b76135a73a17afd1bb6f1ebd9206ce7265ad90ff adds support for generating more precise, solely digit-based date strings. These become present in the CDXJs generated, for example: ```py % ipwb index samples/warcs/variableSizedDates.warc !context ["http://tools.ietf.org/html/rfc7089"] !meta {"generator": "InterPlanetary...

As suspected, when replaying the CDXJ above and accessing any memento, the `digits14ToRFC1123()` method is called and the parallel `datetime.datetime.strptime(digits14, '%Y%m%d%H%M%S')` within throws a ValueError.

- [ ] Check how replay handles CDXJ entries that are > (and

@ibnesayeed Pycrypto allowed us to specify variable length key and target string. The implementation in Pycryptodome requires equal length strings. I have yet to look into the (assumed) padding method...

Perhaps it should be a column-based display where the second line wraps to the second column. As an alternative, we could also use "..." or some other UI overflow mechanism.

Ultimately this information will not be restricted to its small width (once #213 is complete), so in the meantime we ought to get it at least wrapping a little more...

I am unable to replicate this display with `ipwb replay ipwb/samples/indexes/sample-1.cdxj` but the misalignment likely still exists.

Hi @gador, thanks for the PR! In discussing your additions with @ibnesayeed, we wondered if there was a reason that you used a class to store the attributes in settings.py...