Kink meme posts were making the script take forever (sooooo many comments) so I updated the code to be faster. Get the new version here: LJ/DW Title Rewriter.
I don't work on any newsletters right now, but I recently had to post a bunch of links to Delicious using a common newslettering format: all the bookmark titles are formatted as "username: post subject" and all the links are clean (no style=mine, etc). This should be really easy to do, but too often it involves tedious manual c&p work to get the username in there when using the clean link*. If a journal uses custom comment pages, instead of having the username in the post title, often the very useless user-specified "Name" is in there. And on comms, only the comm name appears, never the poster name.

So this script fixes that! Any time you load an entry page in DW or LJ, it makes a quick call to the format=light version of that page to get the "username: post subject" or "username in community: post subject" info, and then sets that as the current page title. When you go to bookmark that page to Delicious, your Delicious posting tool should now automatically fill in a more useful link title for you.

LJ/DW Title Rewriter

It should work out of the box in Opera, but I haven't tested that. I forget what Chrome's user script limitations are, but I suspect it might not work in Chrome. I can make a Chrome version, though, if anyone is interested enough to speak up.

Let me know if you find any bugs and then I will fix them!

*ETA: This script doesn't change the URL! I only mentioned the clean links bit because the two requirements of clean links AND "username: post subject" format are often mutually exclusive. It's pretty easy to get that format (for non-community posts, anyway), but only if you dirty up the URL with ?format=light or ?style=mine.
One of the hotbutton issues for newsletters is whether to cut or uncut newslettter issues, especially when they are long. [community profile] the_dw_herald recently came up with a possible solution: Display Options.

So, I guess, the idea is to create a CSS class for your newsletter like:
<div class="newslettercommunity-content"> [body of newsletter issue a.k.a. the content] </div>
And have your readers add a code in their journal's custom CSS to hide the body of your newsletter issues if they prefer their newsletter cut:
.newslettercommunity-content {
display: none !important;
How very cool! Anyone thinking of possibly testing this out? And how many are thinking of creating a sub-CSS class for each newsletter categories, e.g. Fiction, News, etc., and have their readers customize what they would like to be see for the newsletter? Just me then?

Style Credit

Expand Cut Tags

No cut tags