siderea: (Default)
[personal profile] siderea2017-04-10 09:09 pm

Page Statistics 2: Electric Boogaloo

Title:
Page Statistics 2: Electric Boogaloo

Area:
entries

Summary:
Native journal stats, like LJ used to do, only not horribly invasive like LJ. How many, not whom. Also integrated into the DW user interface.

Description:
Way back when, somebody else suggested, in a suggestion titled Page stats (http://dw-suggestions.dreamwidth.org/570175.html), "something like LiveJournal's My Guests feature", and the commenters here promptly set the suggestion on fire and then drowned it. The My Guests feature of the LJ Stats page makes *reading* journals less private, and gave many DW Suggestion commenters the heebee-geebees.

Unfortunately, that was the end of the proposal to implement any of the LJ Stats Page here. Unfortunately, because the LJ Stats Page also had lots of other useful analytics information, that was in aggregate and didn't violate anybody's privacy. For instance, from my LJ Stats page I just discovered that my LJ typically gets about 35 daily hits to my journal's RSS feed – information that would otherwise be utterly invisible to me. Since in the past I've wondered if anybody cares about RSS, that is usefully informative to me. For another instance, I am able to see how many visitors – not, mind you, LJ users, just unique visitors – came to a given post. If I had the same stats here on DW, I would be able to see how my efforts to move my readers from LJ to here were working.

When last this was proposed, one of the questions a commenter reasonably asked was "How is it different from the Google stats feature available for paid DW accounts?"

1) It doesn't involve Google for one thing. I have two big problems with Google Analytics:

1a) It is, to me, a much bigger privacy violation than My Guests ever was. My Guests was optional: if you ever wanted not to be counted, you turned it off and you never appeared in anybody's My Guest report. I, as a reader, have no way to opt out of GA – except to use a script blocker to clobber GA, which I in fact do, because....

1b) Google Analytics' degrades site performance. I have to block the GA scripts at my browser, because otherwise, from time to time, page loads start hanging on trying to communicate with google-analytics.com. I don't want GA on my journal both because I don't want to inflict on my readers a privacy compromise I don't want inflicted on myself, and I don't want to inflict on either me or my readers the page load times GA periodically (or is it always? as I said, I block it) causes.

2) As per 1b above, GA is client-side and third party. I don't want this sort of functionality coming through *any* third-party javascript. It will always tax the user's browser and internet connection, and expose information to a third-party. I have no interest in trusting any third-party with, for example, statistics *about my locked posts* the existence of which should be a private.

3) Not having a GA account I can't say what it includes in its reports, but knowing what I do about its implementation, I'm guessing it has no way to tell you *the number of times your post appeared on other parts of the site*. AFAIK, GA only knows – only *can* know – about the concept of "webpages". LJ's Stats would give you *two* numbers: the number of unique visitors to a post's page *and* the numbers of unique viewers of your post _in all the other places it appears on LJ_, such as on friends pages, your own Recent Entires pages, your Calendar pages, etc. LJ Stats leverages LJ's knowledge of its own info-architecture to come up with stats that GA can't.

Finally, it would be great if the interface for such a thing were integrated into the general DW journal interface, such that journal owners would have a contextual stats icon/link (visible only to them) wherever appropriate, that takes them to the corresponding stats page. For instance, such a link would appear on posts, and would take one to the stats page for that specific post. One's Calendar would have it on the day, month, and year views, and take one to one's corresponding day, month, and year stats pages. And that's not something that GA or any third-party javascript-based analytics implementation could manage.

More Details

When last this came around, it became clear most commenters didn't know what LJ did provide. Here's an overview:

There are four top level categories to the Stats page that I propose are of interest to DW: Journal, Comments, Entries, and RSS Readers.

