Facebook/Twitter Connect update, TxtLJ, Community rejection enhancement, Pingbacks

[news]

We've got important updates for you this week. As promised, we've made significant changes to Facebook and Twitter Connect integration that respond to your privacy concerns. We're also saying goodbye to an old friend (TxtLJ) and introducing a community moderation enhancement. There's a lot of ground to cover today, so let's get started!

Facebook

Comments

[hfcougar]

Exactly this. The control should lie with the owner of the journal to be able to disable cross-posting of comments, on all entries, regardless of security level or of whether or not the commenter wants to use Cyrillic services. Without the journal owner having to decide to make every one of their entries friends-locked, and without giving special exception to certain sets of users.

Yes, I do understand that in theory any entry that is not friends-locked could be found by anyone on the internet, and reposted elsewhere, or linked to, or its comments posted elsewhere. For that matter, if any of my friends wanted to be a complete douchebag, they could do so with my friends-locked entries as well. There's still a difference between what could happen if someone really wanted to go to sufficient effort, and what we give people a nice shiny convenient clickybox to do without really even having to think about it (or a box to click by accident, for that matter).

LJ is a service that people are paying to use. People aren't going to be satisfied with half-assed fixes when it comes to privacy, especially when the fix still lets a sizeable portion of LJ's users do whatever the hell they want. Plus, now the cat's out of the bag that if you want to circumvent this "fix" all you have to do is opt into the Cyrillic - what's the point then?