On the latest LJ thing

[norwich36]

I've seen a lot of people who are upset about the possibility of someone linking to their posts (especially their locked posts) via the new "post to facebook/twitter" function, and I agree that that possibility is worrisome--I for one don't want my LJ stuff linked all over facebook, even though I'm very pseudonymous here--but I wanted to point out that retreating to DW is not the only option. The very first comment on the LJ news post announcing this is a link to a Greasemonkey script that disables linking to Facebook/Twitter via comments, and it seems to be working for me.

Edited to add: Apparently I am wrong and all the script does is block you (the script user) from seeing it in comments, not everybody--so it isn't really a fix. Sorry about that. It still is useful, I guess, for people afraid they will accidentally crosspost comments, but it doesn't prevent the people commenting in your journal from crossposting.

I'm actually more upset about the no slashes in tags thing--but I hope that's a bug that can be fixed, not a permanent change.

Comments

[daisydumont.livejournal.com]

i don't have News on my f-list because i usually don't understand what they're talking about. (i'm not stupid, just, ahhh, technically challenged, and both my computer-jockey boys have left home.) after reading that post, i wasn't sure if there's any risk of my showing up at FB in other people's links, when my lj is locked down. my comments to them on public posts, or even their own locked posts (if they override the lockage), could show up though, am i right?

thanks for the heads-up, nora.

[norwich36.livejournal.com]

I am actually not sure how it works. I would go read through the comments on the LJ announce post if you have time--I don't actually have time to do it at the moment.

[frelling-tralk.livejournal.com]

I've noticed a lot of people on my flist getting really concerned about this, so it's good to know there's an opt-out option anyway. But then where would LJ be without the annual freak-outs *g*

And I think they've said they're working on the slash tags? So one of my comms said today, so I think it's just a temporary glitch

[norwich36.livejournal.com]

See huzzlewhat's comment below--apparently I was wrong about the way the greasemonkey add on works, and it only blocks it for you, not for commenters. :-(

[nyxocity.livejournal.com]

No slashes in tags? Since when?

[norwich36.livejournal.com]

A lot of people have been reporting that, yes. And since yesterday, I think?

[huzzlewhat.livejournal.com]

As far as I can tell, the script just blocks the ticky-boxes appearing on your LJ; it doesn't prevent the cross-posting by commenters. I could be wrong, though. I'd love to be wrong.

[huzzlewhat.livejournal.com]

fwiw, I've got the Twitter/FB repost boxes appearing right below my message screen when I respond.

[norwich36.livejournal.com]

Well, shoot. I went back on the original link and it actually says that it doesn't block crossposting--I guess I should read more carefully. Thanks for the heads up.

[clari-clyde.livejournal.com]

The way I understand it:

If the post is public AND the commenter’s default is to crosspost comments, the tickies are checked and the commenter has to uncheck them.

If the post is f-locked AND the commenter’s default is to crosspost comments, the tickies appear but are unchecked and the commenter has to check them.

If the commenter’s default is to not crosspost comments, regardless of whether the post is public or f-locked, the tickies will be unchecked and the commenter has to check them.

And as far as I can see, since there is no FB/Twitter account linked to the my LJ account, I can’t check them no matter what.

I guess the issue is that people are upset that when people post comments in their LJs, they can also post their comments elsewhere too. But who owns a comment — the person posting vs the person commenting — is prolly an issue for places like Fandom Wank to mull over.

[norwich36.livejournal.com]

I agree that people own their own comments. My main issue is that (just based on a brief skim of the new FAQ) it appears that at least portions of locked entries may appear on FB when someone crossposts their comments there--which is a big NO as far as I'm concerned. I mean, people could already just cut and paste links to public entries if they wanted to, which is theoretically fine with me--they are public, after all--but I don't want anyone having access to my locked posts because some dillweed felt the need to crosspost their brilliant comments.

[clari-clyde.livejournal.com]

Where are you getting that contents of the post will be crossposted? Because I look at the FAQ (http://www.livejournal.com/support/faqbrowse.bml?faqid=279) and it says:

“For comments, the Facebook update will say "[Your name] posted a new comment to 'clari_clyde' at LiveJournal.", and will contain the subject and text of the comment, as well as a link to the entry. The Twitter update will contain either the subject of the comment or a snippet of the comment itself, as well as a short URL directly to the comment on LiveJournal.

“Please note that you can choose to have comments posted to protected entries cross-posted to Facebook and/or Twitter, and the text of those comments will appear to all your followers on those sites, but clicking the link will not show the full entry to anyone who does not have access to view it. The cross-posting options will automatically be unchecked when commenting to a Friends Only or Private post, so that no protected comments are sent to Facebook or Twitter by accident.”

[bientot.livejournal.com]

If you haven't seen it yet - There's a poll on this issue (http://community.livejournal.com/thequestionclub/86168785.html) - the outcome is pretty clear, but signal boost can't hurt. And LJ will be aware of the results!