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.
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.
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.
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.
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.
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.
I approve of this idea, and would like to subscribe to your newsletter.
(I'm actually hoping to work with 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.)
(no subject)
My bad habit of thinking aloud
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.
Re: My bad habit of thinking aloud
You do :)
And yeah, we're still discussing the best way to handle passwords/authentication for crossposting. Nothing perfect's popped up yet.
Automagic edit propogation
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.
Re: Automagic edit propogation
Re: My bad habit of thinking aloud
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.
Re: My bad habit of thinking aloud
(I'm actually hoping to work with