Styles: rename /tag to /tags OR redirect /tags to /tag

[ninetydegrees]

Title:
Styles: rename /tag to /tags

Area:
styles

Summary:
When you want to go to the tags page of a journal, the URL uses the word 'tag' (e.g. http://dw-suggestions.dreamwidth.org/tag). I suggest it be renamed to 'tags'.

Description:
I can't count the number of times I've typed 'tags' only to get a 'We can't find that page' message.

Alternative suggestion: implement a redirect so that 'tags' works too and leave 'tag' as the default.

Poll #1836 Styles: rename /tag to /tags

Open to: Registered Users, detailed results viewable to: All, participants: 55

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
33 (60.0%)

Should be implemented with changes. (please comment)
20 (36.4%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
1 (1.8%)

(Other: please comment)
1 (1.8%)

Community Management: merge /community/settings and /manage/settings/

[ninetydegrees]

Title:
Community Management: merge /community/settings and /manage/settings/

Area:
community management

Summary:
Community admins have two different sets of community settings in two different places: /community/settings and /manage/settings/. I suggest the former be merged into the latter. OR the other way around: it might be more practical actually.

Description:
To provide more details for non-admins:
- On /community/settings, you mainly set membership access, posting access and adult content level.
- On /manage/settings/ you set various display preferences, all options related to comments and entries, adult content level again and other miscellaneous settings.

I know that there is a redesign planned for /manage/settings/ so I'd like to know what admins think of this idea before it's done.

Alternative suggestion: at least provide a link to /manage/settings/ from the Community Management page and from /community/settings.

Poll #1837 Community Management: merge /community/settings and /manage/settings/

Open to: Registered Users, detailed results viewable to: All, participants: 22

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
13 (59.1%)

Should be implemented with changes. (please comment)
1 (4.5%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
7 (31.8%)

(Other: please comment)
1 (4.5%)

Crossposting of non-public items to Facebook

[acb]

Title:
Crossposting of non-public items to Facebook

Area:
crossposting

Summary:
A means of posting one's own posts which are not open to the public to Facebook. Since one's Facebook feed is by default open only to one's own FB friends (and they're now adding LJ-style subgroup permissions) it's quite conceivable that one would want to share one's posts with authenticated DW/LJ friends and authenticated FB friends but not the general public.

Description:
One possible implementation would involve users linking their Dreamwidth account with a Facebook account (using Facebook Connect) and adding a tag (say, 'facebook' or 'fb_xpost' or 'xpost:fb') to posts they wish to have crossposted to their Facebook account. When the item is posted, at about the same time that LiveJournal crossposting is being handled, DW would crosspost the item to the user's Facebook.

The point would be to allow the item to be seen by the user's trusted Facebook friends without them having to obtain a Dreamwidth account. There would be two ways to implement this: the easiest would involve posting the post to Facebook's own note facility and keeping it on Facebook, effectively letting go of it. Thus people on Facebook would read/comment on the note, and people on DW would read/comment on the DW post. The facility could have a user-configurable option to put a link to the original at the bottom.

A more complex way would involve integration between Dreamwidth and Facebook's API. A Facebook interface would be effectively a Facebook application (albeit one running as an external Facebook Connect app), and would be able to see a connected user's Facebook UID and check whether they are connected to another user. This could be used to either:
a) have an interface tht runs within Facebook and presents the text of Dreamwidth posts, with comments, if the Facebook user is authorised to see them, or
b) integrating Facebook Connect users into the Dreamwidth user identity system (which allows OpenID users, so there is precedent for external users), and allows them to view posts and comment using their Facebook credentials.

IMHO, a system which integrates Facebook users with DW users in one of these two ways would be better for connecting one's various friend circles together.

Poll #1838 Crossposting of non-public items to Facebook

Open to: Registered Users, detailed results viewable to: All, participants: 42

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
7 (16.7%)

Should be implemented with changes. (please comment)
3 (7.1%)

Shouldn't be implemented.
13 (31.0%)

(I have no opinion)
19 (45.2%)

(Other: please comment)
0 (0.0%)