…on how I think a textbox should be filled in WordPress Admin… from simple anchor links… and when the content – in this instance long image links – is too long to be nicely contained… plus some little tricks and things I never noticed or noticed I’d noticed before…
This benefit of WP-RUBI is additional to the one of avoiding “the $8,000 mistake” of using unlicensed images, but for some sites will be much more important.
If the Digital Artists Alliance never amounts to more than a temporary reference point, the basis for a gesture of respect by some site operators toward an ideal, then that will be enough for me, but I invite anyone interested in exploring larger possibilities to join me.
1) The content of deleted tweets, if ever previously fetched and rendered, should remain “there” in an affected post’s post meta, and 2) it should be quite possible to emulate the rendering process programmatically, whether for the sake of presenting deleted tweets in a way that marks them as such and also harmonizes aesthetically with “normal” tweets, or whether for the sake of automating and customizing the display in other ways, without having to resort to hacks.
I discovered many non-rights-cleared images that I now think may have detracted from the posts in some ways, even if they initially seemed to make them more attractive or striking.
A primary use for WP-RUBI will be at sites where administrators have decided to remove images that have been used either without permission or under lapsed or lapsing usage licenses: Proper employment will help to reduce or eliminate legal and actual “exposure” quickly and easily, without harming the site’s search engine rankings and while preserving posts as originally composed, allowing for eventual restoration.
The Twitter default is for “cards” and “conversation” to display, but you can get rid of them either tweet by tweet or through a copy-paste-search-and-replace-re-copy-paste.
Contrary to my tentative conclusions of a month ago, I now understand at least one good reason to use output-buffering while writing WordPress code. Indeed, I now anticipate using the tool frequently.
My general impression is that, unless I have a very good reason for using it – probably involving the kind of script in which I’m not generally interested at this time – I should avoid it.
Seems fitting and probably should have been predictable – for a believer in the Iron Law of Irony – that an application meant to facilitate blogging, in this case by making aggregation of interesting material an easy “few clicks” operation, would annihilate my blogging. Anyway, is what happened.
