Dynamic creation, data population, and communication establishment across various mediums

[0001] This disclosure relates to systems and methods for creating and updating content on various mediums.

[0002] In present day communications technology, there are a variety of mediums on which a user can create a presence. These mediums include a webpage, social networking presence, instant messaging accounts and the like. However, in order to enhance a user's presence and popularity, it can be important to ensure that these mediums are dynamic by constantly changing and updating the content of the medium in order to attract attention of other users and acquaintances to the medium.

[0003] In previous art, patent application 20090182589 entitled “Communicating Information in a Social Networking Website About Activities from Another Domain” discusses methods to bring related advertisements into the social networking realm by “announcing” that connected users to a given user of the social networking web site have performed a certain action, therefore advertising a product or service to a user that will most probably have an interest. This type of advertisement is termed “Social Ads”.

[0004] U.S. Pat. No. 6,839,680 entitled “Internet Profiling” discloses software to provide for consistent identification of web users across multiple web sites, servers and domains, monitoring and capturing of data describing the users' web activities, categorization of the web activity data, aggregation of the data in to time dependent models describing interest of users and groups over time.

[0005] What is required are improved applications, systems and methods for creating a medium and for providing content to a new or existing medium.

[0006] In one aspect of the disclosure, there is provided a method for generating a medium on a network comprising selecting a medium, processing at least one of local user data and remote user data to determine one or more current interests of a user, selecting a category dependent on the one or more current interests, processing at least one of the local user data and remote user data to automatically generate content for the medium, generating the medium on the network, and populating the medium with the automatically generated content.

[0007] In one aspect of the disclosure, there is provided an application for execution on a computing device. The application is configured to present an interface to a user that allows a user to select a medium and indicate one or more parameters of the medium. The application is also configured to automatically create the medium, populate the medium and notify acquaintances of the user of the medium.

[0008] In one aspect of the disclosure, there is provided a computer-readable medium comprising computer-executable instructions for execution by at least one processor, that, when executed, cause the at least one processor to present an automatic content behavior interface to a user, receive one or more parameters of at least one automatic content behavior from the user, generate at least one automatic content update for a medium in accordance with the at least one automatic content behavior, and modify a medium with the at least one automatic content update in accordance with the automatic content behavior.

[0033] The current disclosure is related to U.S. patent application Ser. No. 12/505,109, entitled “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR AUTOMATIC QUERY AND ORDER PROCESSING VIA THE INTERNET” filed on Jul. 17, 2009, U.S. patent application Ser. No. 12/511,112, entitled “METHOD AND APPARATUS OF CREATING ELECTRONIC FORMS TO INCLUDE INTERNET LIST DATA” filed on Jul. 29, 2009, and U.S. patent application 61/317,788, entitled “DYNAMIC COLLABORATION AND DOCUMENT-MANAGEMENT PLATFORM” filed on Mar. 26, 2010, U.S. patent application 61/317,535, entitled “SMART MESSAGING SYSTEM” filed on Mar. 25, 2010 and U.S. patent application 61/317,541, entitled “VOICE BASED SOCIAL MEDIA” filed on Mar. 25, 2010 and U.S. patent application 61/317,805, entitled “AUTOMATIC POSTING TO MEDIUMS WITH A USER'S CURRENT INTERESTS” filed on Mar. 26, 2010 and U.S. patent application 61/317,817, entitled “LIMIT AND FILTER INCOMING DATA PRESENTED TO A USER” filed on Mar. 26, 2010. The disclosure of each of these are incorporated herein in their entity by cross-reference.

[0034] The disclosure now U.S. patent application 61/317,788, entitled “DYNAMIC COLLABORATION AND DOCUMENT-MANAGEMENT PLATFORM” filed on Mar. 26, 2010, referenced above establishes a method to gather knowledge from aspects of the user's online surfing history and other places, and using this knowledge, recommends components on a particular medium that is being created, rather than relying on the user to provide input to attempt to achieve the result.

[0035] The medium created can be one or more of a web page, a blog, a twitter message, an IM, a social networking application such as a Facebook application, etc. Depending on the medium being created, the components recommended will vary. For instance, if a webpage is the medium being created, one component may be a dropdown list that includes elements that reflect the results of querying and utilizing the user's data. Another component on a webpage may be a table that includes any data encountered from the results in querying the user's data. If the medium is an instant messaging type of account, such as Twitter, the component would be a text message (and one that is shorter than 144 characters in the case of Twitter). If the medium is a blog, the component could be any relevant information (such as video, photos, text, etc.) from the result of querying the user's data.

