eftychia: Me in poufy shirt, kilt, and Darth Vader mask, playing a bouzouki (vader)
Add MemoryShare This Entry
posted by [personal profile] eftychia at 03:32pm on 2009-05-11

Didn't fall sleep after all, which puts my evening plans in jeopardy yet again. Finishing up some mostly-written entries I had sitting around while I wait for the next spell of 'maybe I can fall asleep now' ...

Sometime after I started crossposting and realized that I couldn't use <lj user="XXXX"> to refer to people because that would generate a link to that username local to each site (which may or may not exist, and may or may not be the same human for each site on which the username exists), I posted a suggestion in the LJ suggestion area requesting that the syntax of that tag be expanded to be able to refer to 'foreign' users (e.g. to point to an IJ user in an LJ entry, or vice versa). AFAIK, LJ never did anything with it (please correct me if you know I'm mistaken). When composing an entry in my text editor[1], I've been pasting in a chunk of HTML for a fictitious user named 'USER' on each site, and doing a global search-and-replace to substitute the name I want to use. (This is a bit more annoying when posting a comment via the web, since (AFAIK) the text-box thingie in my broswers has no search-and-replace feature, but fortunately it doesn't come up as often there because in comments I'm referring to folks on the same site I'm leaving the comment on, more often or not, but when posting an entry and referring to a *J user, they'll be a 'foreign' user on all but one of the sites the entry is crossposted to.)

Dreamwidth, wanting to facilitate cross-site functionality as much as is feasible, went ahead and implemented that feature right away, of course. That pleased me, because it seems like Right Thing designwise, but the irony is that I'm still not using it. Why? Because until all the other sites I crosspost to either (a) switch to using the DW software or (b) add that feature as a patch to the LJ software (unlikely unless LJ decides to add it, and even then some sites never upgrade to a newer release of the LJ code or take a long time to do so), I'm still posting each entries to a bunch of sites that lack the feature and only one that has it.

[ETA: [info]denise reminded me that if I were using the crossposting feature built-in to DW, it would automatically expand the DW version of the foreign user tag to the same chunk of code I'm pasting in by hand as described above.]

I'm still glad they did it, and it'll come in handy ifwhen I need to refer to a non-DW user within a DW comment (likely to happen sooner or later). I'm just a weensy bit frustrated that even though someone implemented what I asked for (whether they got the idea from my suggestion or elsewhere[2]), I don't get to really take advantage of it. (If anyone else is using that feature, my pleasure at their life being a wee bit easier because DW did the more-useful thing will exceed my frustration.)

[1] Are there Opera and/or Firefox settings/plugins/whatever that'll stick a version of vi in there whenever I click in a text-entry box? That would be convenient.

[2] I think they did get it from me, as, IIRC, one of the DW folks replied to my suggestion when I posted it on LJ -- but it's entirely possible (likely, even) that the idea occurred to several people independently (that is, I think it's "obvious" anyhow) and I was just the first (again, IIRC) to post it as a suggestion there ... and it doesn't really matter either way, as there's no glory in getting credit for seeing a need+solution that obvious. But in my own head I think of it as "my" feature simply because I spent so long wanting LJ to implement it and now it exists (so it's a minor source of warm fuzzies regarding DW, for me). Outside of my skull, any credit goes to the person who actually got around to coding it, methinks.

There are 7 comments on this entry. (Reply.)
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
posted by [staff profile] denise at 08:44pm on 2009-05-11
FYI, if you're crossposting natively from within DW, you can use it and the crossposter will expand the HTML necessary so that all crossposted entries will just Do The Right Thing.
eftychia: Cartoon of me playing electric guitar (debtoon)
posted by [personal profile] eftychia at 09:26pm on 2009-05-11
Oh, right, I should have mentioned that, having run across somebody talking about observing that feature in action! Whoops.

I haven't tried using the native crossposter yet (not sure whether I will or not -- though that one detail is a bit of a motive for trying it -- that and (do I understand correctly?) being able to edit the DW copy of an entry and have the changes propogate to the crossposted copies automagically?).

Between posting QotD entries with a cron script, having specially-tagged email to myself piped in via Procmail, and wanting to use vi to edit entries I compose at the computer, I've continued using the shell script I'd been crossposting with before DW came on line, which in turn calls Clive. I've been meaning to investigate the DW crossposter though, to check out how many of the features I had in mind to put into my DIY one "someday" you've already done.

Hmm. Since I do need a command-line client I can direct a file into, I guess setting up post-by-email to auto-crosspost and using my MUA as the command-line front end would work, huh? Time for me to get around to exploring that bit.

There is, of course, the matter of passwords and security and effectively asking anybody who has friended me on LJ and posts friendslocked entries to trust you (and the rest of DW) as much as I do. I'm not sure whether there's a technically-good solution to that problem unless I set up a second account on each site, and use one account only for (cross)posting and the other only for reading and commenting ... and all my strictly-cautious friends who want to read my posts on their friendspage use access filters so I can be in their default view but not (under my posting ID) see their locked entries. Am I caught up to the stage folks discussing this elsewhere have reached, yet, or am I still a week behind? (I've given DW my LJ password for the importer, but there I can change it after each import attempt finishes running, so the hole isn't left continuously open.) The other solution would be a standalone crossposting client that runs entirely on each user's machine, which winds up just being , in principle, a more polished and featureful version of the clumsy script I've been using.

Anywho, I suppose I ought to go set up some test accounts hither and yon, so I can explore the DW crossposter without spooking my more careful friends. After I've slept. When I'm this babbly, I clearly need sleep before trying to do anything too thinky.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
posted by [staff profile] denise at 09:34pm on 2009-05-11
that and (do I understand correctly?) being able to edit the DW copy of an entry and have the changes propogate to the crossposted copies automagically?).

