lisabelle (lisabelle) wrote in suggestions,

LJ-cut for syndicated feeds

LJ-cut for syndicated feeds

Short, concise description of the idea
Syndicated feed content would automatically be placed behind an LJ-cut tag if it satisfies preset parameters --OR-- user setting up a syndicated feed would have the option to put the content behind an LJ-cut tag.

Full description of the idea
Disclaimer 1: This may be a partial restatement of THIS suggestion -- it sort of hinges on the same idea. I apologize in advance for overlap.

Disclaimer 2: Though a code monkey by trade, I know nothing about LJ code and little about how syndication works, and thus whether my suggestions are even feasible.

Now that that's out of the way...

Not to point fingers, but this idea came about thanks to apod. The good folks at APOD have featured a handful of images in the last couple of weeks that are positively enormous. Even though the site (and the feed content) usually displays a smaller version of the featured image, even the thumbnails of these panoramic photos are in the neighborhood of 2700 pixels wide.

Now, I don't so much mind scrolling sideways on my Friends page to view a breathtaking Martian landscape, but I DO mind scrolling to read my other Friends' entries that just happen to be on the same page. It's a pain to read a paragraph that takes up a single line on the screen, and I know people who've created filters just to read around apod, and others who've dropped the feed altogether because of this.

I'm sure there are other image-based feeds that have this problem; for instance, the images of pvp_comic are considerably wider than most comic images. However, since I use 1024x768 display resolution, I know I can read PVP without scrolling if I enlarge or maximize my browser window. I only tell you this because I realize there must be some variables (display res, browser and window size) that are beyond the ken of what LJ code can be dependent upon.

Suggestion One would occur at post time, whenever LJ checks the feed (or however it is that works). An LJ-cut tag would precede the feed content if a contained image is wider (or taller!) than [X] pixels, or exceeds [Y] KB in size.

Suggestion Two might be easier, code-wise. When a feed is set up, the option is given to automatically put the content behind an LJ-cut. This would allow for duplicate feeds with alternate formatting (e.g., "tagged" APOD for those of us who don't wanna scroll, and "non-tagged" APOD for those of us who don't care).

Perhaps this idea can be extended to text-based feeds, as well. I know officialgaiman gets wordy from time to time...

An ordered list of benefits

  • Easier to read Friends page
  • Better tailors syndicated content to the LJ environment
  • Allows users more control over syndicated feeds
  • An ordered list of problems/issues involved

  • Code change/testing
  • Parsing XML is perhaps difficult?
  • Image size usually isn't in the IMG tag -- difficult to otherwise discern?
  • Too much is dependent on display resolution/browser size/LJ style, etc.?
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • Oops - pretty sure I covered this in the full description.
  • Tags: lj-specific markup, syndication, § historical
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded