MULTI-MEDIA CONTENT

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Patent Application No.

62/220,722, filed on September 18, 2015 and entitled SOCIAL NETWORK FOR CURATING AND CONTEXTUAL DISCUSSION OF HOSTED MULTI-MEDIA CONTENT, the entirety of which is incorporated by reference hereby.

TECHNICAL FIELD

Disclosed are systems, applications, devices and processes for social networking and web- content management.

BACKGROUND

Social networks and online commerce sites provide platforms for users to interact, publish, promote and create. However social networks such as Facebook®, Pinterest®, Twitter®, Behance® and Tumblr® give users a constrained degree of control over how content is presented due to feed- based pushed content, or fail to provide tools for targeted contextual discussion of creative work in a unified platform. Social network platforms also face problems in providing user interfaces that allow users to curate and interact with online content as the user would like to have it presented to them while still engaging new content added by users. None of the extant social networking or blogging platforms provide technological interfaces and interface tools that give users a high degree of control over how information is presented to the user, how that content is presented to the pubic and other network users, and contextual discussion of said content, while at the same time taking advantage of feed-based provision of content to and from other network members in a way that allows the creator to maintain attribution and a degree of control over the content.

SUMMARY

In various embodiments, described is a system for creating and managing content over a social network, comprising: a network computer, including: a transceiver for communicating over the network; the memory for storing at least instructions and including a database including a plurality of hosted webpages, a processor device coupled to the memory and the database and in communication through the network and programmed for executing instructions stored in a memory; a Library interface associated with a social network user profile including a Library webpage for displaying a plurality of arrangeable cover objects, each cover object comprising a dedicated link to a webpage uniquely associated with the cover object and a preformatted icon, the cover objects including a Project cover object linked to a Project webpage and a Collection cover object linked to a Collection interface webpage comprising a Collection of one or more Project cover objects, wherein the Library interface and Collection interface webpage are both configured to allow a user to employ a client computer to manually arrange the cover objects in a default order of the user's choosing; the Project interface configured to allow a user to employ a client computer to create the Project webpage and the preformatted Project cover object for the uniquely associated Project webpage, including selecting an image file to be used for the preformatted Project cover object; wherein the Project interface comprises a plurality of tools for creating arrangeable text objects and media objects for the Project webpage; and the Collection interface being configured allow a user create the Collection of one or more Project cover objects, and to allow the user to employ a client computer to manually arrange the Project cover objects into a default order.

In various embodiments, the system can further comprise: each arrangeable cover object including a tool for generating a contact message for contacting the user profile associated with the cover object.

In various embodiments, the system can further comprise: a discussion database comprising a plurality of discussion interface objects, each discussion interface object configured to contain a message history between specific user participants linked to the discussion interface object, each discussion interface object being uniquely Hnked to a specific Project or Collection; the system being configured to allow a user to create a new discussion interface for a plurality of selected users for any public Project interface or Collection interface in the system, wherein the discussion interface objects are linked to, but independent interfaces from, the uniquely linked Project or Collection.

In various embodiments, the system can further comprise: the system being configured to allow a user to create a new discussion interface for one or more other users about a private Project webpage or private Collection webpage in the system, and only user participants provided a link to the discussion interface object can access to the Project webpage or Collection interface webpage. In various embodiments, the system can further comprise: a Storefront interface comprising a Publications interface webpage, the system being configured to allow a user to employ a client computer to create a profile cover object for the Storefront interface, including selecting an image file to be used for a preformatted profile icon; the Publications interface configured display Project cover objects or Collection cover objects published to the Storefront interface, wherein the publications webpage is configured to allow a user to employ a client computer to manually arrange the cover objects into a default order, the Storefront interface being publicly available to at least other members registered to the network.

In various embodiments, the system can further comprise: the processor device coupled to the memory and the database and in communication through the network and programmed, upon receiving a request from a client computer in network communication with the hosted webpages: to publish Project interface webpage cover objects or Collection interface webpage cover objects to the Publications interface, wherein hosted webpages created by a user are not publicly available to members of the network until published.

In various embodiments, the system can further comprise: the Storefront interface comprising a Followers interface webpage, and a Following interface webpage, the Followers interface webpage displaying profile cover objects for social network users following the user's profile; and the Following interface displaying profile cover objects for other social network users the user is following.

In various embodiments, the system can further comprise: the processor device coupled to the memory and the database and in communication through the network and programmed, upon receiving a request from a client computer in network communication with the processor device: to serve the hosted webpages for the interfaces to the client computer, including the hosted webpages with the arrangeable cover objects.

In various embodiments, the system can further comprise: the processor device coupled to the memory and the database and in communication through the network and programmed, upon receiving a request from a client computer in network communication with the processor device: to share Project webpages or Collection webpages with at least other selected network members. In various embodiments, described is an application for a client computer, the application comprising: a tool for generating a user profile for a social network; a Library interface associated with the social network user profile, including a tool for accessing a Library hosted webpage for listing a plurality of arrangeable cover objects, each cover object comprising a dedicated link to a webp ge uniquely associated with the cover object and a preformatted icon, the cover objects including a Project cover object linked to a Project hosted webpage and a Collection cover object linked to a Collection interface hosted webpage comprising a Collection of Project cover objects, wherein the application is configured to allow a user to employ the client computer to manually arrange the cover objects into a default order on both the library interface and Collection interface; and a Project interface including tools configured to allow a user to employ the client computer to create the Project webpage and the preformatted Project cover object for the uniquely associated Project webpage, including selecting an image file to be used for the preformatted Project icon; the application configured to be operatively connected to a processor device coupled to a memory and in communication through a network to a network server comprising hosted webpages and programmed to request and receive the hosted webpages for the interfaces, including the hosted webpages with the arrangeable cover objects.

In various embodiments, the application can further comprise: the arrangeable cover object including a tool for generating a contact message for contacting the user profile associated with the cover object.

In various embodiments, the application can further comprise: wherein the application further comprises: a discussion tool operatively connected to a discussion database comprising a plurality of discussion interface objects, each discussion object configured to contain a message history between specific user participants linked to the discussion interface object, each discussion interface object being uniquely linked to a specific Project or Collection, the discussion interface objects being linked to, but independent interfaces from, the uniquely linked Project or Collection, the discussion tool being configured to allow a user to create a new discussion interface for a plurality of selected users for any public Project interface or Collection interface in the system. In various embodiments, the application can further comprise the discussion tool being configured to allow a user to create a new discussion interface for one or more other users about a private Project webpage or private Collection interface webpage in the system, and only user participants provided a link to the discussion interface object can access to the Project interface or Collection interface.

In various embodiments, the application can further comprise: a Storefront interface comprising a Publications interface, the application comprising a tool configured to allow a user to employ a client computer to create a profile cover object for the Storefront interface, including selecting an image file to be used for a preformatted profile icon; the Publications interface configured display Project cover objects or Collection cover objects published to the Storefront interface, wherein the application comprises a tool configured to allow a user to employ a client computer to manually arrange the cover objects into a default order on the Publications interface, the Storefront interface being publicly available to at least other members registered to the network.

In various embodiments, the application can further comprise: a publication tool configured to allow a user to employ the client computer to publish Project interface cover objects or Collection interface cover objects to the Publications interface, wherein hosted webpages created by a user are not publicly available to at least members of the network until published. In various embodiments, the application can farther comprise: the Storefront interface comprising a Followers interface, and a Following interface, the Followers interface displaying profile cover objects for social network users following the user's profile; and the Following interface displaying profile cover objects for other social network users the user is following.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present invention are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified.

For a better understanding of the present invention, reference will be made to the following Detailed Description, which is to be read in association with the accompanying drawings, wherein: FIGURE 1 is a system diagram of an environment in which at least one of the various embodiments may be implemented; FIGURE 2 shows an embodiment of a client computer that may be included in a system such as that shown in FIGURE 1 ;

FIGURE 3 shows an embodiment of a network computer that may be included in a system such as that shown in FIGURE 1 ;

FIGURES 4A-4C illustrate logical architectures of a system for the social networking system in accordance with at least one of the various embodiments;

FIGURES 5-25 show user interfaces and processes therefor in accordance with various embodiments.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific embodiments by which the invention may be practiced. The embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the embodiments to those skilled in the art. Among other things, the various embodiments may be methods, systems, media, or devices. Accordingly, the various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.

Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The term "herein" refers to the specification, claims, and drawings associated with the current application. The phrase "in one embodiment" as used herein does not necessarily refer to the same embodiment, though it may.

Furthermore, the phrase "in another embodiment" as used herein does not necessarily refer to a different embodiment, although it may. Thus, as described below, various embodiments of the invention may be readily combined, without departing from the scope or spirit of the invention.

In addition, as used herein, the term "or" is an inclusive "or" operator, and is equivalent to the term "and/ or," unless the context clearly dictates otherwise. The term "based on" is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the s ecification, the meaning of "a," "an," and "the" include plural references. The meaning of "in" includes "in" and "on."