[0036] The above-referenced disclosure now U.S. patent application 61/317,788, entitled “DYNAMIC COLLABORATION AND DOCUMENT-MANAGEMENT PLATFORM” filed on Mar. 26, 2010, discloses using the results from querying the local and remote systems to generate components on the medium. The present disclosure utilizes the functionality of the above referenced disclosure, but goes further in automating the process of creating a medium on a network, such as the Internet, as well as automatically propagating the data on the medium to the user's acquaintances.

[0037] Additional functionality described herein includes suggesting a topic or category of the medium by utilizing current interests of the user received from querying local and remote systems, automatically populating the medium with content from the user's data received from querying the local and remote systems, establishing communication of the new medium with the user's acquaintances or with users that have a similar interest, and automatically throttling the communication by removing acquaintances that do not respond to messages.

[0038] FIG. 1 displays a network architecture that may be used with an embodiment of the present disclosure. The network architecture 100 allows a user utilizing a client machine 103 to access one or more applications configured to perform the methods of the present embodiments as will be described below. The applications may take the form of software, for example to be downloaded from the server 104 or that currently resides on the client's machine 103. The client machine can be any of a mobile laptop device 106, a personal desktop computer 108, a wireless device 110 or any other personal computing device. The client machine 103 is connected to the Internet 102 or a similar communications network.

[0039] In FIG. 2, there is shown a process 20 for generating a medium on a network. The process 20 commences by selecting a medium to be created (step 21). Local and/or remote user data is then processed to determine and suggest the current interests of the user (step 22). A category or topic for the medium is then selected from the current interests (step 23). The local and/or remote data is again queried to automatically generate content for the medium (step 24) after which the medium is generated (step 25) and populated with the automatically generated content (step 26).

[0040] By example only, an application used for enacting the above described method could reside on the server 104 but could also reside completely or in a distributed manner on one or more of the devices or networks in FIG. 1. The user may access the client machine 103, and connect to a remote machine 105 which includes any of a mobile laptop device 112, a personal desktop computer 114, or a wireless device 116. The remote machine 105 is connected to the Internet 102. If the client is on a wireless device 110/116, the system 104 can be accessed via the Internet 102, or the Wireless Network (such as a Cellular Network, for example) 118. It should be noted that other types of devices, in addition to devices 103 and 105, might be used with the present embodiments. For example, a PDA, an MP3 player, a gaming device (such as a hand held system or home based system) and the like that can also transmit and receive information could be used.

[0041] The user will interface through a GUI that is presented when the application is executed. The GUI is accessed via one or more of the devices 103. An interface screen 30 that allows the user to indicate the medium of interest is depicted in FIG. 3. The interface screen 30 shows selections for a webpage 31, a blog 32, a social networking page (e.g. Facebook) 33, and an instant messaging application (e.g. Twitter application) 34. Many more mediums can be present but are not depicted such as a Photo Sharing application, a Data Sharing application, a Cellular Telephone application, etc.

[0042] The user selects the medium or mediums desired and presses the “Start” button 35 to begin the functionality of the application, or presses the “Cancel” button 36 to end the application. In other embodiments, the medium or desired mediums can automatically be picked based on a level of activity in a certain area as will be described below. For example, the application, when parsing through the user's local files, specifically the temporary internet files, can note that the user continuously access other users' blogs and thus ascertains that the current user would want to create a blog. In other embodiments, utilizing the user's historical surfing history, the mediums are presented in the Application Top Window, e.g. interface screen 30, in the order that the user would likely be most interested in. The application keeps track of which mediums the user has created (in a memory of the server 104, for example) and if the user runs the application again, the already created application will not appear again, or will appear at the bottom of the list in case the user wants to create a similar medium (such as another blog covering a different topic, for example).

[0043] Assuming that the user continues, by pressing the “Start” button 35, the application utilizes the logic described in U.S. patent application 61/317,788, entitled “DYNAMIC COLLABORATION AND DOCUMENT-MANAGEMENT PLATFORM” filed on Mar. 26, 2010, to gather current interests of the user from both the local and remote systems. As described in Ser. No. 61/317,788, the application gathers the data of the user based on one or more of the following elements:

