Hosting provider hosting routes from a media repository
View Patent ↗A hosting provider may be bi-directionally authenticated with one or more media repositories. The hosting provider preferably has domain name registration and hosting capabilities. The media repositories may collect data (such as pictures and/or files) from one or more users. Once authenticated, the hosting provider and media repositories may cooperate in storing, aggregating and transmitting data to a user. Routes may be hosted by the hosting provider and used to organize and access the data. For example, a user may enter a route into a browser and receive media/data, possibly from a plurality of media repositories, that is associated with that route. In another example, the user may enter a route into the browser and be redirected from the hosting provider to a website of the media repository.
1. A method for redirecting a user to a media repository, comprising the steps of:
registering by a hosting provider, comprising a first hardware server, a domain name to a user;
hosting by the hosting provider on a second hardware server a root, wherein the root comprises a third level domain combined with the domain name registered to the user;
storing by the hosting provider the root in a nameserver that is part of a domain name system;
receiving by the hosting provider a plurality of routes from a media repository, wherein each route in the plurality of routes comprises the root;
storing by the hosting provider on the second hardware server the plurality of routes from the media repository with the root hosted by the hosting provider;
receiving by the hosting provider a route in the plurality of routes that is a first uniform resource locator from a browser running on a client device, wherein the first uniform resource locator is associated with a second uniform resource locator; and
redirecting by the hosting provider the browser on the client device to the second uniform resource locator.
2. The method of claim 1 , wherein at least one route in the plurality of routes points to data in a database.
3. The method of claim 1 , further comprising the step of:
storing by the hosting provider the second uniform resource locator and a corresponding IP address that points to a website of the media repository in the domain name system.
4. The method of claim 1 , wherein at least one route in the plurality of routes comprises the root and a user applied tag, wherein the user applied tag was applied by the user while logged into the media repository.
5. The method of claim 1 , wherein at least one route in the plurality of routes comprises the root and a user applied filter, wherein the user applied filter was applied by the user while logged into the media repository.
6. The method of claim 1 , further comprising the steps of:
receiving by the hosting provider a second plurality of routes from a second media repository, wherein each route in the second plurality of routes comprises the root; and
storing by the hosting provider on the second hardware server the second plurality of routes from the second media repository with the root hosted by the hosting provider, wherein the first media repository is a different media repository than the second media repository.
7. A method of transmitting aggregated data, comprising the steps of:
registering by a hosting provider comprising a first hardware server a domain name to a user;
hosting by the hosting provider on a second hardware server a root, wherein the root comprises a third level domain combined with the domain name registered to the user;
storing by the hosting provider the root in a nameserver that is part of a domain name system;
receiving by the hosting provider a first route from a first media repository, wherein the first route comprises the root and the first route points to a first data;
storing by the hosting provider on the second hardware server the first route from the first media repository with the root hosted by the hosting provider;
receiving by the hosting provider a second route from a second media repository, wherein the second route comprises the root and the second route points to a second data and wherein the first route comprises a tag and the second route comprises the tag;
storing by the hosting provider on the second hardware server the second route from the second media repository with the root hosted by the hosting provider;
receiving by the hosting provider the tag from a browser running on a client device; and
transmitting by the hosting provider the first data and the second data to the browser running on the client device.
8. The method of claim 7 , further comprising the step of:
receiving by the hosting provider a third route from the first media repository comprising a redirect to a website of the media repository.
9. The method of claim 7 , wherein the tag was applied by the user while logged into the first media repository.
10. The method of claim 7 , further comprising the step of:
receiving by the hosting provider a third route from the first media repository comprising a user applied filter and wherein the user applied filter was applied by the user while logged into the first media repository.
11. The method of claim 7 , further comprising the steps of:
receiving by the hosting provider a plurality of routes from a plurality of media repositories, wherein each route in the plurality of routes comprises the tag and wherein the plurality of routes point to a corresponding plurality of data stored in a database;
receiving by the hosting provider the tag from the browser running on the client device; and
transmitting the plurality of data pointed to by the plurality of routes that comprise the tag to the browser running on the client device.