As used herein, the term "widget controller" refers to a computer program that may be operative on a client application. Widget controllers may be downloaded and/or otherwise deployed to a client application. Widget controllers may be arranged to be operative for downloading content, monitoring consumer actions, or otherwise managing widgets located within client applications.

As used herein, the term "widget" refers to a user-interface element located in the client application. Widgets may be invisible or visible to users of the client applications. In some cases, a widget controller may generate widget "on-fhe-ffy" before deploying content into the widget. Widgets may be adapted to reflect the operating environment of the client application that they are being hosted within. For example, in clients that support HTML, CSS a widget may be an HTML element such as a DIV, P, or the like. For client application operative in a Java environment, a widget may be a View object or Window object, and so on.

As used herein, the term "Host" may refer to an individual person, partnership, organization, or corporate entity that may own or operate one or more digital media properties (e.g., web sites, mobile applications, or the like). Hosts may arrange digital media properties to use hyper-local targeting by arranging the property to integrate with widget controllers, content management servers, or content delivery servers.

The following briefly describes embodiments of the invention in order to provide a basic understanding of some aspects of the invention. This brief description is not intended as an extensive overview. It is not intended to identify key or critical elements, or to delineate or otherwise narrow the scope. Its purpose is merely to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

Illustrative Operating Environment

FIGURE 1 shows components of one embodiment of an environment in which embodiments of the innovations described herein may be practiced. Not all of the components may be required to practice the innovations, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of the innovations. As shown, system 100 of FIGURE 1 includes local area networks (LANs)/ wide area networks (WANs)— (network) 110, wireless network 108, client computers 102-105, Social Network Server Computer (CDSC) 112, and Network Server Computer 114 (e.g. other computer services or networks).

At least one embodiment of client computers 102-105 is described in more detail below in conjunction with FIGURE 2. In one embodiment, at least some of client computers 102-105 may operate over a wired and/ or wireless network, such as networks 110 and/or 108. Generally, client computers 102-105 may include virtually any computer capable of communicating over a network to send and receive information, perform various online activities, offline actions, or the like. Client computers 102- 05 may be employed, for example, as an end-user computing node. In embodiments, one or more of client computers 102-105 may be configured to operate within a business or other entity to perform a variety of services for the business or other entity. For example, client computers 102-105 may be configured to operate as a web server, an accounting server, a production server, an inventory server, or the like. However, client computers 102-105 are not constrained to these services. It should be recognized that more or less client computers may be included within a system such as described herein, and embodiments are therefore not constrained by the number or type of client computers employed.

Computers that may operate as client computer 102 may include computers that typically connect using a wired or wireless communications medium such as personal computers, multiprocessor systems, microprocessor-based or programmable electronic devices, network PCs, or the like. In some embodiments, client computers 102-105 may include virtually any portable personal computer capable of connecting to another computing device and receiving information such as, laptop computer 103, smart mobile telephone 104, and tablet computers 105, and the like. However, portable computers are not so limited and may also include other portable devices such as cellular telephones, radio frequency (RF) devices, infrared (IR) devices, Personal Digital Assistants (PDAs), handheld computers, wearable computers, integrated devices combining one or more of the preceding devices, and the like. As such, client computers 102-105 typically range widely in terms of capabilities and features. Moreover, client computers 102-105 may access various computing applications, including a browser, or other web- based application.

A web-enabled client computer may include a browser application that is configured to receive and to send webpages, web-based messages, and the like. The browser application may be configured to receive and display graphics, text, multimedia, and the like, employing virtually any web-based language, including a wireless application protocol messages (WAP), and the like. In one embodiment, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), extensible Markup Language (XML), and the like, to display and send a message. In one embodiment, a user of the client computer may employ the browser application to perform various activities over a network (online). However, another application may also be used to perform various online activities.

Client computers 102-105 may also include at least one other client application that is configured to receive and/ or send content between another computer. The client application may include a capability to send and/ or receive content, or the like. The client application may further provide information that identifies itself, including a type, capability, name, and the like. In one embodiment, client computers 02-105 may uniquely identify themselves through any of a variety of mechanisms, including an Internet Protocol (IP) address, a phone number, Mobile Identification Number (MIN), an electronic serial number (ESN), or other device identifier. Such information may be provided in a network packet, or the like, sent between other client computers, Social Network Server Computer 112, Network Server Computer 114, or other computers.

Client computers 102-105 may further be configured to include a client application that enables an end-user to log into an end-user account that may be managed by another computer, such as Social Network Server Computer 112, Network Server Computer 114, or the like. Such end-user account, in one non-limiting example, may be configured to enable the end-user to manage one or more online activities, including in one non-limiting example, search activities, social networking activities, browse various websites, communicate with other users, or the like. However, in embodiments participation in at least some online activities may also be performed without logging into the end-user account.

Wireless network 108 is configured to couple client computers 103-105 and its components with network 110. Wireless network 108 may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection for client computers 103-105. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, cellular networks, and the like. In one embodiment, the system may include more than one wireless network. Wireless network 108 may further include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links, and the like. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of wireless network 108 may change rapidly.

Wireless network 108 may further employ a plurality of access technologies including 2nd (2G),

3rd (3G), 4th (4G) 5th (5G) generation radio access for cellular systems, WLAN, Wireless Router (WR) mesh, and the like. Access technologies such as 2G, 3G, 4G, 5G, and future access networks may enable wide area coverage for mobile devices, such as client computers 103-105 with various degrees of mobility. In one non-limiting example, wireless network 108 may enable a radio connection through a radio network access such as Global System for Mobil communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Wideband Code Division Multiple Access ( CDMA), High Speed Downlink Packet Access (HSDPA), Long Term Evolution (LTE), and the like. In essence, wireless network 108 may include virtually any wireless communication mechanism by which information may travel between client computers 103-105 and another computer, network, and the like.

Network 110 is configured to couple network computers with other computers and/ or computing devices, including, Social Network Server Computer 112, Network Server Computer 114, client computer 102, and client computers 103-105 through wireless network 108. Network 110 is enabled to employ any form of computer readable media for communicating information from one electronic device to another. Also, network 110 can include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, other forms of computer-readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within LANs typically include twisted wire pair or coaxial cable, while

communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including Tl , T2, T3, and T4, and/ or other carrier mechanisms including, for example, E- carriers, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Moreover, communication links may further employ any of a variety of digital signaling technologies, including without limit, for example, DS-0, DS-1, DS-2, DS-3, DS-4, OC-3, OC-12, OC-48, or the like.

Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In one embodiment, network 110 may be configured to transport information of an Internet Protocol (TP). In essence, network 110 includes any communication method by which information may travel between computing devices.

Additionally, communication media typically embodies computer readable instructions, data structures, program modules, or other transport mechanism and includes any information delivery media. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.

One embodiment of a Social Network Server Computer 112 is described in more detail below in conjunction with FIGURE 3. Briefly, however, Social Network Server Computer Server Computer 112 includes virtually any network computer capable of providing the interfaces and social networking capabilities once configured to include the technological interfaces as described herein. Computers that may be arranged to operate as Social Network Server Computer 112 include various network computers, including, but not limited to sever computers, multiprocessor systems, microprocessor- based or programmable consumer electronics, network PCs, server computers, network appliances, and the like.

Although FIGURE 1 illustrates Social Network Server Computer 112 as a single computer, the invention is not so limited. For example, one or more functions of the Social Network Server

Computer 112 may be distributed across one or more distinct network computers. Moreover, Social Network Server Computer 112 is not limited to a particular configuration. Thus, in one embodiment, Social Network Server Computer 112 may contain a plurality of network computers. In another embodiment, Social Network Server Computer 112 may contain a plurality of network computers that operate using a master/ slave approach, where one of the plurality of network computers of Social

Network Server Computerl l2 is operative to manage and/ or otherwise coordinate operations of the other network computers. In other embodiments, the Social Network Server Computer 112 may operate as a plurality of network computers arranged in a cluster architecture, a peer-to-peer architecture, and/or even within a cloud architecture. Thus, the invention is not to be construed as being limited to a single environment, and other configurations, and architectures are also envisaged. In some embodiments, either Social Network Server Computer 112 may be enabled to deliver content, respond to user interactions with the content, track user interaction with the content, update widgets and widgets controllers, or the like.

Illustrative Client Computer

FIGURE 2 shows one embodiment of Client Computer 200 that may be included in a system implementing embodiments of the invention. Client Computer 200 may include many more or less components than those shown in FIGURE 2. However, the components shown are sufficient to disclose an illustrative embodiment for practicing the present invention. Client Computer 200 may represent, for example, one embodiment of at least one of Client Computers 102-105 of FIGURE 1.

As shown in the figure, Client Computer 200 includes a processor 202 in communication with a mass memory 226 via a bus 234. In some embodiments, processor 202 may include one or more central processing units (CPU). Client Computer 200 also includes a power supply 228, one or more network interfaces 236, an audio interface 238, a display 240, a keypad 242, an illuminator 244, a video interface 246, an input/ output interface 248, a haptic interface 250, and a global positioning system (GPS) receiver 232.