• • [0044] ads that have been served to the user's email program
  • [0045] ads that the user clicked on
  • [0046] searches requested
  • [0047] groups that the user is a member of
  • [0048] emails that the user sent or received
  • [0049] calendar events that the user is subscribed to
  • [0050] historical surfing habits
  • [0051] current location of the user
  • [0052] online games that the user has shown interest in
  • [0053] DVR
  • [0054] live video streaming/IPTV
  • [0055] web based shows
  • [0056] GPS (Cellular)

[0057] Other elements that may be searched to provide an indication of a user's current interests may be apparent to a person skilled in the art and are intended to be encompassed herein.

[0058] One way to use the history of the user's online surfing is through the history on the user's computer. Most web browsers retain Internet surfing information in the form of cache files, or cookies stored on the user's computer. These files can be scanned to determine information that will aid the application in creating a dynamic web page.

[0059] Other methods can be employed to gain an understanding of the user's previous Internet surfing history. Google and Yahoo, for instance, offer free services that users can utilize to perform email capabilities, manage groups, search the web, manage advertisements, manage calendar activities, manage documents, as well as many other services. Data associated with these services can be interworked with the current embodiments to aid in making choices in the components of the created page.

[0060] In another embodiment, using the location of the user, the application can tailor the created page. The location of the user can be found using different methods. One way is to compare the IP address to a broad geographical location. This method may not give an exact location, but should provide an approximation of the location. Another method is to examine the search history, groups joined, direction information provided to and/or received from map applications (for example, an address that recurrently appears in the TO: field) and ads appearing near the emails or searches performed, looking for any address information.

[0061] FIG. 4 shows an overall flow 300 of the system. The application starts at step 301 by displaying the interface screen 30 of FIG. 3. When the user selects a medium and selects the start button 35 (step 302), the application selects criteria for the selected medium (step 303) and begins the process of collecting data on the user from both the local and remote systems based on one or more of the elements listed above (step 304). For example, processing of ads that have been served follows a process “A”, processing of ads that the user clicked on follows a process “B” etc, each of which are described in more detail below.

[0062] FIG. 5 depicts a process 400 representing process “A” undertaken by the application for gathering user data from ads that have been served. First a check is made to determine if the user has an internal application that serves ads (step 401). This would be a local application used to deliver ads to the user. If there is a local application, the list of served ads is queried for keyword(s) (step 402). The application will then query the remote system's (Google, for instance) list of ads served to the user using the remote data server that is internal to the remote system (step 403). In either case, the results of the query are returned to the application which processes the query results (step 404).

[0063] FIG. 6 depicts a process 500 representing process “B” undertaken by the application for gathering user data from ads that the user has clicked on. The local file system (cookies and temporary internet files) is searched for advertisements that the user has previously clicked (step 501). The found websites are searched for keyword(s) and the results of the query are returned for processing by the application (step 502).

[0064] FIG. 7 depicts a process 600 representing process “C” undertaken by the application for gathering user data from searches requested. The local file system (cookies and temporary internet files) is searched for the internet searches requested by the user (step 601). The history of what the user has searched for is stored in the Internet history stored on the local computer. The search history is searched for keyword(s) and the results of the query are returned for processing by the application (step 602).

[0065] FIG. 8 depicts a process 700 representing process “D” undertaken by the application for gathering user data from groups that the user is a member of. A check is first made to determine if the user has subscriptions to an online group's application (i.e., Google, or Yahoo) (step 701). If the user does not subscribe to an online group, the process returns as all group applications are online (step 705). If the user does subscribe to an online groups application and the user is the current owner or member of a group (step 702), the group's data is searched by querying the remote system's (Google or Yahoo, for instance) data of groups wherein the user is an owner or member (step 703). The remote data server that is internal to the remote system may be searched. The result of the query is returned for processing by the application (step 704).

[0066] FIG. 9 depicts a process 800 representing process “E” undertaken by the application for gathering user data from emails sent and/or received. A check is first made to determine if the user has subscriptions to an online email application (i.e., Google, or Yahoo) (step 801). If the user does have an online email application, the email is scanned for keyword(s) (step 803). This functionality would be internal assuming that the application resided in the Google or Yahoo application, or any other online email provider. If the user does not subscribe to an online email application but uses an application that stores the history of the emails locally on the user's local system, the application scans the emails on the local computer (step 802). Developer applications exist to scan mail folders that are stored on the user's local computer. The result of the query is returned for processing by the application (step 804).

