Abstract: A method and apparatus to create a “diary” containing multimedia references to contents of Websites. These references (also called addresses) can be to, for example, text, bookmarks, images, programs, movies, etc. Many content objects are provided via the Websites of “content providers,” with the specific intent of making the content objects available to a user to place in his diary. Each diary page has a format specified by a cover. The cover is provided by a cover provider and specifies where on the diary page the diary owner can place his content. The name “diary” arises because the invention preferably allows the user to save these references in association with dates and/or times. The pages of a user's diary may be navigated like a book, moving forward and backward through the pages or jumping to a particular page. In addition to storing references to Web information, the user can also jot down reminders, enter appointments, and birthdays, etc. for dates.

Abstract: A method and apparatus to create a “diary” containing multimedia references to web sites that a user has visited. These references (also called “content objects” or “objects”) can be addresses of, for example, text, bookmarks, images, programs, movies, etc. Many content objects are provided via the Web sites of “content providers,” with the specific intent of making the content objects available to a user to place in his diary. The name “diary” arises because the invention preferably allows the user to save these references in association with dates and/or times. The pages of a user's diary may be navigated like a book, moving forward and backward through the pages or jumping to a particular page. In addition to storing references to Web information, the user can also jot down reminders, enter appointments, and birthdays, etc. for dates. A user is allowed to choose a visual “theme” for the pages of his diary.

Abstract: A method and apparatus to allow an executable program, received from a first machine to a second machine, to communicate with a third machine. Certain security restrictions prohibit an executable from communicating with a machine other than that from which it was loaded. In, for example, a web page diary application, content is downloaded from a first machine to a second machine. A user then chooses to store the content on a third machine. In a first embodiment, a first executable “knows” the name of a second transfer executable that is stored on the third machine. The executable downloads and executes the transfer executable, which passes the information to be stored to the third machine. Because the transfer executable is downloaded from the third machine, it can communicate with the third machine. A second embodiment does not “know” the name of the transfer executable.

Abstract: A system enables a user to maintain a catalog of network objects of interest to the user. The system comprises a diary owner system, a diary server and content providers, each coupled to a computer network. Each content provider includes presentable objects, annotated universal addresses which identify the objects and have annotations for controlling aspects of the objects or addresses, and transfer scripts enabling the transfer of the annotated universal addresses to the diary server. The diary server maintains the annotated universal addresses and presentation context information for subsequent retrieval. Accordingly, a diary owner or other user can access the annotated universal addresses and presentation context information to present the diary. Since content providers generate the annotations within the annotated universal addresses, the content provider can control aspects of the objects from within the user's diary.