CAPS LIKE WHOA (jc) wrote in suggestions,
CAPS LIKE WHOA
jc
suggestions

<lj-include> and/or $include(url) - embed dynamic content in journal entries and layouts

Title
<lj-include> and/or $include(url) - embed dynamic content in journal entries and layouts

Short, concise description of the idea
Allow users to include dynamic content in their journals while not exposing LiveJournal to security risks, by implementing an <lj-include> tag.

Full description of the idea
Many users have in the past requested the ability to include dynamic content in their journals - for example, that of frequently updated news aggregators - but as most of this content involves the use of JavaScript or Flash they can't do this for security reasons. Additionally, as it stands there is no way to play with an equivalent of the *_WEBSITE variables in LiveJournal's new style system, S2, or configure any block of code longer than the maximum allowed string length through the customisation User Interface.

Many LiveJournal users already have access to off-site scripting languages such as PHP, which can be used to generate dynamic content without posing a security risk to LiveJournal. The implementation therefore of an <lj-include> tag, and/or its equivalent function in S2, would benefit many users.

When such a tag or function is called within a layout or entry, the server could access the remote document, and (if it determines the content has changed) pass the document's content through LiveJournal's existing HTML cleaner, and cache the content locally to save bandwidth.

An ordered list of benefits

  • Much more creative and interesting journal layouts
  • A much more advanced degree of customisation
  • Integration with S2, without the need to implement the customisation of larger code blocks
  • Little to no security risk posed to other users
  • An ordered list of problems/issues involved

  • Much more potential for less advanced users to completely mess up their journal layouts, creating a potentially huge Support headache
  • Logistical implications in implementation
  • Probably will never be supported in S1
  • May need to restrict the feature and offer it to paid users only
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • Create a system for calling remote documents and passing output through the HTML cleaner
  • Implement this as a builtin function in S2 called "include", which takes a string URL as its input and returns the cleaned content of the remote document
  • Tags: ~ historical
    Subscribe
    • Post a new comment

      Error

      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded 

    • 10 comments