[0067] FIG. 10 depicts a process 900 representing process “F” undertaken by the application for gathering user data from calendar events. A check is first made to determine if the user has subscriptions to an online calendar application (i.e., Google, or Yahoo) (step 901). If the user does have an online calendar application, the calendar items are scanned for keyword(s) (step 903). This functionality could be internal assuming that the application resided in the Google or Yahoo application, or any other online calendar provider. If the user does not subscribe to an online calendar application but uses an application that stores the history of the calendar items locally on the user's local system, the application scans the calendar items on the local computer (step 903). Developer applications exist to scan calendar folders that are stored on the user's local computer. The result of the query is returned for processing by the application (step 904).

[0068] FIG. 11 depicts a process 1000 representing process “G” undertaken by the application for gathering user data from the user's surfing habits. The local file system (cookies and temporary internet files) is searched for the internet surfing history of the user (step 1001). The history of the user's Internet surfing is stored in the Internet history stored on the local computer. The Internet history is searched for keyword(s) and the results of the query is returned for processing by the application (step 1002).

[0069] FIG. 12 depicts a process 1100 representing process “H” undertaken by the application for gathering user data from the user's location. The current IP address is sought from the local system, and the approximate location is obtained using the IP address (step 1101). The geographic location can be determined from the IP by utilizing external services like hostip.info and other similar services. After the approximate location is determined, this information is then used to scan the local file system to determine a more exact location by scanning through the cache and temporary internet files (step 1102). This location is returned to the application for processing (step 1103).

[0070] FIG. 13 depicts a process 1200 representing process “I” undertaken by the application for gathering user data from online games of interest to the user. A check is first made to determine if the user has subscriptions to an online gaming application (step 1201). If the user does have an online gaming application, the gaming data is scanned for keyword(s) (step 1203). This functionality would be internal assuming that the gaming application resided in the Google or Yahoo application, or any other online gaming provider. If the user does not subscribe to an online gaming application but uses an application that stores the games locally on the user's local system, the application scans the gaming data on the local computer (step 1202). Developer applications exist to scan various folders that are stored on the user's local computer. The result of the query is returned to the application for processing (step 1204).

[0071] FIG. 14 depicts a process 1300 representing process “J” undertaken by the application for gathering user data from DVR programs and the like. A check is first made to determine if the user has subscriptions to an online DVR service (step 1301). If the user does not subscribe to an online DVR service, the process returns as all DVR services are online (step 1304). If the user has an active subscription to an online DVR service application, the DVR data is scanned for keyword(s) (step 1302). Depending on the provider of the DVR data, the data can be made available by an external API provided by the company of the DVR application. If no API is available, the data can be obtained by various websites wherein the DVR subscription resides. The result of the query is returned to the application for processing (step 1303).

[0072] FIG. 15 depicts a process 1400 representing process “K” undertaken by the application for gathering user data from live video streaming, IPTV and the like. A check is first made to determine if the user has subscriptions to live video streaming or IPTV (step 1401). If the user does not subscribe to a live video streaming or IPTV, the process returns (step 1404), as all video streaming is online. If the user has an active subscription to an online video streaming or IPTV service, the recorded and scheduled data is scanned for keyword(s) (step 1403). Depending on the provider of the live video streaming and IPTV data, the data can be made available by an external API provided by the company of the live video streaming or IPTV application. If no API is available, the data can be obtained by various websites wherein the live video streaming or IPTV subscription resides. The result of the query is returned to the application for processing (step 1403).

[0073] FIG. 16 depicts a process 1500 representing process “L” undertaken by the application for gathering user data from web based shows. The local file system is searched for data pertaining to any web based shows that the user may have stored (step 1501). The data is then scanned for keyword(s) (step 1502) and the results are returned to the application for processing (step 1503).

[0074] FIG. 17 depicts a process 1600 representing process “M” undertaken by the application for gathering user data from GPS (cellular). The location is received by utilizing GPS on the user's mobile device (step 1601). Applications residing on mobile devices can utilize location-based services, as the devices that contain GPS provide APIs that allow interaction for location based services. The location is returned to the application for processing (step 1602).

[0075] As described in the Applicant's co-pending patent application now U.S. patent application 61/317,788, entitled “DYNAMIC COLLABORATION AND DOCUMENT-MANAGEMENT PLATFORM” filed on Mar. 26, 2010, referenced above, weights may be assigned to the results obtained as described above that give preference to certain types of query results over others, depending on how the system is configured.

[0076] After querying the user's local and remote systems, the results are analyzed, including applying any weightings, and key words are sought out that reflect the current interests of the user. The results from both the local and remote systems may be stored in a temporary text file. Information that may be stored for the different data types may be as follows:

