?

Log in

Suggestions Box
Want to improve LiveJournal? Contribute your ideas!
Recent Entries 
3rd December 2016 @ 06:52 pm - Fix the WYSIWYG editor
default

Title
Fix the WYSIWYG editor

Short, concise description of the idea
The WYSIWYG editor must generate HTML without any presentation markup by default.

Full description of the idea
Currently, LiveJournal offers two ways to post; the classic HTML editor where the poster sees all markup and has to keep it in mind, and the rich text editor where the poster clicks buttons and the editor generates markup.

The markup generated by the rich text editor is often excessive and non-semantical, especially if formatted text is copy/pasted from Word or another web site. Posters cannot easily see that their post specifies white background, gray text, a fixed font size or a hardcoded font face such as Proxima Nova or Helvetica Neue.

Such posts are annoying when viewed in a customized Friends feed or even in the list of community posts.

The ru_chgk community, for example, has an explicit rule against excessive and obnoxious markup, and it is violated on a regular basis. When called out, posters retort that they are “just typing text into the post message window”.

I hereby suggest the following list of modifications to the WYSIWYG editor:

* As long as the author does not use any of the visual formatting controls, the post shall not contain any presentation markup, as deprecated in HTML 4 and obsoleted in HTML 5, nor style="…" attributes.

* Pasting from clipboard, when the clipboard contains formatted text, shall strip all formatting, unless the clipboard copy source was the current instance of the LJ visual editor. (That is, content copied from another site, or another post, or Word, shall lose all formatting.) This must be tested in all major browsers.

* If the author *has* invoked any of the visual editing controls, there shall be a way to remove any applied formatting in a way that removes the previously inserted style attributes or reduces their scope.

An ordered list of benefits
  • Readers benefit by seeing all community posts in a reasonably consistent style.
  • Posters also benefit by being confident they are not unknowingly annoying their readers.
  • Moderators benefit by having less yelling to do.
  • The Internet benefits by becoming closer to the ideal of semantic markup.
  • Kittens benefit by not being killed by gods every time somebody posts in 12px #333 Proxima Nova on a white background at 19.6px line height.
An ordered list of problems/issues involved
  • Internet providers and mobile carriers indirectly lose by having less data to transfer and therefore less money to extort from users.
18th November 2016 @ 05:49 pm - Allow users to set OG properties per post
ffxv-moogle:- official

Title
Allow users to set OG properties per post

Short, concise description of the idea
When making a post to be shared on facebook, allow users' open graph tags to be recognised by the facebook crawler.

Full description of the idea
I run a _daily picture community which we share to our associated facebook page. For a few weeks now, the links have been presenting with the post title, the LJ logo, and the poster's username over a greyed out image from the post (not always the same one, making it impossible to predict), Previously, it would pull the first image preview being the first image from the post. In both cases, the title of the post appears under the image as does the first few words of the post.

When I tried to change this by using open graph tags, it then reverted to using the open graph tags in the LJ code, overriding any customisation and the best guess of the facebook crawler. The link had the LJ logo and welcome text, not anything to do with the community or that particular post.


I would like to be able to use the open graph tags in my post to direct the crawler to the image I would like it to. Because our facebook community users don't always click on the link at the time they see it, having the extra text there impedes their ability to engage and since the change we have had fewer people coming over to LJ and commenting. It also means that, even if I had maintainer access and was able to set up auto-cross-posting to the fb page, I wouldn't be able to control the content of the posts which were automatically cross posted. For people who don't know how to use open graph tags, their links would go back to the old way, so they could predict what image would be used.

An ordered list of benefits
  • Greater compatibility with services which use open graph tags.
  • Ability for users to control how their links look on other sites.
  • Ability to prevent NSFW images being used as link images on other sites.
An ordered list of problems/issues involved
  • Time recoding and testing with the facebook test crawler.
  • Confusion for some users who are not familiar with open graph tags or who might not know why their links look different again.