Power supply 228 provides power to Client Computer 200. A rechargeable or non-rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an alternating current (AC) adapter or a powered docking cradle that supplements and/ or recharges a battery.

Client Computer 200 may optionally communicate with a base station (not shown), or directly with another computer. Network interface 236 includes circuitry for coupling Client Computer 200 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, GSM, CDMA, TDMA, GPRS, EDGE, WCDMA, HSDPA, LTE, user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), short message service (SMS), WAP, ultra wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), session initiated protocol/real-time transport protocol (SIP/RTP), or any of a variety of other wireless communication protocols. Network interface 236 is sometimes known as a transceiver, transceiving device, or network interface card (NIC). Audio interface 238 is arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 238 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others and/ or generate an audio acknowledgement for some action.

Display 240 may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), organic LED, or any other type of display used with a computer. Display 240 may also include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand.

Keypad 242 may comprise any input device arranged to receive input from a user. For example, keypad 242 may include a push button numeric dial, or a keyboard. Keypad 242 may also include command buttons that are associated with selecting and sending images.

Illuminator 244 may provide a status indication and/ or provide light. Illuminator 244 may remain active for specific periods of time or in response to events. For example, when illuminator 244 is active, it may backlight the buttons on keypad 242 and stay on while the Client Computer is powered. Also, illuminator 244 may backlight these buttons in various patterns when particular actions are performed, such as dialing another client computer. Illuminator 244 may also cause light sources positioned within a transparent or translucent case of the client computer to illuminate in response to actions.

Video interface 246 is arranged to capture video images, such as a still photo, a video segment, an infrared video, or the like. For example, video interface 246 may be coupled to a digital video camera, a web-camera, or the like. Video interface 246 may comprise a lens, an image sensor, and other electronics. Image sensors may include a complementary metal-oxide-semiconductor (CMOS) integrated circuit, charge-coupled device (CCD), or any other integrated circuit for sensing light.

Client computer 200 also comprises input/ output interface 248 for communicating with external devices, such as a headset, or other input or output devices not shown in FIGURE 2.

Input/ output interface 248 can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like.

Haptic interface 250 is arranged to provide tactile feedback to a user of the client computer. For example, the haptic interface 250 may be employed to vibrate client computer 200 in a particular way when another user of a computing computer is calling. In some embodiments, haptic interface 250 may be optional.

Client computer 200 may also include GPS transceiver 232 to determine the physical coordinates of client computer 200 on the surface of the Earth. GPS transceiver 232, in some embodiments, may be optional. GPS transceiver 232 typically outputs a location as latitude and longitude values. However, GPS transceiver 232 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of client computer 200 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 232 can determine a physical location within millimeters for client computer 200; and in other cases, the determined physical location may be less precise, such as within a meter or significantly greater distances. In one embodiment, however, client computer 200 may through other components, provide other information that may be employed to determine a physical location of the computer, including for example, a Media Access Control (MAC) address, IP address, or the like.

Mass memory 226 includes a Random Access Memory (RAM) 204, a Read-only Memory (ROM) 222, and other storage means. Mass memory 226 illustrates an example of computer readable storage media (devices) for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory 226 stores a basic input/ output system (BIOS) 224 for controlling low-level operation of client computer 200. The mass memory also stores an operating system 206 for controlling the operation of client computer 200. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized client communication operating system such as Microsoft Corporation's Windows Mobile™, Apple Corporation's iOS™, Google Corporation's Android™ or the Symbian® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components and/or operating system operations via Java application programs.

Mass memory 226 further includes one or more data storage 208, which can be utilized by client computer 200 to store, among other things, applications 214 and/ or other data. For example, data storage 208 may also be employed to store information that describes various capabilities of client computer 200. The information may then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 208 may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Further, data storage 208 may also store message, we page content, or any of a variety of user generated content. At least a portion of the information may also be stored on another component of client computer 200, including, but not limited to processor readable storage media 230, a disk drive or other computer readable storage devices (not shown) within client computer 200.

Processor readable storage media 230 may include volatile, nonvolatile, removable, and non- removable media implemented in any method or technology for storage of information, such as computer- or processor-readable instructions, data structures, program modules, or other data.

Examples of computer readable storage media include RAM, ROM, Electrically Erasable

Programmable Read-only Memory (EEPROM), flash memory or other memory technology, Compact