• • [0077] Ads Clicked—the URL of the websites and any text, images and/or video associated with the advertisement;
  • [0078] Ads Served—the URL of the websites and any text, images and/or video associated with the advertisement;
  • [0079] Request Searches—the text that the user entered into the search engine;
  • [0080] Groups—the group titles and any text, images and/or video associated with the group description;
  • [0081] Emails/IMs/SMSs—the title and body of the emails and the data in the IMs and SMS msgs;
  • [0082] Calendar—the title of the calendar events and any associated text describing the event such as a location, date, time, duration, call-in data, participants, etc.;
  • [0083] Surfing History—the URL of the websites and any associated description stored about the websites as well as amount of time spent on the site, on each page of a site, etc.;
  • [0084] Location—the most specific description of the location that can be determined based on an IP address, a known address, product ordering history, etc.;
  • [0085] Games—the title of the games and any associated descriptions;
  • [0086] Video—the title of the video and any associated descriptions; and
  • [0087] GPS—the most specific description of the location that can be determined.

[0088] In another embodiment, the temporary text file is searched by the application of the invention for similarities. APIs are published that convert text into indexable/searchable tokens. One such API is the Java Package: org.apache.lucene.analysis. This Package implements tokenization—namely breaking of input text into small indexing elements or tokens. Some of the other analysis tools included in the Java package include:

• • [0089] Stemming—Replacing the words by their stems. For instance with English stemming “bikes” is replaced by “bike”; now query “bike” can find both documents containing “bike” and those containing “bikes”.
  • [0090] Stop Words Filtering—Common words as “the”, “and” and “a” rarely add any value to a search. Removing these shrinks the index size and increases performance. It may also reduce some “noise” and actually improve search quality.
  • [0091] Text Normalization—Stripping some or all accents and other character markings can make for better searching.
  • [0092] Synonym Expansion—Adding in synonyms at the same token position as the current word can mean more accurate matching when users search with words in the synonym set.

[0093] Utilizing a tokenizer program, main words from the temporary text file are stored and analyzed for repetition. The application analyzes (or together with another application running on at least one of the devices depicted in FIG. 1) text in a document for various occurrences. For example, using the Java tokenizer, the following code will tokenize a sentence:

[0094] String speech=“Four score and seven years ago”;

• • [0095] StringTokenizer st=new StringTokenizer(speech);
  • [0096] while (st.hasMoreTokens( )) {
    • [0097] println(st.nextToken( ));
  • [0098] }

[0099] The resulting output of the above code would be:

[0100] Four

[0101] score

[0102] and

[0103] seven

[0104] years

[0105] ago

[0106] Once the text is tokenized, it is analyzed for repetitious words, or apparent categories. The main categories found after analyzing the results of the queries are placed in a dropdown component and included in a Category List Window. In other embodiments, these categories can be presented in a drop down menu or in any other manner that can be viewed and/or acted upon by the user. FIG. 18 is an example GUI of a Category List Window 180 showing the categories the application displays to the user. The application presents a list of possible categories 181 for the new medium using the main topics found from the queries. The user selects a category or categories from the list 181 and presses the “Start” button 182, allowing the functionality to continue. The user can also press the “Go Back” button 183 to return to the previous window or can pick a category with a “Pick Your Own Category” option (not shown).

[0107] In another embodiment, the list of categories presented to the user is listed from the most popular at the top and the least popular at the bottom of the list. In another embodiment, the application does not present the list of categories to the user, but decides the category by utilizing the top (or most present) category after analysis of the temporary text file.

[0108] The application then allows the user to configure the medium. A sample interface 190 for configuring the medium is shown in FIG. 19. Through the interface 190, the user is able to configure various functional parts of the application that generates the medium including the number 191 and rate 192 of automatic entries, whether notifications of updates are sent to acquaintances 193 and a timeout for notifications 194. The options to configure in this example GUI 190 are only a sample of options that could be available. Additional options can be added and/or some of the current options can be subtracted from this example as will be apparent to a person skilled in the art.

[0109] The number 191 and rate 192 options of the configuration window 190 allow the user to specify the number and rate of automatic entries (including minutes and seconds, not shown) posted into the newly created medium. The next setting allows the user to specify if outgoing notifications are automatically sent to the individuals associated with the user. If the checkbox 193 is set, outgoing messages will be sent out.