You do :)

And yeah, we're still discussing the best way to handle passwords/authentication for crossposting. Nothing perfect's popped up yet.
eftychia: Cartoon of me playing electric guitar (debtoon)
posted by [personal profile] eftychia at 09:51pm on 2009-05-11
Sweeeeet!!! I'd been thinking of ways to approach that but hadn't gotten as far as writing any pseudocode yet. Nice!

The authentication issue is a thorny one, for sure. What's the best place to drop in on a conversation about it so I'm not just suggesting things that have already been wrestled with? One of the communities here? (I haven't seen any mailing list traffic the last few days.)

I've got an idea that may have already been brought up, and has the downside that it requires convincing all the other sites to make a significant change: let users set up alternate, reduced-privilege passwords so they could give DW a post-only (no reading anything locked, no changing other passwords) password for their LJ account instead of their main LJ password. Getting the tiered-access password code propagated everywhere would be a heck of a task though.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
posted by [staff profile] denise at 05:20am on 2009-05-12
We don't really have a conversation going per se -- it's kinda been scattered. Some kind of limited-access authentication scheme is definitely in the cards, though, with a fallback to the 'old' way of doing it if the site doesn't support that kind of authentication.
siderea: (Default)
posted by [personal profile] siderea at 05:11am on 2009-05-12
And yeah, we're still discussing the best way to handle passwords/authentication for crossposting. Nothing perfect's popped up yet.

I'm increasingly favoring the plan of sending a team of ninjas to break into LJ's datacenter and patch their code with an OAuth implementation in the dead of the night.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
posted by [staff profile] denise at 05:19am on 2009-05-12
I approve of this idea, and would like to subscribe to your newsletter.

(I'm actually hoping to work with [livejournal.com profile] tupshin to fix up a lot of cross-site authentication stuff both on LJ and DW, but I am uncertain about how far he's going to be a). willing to go with it and b). able to get Product to go along with it.)

Links

January

SunMonTueWedThuFriSat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24
 
25
 
26
 
27
 
28
 
29
 
30
 
31