Disc Read-only Memory (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other physical medium which can be used to store the desired information and which can be accessed by a computer.

Processor readable storage media 230 may also be referred to herein as computer readable storage media and/ or computer readable storage device.

Applications 214 may include computer executable instructions which, when executed by client computer 200, transmit, receive, and/ or otherwise process network data. Network data may include, but is not limited to, messages (e.g. SMS, Multimedia Message Service (MMS), instant message (ΊΜ), email, and/ or other messages), audio, video, and enable telecommunication with another user of another client computer. Applications 214 may include, for example, browser 218, and other applications 220, including interface applications configured to provide some or all of the interfaces or processes and operations therefor as described with respect to the use cases of FIGURES 5-25. Other applications 220 may include, but are not limited to, calendars, search programs, email clients, IM applications, SMS applications, voice over Internet Protocol (V OIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. Browser 218 may include virtually any application configured to receive and display graphics, text, multimedia, messages, and the like, employing virtually any web based language. In one embodiment, the browser application is enabled to employ HDML, WML, WMLScript, JavaScript, SGML, HTML, XML, and the like, to display and send a message. However, any of a variety of other web-based programming languages may be employed. In one embodiment, browser 218 may enable a user of client computer 200 to communicate with another network computer, such as Social Network Server Computer 112 and/ or Network Server Computer 114 of FIGURE 1.

Applications 214 may also include Widget Controller 210 and one or more Widgets 212.

Widgets 212 may be Collections of content provided to the client computer by Social Network Server Computer 112. Widget Controller 210 may be a program that may be provided to the client computer by Network Server Computer 114. Widget Controller 210 and Widgets 212 may run as native client computer applications or they may run in Browser 218 as web browser based applications. Also, Widget Controller 210 and Widgets 212 may be arranged to run as native applications or web browser applications, or combination thereof. Widget Controller 210 and Widgets can also be arranged to provide and run some or all of interfaces as described with respect to the use cases of FIGURES 5-25 and processes and operations therefor.

Illustrative Network Computer

FIGURE 3 shows one embodiment of a network computer 300, according to one embodiment of the invention. Network computer 300 may include many more or less components than those shown. The components shown, however, are sufficient to disclose an illustrative embodiment for practicing the invention. Network computer 300 may be configured to operate as a server, client, peer, a host, or any other computer. Network computer 300 may represent, for example Social Network Server Computer 112 of FIGURE 1, and/or other Network Computers 114.

Network computer 300 includes processor 302, processor readable storage media 328, network interface unit 330, an input/output interface 332, hard disk drive 334, video display adapter 336, and memory 326, all in communication with each other via bus 338. In some embodiments, processor 302 may include one or more central processing units.

As illustrated in FIGURE 3, network computer 300 also can communicate with the Internet, or some other communications network, via network interface unit 330, which is constructed for use with various communication protocols including the TCP/IP protocol. Network interface unit 330 is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

Network computer 300 also comprises input/ output interface 332 for communicating with external devices, such as a keyboard, or other input or output devices not shown in FIGURE 3.

Input/ output interface 332 can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like.

Memory 326 generally includes RAM 304, ROM 322 and one or more permanent mass storage devices, such as hard disk drive 334, tape drive, optical drive, and/ or floppy disk drive. Memory 326 stores operating system 306 for controlling the operation of network computer 300. Any general- purpose operating system may be employed. Basic input/ output system (BIOS) 324 is also provided for controlling the low4evel operation of network computer 300.

Although illustrated separately, memory 326 may include processor readable storage media 328. Processor readable storage media 328 may be referred to and/ or include computer readable media, computer readable storage media, and/ or processor readable storage device. Processor readable storage media 328 may include volatile, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of processor readable storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other media which can be used to store the desired information and which can be accessed by a computer.

Memory 326 further includes one or more data storage 308, which can be utilized by network computer 300 to store, among other things, applications 314 and/or other data such as content 310. For example, data storage 308 may also be employed to store information that describes various capabilities of network computer 300. The information may then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 308 may also be employed to store messages, webpage content, or the like. At least a portion of the information may also be stored on another component of network computer 300, including, but not limited to processor readable storage media 328, hard disk drive 334, or other computer readable storage medias (not shown) within client computer 300.

Data storage 308 may include a database, text, spreadsheet, folder, file, or the like, that may be configured to maintain and store user account identifiers, user profiles, email addresses, IM addresses, and/ or other network addresses; or the like.

In at least one of the various embodiments, Data storage 308 may include action/ view information 310, which may contain information for one or more users.

Data storage 308 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 302 to execute and perform actions. In one embodiment, at least some of data store 308 might also be stored on another component of network computer 300, including, but not limited to processor-readable storage media 328, hard disk drive 334, or the like.

Applications 312 may include computer executable instructions, which may be loaded into mass memory and run on operating system 306. Examples of application programs may include transcoders, schedulers, calendars, database programs, word processing programs, Hypertext Transfer Protocol (HTTP) programs, customizable user interface programs, IPSec applications, encryption programs, security programs, SMS message servers, IM message servers, email servers, account managers, search programs, voice over Internet Protocol (V OIP) applications, contact managers, task managers, transcoders, search programs, and so forth. Applications 312 may also include Website Server 314, Feed Generator 316, Privacy Server 318, Action Logger 319, Request Server 320, and/or Page Builder 321.

Applications 312 can be configured to provide page and tool interfaces that may be hosted on

Social Network Server Computer 112, or the like. In any event, Applications 316 may employ processes, or parts of processes, similar to those described in conjunction with the use cases of FIGURES 5-25, to perform at least some of its actions.

Website server 314 may represents any of a variety of information and services that are configured to provide content, including messages, over a network to another computer. Thus, website server 314 can include, for example, a web server, a File Transfer Protocol (FTP) server, a database server, a content server, or the like. Website server 314 may provide the content including messages over the network using any of a variety of formats including, but not limited to WAP, HDML, WML, SGML, HTML, XML, Compact HTML (cHTML), Extensible HTML (xHTML), or the like. Illustrative Logical System Architecture

FIGURES 4A-4B illustrate block diagrams of a logical architecture 400 for a social network server in accordance with at least one of the various embodiments. As used herein, the term "website" means any system providing content and is not limited to those systems supporting content provided via the Internet or the http protocol. In general functions described herein as being performed on the server side may also be performed on the client side as appropriate.

A user is also a member of a social network 112. Generally, the social network 112 provides its members 116-1 to 116-5 with a platform to interact with other members 116-1 to 116-5 of the social network 112. The members 116-1 to 116-5 may link to one another, or otherwise make internal connections, by authorizing other members 116-1 to 116-5 to access information associated with their social network profiles as described herein. Members 116-1 to 116-5 may add connections 118 to other members 116-1 to 116-5 individually, or may add teams of members 116-1 to 116-5 associated with a particular organization, hobby or group as allowed by the social network 114. Alternatively, the social network 114 may automatically add connections 118 between members 116-1 to 116-5 given various members' similar interests in various activities or past connections, such as work history or prior matriculation.

Connections 118 can be "two-way" connections 120, where both parties are allowed to directly communicate with one another or "one-way" 118 connections 122, where a user profile 124 is authorized to communicate directly with another user's profile 126, but the other user's profile 126 is not authorized to communicate directly with the user profile 124. The other user's pro file 126 may still have access to other information associated with the user profile 124, for example via a following feed, but may be restricted from adding text, video or pictures to the user profile 124 or from sending nonpublic communication to the user profile 124 within the social network 112. The social network 112 may also allow expanded rings of communication, whereby even if one user profile 126 is not directly authorized to communicate with another user profile 128, if the user profile 126 is authorized to connect to other user profiles which are authorized to direcdy communicate with the user profile 128, the user profile 126 is thereby authorized, through this string of authorizations, to communicate directly with the user profile 128. The Social Network Server Computer 112 has a web server 314, an action logger 319, an application programming interface (API) request server 320, an action log 338, a feed generator 316, a user profile database 342, a connection database 344, and a page/interface database 345, and a cover object database 360. The Social Network Server Computer 112 is configured to host and generate web interfaces as described with respect to FIGURES 5-25, including a Library interface, a Storefront interface, a Collection interface, a Publication interface, and Following and Follower interfaces. The social network and Social Network Server Computer 112 may include more or less features, or may include modifications of the features described herein. Conventional features, such as firewalls, load balancers, application servers, fail over servers, site management tools, as well as additional conventional known features are not shown to allow a clearer illustration of the novel features of the system.

The page/interface database 345 comprises multi-media hosted Project webpages and hosted Collection webpages as described herein with respect to FIGURES 5-25. The user profile database 342 also can comprise multi-media hosted Project webpages as described herein with respect to FIGURES 19A-19B. The hosted webpages are linked to cover objects uniquely associated with hosted profile pages, Project pages, and Collection pages. Each user profile includes or is operatively connected to a unique Library interface comprising Project cover objects and Collection cover objects. The Library interface can be private to users or teams associated with the user profile for the Library. Each user profile is operatively connected to a unique public Storefront. When a user publishes a cover object to a Storefront, the cover object and uniquely linked Project or Collection hosted webpage is made publicly available and discoverable to at least the social network members or to the general public. The cover object can also be published to the feeds of Followers interface following the user. The cover objects include tools configured to allow users to add the cover objects to their own libraries and Storefronts as described herein with respect to FIGURES 5-25. Because each cover object is uniquely associated with a specific profile page, Project page, or Collection page, as the cover objects are shared through the social network, the cover objects act as interface nodes that directly link the user with the uniquely associated pages. As described below with respect to FIGURES 5-25 the pages in the page interface database 345 for the Library, publication, and Collection databases are served as web interfaces that are configured to allow a user to arrange cover objects into default arrangements, for example using draggable interfaces as described herein. For example the cover objects 360 can be configured as widgets or as arrangable objects on a server side pages or both.

The Social Network Server Computer 112 allows a user to create a user profile 128. The Social Network Server Computer also stores information regarding the connections 118 associated with the user profile 124. As described herein, the social network platform 1 2 is configured to allow a user to maintain a private Library as well as a public Storefront. To make a connection with another user's profile 128, the user accesses that user's profile 128 using the user profile 124 of the social network 112, including via profile cover objects, Project cover objects and connection cover objects as described herein, whereby the user can follow the other user's 128 publications. While the user profile 128 and Storefront may be completely or partially visible, there will be a designated process to request a connection to a team or follow the user, such as a button or hyperlink, including those associated with profile cover objects, Project cover objects and connection cover objects as described herein. For team requests, the user's request for connection is passed along to the owner of the user profile 128. In an embodiment, the social network 112 allows the user to view a team member's Library or unpublished Projects upon requesting the connection. In another embodiment, the social network 112 does not allow viewing of the team member's Library or unpublished Projects 112 until the owner of the profile 128 accepts the connection request, in which case the social network 114 stores the connection between the user profile 124 and another user's profile 128 in the connection database 344.

In addition to serving webpages to the users via the Social Network Server Computer, the social network 112 may serve other web related content, such as Flash, Java, XML and similar content. The web server 332 is provided with a message server 350 to allow messages to be transmitted between the profiles 124, 126, 128 and 148 associated with the social network 112 via, inter alia, the cover objects as describe herein with respect to FIGURES 5-25. The messages may be in the form of email, chat, text, SMS, or any desired messaging format known in the art.

In an exemplary embodiment, an API request server 336 may correspond to one or more dynamic link libraries DLL or other libraries that comprise standardized functions for communicating with the web server 132. The API request server 336 allows servers 152-1, 152-2 associated with external websites 154-1, 154-2 to access information associated with the Social Network Server Computer by calling APIs 356 and to execute operations on the Social Network Server Computer, such as sending messages to other user profiles, by calling other APIs. The external websites 154-1, 154-2 may be any websites operating from a server 114 other than the server operating the social network 1 2, for example other social networks, media hosting services or other external websites 154-1, 154-2.

The action logger 334 can monitor between users associated with the social network 114, whether such actions take place on their respective profiles 124 and 148, elsewhere on the Social Network Server Computer 112 or, if authorized, other places outside of the Social Network Server

Computer 112. All actions of the users are monitored by the action logger 334 are recorded and stored in the action log 338 or other database. Types of actions that may be recorded and stored include, but are not limited to, requesting connections between members, authorizing connections between members, sending messages between members, opening messages between members, suggesting connections, viewing content on other member's profiles, requesting, announcing or RSVPing to events.

The feed generator 340 displays published cover objects 360 in reverse chronological order on each user profile's Following interface feed 2200 as described herein with respect to, inter alia, FIGURES 22A-22B. The Social Network Server Computer 112 can also be provided with a privacy server 362 that can restricts access to information stored on the social network server 112. In an embodiment, the user may be allowed to modify settings associated with the privacy server 362 via the user profile 124 to determine how information related to the user 102 is stored and shared on the Social Network Server Computer 112. The user may authorize the Social Network Server Computer 112 to share information about the user only with specifically authorized members associated with Social Network Server Computer with various software applications, external systems or any system seeking access to the information. The information stored by the user on the Social Network Server Computer may include text, photographs, audio recordings, video, including contact lists and connections formed by the user through the Social Network Server Computer.

FIGURE 4C shows a logical architecture 500 for an embodiment. The system can be built on an exemplary platform, for example Amazon Web Service platform, although other platforms for supporting social networking and network infrastructure can be employed. As shown in FIG. 4C, a Delivery Channel tier 410 can be provided via a cloud front 412 to client computers as described herein. A front-end web server tier 420 can be built on on an elastic cloud (EC2) architecture 422 can provide front end interfaces built on, for example Angular JS 424 and other JS modules. The back-end tier 430 can be operatively connected to front end architecture tier 420 by web sockets 402, and can be built on an S3 architecture 432v using Grails on Linux 434, and the databases layer 440 can include, for example, a Postgres database 444 on an RDS tier 442 architecture. One or more third party systems 450 can be integrated or operatively connected to the architecture 500. As will be appreciated, provision of tiers and builds are exemplary, other platforms for supporting social networking and network infrastructure can be employed.

Generalized Operation and Illustrative User Interface Use Cases

The operation of certain aspects of the invention will now be described with respect graphical user interfaces for the platform illustrating processes described in conjunction with FIGURES 5-25, respectively. In embodiments, these processes or portions of these processes which may be implemented by and/ or executed on a single network computer or a plurality of network computers, such as network computer 300 of FIGURE 3. Likewise, in at least one of the various embodiments, processes, or portions thereof, may be operative on one or more client computers, such as client computer 200. However, embodiments are not so limited, and various combinations of network computers, client computers, virtual machines, or the like may be utilized. Further, in at least one of the various embodiments, the processes described in conjunction with FIGURES 5-25 may be operative in system with logical architectures such as those described in conjunction with FIGURES 4A-4C.

FIGURES 5-25 represent graphical user interfaces for the platform with at least one of the various embodiments. In at least one of the various embodiments, user interfaces other than user interfaces described below may be employed without departing from the spirit and/ or scope of the claimed subject matter. Such user interfaces may have more or fewer user interface elements, which may be arranged in various ways. In some embodiments, user interfaces may be generated using webpages, mobile applications or the like. In at least one of the various embodiments, applications may include processes and/ or API's for generating user interfaces user interfaces such as those described below.

According to an embodiment, as shown in FIGURE 5, the system includes a system menu interface 1120 for accessing the interfaces for the system. The menu 1120 includes a New Project interface link 1121, a Library interface link 1122, a Storefront interface link 1123, a Following interface link 1124, a Notifications interface link 1125, a Contacts interface link 1127, and Account interface link 1128, a Messages interface link 1129, and a Logout link 1126. According to an embodiment, FIGURE 6A shows a Library interface 1100 associated with a social network user profile comprising a library hosted webpage for listing a plurality of interactive, arrangeable cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110. Each cover object 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 comprises a dedicated link to a Project or Collection and a preformatted cover icon. The Library interface can include one or more Project cover objects 1103, 1105, 1106, 1107, 1108, 1109, 1110 and one or more Collection cover objects 1101, 1104. Cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 can be cover objects 1101, 1103, 1104, 1107 for Projects and Collections created using a user profile for the social network or cover objects 1102, 1105, 1106, 1108, 1109, 1110 for Projects and Collections associated with other network user profiles.

According to an embodiment, the cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 are configured to be arranged into a default order by a user. The cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 are configured as draggable "drag and drop" cover objects which are in a draggable area 1001 on the webpage interface 1100. As shown in the

embodiments herein, the user can employ the client computer input to drag and drop the cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 into a desired location or order in the draggable area 1111. As shown in FIGURE 7A, using the input device, such as a mouse or touch screen for example, the user grabs an cover object 1103 from a location on the draggable area 1001 from its location on a grid 1112, shown as the third cover object 1103 in the first of two rows 1113, 1114. As shown in FIGURE 7B, the interface is configured to allow the user to move the cover object 1103 to another location in the grid 1112. As shown in FIGURE 7C, once the user drops 1103 the cover object via a release command (e.g. releasing held mouse click, or removing finger or stylus from a touch screen) the cover object 1103 snaps into the location on the grid 1112 corresponding to the area the user 1115 has dragged the cover object to, shown in FIGURE 7C as the second cover object in the second row 1114 of the grid 1112.

As a draggable cover object 1103 is moved, the Library interface is configured to dynamically rearrange cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108, 1109, 1110 the grid 1112, thereby displaying to the user how the rearranged cover objects 1101, 1102, 1103, 1104, 1105, 1106, 1107, 1108 will be displayed on a graphic user interface. For example, as shown in FIGURE 7B as the cover object 1103 moves to the prospective location in the grid 1112 the cover icon becomes transparent and a placeholder icon 1115 appears as the cover object moves over the prospective location as the other cover objects 1101, 1102, 1104, 1105, 1106, 1107, 1108, 1109, 1110 automatically move into the new sequence of the arrangement. The placeholder icon 1115 appears between cover object 1107 and cover object 1108 as cover object 1103 is dragged toward that location. As the user drags the cover obj ect 1108 to other locations in the draggable area 1111, the placeholder icon 1115 appears in these other locations and the cover objects rearrange in sequence accordingly until the cover object 1103 is dropped and snaps into the grid 1112. The rearranged grid 1112 as shown in FIGURE 7C thus becomes the new default arrangement for the Library interface 1100.

According to an embodiment, as shown in FIGURES 8A-9I, a New Project interface 1200 comprises tools to allow a user to build a robust multi-media Project webpage which is hosted on the social network platform and is linked to a Project cover object; the Project cover object includes tools for publication, sharing and contextual discussion across the social network as well as tools for user curated content both inside and outside the network. The New Project Interface 1200 is accessible from the Menu Interface 1120 (FIGURE 5). As shown in FIGURE 8A, the New Project interface 1200 includes a cover creation interface 1300 including a Title field 1201 and a Description field 1202, a canvas element 1209 as well as cover object building tools including an Upload Image tool 1203, an Add Text tool 1204, a Background Color tool 1205, a Grid tool 1206, and Add Content tool 1207, and a Save button 1208 for saving the page. The title 1201, uploaded image 1204, Text tool 1204 and Grid tool 1206 are also configured to build the cover object associated with the Project page 1215 being created. FIGURE 8B shows the entry of a title for the Project ("New Project Use Case") in the Title field 1201 and FIGURE 8C shows the entry of the description text in the Description field 1202. FIGURE 8D shows an image 1210 uploaded by a user using the Upload Image tool 1203, which uploads the image into the canvas element 1209.

As shown in FIGURES 8E-8F, once uploaded, the image 1210 for the cover object can be edited using editing tools 1213, for example, to rotate and resize the image within the confines of the canvas element 1209. The Grid tool 1206 displays a grid 1211 to align the image within the canvas element 1209, and the background color for any negative space in the canvas element 1209 for the cover object can be changed using the Background Color tool 1205. Text 1214 can be added to the cover object with the Text tool 1204, which brings up a text menu 1212 to choose fonts. All the cover object building and editing tools create the Project cover object in the confines of the canvas element 1209, which is shown as an exemplary 3:4 ratio, although other preformatted sizes or shapes can be employed to build the cover object. The Add Content Tool 1207 accesses an Add Content Interface 1400, described below.

The New Project interface 1200 also includes an Add/Edit Content Interface 1400 for building a robust object oriented multi-media webpage which is hosted on the social network platform and is linked with the Project cover object. According to an embodiment, in FIGURES 9A-9I, the Add/Edit Content Interface 1400 includes an add image tool 1401 and add text 1402 tool, an add video tool 1403, and add music tool 1404. Each tool embeds images, text, video and music as elements of arrangeable objects the user can edit, thus the interface provides system tools that provide a balance of

customization and preformatted arrangeable objects to create, present, and publish content. As shown in FIGURE 9B, when user selects the add image tool, the system provides a container 1405 to upload single images or a plurality of images for a slideshow, for example GIF, PNG or JPEG images. As shown in FIGURE 9C, the image tool is also configured with an insert caption container 1407 for each uploaded image 1406 as well as a slideshow if selected. As shown in FIGURE 9D, the text tool 1402 is configured to prove a text container 1407 to enter text as well as a formatting tool 1408 for formatting the text. As shown in FIGURE 9E, once entered, the text object 1409 is placed above the image object 1406, however the Add/Edit interface 1400 is configured to allow text object to be positioned below the image object on the Project page. FIGURES 9F-9G show the music tool 1410 and video tool 1411 respectively, which are configured to embed audio and video files via links to, for example, third party hosted media sites such as Soundcloud® for audio media and YouTube® or Vimeo ® for video media. In an embodiment the Content Interface 1400 can include a tool for, inter alia, video and sound consolidated as a single 'media' button configured to allow a user to embed many other types of media files. As will be appreciated, in embodiments the Content Interface 1400 can be configured to include tools for other forms of media content and to upload other types of media files without limitation.

According to an embodiment, FIGURE 9H shows a page view and Figure 91 shows an Index view of the Add/Edit interface 1400 including the arrangeable media objects 1409, 1410. As shown in FIGURE 9H and FIGURE 91, once added, the add/ edit content interface is configured to allow the user to arrange the image objects 1409, text objects 1410, audio objects (not shown) and video objects (not shown) in any order. For example, FIGURE 9H and FIGURE 91 shows the image object 1409 moved to a position in sequence before the text object 1410, in contrast to FIGURE 9E, where the text object is first in order. As shown in FIGURE 9H, when employing the Add/Edit content interface 1400, the object displays a down button 1412 allowing the user to place each media object 1409,1410 below the other on the Project page. If the index interface 1415 is selected from an Add/Edit menu 1413, a pop-up index interface 1415 is configured to display draggable thumbnail object icons 1409, 1410 in a draggable area 1414. The interface index 1415 is configured to allow the user to arrange the media object icons 1409,1410 into the desired view order for the Project page by dragging and dropping each object in the desired order in the draggable area of the index interface 1415.

According to an embodiment, FIGURE 9J shows a slideshow tool for the Project interface 1200. The Project interface 1200 is configured to allow a user to select a plurality of image objects 1409, 1420 and video objects (not shown) for a slideshow. As will be appreciated, though the present embodiment is described in terms of image files, in embodiments the slideshow tool can be configured to select and other forms of media content and to upload other types of files and media objects, (e.g. text files, audio files, etc.) without limitation. When the user selects a plurality of objects, the interface is configured to present an "Add to Slideshow" item 1423. When the Add to Slideshow item 1423 is selected, the system shows an index edit interface 1424 of the selected image objects as shown in FIGURE 9K, which is configured to allow the user to arrange the image objects 1409, 1420 in any order using a draggable interface for thumbnail images 1409, 1420 similar to interface indexes described herein. For example, in the index edit interface 1424, the order of the two thumbnail images 1409,1420 have been reversed from the order in which they were selected from the Project interface 1200. For simplicity two images are shown, but any number of images or videos can be added or arranged in a slideshow. The index edit interface 1424 is also configured to allow the user save as a new slideshow ("Save" 1425) or to add to an existing slideshow ("Add to Existing" 1426). As shown in Figures 9L, once saved, the system is configured to save the plurality of selected images as a slideshow 1421 on the Project interface 1200 in the selected order, which can be navigated using, for example arrow buttons 1428. The slideshow tool is also configured to allow as user to add a caption to the slideshow ("Add slideshow caption" 1422). The slideshow tool also includes a slideshow edit button 1427 and an Edit menu item 1436, either of which is configured to bring up the slideshow edit interface 1435 as shown in FIG. 9M. The slideshow edit interfacel435 includes the image thumbnails 1409, 1420 and is configured as an index interface to allow the user to arrange the image objects 1409, 1420 in any order, and also incudes options to Upload Images 1429, Add Video 1430, and Save 1431, as well as the ability to delete images and videos from the slideshow. The slideshow edit interface 1435 also includes and Undo Slideshow tool 1432. The Undo Slideshow tool 1432 is configured allow a user undo the slideshow and to retain the images on the project interface. As shown in FIGURE 9N, when the user selects the Undo Slideshow button 1432, the system is configured to order the images on the project interface as individual images or videos in the same order as previously in the slideshow. The user can then order or edit the images and videos as described on the Project interface 1200 as described herein.

As shown in FIGURE 10, once the new Project page 1215 is created, the Library interface 1100 includes a new Project cover object 11 6 linked to the newly created Project page 1215, which is in the first position in the first row of the grid layout 1112, but can be arranged as described herein.

Cover objects are configured as interfaces for Projects, Collections, and profiles. According to an embodiment as shown in FIGURE 11 A, when a Project cover object 1116 is selected, e.g. via mouseover on a grid layout 1112, the Project cover object's 1116 cover icon is configured to show the title 1134, a name of the user profile associated with the Project cover object 1132, the Project description 1133, and includes a selection box 1134, a edit box 1135, and a menu button 1136 which activates a menu 1142. If the user selects a cover object 1107 created using that user's profile, the cover object includes an edit tool 1135 to allow the user to edit the cover object 1102 as described herein. The selection box 1134 for the Project cover object 1116 is configured allow the user to select the Project icon 1116 in conjunction with other Project icons, which can then be added to a Collection of Projects, or to publish the Project by adding it to a Storefront interface as described herein. The menu 1142 also comprises options to add the Project to a Collection via a Collection button 1138, or to publish the Project by adding it to a Storefront interface via a Storefront button 1138.

The menu 1142 also includes a Share button 1141 to share the Project with other selected persons. In an embodiment the "Share" button 1141 can also include options to share the Project across other third party platforms or social networks as known in the art. The cover object can also include tools configured to allow social network users to interact with one another in the context of the Project or Collection associated with the cover object. For example, in an embodiment (not shown) the cover object can include a messaging tool, which allows network users to engage in conversations or comment on the Project or Collection. The menu 1142 also includes options to delete 1140 the Project from the system, as well as to get more information ("Get More Info") 137 about the Project and/ or the user profile associated with the Project. As shown in FIGURE 1 IB, when the Project cover object 1102 is that of another network member, the cover object does not include an edit option or edit box 1135.

As shown in FIGURE 11C, when the "Get More Info" option from menu 1142 from the user's own Project cover object is selected, the Project cover object 1116 is configured to give the more information about their Project, including when created ("Created") 1170, when last updated

("Updated") 1171, the total views the cover object has received ("Total Views") 1172, the number of Library interfaces the Project has been added to ("Libraries") 1173, the number of Collections the Project has been added to ("Collections") 1174, the number of Storefronts the Project has been published to ("Storefronts") 1175, and the number of times the product has been shared ("Shared") 1176. The cover object can also be configured to show information about a corresponding Project or Collection without the need for selecting the cover object, for example total views 1172 and the creation 1170 or last update 1171, and this information can be made publicly available with the cover object. When the Project cover object 1102 is that of another network member, the cover object menu 1 42 may or may not include options to get more information, and can be configured to include an option to message the user associated with the cover object (not shown).

As shown in FIGURE 12A, the selection box 1134 for the Project cover objects 1116, 1101, 1104, 1107 is configured allow the user to select multiple cover objects 1116, 1107, 1103, which can then be added to a Collection of Projects, removed or deleted from the Library interface 1100, or published to make them publicly available to network members by adding it to a Storefront interface. The Library interface 1100 is configured to display menu buttons to Add to Collection 1143, Add to Storefront 1144, and Remove Selection 1145. As shown in FIGURE 12B, if selection boxes 1134 for cover objects 1101, 1104 for Collections are selected, the menu option to Add to Collection 1143 is removed as in embodiments the system interface may not be configured to host a Collection interface in another Collection interface. The system is configured to allow the user to select cover objects created using the user profile or other network users' cover objects for Collections or publication.

FIGS 13A-13B show an embodiment for creating a Collection interface for one or more Projects and a corresponding Collection cover object for the Collection interface. As shown in FIG. 13A the library interface 1100 is configured to generate a pop up interface 1150 including a selection table 1151 including one or more selection boxes 1152, 1153 to add a single Project (if selected from the cover object's menu 1136 or the selection box 1134) or multiple Projects (if selected via the Project cover objects' selection boxes 134) to an existing Collection or an option button 155 to create a new Collection. If the user selects 1154 an extant Collection, the system is configured to add the Project cover objects to the extant Collection. In an embodiment, the system can be configured to update the cover object for the extant Collection to reflect the additions (not shown). If the user selects the option 1155 to create a new Collection, the interface 1150 is configured to present the user with a Tide input field 1156 and a Description field 1157 to name and provide a description for the Collection being created. Once entered and saved 1158, the system generates a Collection interface 1150 including the selected Project cover objects as shown in FIG. 12B, and a corresponding new Collection cover object 1159 for the Collection and adds the Collection cover object 1159 to the Library interface 1100 as shown in FIG 14.

According to an embodiment a Collection interface 1500 is shown in FIGURE 15. As shown in FIGURE 15, in an embodiment, the default cover icon 1160 generated for the Collection cover object 1159 can be a pastiche of the Project cover icons 1160 for the Projects cover objects 1116, 1103, 1107 in the Collection, however the system is configured to allow the user to edit the cover icon 1160 for the Collection cover object in the same manner as described for editing the Project cover icon with respect to the embodiments described in conjunction with FIGURES 8A-8F herein. The Collection interface 1500 comprises Project cover objects 1116, 1107, 1103, which include links to the associated Project pages for each of the Project cover objects. The Collection interface 1500 is configured to allow the user to manually arrange the cover objects 1116, 1107, 1103 in the same manner as described with respect to FIGURES 7A-7C and includes options for a grid layout 1119, vertical layout 1117, and list layout 1118 options for the Collection interface 1500.

In an embodiment, the Library interface 1100 includes a menu for selecting a grid layout option 1119, a vertical layout option 1117 and a list layout 1118 option of the Project cover objects, and the Library interface 1100 is configured to allow the Project cover objects to be arranged in each layout. FIGURE 16 shows an embodiment of the vertical layout for the Library interface and FIGURE 17 shows an exemplary embodiment of the list layout for the Library interface. The Library interface 1100 is configured to allow the user to manually arrange the cover objects 1116, 1101, 1103, 1139, 1102 in the vertical layout 1147 and list layout 1148 into a default order in manner similar to that described with respect to the grid layout 1112 in FIGURES 7A-C. In the vertical layout 1147 and list layout 1148 the Title 1102, Description 1 33, User Profile Name 1132 and cover object Menu 1 36 for the cover object are outside the cover icon 1160, whereas the selection box 1134 and/ or edit button 1135 are still configured so as to only display when the cover object is selected (e.g. via mouseover). The vertical layout 1147 and list layout 1148 is also configured to display Project cover objects 1103, 1139 in

Collections 1101 on the same Library interface 1100 indented under the Collection cover objects 1101, which can be displayed as a dropdown Collection interface 1146; Project cover objects are manually arrangeable into a default order by a user within the Collection interface.

As shown in FIGURES 18A-18C, the Storefront interface 1600 comprises a Publications interface 1700, a Followers interface 2000, and a Following interface 2100, each of which allow cover objects to be arranged in a grid layout 1119, a vertical layout 1117 and a list layout 1118 as described herein. The system is configured to allow users to publish Projects and Collections to their Storefront interface 1600, whereupon the cover objects 1103, 1101, 1102 for the published Projects or Collections are publicly available on the Publications interface 1700 of the Storefront interface 1600. In an embodiment, the system is configured to allow a user to publish their own Projects 1103 and

Collections 1101 as well as add the publicly available Projects and Collections of other network users to the user's own Publication interface 1700 on the Storefront interface 1600. The Publications interface 1700 is configured to allow a user to manually arrange the cover objects 1103, 1101, 1102 in a preferred default order in each layout as described herein.

According to an embodiment, as shown in FIGURES 18A- 8D, the system includes a social networking interface for the user, shown as a Storefront interface 1600. The Storefront interface 1600 is associated with the user can accessed from menu interface 1120 (see FIGURE 5). The Storefront interface 1600 is configured to be accessible by other members of the social network and/ or the public. In an embodiment, the Storefront interface 1600 can be made available to at least other network users or publicly to anyone accessing the network. Other embodiments of organizing and setting privacy filters as known in the art can be employed. As noted above, cover objects and associated Collections and Projects in a user's Library interface 1100 are private to the user or user teams, whereas the Storefront interface 1600 allows the user to interact with at least other users on the social network as well as make Projects and Collection of Projects accessible for sharing and distribution throughout the network using the cover objects 1103, 1101, 102. In embodiments, the Storefront interface can include an e-commerce engine (not shown) to allow social network users or others purchase content associated with the Projects or Collections.

The Storefront interface 1600 comprises a profile cover object 1601 and a Storefront banner 1602. The Storefront interface is configured to allow a user to add and edit the Storefront banner using a Storefront banner edit tool 1603. The profile cover object is 1601 associated with a profile page associated with the user account, and includes a User Name 1801 and Description 1802. As shown in FIGURE 18D, when a user cover object 1116 is selected by the user for the account, e.g. via mouseover on a grid layout 1 12, the Project cover object's 1116 cover icon shows the an edit box 1604, and a menu button 1605 which activates a menu 1606 including sharing options. If a profile cover object 1601 is that of another user, the profile cover object 1601 can include tools for contacting the user, sharing the user's profile, and engaging the user in a discussion, thereby providing a direct communication interface with the user as the profile cover object is employed throughout the social network.

In an embodiment, FIGURE 18B and FIGURE 18C respectively show a Followers interface 2000 and a Following 2100 interface of the Storefront interface 1600. The Followers interface 2000 and Following interface 2100 each are configured to display user profile cover objects 1809, 1810, 1811 of other network users the user is being followed by or is following respectively. In an embodiment the Followers interface 2000 and Following interface 2100 are not configured to allow manual arrangement of the other network user profile cover objects 1809, 1810, 1811 by a user, and are, for example, chronologically ordered (e.g. when first followed) or on a feed order (e.g. rearranging when a followed or following users publishes new content). In alternative embodiments, the Followers interface 2000 and Following interface 2100 can be configured to allow profile cover objects be manually arrangeable. The Followers interface 2000 and Following interface 2100 of the Storefront interface 1600 is each configured to display the cover objects 1809, 1810, 1811 in a grid, vertical, or list layout as described herein. Each profile cover object 809, 1810, 1811, 1812 for the other users includes a link to that user's profile information interface 1900, which each user can build as described herein with respect to FIGURES 19-19B. Each profile cover object 1809, 1810, 1811, 1812 for the other users can include tools for contacting the user, sharing the user's profile, and engaging the user in a discussion, thereby providing a direct communication interface with the user. In an embodiment, as shown in FIG. 20, a user profile page for other network users also includes a menu button 2001 for sharing that user's profile with other network users or outside the network (e.g. via email or other tools for sharing as may be integrated into the platform for other social networks). The menu can also include a messaging tool to message the user profile associated with the creation of the Project or Collection. The profile information interface also includes the User Name

1801 and Description 1801 for that user. The User Name 802 from the Profile Information Page 1900 includes a link to that user's Storefront interface 1600.

According to an embodiment, as shown in FIGURE 19 A, a Profile Interface comprises tools to allow a user to build a robust multi-media webpage which is hosted on the social network platform and is linked to the profile cover object 1601. The Profile interface comprises a cover creation interface

1800 including a User Name field 1801 and a Description field 1802 as well as profile cover object 1601 building tools such as those available for the Project creation and editing interface 1200 described herein, including an upload image tool 1803, an add text tool 1804, a Background Color tool 1805, a Grid tool 1806, and an Add More Info (content) tool 1807, and a Save button 1808 for saving the page. The title 1801, uploaded image 1804, Text tool 1804 and Grid tool 1806 are also configured to build the cover object associated with the profile page being created. The cover creation/ editing interface 1800 is configured to allow a user to create and edit a profile cover object 1601 using the cover object building and editing tools in the same manner as shown and described with respect to the creation and editing of the Project cover object with respect to FIGURES 8A-8F.

According to an embodiment, as shown in FIGURE 19B, the Profile interface also includes a

Profile interface 1900 which employs the same tools as the Add /Edit Content Interface 1400 described herein with respect to FIGURES 9A-9I, and is configured to allow user to build a robust object oriented multi-media webpage which is hosted on the social network platform and is linked with the profile cover object 1601. According to an embodiment, as shown in FIGURE 19B, the Profile Interface 1900 includes an add content tool 1901 including an add image tool 1902 an add text tool 1903, an add video tool 1904, and an add music tool 1905. Each tool embeds images, text, video and music as elements of arrangable cover objects thus the interface provides system tools that provide a balance of customization and preformatted arrangeable cover objects to create and present content. The Profile interface 1900 is configured to allow a user to create and edit a profile page using the page building and editing tools in the same manner as shown and described with respect to the creation and editing of the Project page 1215 with respect to FIGURES 9A-9I. The Profile interface 1900 also includes a menu 1906 that includes menu options for the profile, for example a Share tool to share the profile on the network or with other networks or persons, for example as shown in FIG. 19C. As shown in FIG. 19C, the system is configured to allow a user to maintain a database of contacts of other users on the social network, which can be accessed via cover object menus for messaging or sharing as described herein. According to an embodiment, the system also has a Contacts interface 2400, accessible via menu 1127 (see FIGURE 5) as shown with respect to FIG. 24.

In an embodiment, cover objects are searchable. The system is provided with a discovery engine which allows users to search for content and Projects associated with published and publicly available cover objects, which returns the cover objects in the search results. In embodiments the system can also be provided with a discovery stream (not shown) where users are presented with a stream of cover objects, which can be provided based on, for example, user profile interests, editorial picks, Followers interface, or other methods for serving content to users as known in the art.

According to an embodiment, as shown in FIGURES 21A-21C, the Storefront interface 1600 is configured to be accessible by other members of the social network and/ or the public. On other network user's Storefront interfaces 1600, the Storefront interface 1600 comprises a profile cover object 1601 and a Storefront banner 1602. The profile cover object 1601 is associated and linked to with a profile page 1900 associated with the user account, and includes a User Name 1801 and

Description 1802, as well as a Follow button 1813 giving the option to follow or unfollow the user. As shown in FIGURE 21B, when a user's cover object 1601 is selected by the user for the account, e.g. via mouseover, the profile cover object's 1601 cover icon shows a menu button 605 which activates a menu 1606 including options to invite the user to join a user profile's team 1607 and to share the Storefront 1608 associated with the user profile with other network member. Other sharing and messaging options can be added as well. The user profile cover object 1601 can thus include, as discussed herein, tools for contacting the user, sharing the user's profile, engaging the user in a discussion, thereby providing a direct communication interface with the user as the profile cover object is employed throughout the social network.

As shown on FIGURES 21A and 21C, published Project cover objects 1010, 1011 and Collection cover objects on the other network user's Storefront 1600 can be added to the user's own Library interface 1100, where they can be arranged and published in accord with the user's preferences as described herein. Each cover object 1010, 1011 includes a menu 1005 with options to Add to library 1002 and Share 1003 the Project or Collection, which are shown when the user selects the cover object (e.g. via mouseover), as well as a messaging tool 1004 to directiy message the user associated with the Project or Collection. Each of the published Project options include a selection box 1134 which is configured to allow a user to select multiple cover objects 1010, 1011 on the Publications interface 1700 of the Storefront interface 1600. The Selection box 1134 for the Project cover objects 1010, 1011 is configured allow a any network user to select multiple cover objects 1010, 1011 and add the cover objects 1010, 1011 to their own library interface 1100.

In an embodiment, the other user's Storefront interface comprises a tabbed Followers interface 2000 and Following 2100 interface of the Storefront interface 1600 configured in the same manner as described with respect to FIGURES 18B and 18C as described herein. The Followers interface 2000 and Following interface 2100 each are configured to display user profile cover objects of other network users the user is being followed by or is following respectively.

In an embodiment, as shown in FIGURE 22A, the system comprises a Following stream interface 2200, which is accessible from the Following interface option 1124 from menu 1120 (see FIGURE 5). The Following stream interface 2200 is configured to stream cover objects 1006, 1007, 1008, 1009, 1012, 1013, 1014, 1015 1110, 1016 for Projects and CoUections created by other network users that a user is following. As users publish Projects and Collections to Storefront interfaces 1600, the system is configured to post the cover objects 1006, 1007, 1008, 1009, 1012, 1013, 1014, 1015 1110, 1016 to the feeds of other users who are following the publishing user. On the Following stream interface 2200, the cover objects 1006, 1007, 1008, 1009, 1012, 1013, 1014, 1015 1110, 1016 are displayed in reverse chronologic order. As shown in FIG. 22B, each cover object 1006 includes a menu 1005 with options to Add to library 1002 and Share 1003 as discussed herein, which are shown when the user selects the cover object (e.g. via mouseover). The Following stream interface 2200 is configured with options to show the cover objects 1006, 1007, 1008, 1009, 1012, 1013, 1014, 1015 1110, 1016 in a grid layout 1119, vertical layout 1117, and list layout 1118 as described herein.

In an embodiment, as shown in FIGURE 23, the system comprises a team interface 2300. The team interface is configured to allow users to create and manage teams the user belongs to. Team members can be assigned various roles for creating and managing Projects, Collections, Storefronts, Libraries and the other system tools, databases and interfaces as described herein. Different roles may also have differing levels of administrative access.

According to an embodiment, as shown in FIGURE 24A to FIGURE 24C the system includes discussion tools configured to allow social network users to interact with one another in the context of a Project or Collection associated with the cover object on the social network. The system is configured to include a discussion interface, for example a pop-up chat or page interface, which includes an entire message history between specific users with respect to that specific Project or Collection. Each discussion interface is an object uniquely tied to that Project for those users, for example with a parent identification uniquely identifying the linked Project or Collection as well as entity data indicating whether the parent is a Collection or a Project. The discussion interface object maintains all contributions to that discussion.

In an embodiment, a user can initiate a discussion with one or more other users about any Project or Collection in the system. For example, each Project or Collection cover object can include a sharing or messaging tool that allows a user to share the Project or Collection with one or more other users with an initiating message. A receiving user can then be presented with a notification including a link or object that opens the discussion interface. Any further interactions between the users with respect to that Project or Collection are then maintained in the discussion object in a chronological stream, for example as a "chat" format as known in the art. The system is thereby configured to host discussions uniquely tied to a Project or Collection and a group of users, thereby allowing independent unique discussions tied to each Project that are specific to the users linked to that discussion. The system can also be configured to allow a user to send an message to a non-registered user, for example via a email sent from user's client computer over another network, which can require a user to register or subscribe with the network in order to participate in the discussion, although in embodiments the system can be configured to allow non-registered users to use the specific discussion interface the user is invited to.

As shown in FIGURE 24A, a Project discussion interface 2400 or Collection discussion interface includes the Project cover object or Collection cover object in the discussion object. The system is configured to serve the Project interface or Collection interface corresponding to the Project cover object 1261 or Collection cover object, and the discussion interface 2400 is presented as a pop-up interface which is viewed together with the selected Project or Collection interface. For example, as shown in FIGURE 24A, a user invited to or engaging in a Project discussion can be presented with a discussion interface 2400 in the form of a "chat" pop-up. As shown in FIG. 24B, by clicking on the Project cover object 1261, is taken to that Project page 1215 while keeping the discussion interface 2400 active. Accordingly, the system is configured to allow users participating in the discussion to discuss the Project or Collection in context of the Project page 1215 or Collection. In an embodiment, a user can start a discussion for any published Project or Collection on the network. Discussion interfaces thus encourage in-depth and targeted engagement of Projects by users that is more focused than open or moderated comment-based pages as known in the art, yet retains the advantage of discussion in context of the page being discussed and can present the discussion interface 2400 together with the navigable Project page 1215. Moreover, the cover objects and links to parent Project pages provide tools whereby Project and Collection creators are only one hop away from any user discussing the Project, giving the Project or Collection creator responsive access to wide, yet more engaged, user exposure across the social network. As will be appreciated, however, in embodiments the discussion interface objects are linked to, but can be in an independent database from, the Project or Collection webpages they are uniquely associated with.

In an embodiment, user initiating a message can join one or more other users to the discussion interface, for example by sharing a user message link to one or more users when or after initiating a discussion about a Project or Collection. Thus a discussion can include a plurality of users, for example an initiator user and a plurality of participating users. Each participating user has participant link identified with that user and linked to the discussion object interface. In an embodiment, the discussion object can include tools to allow users to join or leave the discussion, for example by accepting a request to join or subscribe to the discussion, which the user can later unsubscribe or leave, or by simply deleting a discussion link. In an embodiment, an initiator or user can have administrative access to the discussion permitting them to join or remove other participants to the discussion. In an embodiment, discussions can have differing levels of access, for example may be publicly available for reading and viewing but only participants can comment, can be private and include contributor access and non-contributor access, or can be private and allow all users participating the message to contribute.

In an embodiment, as shown in FIGURE 24C, the system is configured to include a Messages interface 2500. The Messages interface 2500 includes a history of discussion messages 2402a, 2402b, 2402c, 2402d, 2402e, 2402f, 2402g, 2402h between a user and one or more other users with respect to individual Projects or Collections. For example in the users Messages interface 2500 the user is shown in a right hand side of a list of messages 2402a, 2402b, 2402c, 2402d, 2402e, 2402f, 2402g, 2402h the user has sent or received to other users 2404, 2405 2406, 2407, 2408; users on the system can be identified by a user's profile cover object 1601. Each of the messages 2402a, 2402b, 2402c, 2402d, 2402e, 2402f, 2402g, 2402h is for a specific Project or Collection, which is identified with a Project cover object 2409, 2410, 2411, 2412, 2413, 2414 or Collection cover object as well as the Project or Collection name, and user/ creator name. In an embodiment, the interface can also be configured to show part of the message 2415 in the interface. By selecting a message, the user is presented with a discussion interface 2400, for example a pop-up chat or page interface 2400, which includes the entire message history between those users with respect to that specific Project or Collection. Each discussion interface 2400 is an object uniquely tied to that Project for those users, for example with a parent identification uniquely identifying the linked Project or Collection as well as entity data indicating whether the parent is a Collection or a Project. The discussion interface object 2400 maintains all contributions to that discussion.

In an embodiment, the system can also be provided with a discussion interface for user-to-user communications. For example, as shown in FIGURES 24C and 24D, when a user mouses-over or selects another user's profile cover object 1601, a profile popup 2416 showing a thumbnail of that other user's Storefront interface includes options to Follow 2417 or message 2418 that user. If a user messages that user via their Storefront interface, or via a message interface on a profile cover object 1416, a discussion object (not shown) linked to each user is generated, and the discussion object hosts a general discussion between those users (e.g. not linked to a particular Project or Collection), for example as a "chat" format. The discussion object thus keeps a history of any interaction between the users independent of discussions of specific Projects or Collections as described herein. In an embodiment, a discussion object can be initiated or joined by a team as described with respect to FIGURE 23.

According to an embodiment, as shown in FIGURE 25, the system also has a Contacts interface 2600, accessible via menu 1127 (see FIGURE 5).

The particular embodiments disclosed above are illustrative only, as the invention may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. Furthermore, no limitations are intended to the details of construction or design herein shown, other than as described in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope and spirit of the invention. Although illustrative embodiments of the invention have been described in detail herein, it is to be understood that the invention is not limited to those precise embodiments, and that various changes and modifications can be effected therein by one skilled in the art without departing from the scope and spirit of the invention.