[0110] Using these configuration parameters the application may be configured to handle automatic entries into the medium using the data found from the local and/or remote system search (which may be a one-time, a predetermined amount of times, or as a continuous search). For example, the application can automatically provide posts to the user's medium (which has just been created or which was previously created), such as blog posts to the user's blog based on information from at least one of the elements presented above (such as ads served, emails, GPS data, etc.). The application also uses the configuration parameters to manage the sending of outgoing messages automatically to individuals associated with the user, such as the user's acquaintances or individuals the user is interested in providing such information to, or who have expressed an interest in receiving such information, or who are currently receiving such information. The application may attempt to push data from the new or existing medium to one or more of the individuals referenced above. This occurs without the user's specification, but can be monitored by the user, or can be entirely turned off. The individuals may be found by any of the following: location of the user, remote information of the individuals, previous messages sent to/from the user to/from the individuals, etc.

[0111] The timeout window 194 of the configuration interface 190 allows the user to specify the time to allow the acquaintances to respond to the automatic message before the application will cease the sending of further notification messages.

[0112] In another embodiment, an encrypted text file external to the application is made available wherein the configuration settings can be configured outside of the running application. This text file is a file where the configuration element is provided (one per line), followed by “=”, then the setting. For instance:

[0113] AUTOENTRIES=2PERDAY

[0114] TIMEOUTNOTE=1DAY

[0115] TIMEOUTNOTE=1WEEK

[0116] In another embodiment, the timeout for notifications are set automatically, determined based on the historical response times by the user and the acquaintance, the user and a similar acquaintance, the average response time based on all users executing the application, the average response times based on all users utilizing the particular category, the average response time based on certain users exhibiting/utilizing features for establishing the content as described above, etc.

[0117] In another embodiment, the timeout period can automatically be extended if an acquaintance has previously responded. For instance, the timeout of notifications may automatically be increased to 2 days from 1 day if the acquaintance has previously responded. Also, the amount of responses and the elapsed time in between responses can be taken into account. For example, if the user and the acquaintance have each responded to one another on the same topic a number of times in a certain time frame with a small amount of time elapsed (a few minutes to a few days) in between responses, then the timeout of notifications may automatically be increased to 3 days or more from 1 day. This information and the logic to determine these increases is stored on at least one of the devices depicted in FIG. 1.

[0118] Once the user has made selections in the Configuration Window, if the “Create” button 195 is pressed, the Configuration Window is removed and the application begins to create the medium that was previously specified by the user. If the “Cancel” button 196 is pressed, the Configuration Window is removed and the application returns to the previous state.

[0119] In creating the medium, the application may include data from the results according to the user's choice in the Configuration Window. If an automatic entry is placed in the medium, the application may obtain the data from one or more of the following query results:

• • [0120] Calendar Event Titles and/or Descriptions;
  • [0121] Web page URLs and descriptions of ads served to the user;
  • [0122] Web page URLs and descriptions of ads the user clicked on;
  • [0123] Search terms entered by the user for searches;
  • [0124] Name of groups that the user is a member of;
  • [0125] Title and body of emails sent/received by the user;
  • [0126] City/State/Region of the user;
  • [0127] Title of games/video/streaming video that the user has interacted with.

[0128] There are sites available today allowing mediums of any nature to be created. A registration form typically needs to be filled out in order to create or to begin using a medium. The application of the instant embodiments will interact with the medium (for example, the website related to the medium) via a published API that is made available to developers/programmers. The API establishes a way for developers/programmers to give external applications the ability to log into the medium's website, as well as setting the ability to accept and submit data (such as text, photos, and video) into the medium, create an account in the medium. The interaction of the application of the current embodiments with the APIs of the mediums (such as websites including Facebook, Twitter, etc) is provided. This interaction will allow the current application to have seamless interaction with remote products, and give the application an intuitive user experience.

[0129] In another embodiment, when the medium is created the application will then have the option to automatically establish relationships to individuals associated with the user via Twitter, Facebook, MySpace, LinkedIn and other messaging and social network services by finding individuals/groups related to the medium's category.

[0130] The application utilizes APIs of popular applications (such as Facebook, MySpace, Twitter, etc) made available to developers to find individuals previously associated with the user and are related to the medium's category.

[0131] For instance, in social networking sites, such as the Facebook application, methods are exposed in the published API giving the ability to examine all of the comments of users that are friends of a user in Facebook. The following are some of the methods (in the Facebook API) allowing this functionality:

