On the architecture of the distributed blogosphere
The policy of new owners of livejournal does not leave indifferent owners of cozy Zhzhshechek. Someone, without much talk, starts a sandalone blog , someone repeats the mantra " In pidaras soup ". Someone is going to Goa and not soared.
Recently, the highly respected Nestor saw counterfeit copyright icons in his journal and decided it was time to do something. To begin with, I closed access to all my records and called Mamut a mazerfaker. But it did not help. Then he called on the progressive public to build a distributed Bolcosphere 2.0 .
Such a formulation of the question seems to me the most correct and here are my 5 cents in the collection of ideas.
')
Distributed blogosphere should be divided into strictly delineated entities.
Consider them in more detail:
The simplest and most crucial component. According to the form, the UID is a url. In terms of content, the UID should include a set of standard blogosphere interfaces:
It is very important that the user has the opportunity at any time to change the DNS settings for his UID and redirect him to the new server. The most correct guarantee that the url (that is, the UID) will always remain with the owner is to have it in the form of a pure domain (without additional directories), which is registered to the owner of the UID. Although it does not have to be something pretentious type tema.ru. Geographical third level domains are in bulk and free.
This is what now makes of an empty LJ account - the thousandth. Namely:
The content format of the user must be standardized. Those. for example, the directory structure should be defined where XML and media files are laid out in a strict order and which can be packed into a neat zip file.
Hardware, infrastructure and software that can host the contents of one or many users. It should look like this:
I felt sad, offended:
Who will keep the content server? I see at least three obvious scenarios:
This is a server that knows the profiles of a large number of users (all?) And can answer questions like:
The search server plays the role of an aggregator and some common denominator for the blogosphere. We go there to see and show others. Notice the huge role that people search for current social network operators. It is this functionality that binds users to the service and “cements” the audience. Separating the search from the servers and content, we make it a nice and innocuous assistant. After all, there can be several independent search servers.
Technically, server software can be quite simple. Monetization is obvious. Over time, the search function will gladly pick up large search companies.
Thus we have a distributed network of content servers. The part works on a commercial basis, part amateur. We also have the blogosphere population. Everyone has their own name in the form of url. Which does not take away. Each user grows the content of his blog on a particular server. However, the user is not tied to his server as serfs, but is free to pick up his content and go where it is better. For other members of the blogosphere, this transition will be absolutely transparent. Url has not changed. All this life is watched by a search server. Collect and cache open information. Help users find each other.
Everyone is happy.
PS: I wanted to publish in the blogosphere blog, but they have something broken there. gives some kind of error about karma. : - /
Recently, the highly respected Nestor saw counterfeit copyright icons in his journal and decided it was time to do something. To begin with, I closed access to all my records and called Mamut a mazerfaker. But it did not help. Then he called on the progressive public to build a distributed Bolcosphere 2.0 .
Such a formulation of the question seems to me the most correct and here are my 5 cents in the collection of ideas.
')
Distributed blogosphere should be divided into strictly delineated entities.
- User ID
- User Content
- Container (or server).
- Search server.
Consider them in more detail:
User ID (UID).
The simplest and most crucial component. According to the form, the UID is a url. In terms of content, the UID should include a set of standard blogosphere interfaces:
- Open user ID. (so that it can always be authorized).
- RSS feed blog.
- what else standard interfaces.
It is very important that the user has the opportunity at any time to change the DNS settings for his UID and redirect him to the new server. The most correct guarantee that the url (that is, the UID) will always remain with the owner is to have it in the form of a pure domain (without additional directories), which is registered to the owner of the UID. Although it does not have to be something pretentious type tema.ru. Geographical third level domains are in bulk and free.
User content
This is what now makes of an empty LJ account - the thousandth. Namely:
- Structured information from the profile. Name, nickname, email, ICQ, birthday, etc.
- Avatar (s)
- A set of static pages.
- Blog feed
- Comments to blog entries, pages, photos, etc.
- Media storage Photos, podcasts, videos, etc.
- Friends lists and security settings. Who sees what / who can.
- Design pages (in the form of CSS probably).
The content format of the user must be standardized. Those. for example, the directory structure should be defined where XML and media files are laid out in a strict order and which can be packed into a neat zip file.
Container (or server).
Hardware, infrastructure and software that can host the contents of one or many users. It should look like this:
- register on the server.
- redirect your uid to the DNS server.
- we load on the server a backup of your content (the format, as we remember, is standardized).
- We get our cozy ZHrshechka at the usual address.
I felt sad, offended:
- pick up the backup content. (which of course we did regularly)
- registering your own hosting
- we deploy standard (and open) server software.
- redirect to your hosting DNS your UID.
- we load to ourselves a backup of the content.
- We get back our cozy ZhZhishechka at the usual address.
Who will keep the content server? I see at least three obvious scenarios:
- a small server on your own hosting for your loved one (and maybe for a few more friends).
- service for a monthly fee. Gentlemen pay 5 tanks per month and they are not interested in issues of availability, connectivity, business continuity and emergency recovery.
- service for advertising. Boys allocate space for banners and text ad units and do not soar with payment.
Search server.
This is a server that knows the profiles of a large number of users (all?) And can answer questions like:
- find me Vasya Pupkin, who studied at school 13 in the town of Muhosransk, graduated in '67.
- find all users with the interest of “dried chamomile”.
- find all girls aged 14 to 20 years from the city of Upper Podgorsk who have been online in the last 7 days.
The search server plays the role of an aggregator and some common denominator for the blogosphere. We go there to see and show others. Notice the huge role that people search for current social network operators. It is this functionality that binds users to the service and “cements” the audience. Separating the search from the servers and content, we make it a nice and innocuous assistant. After all, there can be several independent search servers.
Technically, server software can be quite simple. Monetization is obvious. Over time, the search function will gladly pick up large search companies.
Thus we have a distributed network of content servers. The part works on a commercial basis, part amateur. We also have the blogosphere population. Everyone has their own name in the form of url. Which does not take away. Each user grows the content of his blog on a particular server. However, the user is not tied to his server as serfs, but is free to pick up his content and go where it is better. For other members of the blogosphere, this transition will be absolutely transparent. Url has not changed. All this life is watched by a search server. Collect and cache open information. Help users find each other.
Everyone is happy.
PS: I wanted to publish in the blogosphere blog, but they have something broken there. gives some kind of error about karma. : - /
Source: https://habr.com/ru/post/47753/
All Articles