The Journal page shows stats for your whole journal, breaking it out by number of total visits, total unique vistors, and how many of those unique visitors were logged-in LJ users. It allows you to view this information by either your journal itself, or your journal plus all friends pages on which your posts appear, and it allows you to drill down in either of these views to any year (shows bar chart by month), month (shows bar chart by day), or day (shows bar chart by hour). This last allows one to get a sense of on what days and at what times of the day one's readers are seeing one's journal.

The Comments page shows the stats on numbers of comments and numbers of commenters. Like the Journal page, you can drill down by time span.

The Entries page shows the stats for a given entry (post). It defaults to the most recent entry in your journal, has a list at the bottom of your ten most recent posts with links to their stat pages, for user convenience, and a text box in which you can put the URL to any of your entries to get the stats for it (not the most convenient of user interfaces). For a given entry, it shows Visits, viewers ("Who Viewed"), and Comments. Visits breaks out by Entry Views, All Visitors and Livejournal Visitors. "Entry Views" is the other sense of "entry": when that page is the page-of-entry of a reader to LJ – what happens when somebody follows a link somewhere else, like Twitter or Tumblr or FB or an RSS reader or an email, to a post of yours. That gives one a sense of how much traffic is being driven to a post by virality elsewhere. Visits also allows drill down by year/month/day, same as above. "Who Viewed" gives a break down between the number of all viewers of the post vs. the number of the subset that are Friends of you - it shows you whether it's just Friends reading your posts or other people. Also allows drill down by year/month/day. "Comments" shows comments vs number of unique commenters for the post, with year/month/day drill down.

The RSS Readers page shows a chart of number of requests to one's RSS feed, with drill down by year/month/day.

Poll #18206 Page Statistics 2: Electric Boogaloo
Open to: Registered Users, detailed results viewable to: All, participants: 61


This suggestion:

View Answers

Should be implemented as-is.
42 (68.9%)

Should be implemented with changes. (please comment)
5 (8.2%)

Shouldn't be implemented.
1 (1.6%)

(I have no opinion)
13 (21.3%)

(Other: please comment)
0 (0.0%)

feicui: (Default)
[personal profile] feicui2017-01-14 10:24 am

Allow users to specify an account as a roleplaying account

Title:
Allow users to specify an account as a roleplaying account

Area:
accounts, statistics

Summary:
Allow users to specify an account for roleplay without affecting paid account services.

Description:
This is a suggestion mainly for statistical purposes! Dreamwidth has an active, sizable roleplaying community, a consequence of which is that there are a lot of "character accounts" scattered across the site. As someone who's very curious about DW's site statistics, I can't help but think that means there's a lot of essentially fictional data skewing things one way or another.

If possible, I'd like for roleplayers to be able to specify an account as being made for roleplay. It would have to be in a way that doesn't affect paid services, since some get paid/paid premium accounts and some don't. In addition to being able to choose it during account creation, there would also need to be an option for existing accounts to "switch over", since there are many, MANY existing character accounts.

Challenges involved: oh boy! I'm not at all familiar with site coding, especially Dreamwidth's, so I can't imagine how complicated this might be. I also don't know how many people would actually use this option, but I thought I'd throw this out there anyway.

Poll #18026 Allow users to specify an account as a roleplaying account
Open to: Registered Users, detailed results viewable to: All, participants: 56


This suggestion:

View Answers

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

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
21 (37.5%)

(Other: please comment)
1 (1.8%)

skakri: (Default)
[personal profile] skakri2012-02-05 06:41 pm

OpenGraph implementation

Title:
OpenGraph implementation

Area:
frontend, accessibility, cross-site data sharing

Summary:
It would be nice if sites, that use OpenGraph metadata, could use our provided data, instead of crawling the page in question and collecting arbitrary data (article image, article title, author, etc.)