• • [0132] friends.get—Returns the identifiers for the current user's Facebook friends.
  • [0133] stream.getComments—This method returns all comments associated with a post in a user's stream.
  • [0134] users.getlnfo—Returns a wide array of user-specific information for each user identifier passed, limited by the view of the current user.
  • [0135] comments.add Adds a comment for a given xid on behalf of a user. Calls with a session secret may only act on behalf of the session user.

[0136] Using these, and similar methods, the application first obtains a list of all Facebook friends of the current user of the application, then stores in a temporary file (such as a text file stored in 104, see FIG. 1), all of the comments posted on the user's Facebook wall. This temporary file is parsed and any users are found that have posted comments relating to the medium's category. The application can use the published APIs to automatically post messages to those users. These messages contain the content of the data that is posted inside the medium either automatically by the application, or manually via the user. A similar process is followed for each of the social networking applications wherein the user has an active account (MySpace, Twitter, etc).

[0137] The individuals' responses are “placed inside” or provided to the medium for display as well. To avoid cluttering the medium with additional messages in-line with the existing content, they may not be directly in-line in the main section of the medium, but may be included in a sidebar where appropriate messages would be found. For instance, a new component 200 as shown in FIG. 20 and entitled “Messages” that consists of a Text box 201, a scrollbar 202, a listing of the message content 203 can be included on the medium, and a rolling display of the communication between the user and the acquaintance can be included therein. Also included below the message window is a button enabling the user to interact with messages. By example only, a button entitled “Post” 205 enables the user to post a response to the current message in the message window. Another button entitled “Clear” 206, for example, will clear out the messages in the window.

[0138] Each message that is sent out from the application has a configurable notation that is included (one or more of an icon, text, an image, video, a color or a sound) that may indicate that the message is not directly from the user, but automatically generated from the application. For instance, if the message is sent from the application to a blog, Twitter account, website, or any other webpage accepting messages, the name of the application will be appended to the user for the name or id of the person submitting the blog. Also, the name of the application can be replaced with the notation if the remote application's API accepts that format.

[0139] In one embodiment, a timer is set on every outgoing message to manage the individual(s). If 2-way communication is not established within the configurable amount of time, the relationship will be severed, and if 2-way communication is made, the communication will continue.

[0140] FIG. 21 depicts a message flow between the elements of the system. The user 214 selects the type of medium desired 2102, then the application queries the local 212 and remote 218 system in regards to the current user 2104, 2106, 2108, 2110. The local data 2118 and remote data 2116 responses are received by the application and a temporary data file is created and analyzed 2130. The text file is parsed 2130 for commonalities to determine the proper categories to present to the user 2132. The user selects the category for the medium and configures the application 2134. The medium is then created by the application 2136. Individuals relating to the chosen category and associated with the user are sought by querying the remote system 2138 and the individuals are returned to the application 2144. The application, according to the user's specific configuration will send messages to the remote individuals 2146.

[0141] A specific example for creating a blog will now be described. When the user starts the application, they are presented with the Application Top Window (see FIG. 3). The user selects the “Blog” category 32, and selects the “Start” button 35.

[0142] The application begins to gather personal information about the user by querying the user's local file system, as well as the remote systems. The application finds the following information regarding running from the user's local system:

[0143] Emails

• • [0144] A chat/IM history was saved between the user and another person with the following text: “What about doing a 5 mile run on Saturday, you in?”
  • [0145] An email is encountered from “runningclubofchicago.com”. It discusses upcoming running events that are in the user's local area.
  • [0146] An email is encountered discussing the “Runners World” magazine, regarding subscription renewal.

[0147] Surfing History

• • [0148] The “RunnersWorld.com” URL was perused by the user including many internal sites to the domain.
  • [0149] The “Brooks.com” website was found and many running shoes were viewed on the domain.
  • [0150] A YouTube reference was found entitled “Trail Running—Best of”.

[0151] Calendar Events

• • [0152] An event was scheduled in the user's local calendar with the title: “5-mile run with Tony”.
  • [0153] An event was scheduled in the user's local calendar with the title: “Run for the Arts 10k July 22nd 2009”

[0154] Videos

• • [0155] A video was found in the user's local file system entitled “Marathon Training—The Long Run.mp4”

[0156] The application finds the following information regarding running from querying the remote systems:

[0157] Google/Groups

• • [0158] The user was found to be a member of the Chicago Long-Distance Running Group.

[0159] www.running-log.com

