?

Log in

Suggestions Box
Want to improve LiveJournal? Contribute your ideas!
Recent Entries 
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
running, bomb tech

Title
Tools to mitigate aggressive community invitation behavior

Short, concise description of the idea
Community invitations are a means of contact which can be used for evil, but shouldn't be.

Full description of the idea
Most community invitations are legitimate or accidental. Some community invitations are a form of unwanted contact or spammy.

Make sure there isn't a loophole where aggressive promoters can send invitations and then rescind them quickly to generate more notifications than they're entitled to.

Create a way for users to report invitations (especially rescinded invitations) as unwanted.

An ordered list of benefits
  • Users won't have to turn off notifications for community invitations and potentially miss out on legit invitations just to avoid flooding with bogus ones
  • Less gaming the system
  • Consequences for communities which are doing this thing
An ordered list of problems/issues involved
  • There's already a setting to turn off notifications of invitations.
  • Unhappy maintainers
  • If someone is invited accidentally, they may think it's spammy even though it was actually accidental
1st April 2016 @ 09:42 am - Support secure connections by default
feet

Title
Support secure connections by default

Short, concise description of the idea
All connections to LiveJournal should be over HTTPS, not HTTP; all email from LiveJournal should be via secure connection, not insecure.

Full description of the idea
Insecure web connections are becoming very dangerous.

They do not only secure browsing; they largely eliminate the risk of code injection and drive-by exploits.

Please secure all web connections to LiveJournal, not just the login part. Require https. It's faster, too!

This includes outbound email; LJ comment notifications often contain sensitive information and links, but are one of the few emails I receive that are still transmitted in the clear.

Here is additional background:
https://scotthelme.co.uk/still-think-you-dont-need-https/

An ordered list of benefits
  • Contents of communication are private between LJ and the viewer.
  • Much lower risk of malicious content injection. I hate the thought of having my readers getting their computer hacked just for viewing my blog.
  • HTTPS is now faster than HTTP, in some cases almost twice as fast.
  • Browsers show warnings to users for insecure connections, scaring away potential readers.
  • Google has already started ranking insecure websites lower than secure ones; this harms the LJ brand.
  • Some major browsers (e.g., Chrome) are disabling some features for insecure connections.
  • Let's Encrypt offers free, public, and automated SSL/TLS certificates.
    https://letsencrypt.org/
An ordered list of problems/issues involved
  • Changing over will require development effort, and require LiveJournal to acquire and maintain a signing certificate.
  • Introduces overhead on the server-side (of less than 1% CPU load).
25th February 2016 @ 02:56 pm - filter banned users from friend-of-friend feed

Title
filter banned users from friend-of-friend feed

Short, concise description of the idea
Ideally, entries and comments from banned users should not be seen anywhere (short of going to their journal directly). Barring that, at least filter them from foaf.

Full description of the idea
LJ already filters the user's direct friends from the friend-of-friend feed (/friendsfriends), so the functionality is there. I'd like the banned users to be included into that filter as well

An ordered list of benefits
  • Banning a user clearly means that the person doing the banning does not want to see anything from that user; the foaf feed is closer to the friends page than to simply wandering around the site looking at random journals; so, this would move LJ in the direction of better consistency in handling the entries from banned users
An ordered list of problems/issues involved
  • technically - none I can see; the code is already there, it should be a simple enough fix
  • wrt policy - I'm having a hard time imagining that by flipping the default from "seeing banned users" to "not seeing banned users" would upset anyone, but if you want to be extra nice, make the behavior configurable
frank sinatra, mercedes-benz, mb 230sl automatic

Title
Please add IP address and time of the comment in mail notifiaction template

Short, concise description of the idea
Current mail notifications does not contain:
* Full time stamp of the comment
* IP address of comment poster, even if you had enabled to save IP addresses

Full description of the idea
Please add IP address and time of the comment in mail notifiaction template

Current mail notifications does not contain:
* Full time stamp of the comment
* IP address of comment poster, even if you had enabled to save IP addresses

So,
1) you are not able to search by IP address in mail notifications archive
2) you are not able to see anything, if comment was removed by a guy who had posted it (you have the text, but not IP address and timestamp)

An ordered list of benefits
  • 1. You will be able to see IP address immediately, in notification.
    2. You will be able to search by IP address in mail notification archive
    3. You will see exact timestamp in notification
    etc
An ordered list of problems/issues involved
  • There is no any problems/issues.
    It is easy to do, just modify notifcation template, inserting a few entries - IP address and timestamp
12th December 2015 @ 09:58 am - Repost any post
wyvern

Title
Repost any post

Short, concise description of the idea
Extend the repost feature from communities to all posts

Full description of the idea
Tumblr has been getting worse every release, giving LJ a chance to reclaim lost users. The main feature that Tumblr has over LJ right now the ability to repost any other post and add text and new tags.

Currently, LJ can only do this to a post within a community. I would extend this to any post and add a locking mechanism that can be applied to posts so people can disallow their posts to be reposted if they want.

An ordered list of benefits
  • Allows content to be spread more widely
  • Switches reposting from an author choice to a reader choice, allowing readers to interact with content
  • Makes LJ more competitive in the social media market
  • The locking mechanism would allow authors to control how their content is used
An ordered list of problems/issues involved
  • Users would see multiple copies of the same post in their Feed potentially. They may wish to have an option to turn reposts off, so their feed is only ever original content.
3rd August 2015 @ 01:31 pm - Tumblr as an option for commenting.
SAKURAI SHO ♥♥♥ [main]

Title
Tumblr as an option for commenting.

Short, concise description of the idea
There should be a feature that allows users to comment using their Tumblr account.

Full description of the idea
While adding Tumblr to the list of account you can use to comment with will certainly be easier for some people, it will also allow more people in becoming interested in LiveJournal itself. This option of commenting on posts in LiveJournal using a Tumblr account should be allowed for a busier and more inclusive network.

An ordered list of benefits
  • More people will be using LiveJournal.
  • The dead communities may be revived with those people who have Tumblr account now because of how easy and efficient it will be for them to use.
  • There will be a better sense of community. If one person sees an account that is familiar they can find each other on other networks thus creating a stronger bond.
  • You can easily find the bots or "trolls" that are making sock puppet accounts that may be harmful to the website through this form of ID.
  • Users can have a better sense of who they are speaking with.
  • For users on the go and who are very busy, this can be a faster and efficient way from their mobile devices.
An ordered list of problems/issues involved
  • There will be some stimulation aspect for the other website/social media site as well such as is the case for many different platforms of social media. Those that find this through LiveJournal may be interested in creating a Tumblr account as well.
This page was loaded Aug 27th 2016, 8:05 am GMT.