Description:
Sites that support OpenGraph Protocol (http://ogp.me/), like Facebook and Google+ would benefit from already provided data; that would help those sites 1) categorize that data (entry title, tags), 2) provide correct information, when posting to FB or G+ (title, image), instead of full page title (username | post, for example).

Example - http://skakri.grab.lv/2360053.html (check source; done: profile username, entry image, entry title, publishing date and used tags). Could be implemented also in profile pages - user.domain.tld/profile

Poll #9490 OpenGraph implementation
Open to: Registered Users, detailed results viewable to: All, participants: 40


This suggestion:

View Answers

Should be implemented as-is.
5 (12.5%)

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

Shouldn't be implemented.
3 (7.5%)

(I have no opinion)
31 (77.5%)

(Other: please comment)
0 (0.0%)

Adding Jersey, Guernsey, and Isle of Man to profile

Title:
Adding Jersey, Guernsey, and Isle of Man to profile

Area:
profile

Summary:
Adding the Crown Dependencies of the Channel Islands (Jersey and Guernsey) and Isle of Man to the location drop down on the profile.

Description:
I'm sure that users from these places can easily select the UK as their location, but I suspect that they might like the option of their specific island as well. If nothing else, I doubt having the option would be detrimental.

Poll #9055 Adding Jersey, Guernsey, and Isle of Man to profile
Open to: Registered Users, detailed results viewable to: All, participants: 75


This suggestion:

View Answers

Should be implemented as-is.
53 (70.7%)

Should be implemented with changes. (please comment)
2 (2.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
20 (26.7%)

(Other: please comment)
0 (0.0%)

Better multilingual entry support

Title:
Better multilingual entry support

Area:
entries, search

Summary:
Allow entries to be tagged with the language(s) that they are composed of. This can be used to power more interesting things around the site.

Description:
Entries composed of written or spoken material (text, images of writing, audio, video) usually have one or more languages in which the material is presented. Allowing entries to be voluntarily tagged by their owners to describe the language(s) they are using might allow some interesting features to be developed based on entry tagging.

If a particular spelling appears in more than one language, specifying the language of the entry in site search could help find the thing someone's looking for.

Statistics on actual use of the site by users who speak different languages might be helpful to staff, especially if the technical barriers to offering the site in translation are overcome.

It could help users better connect with people who speak their same language, especially users whose preferred language is in a minority on the site.


What would the user interface be like? A whole long list of possible languages could a) be unwieldy, b) might also leave out languages used by actual site users (sign languages and constructed languages spring to mind as languages that might be left out of even a fairly exhaustive list of languages, and entries with embedded video might have sign language, and fannish communities are reasonably likely to include Tengwar and Klingon, and goodness knows there are probably more use cases that I know nothing of).

One way to do it might be like the tags interface, where something can be typed in, and attempt to autofill from a preset list, but accept new entries gracefully. If designed properly, unique data entered here on public entries could be logged, collated, and presented to an administrator on a regular basis for review; items that are found to be actual common languages not present on the list could then be entered.

Any site function that involves searching by language should allow for synonyms -- three different people might use "tlhIngan Hol", "pIqaD", and "Klingon" to mean the same language -- to say nothing of the typos. There should be a way to bundle known synonyms and known typos -- and also a way to override this bundling.

Another challenge is that people might not tag all their entries (to say nothing of back entries). How hard/expensive would it be to autodetect languages? Failing autodetection, could a default be set by user, like the last language they used?

Poll #7733 Better multilingual entry support
Open to: Registered Users, detailed results viewable to: All, participants: 66


This suggestion:

View Answers

Should be implemented as-is.
38 (57.6%)

Should be implemented with changes. (please comment)
4 (6.1%)

Shouldn't be implemented.
2 (3.0%)

(I have no opinion)
20 (30.3%)

(Other: please comment)
2 (3.0%)

danicast: (Default)
[personal profile] danicast2011-06-20 09:26 pm

Page statistics

Title:
Page statistics

Area:
features

Summary:
I would like to have something like LiveJournal's My Guests feature. Is free to use (you don't have to be a paid member to use) and it's very useful. Thanks!

