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

[digitalstarry]

Wow a news post with substance this time.

Thank you for removing the checkboxes. It feels nice to not see them anymore.

But

"If you've opted into Cyrillic services, you'll still be able to cross-post protected and screened comments."

Why? That still doesn't get rid of the problem and it still violates the TOS :/.

Have you fired your privacy violating/trolling staff yet?

[ladysunflow]

I'm guessing it's because the Cyrillic side of LJ actually wants this feature, is bigger and/or earns LJ more money (than non-Cyrillic users), ergo they win. I honestly don't care if it means LJ stays up and running as a service (unlike e.g. VOX).

[digitalstarry]

Yeah I understand they had to reach a compromise on this but its still very possible for a Cyrillic user to crosspost comments on somebody's locked entry.

[titaniumdiva]

Yeah, I'd like a way to find out who on my flist has opted into Cyrillic services, so I can limit their access.

[d_floorlandmine]

Nice point.

[pearl]

Make a blanket decision that anyone with a custom userhead is banned?
(Won't catch the ones who don't do that, and will punish the people who joined Cyrillic services for the userhead and then unsubscribed though...)

[marilla_pm67]

Yeah I understand that too, but can't they simply make it so that when a using don't want the option nothing, and I mean NOTHING from his/her journal can be crossposted? Is that so difficult to understand? I don't want any 'Cyrillic' user being able to crosspost anything from my lj ...

Pesting even more against LJ .... thinking even more to use that DW account I have.

Sam.

[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

[rose_cat]

Is that so difficult to understand?

REALLY. Are TPTB a bunch of contrary six-year-olds, or what?

[dawna]

The Terms of Service doesnt apply to the company. It applies to the users. Good god LOLOL

[gerg]

Users who post their own content to another site are breaking the TOS? How do you figure?

(Hint: they're not.)

[sodoesrachael]

Nope. I'm opted into Cyrillic services and the option to cross-post is gone from from any comments I leave, other than in my own journal.

[suededsilk]

OK, this is good. I wonder if it also blocks cross-posting if a Cyrillic user has automatic cross-posting set up. I suspect not. :/

[littlexdream]

I gather you will only see those boxes as a Cyrillic user IF you have enabled your Facebook and/or Twitter in your settings. If you haven't then that's why those boxes have gone.