• • [0160] The online training log was encountered when viewing surfing history. A published API allowed the program access to the history of events in the application.

[0161] Hulu

• • [0162] The video “Chariots of Fire” was viewed by the user online.

[0163] When creating components used in the application, the application incorporates lists to be included as the dropdown or menu components. Using the results from querying the user's local system, as well as the remote system, the application creates a text-based data file wherein the data is stored for analysis. In analyzing the text data, the application classifies the elements it encounters into various categories. These categories become the list elements 181 in the category list window 180 shown in FIG. 18. Because the word, or various forms of the word “run” were encountered, the application made “running” one of the list elements.

[0164] The user selects the “Running” list element, and selects the “Start” button 185 indicating that a blog on running is desired.

[0165] The Configuration Window 190 is then presented to the user to allow the user to configure the behavior once the medium is created. The user selects to have the application automatically add one new blog per day from the email and surfing history areas. The user also selects to have outgoing notifications sent to acquaintances by checking the element 193. Finally, the user sets the timeout for notifications 194 to one day. The user then selects the “Create” button 195, and the application begins to generate the new running blog. There are various blogging sites available today allowing blogs of any nature to be created. One such site is www.blogger.com. Blogger is a Google based blogging creation site that allows a user to share thoughts with the world, as well as include photos, text, and videos. There is a registration form that needs to be filled out in order to begin a blog, as is for most, if not all, blogging sites.

[0166] The application will interact with the Blogger website via an API that is provided to developers. The API establishes a way for programmers to give external applications the ability to log into the www.blogger.com website, as well as setting the ability to accept comments to your blog, create a blog, post to a blog, etc.

[0167] The application creates the blog, and the new running blog is begun. The first blog entry is automatically entered from the data found in the Calendar events of the user's local system: “Run for the Arts 10k July 22nd 2009”.

[0168] Using the published Twitter API, the application queries the user's followers and searches through the Twitter messages to find that there are three Twitter users that have been contacted in the past by the user regarding running. The three users are automatically sent the blog entries via Twitter. Their responses are posted to the blog. The Twitter entries are not inline with the main blog, but in a separate “Message” section of the blog.

[0169] As will be apparent from the foregoing, the components of the system 100 may be embodied in hardware, software, firmware or a combination of hardware, software and/or firmware. In a hardware embodiment, the application may be executed on a processor of a personal computing device 103 of the user (FIG. 1). As shown in FIG. 22, a processor 2205 may be operatively associated with a memory 2206. The processor 2205 may communicate with other processes, such as a processor 2215 of a remote system 218 (FIG. 21) through communications link 2220, such as an internet link, FTP link, cellular link, and the like. The remote system processor 2215 may also be operatively associated with a memory 2216 and may also be operatively associated with the remote data servers 220 shown in FIG. 21.

[0170] The memory 2206 may store instructions that are executable on the processor 2205, such as for executing various aspects of the application as described above. An example instruction set 2300 that may be executed on the processor 2205 is depicted in the flowchart of FIG. 23. Specifically, when executed, the instruction set 2300 allows the processor 2205 to present an automatic content behavior interface to a user (step 2301), such as the configuration window 190 shown in FIG. 19. The processor may receive one or more parameters for automatic content behavior from the user (step 2302). At the appropriate time, such as set by an automatic update schedule configured by the user through the configuration interface 190, the processor generates an automatic content update for the medium in accordance with the at least one automatic content behavior (step 2303). The update may be generated from content received from the remote system processor 2215 as well as local systems (not shown in FIG. 22). The processor 2205 then posts the automatic content update to the medium as set by the configured automatic content behavior parameters (step 2304).

[0171] Although embodiments of the present invention have been illustrated in the accompanied drawings and described in the foregoing description, it will be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit of the invention as set forth and defined by the following claims. For example, the capabilities of the invention can be performed fully and/or partially by one or more of the blocks, modules, processors or memories. Also, these capabilities may be performed in the current manner or in a distributed manner and on, or via, any device able to provide and/or receive information. Further, although depicted in a particular manner, various modules or blocks may be repositioned without departing from the scope of the current invention. Still further, although depicted in a particular manner, a greater or lesser number of modules and connections can be utilized with the present invention in order to accomplish the present invention, to provide additional known features to the present invention, and/or to make the present invention more efficient. Also, the information sent between various modules can be sent between the modules via at least one of a data network, the Internet, an Internet Protocol network, a wireless source, and a wired source and via plurality of protocols.