Description:
I would like to have something like LiveJournal's My Guests feature. Is free to use (you don't have to be a paid member to use) and it's very useful, it shows how many people visit each one of your entries, who they are, how many people visited the whole journal. Is so useful! And all users have. I think we could have something like that here. Thanks!

Poll #7710 Page statistics
Open to: Registered Users, detailed results viewable to: All, participants: 65


This suggestion:

View Answers

Should be implemented as-is.
11 (16.9%)

Should be implemented with changes. (please comment)
7 (10.8%)

Shouldn't be implemented.
31 (47.7%)

(I have no opinion)
10 (15.4%)

(Other: please comment)
6 (9.2%)

Statistics: link /stats and stats/site

Title:
Statistics: link /stats and stats/site

Area:
site

Summary:
There are two pages for stats: http://www.dreamwidth.org/stats and http://www.dreamwidth.org/stats/site. I wish there was a link from one to the other, and that the second page was added to the site map.

Description:
Well, I've said it all. :)

Poll #6527 Statistics: link /stats and stats/site
Open to: Registered Users, detailed results viewable to: All, participants: 63


This suggestion:

View Answers

Should be implemented as-is.
48 (76.2%)

Should be implemented with changes. (please comment)
4 (6.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
10 (15.9%)

(Other: please comment)
1 (1.6%)

yvi: Kaylee half-smiling, looking very pretty (Default)
[personal profile] yvi2010-04-01 10:53 am

Anonymous stats on tracking

Title:
Anonymous stats on tracking

Area:
Stats/Notifications

Summary:
Since Dreamwidth allows users to track things, it might be interesting to have a page where we can look up how many people are tracking what things.

Description:
Dreamwidth users have the option to track (get inbox/e-mail notifications) of certain things: posts, comments, posts with certain tags,...

It might be of interest to know how many people are tracking what in your journal: how many are tracking post X, how many comments on post Y, are there people getting notified when I post using the tag "dreamwidth dev", etc. This suggestion has been brought up on Livejournal before: http://community.livejournal.com/suggestions/969654.html

For privacy reasons, I am suggesting implementing this completely anonymously: only the number of people tracking should be shown, no further identifying data.

As for the "security by seeing no-one tracking you" raised in the LJ suggestions community, a note on the page, as suggested here: http://community.livejournal.com/suggestions/969654.html?thread=15741878#t15741878 ("these stats have been gathered from XYZ however please note that they do not include who is tracking your journal using different methods") might be a good idea.

This would also fit in neatly with http://dw-suggestions.dreamwidth.org/253742.html , as part of a "personal stats" page", in my opinion.

Poll #2594 Anonymous stats on tracking
Open to: Registered Users, detailed results viewable to: All, participants: 44


This suggestion:

View Answers

Should be implemented as-is.
23 (52.3%)

Should be implemented with changes. (please comment)
6 (13.6%)

Shouldn't be implemented.
7 (15.9%)

(I have no opinion)
8 (18.2%)

(Other: please comment)
0 (0.0%)

ciaan: revolution (Default)
[personal profile] ciaan2010-02-10 07:54 pm

Comment statistics

Title:
Comment statistics

Area:
entries/comments/circle

Summary:
I would like to be able to know statistics of who has commented in my journal.

Description:
There is an external app that can be used on LJ/DW to see who has commented in your journal and how many times they have commented. I would like the site to have a built-in feature similar to that. The two stats I would most like to be able to run are:

1. A list of everyone who has commented in my journal ever, and how many times each account has commented, ordered by number of comments.

2. A list of everyone I have added to my reading/access circles, and when the date was that each of them most recently commented on my journal.

Probably there are other stats other people would like to see.

Poll #2261 Comment statistics
Open to: Registered Users, detailed results viewable to: All, participants: 44


This suggestion:

View Answers

Should be implemented as-is.
25 (56.8%)

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

Shouldn't be implemented.
5 (11.4%)

(I have no opinion)
12 (27.3%)

(Other: please comment)
0 (0.0%)