Azure Jane Lunatic (Azz) 🌺 (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
azurelunatic) wrote2003-08-28 01:42 pm
azurelunatic) wrote2003-08-28 01:42 pm
Dream Livejournal Publisher (Vaporware, disorganized specs)
Livejournal publisher would either be an LJ-hosted service on the page, a separate page, or a downloadable client.
Livejournal publisher would take the LJ of any given user and convert it into printable form.
User would be able to produce a file containing entries from any given month for a user.
User would be able to create a file of the public entries (by month) of any user (no password required) or create a file of the viewable by their username/password entries for any user. Example: aaa is listed as a friend by bbb. aaa logs in to LJ Publisher and requests to publish all viewable entries from bbb in mm/yyyy. aaa gets the file containing all entries from bbb in mm/yyyy that user aaa is authorized to view.
User would be able to specify security levels for the printout of their own journal: public entries, public and friends, or public, friends, and private.
In addition to printing out by month, user would be able to publish by memories section. User aaa would be able to select user, memories, and memory category (example: User, aaa; memories; keyword: spam) and get all memorable entries on the selected subject.
Format: User would be able to choose format of output file. Suggested: .pdf, .wpd, .doc, .txt, .htm (possibly others)
LJ Publisher would be available for multiple platforms, especially if a web-based service.
User would be able to specify size of page and margins.
LJ Publisher would create a Table of Contents, ordering the entries chronologically, with large headings for day, and smaller headings for each entry title. Entry number would be listed next to entry title (if any). Page number for the LJ Publisher file would be shown.
Informational page would show the static information from the main journal page, and the information from the userinfo page. Also helpful would be all user pictures with associated keywords. The URL of the journal month would be listed.
Each day begins a new page. Full date (day, month, year, day of the week) is printed at the top of the page. The URL of the day's entries would be listed.
A chosen divider separates entries within a day. (New page, horizontal rule, graphic, etc.)
Each entry begins with the title, the selected user picture, the time and date. Entry in fully accessed form is shown. Currents (mood, music) are shown after the entry. (Optionally, user could select whether to show currents before or after entry?) Mood image is shown.
Comments:
User may choose whether or not to publish comments with entries. Comments are shown fully accessed, arranged by thread. ID numbers of comments are shown, along with "In reply to [ID number]". User pictures and user names of commenters are shown. Silly icon (smily, frowny, etc.) is shown if present. Keyword for user picture should be provided.
Links:
All clickable links are underlined and footnoted.
External links are footnoted with the full URL of the link.
Anchors are indicated by an anchor symbol in the margin, and the name of the anchor listed next to it.
Links to other Livejournal pages are footnoted with the full URL and the title of the page if available.
Links to other entries in the same user's journal are footnoted with the full URL and the year, month, and date (and anchor if applicable).
Links to other items in the same published volume are footnoted with the full URL, the full date, anchor if applicable, and page in the volume on which the link can be found.
Ideally, you'd wind up with something you could print out and bind...
Livejournal publisher would take the LJ of any given user and convert it into printable form.
User would be able to produce a file containing entries from any given month for a user.
User would be able to create a file of the public entries (by month) of any user (no password required) or create a file of the viewable by their username/password entries for any user. Example: aaa is listed as a friend by bbb. aaa logs in to LJ Publisher and requests to publish all viewable entries from bbb in mm/yyyy. aaa gets the file containing all entries from bbb in mm/yyyy that user aaa is authorized to view.
User would be able to specify security levels for the printout of their own journal: public entries, public and friends, or public, friends, and private.
In addition to printing out by month, user would be able to publish by memories section. User aaa would be able to select user, memories, and memory category (example: User, aaa; memories; keyword: spam) and get all memorable entries on the selected subject.
Format: User would be able to choose format of output file. Suggested: .pdf, .wpd, .doc, .txt, .htm (possibly others)
LJ Publisher would be available for multiple platforms, especially if a web-based service.
User would be able to specify size of page and margins.
LJ Publisher would create a Table of Contents, ordering the entries chronologically, with large headings for day, and smaller headings for each entry title. Entry number would be listed next to entry title (if any). Page number for the LJ Publisher file would be shown.
Informational page would show the static information from the main journal page, and the information from the userinfo page. Also helpful would be all user pictures with associated keywords. The URL of the journal month would be listed.
Each day begins a new page. Full date (day, month, year, day of the week) is printed at the top of the page. The URL of the day's entries would be listed.
A chosen divider separates entries within a day. (New page, horizontal rule, graphic, etc.)
Each entry begins with the title, the selected user picture, the time and date. Entry in fully accessed form is shown. Currents (mood, music) are shown after the entry. (Optionally, user could select whether to show currents before or after entry?) Mood image is shown.
Comments:
User may choose whether or not to publish comments with entries. Comments are shown fully accessed, arranged by thread. ID numbers of comments are shown, along with "In reply to [ID number]". User pictures and user names of commenters are shown. Silly icon (smily, frowny, etc.) is shown if present. Keyword for user picture should be provided.
Links:
All clickable links are underlined and footnoted.
External links are footnoted with the full URL of the link.
Anchors are indicated by an anchor symbol in the margin, and the name of the anchor listed next to it.
Links to other Livejournal pages are footnoted with the full URL and the title of the page if available.
Links to other entries in the same user's journal are footnoted with the full URL and the year, month, and date (and anchor if applicable).
Links to other items in the same published volume are footnoted with the full URL, the full date, anchor if applicable, and page in the volume on which the link can be found.
Ideally, you'd wind up with something you could print out and bind...
no subject
no subject
As long as you follow the requirements for polling frequencies and the like, LJ can't really complain if people use the APIs they open up.
no subject
no subject
Comment support has been written, but I don't think it's anywhere near ready to go live, yet.
Once you get the raw entries, everything else is just SGML/XML transformations and formatting - tools exist to do those things already, it'd just be a case of writing code to pull them all together.
It'd be a popular application, if someone wrote it.
no subject
This is the sort of thing that LJ would only want to make available to paid people, and then only with a volume restriction, to prevent the server suckitude that sithjawa mentioned.
Scripting language, no? I'd say perl or python.
no subject
no subject
Would be nice to pull it all in one sell fwoop instead of printing the pertinent entries on an occasional basis.
no subject
I have a lot of my meta-information in comments, and the current thing doesn't do it justice...
no subject
geeky people _need_ to know :P
no subject
no subject
no subject
Converting to printed format is sometimes difficult, because each printer reads things differently (like fonts). I would recommend converting to PDF, and then making the PDF on the fly. The printer will create it exactly as it appears in the PDF (baring extreme weirdness).
The last thing I would add would be a micropayment system. I'm currently working on this right now, and hoping to file patents soon. (free to use for everyone except banks)
If anyone wants to work on this, I have space and a server to use. I can also train people in how to code in PHP/MySQL/XML and get things started.