1st November 2016 @ 09:52 pm - Bug about replies

Title
Bug about replies

Short, concise description of the idea
Someone replied my comment on a blog, the blog author not published the comment yet, on my messages page it shows "(You are not authorized to view this comment)", but i can read the comment on my e-mail notification.

Full description of the idea
Someone replied my comment on a blog, the blog author not published the comment yet, on my messages page it shows "(You are not authorized to view this comment)", but i can read the comment on my e-mail notification.

An ordered list of benefits
  • user privacy
An ordered list of problems/issues involved
  • user privacy
3rd October 2016 @ 10:52 pm - Logging in from the Feed page
default

Title
Logging in from the Feed page

Short, concise description of the idea
When logging in from the Feed page, redirect to Friends if that’s the user’s preference

Full description of the idea
There is a profile preference allowing one to choose between the Friends page and a Feed page. There are various reasons to prefer Friends and never want to see Feed.

Once in a while, my login cookie expires and I get logged out. When that happens, the next time I visit my Friends page, I get redirected to Feed. I catch a glimpse of irrelevant posts and advertisement in an unfamiliar page style, say a bad word or two, wash my eyes in acid, and click the Login link in the corner. Then I enter my user name and password, check [x] Remember me, and finally click Log In.

After that, I’m logged in but stay on the Feed page.

I suggest that, when:

* the login form is activated from a user’s Feed page,
* if that exact user logs in,
* and that user’s preference is for the Friends page,

then logging in should return a redirect to the user’s Friends page.

Alternatively, the implementation of the Feed page needs to be finished. It should be styled with the user’s (or reader’s) preferred scheme, theme, and custom CSS; and, when the scheme is Lynx, avoid setting a font face, size, color, or background. If these conditions were satisfied, I would not be as averse to using the Feed page.

An ordered list of benefits
  • Decreased cursing
  • Decreased wasting of acid
An ordered list of problems/issues involved
  • The downside to the alternative suggestion is that it might require updating all themes.
chendamoni [me] - 05/24/2014

Title
As Owner of Community, I should be able to Unsticky Posts

Short, concise description of the idea
The Owner of a Community should be able to Unsticky or Sticky a Moderator's (or really any Member's) post.

Full description of the idea
The Owner of a Community should be able to Unsticky or Sticky a Moderator's (or any Member's) post in order to have better control over their communities.

An ordered list of benefits
  • Owners have more control over the content of their communities.
  • No need to request that MIA mods Unsticky their posts.
An ordered list of problems/issues involved
  • Some mods may get upset that the Owner unstickied their post.
1st September 2016 @ 06:20 pm - Robots.txt Disallows All User-Agents
skillsfuture

Title
Robots.txt Disallows All User-Agents

Short, concise description of the idea
Robots.txt disallows all user-agents, which means that my livejournal cannot be indexed by search engines.

Full description of the idea
Hi,

Despite setting my journal to public, and unchecking "minimize inclusion to search engines," my robots.txt remains the same, it blocks all search engines. What's the use of having a blog if not crawled by search engines anyway? How would one get new visitors?

My LiveJournal URL is: http://skillsfuture.livejournal.com/
Robots.txt: http://skillsfuture.livejournal.com/robots.txt

Regards,

An ordered list of benefits
  • It's user-friendly.
An ordered list of problems/issues involved
  • Robots.txt is not changed despite setting privacy setting to PUBLIC.
Me

Title
Provide one-click embedding of Tumblr posts from Friends Feed

Short, concise description of the idea
The Tumblr widget in the Friends Feed should include a button that, when clicked, starts a new entry with that Tumblr post already embedded.

Full description of the idea
The Twitter widget on the Friends Feed includes a "Repost to LiveJournal" link that, when clicked, starts a new entry with that tweet automatically included. If LiveJournal ever allows embedding of Tumblr posts (as suggested a couple of weeks ago) then I would like to see a similar function included in the Tumblr widget on the Friends Feed.

An ordered list of benefits
  • * Simplifies the embedding process from Tumblr.
    * Creates new opportunities and content on LiveJournal.
An ordered list of problems/issues involved
  • * Programming effort
    * The Tumblr widget often truncates posts, so LiveJournal users may embed Tumblr content into their journal without having first seen the entire post they are embedding.
Me

Title
Allow embedding of Tumblr posts on LiveJournal

Short, concise description of the idea
Add Tumblr to the list of sites that can be embedded into LiveJournal entries.

Full description of the idea
Tumblr offers an embed option an all posts ( such as this one: http://fiddlingfrog.tumblr.com/post/144274136268/i-love-these ) so that their posts can be seen across the web. However, the code that Tumblr provides, available here ( http://fiddlingfrog.tumblr.com/post/144274136268/i-love-these/embed ) along with a preview of what they embed would look like, does not work on LiveJournal. The style information and JavaScript are stripped away, leaving only a plain URL link to the Tumblr post.

I'd like to see Tumblr added to the list of approved embed sources so that LiveJournal users can embed Tumblr posts directly into their entries.

An ordered list of benefits
  • Gives LiveJournal users more options for content in their entries.
  • It allows for cleaner inclusion of content from Tumblr into LiveJournal. Currently there are a number of hacks and workarounds that people use, none of which are entirely adequate.
An ordered list of problems/issues involved
  • Programming time/effort.
  • I believe that Tumblr's embed function presents a cleaned-up version of that particular post, but more investigation is needed to see how successful it as at removing additional JavaScript (Tumblr allowing users to include additional JavaScript in their layouts and LiveJournal blocking it on security grounds.)
default

Title
Allow communities to disable the WYSIWYG editor

Short, concise description of the idea
Provide a way for community owners/maintainers/moderators to disable the rich text editor, so that everybody who wants to post has to use the HTML editor.

Full description of the idea
Currently, LiveJournal offers two ways to post; the classic HTML editor where the poster sees all markup and has to keep it in mind, and the rich text editor where the poster clicks buttons and the editor generates markup.

The markup generated by the rich text editor is often excessive and non-semantical, especially if formatted text is copy/pasted from Word or another web site. Posters cannot easily see that their post specifies white background, gray text, a fixed font size or a hardcoded font face such as Proxima Nova or Helvetica Neue.

Such posts are annoying when viewed in a customized Friends feed or even in the list of community posts.

The ru_chgk community, for example, has an explicit rule against excessive and obnoxious markup, and it is violated on a regular basis.

I propose that there should be a per-community preference that community owners and/or maintainers and/or moderators could activate, which would disallow posting through the rich text editor to their community. Everybody who wants to post would need to think carefully about any markup they use.

An ordered list of benefits
  • Readers benefit by seeing all community posts in a reasonably consistent style.
  • Posters benefit by having an incentive to learn HTML.
  • Posters also benefit by being confident they are not unknowingly annoying their readers.
  • Moderators benefit by having less yelling to do.
  • The Internet benefits by becoming closer to the ideal of semantic markup.
  • Kittens benefit by not being killed by gods every time somebody posts in 12px #333 Proxima Nova on a white background at 19.6px line height.
An ordered list of problems/issues involved
  • Would-be posters who are incapable of learning the basics of HTML lose by not being able to post in communities that have activated the proposed switch.
  • Internet providers and mobile carriers indirectly lose by having less data to transfer and therefore less money to extort from users.
23rd April 2016 @ 04:36 pm - blockquote in HTML editor
kluven

Title
blockquote in HTML editor

Short, concise description of the idea
Will LiveJournal HTML editor *ever* have a slide-in/slide-out (blockquote/quoting) capability?

I mean, in every single HTML editor out there it is considered one of the most basic things.

Full description of the idea
see above

An ordered list of benefits
  • see above
An ordered list of problems/issues involved
  • see above
This page was loaded Dec 8th 2016, 12:04 am GMT.