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

[darkblysse]

If you're a community maintainer, you can now offer an explanation and/or further instructions whenever you reject a user who requests to join your community (similar to when you reject an entry submitted to a community). Just type in your explanation in the text box before you hit the "Reject" button.

HALLE-FUCKING-LUJAH.

I am so sick of people obviously ignoring the community's rules and then PMing me with "But why was I rejected ;_;" NO MORE, YOU BASTARDS.

[lafinjack]

YOU STILL HAVEN'T TOLD ME WHY I WAS REJECTED

[accioslash]

+ eleventy billion.

[astronewt]

As an extra note on the community rejection feature -- maintainers, if you want to be notified of when another maintainer rejects someone from a community you co-maintain, click the Track button on the comm's Profile page. You'll see a new notification has been added for that at the bottom.

You won't get notified if you're the one that performed the rejection, but you'll get notified if another maintainer rejects someone.

[darkblysse]

Ooh, that's spiffy. Thanks~

[azurelunatic]

Oooh, excellent.

[snowweisz]

Oh this is pretty cool. Thanks! Also, do you think this could ever be implemented for the moderation queue too?

[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.

[rheakurokawa]

thank you

[moreteadk]

I'm very glad to see the changes on the crossposting issue! That certainly took care of my worries, and I'm very glad you listened to the concerns of the userbase.

But, We've disabled the ability to cross-post comments on privacy-protected entries and screened comments for non-Cyrillic users.

Just out of curiosity, why only non-Cyrillic users? Is privacy different in Russian or what?

[alextiefling]

In Russia, privacy controls you!

[hellotini]

this.

[andy]

From how it seems to me, Russian userbase is generally less concerned about privacy, and also less concerned about this issue in particular, because the overwhelming majority of the content/entries is public.