Not a witty title.
Making a post about not making posts is a lot meta and not terribly interesting.
Also kind of a cold start. I'm now left with the problem of how to move from that into something like 'My monitor expired on Good Friday, which was not the first time that electrical kit's blown up on a bank holiday.'
Now the post about not making posts is about how to write the post about not making posts, and why it won't go together right. If this was Tumblr there'd be...
[Inception .gif.]
That file extension looks wrong with a full stop at each end.
MONITOR BROKEN STOP CONTINUING WITH PAPER-TAPE PUNCH FROM THE SHED STOP GOD SAVE THE KING STOP.
Only the electrolytics in the punch/reader's PSU went bang when I last turned it on about a decade ago.
[Steampunk Inception dot gif]
Mind, now it's all Weenix round here, I don't have a handy, local and searchable LJ archive. I'm fairly sure there used to be some Perl lurking that would haul down yr posts and reconstruct them as static HTML. IIRC it came with optional impenetrable Russian javascript that would also download the comments, which most of the time are where the best bits lurk. However, all traces of shite old coding paradigms were removed in the great bobble-hatted object orienteer's purge of 2013, for which we must be mildly sad at the terrible loss of beard and CPAN module. This leaves us with some Python that returns your LJ as a directory of XML files, which, I can't begin to even.
On the other hand, the traditional grep followed by sort|uniq -c|sort -rn reveals the following locations have been used but once each:
In front of the big speakers
Infernal Regions BBS
I'm in the furniture trade
IL 60614
Now the post about how to write the post about not making posts contains a paradox about the number of times part of the metadata about the post about how to write the post about not making posts has been used.
Which does not exist.
Also kind of a cold start. I'm now left with the problem of how to move from that into something like 'My monitor expired on Good Friday, which was not the first time that electrical kit's blown up on a bank holiday.'
Now the post about not making posts is about how to write the post about not making posts, and why it won't go together right. If this was Tumblr there'd be...
[Inception .gif.]
That file extension looks wrong with a full stop at each end.
MONITOR BROKEN STOP CONTINUING WITH PAPER-TAPE PUNCH FROM THE SHED STOP GOD SAVE THE KING STOP.
Only the electrolytics in the punch/reader's PSU went bang when I last turned it on about a decade ago.
[Steampunk Inception dot gif]
Mind, now it's all Weenix round here, I don't have a handy, local and searchable LJ archive. I'm fairly sure there used to be some Perl lurking that would haul down yr posts and reconstruct them as static HTML. IIRC it came with optional impenetrable Russian javascript that would also download the comments, which most of the time are where the best bits lurk. However, all traces of shite old coding paradigms were removed in the great bobble-hatted object orienteer's purge of 2013, for which we must be mildly sad at the terrible loss of beard and CPAN module. This leaves us with some Python that returns your LJ as a directory of XML files, which, I can't begin to even.
On the other hand, the traditional grep followed by sort|uniq -c|sort -rn reveals the following locations have been used but once each:
In front of the big speakers
Infernal Regions BBS
I'm in the furniture trade
IL 60614
Now the post about how to write the post about not making posts contains a paradox about the number of times part of the metadata about the post about how to write the post about not making posts has been used.
Which does not exist.