Interesting concept
Reading about all these semantics and other web3.0 I had an idea.
About social networks
I'll start from afar. Now social networks are very popular:
')
Take for example VKontakte (most of its structure is familiar to most). VKontakte has a huge amount of information concentrated in one place, which gives a number of drawbacks (difficult search, server load, etc.). In fact, VKontakte is created for sharing multimedia (photo, video and so on). But for each function of a vkotnakt there is a separate service that gives even more opportunities than a social network, an example would be youtube for video or flickr for a photo.
Idea
So, in general, the very idea: to create a service with a single authorization system, which has its own api for creating web applications. This service will store information about the user and his data (blog posts, videos, photos, etc.). Integrate into this semantic search service, associate it with a large number of sites and what will we get? We will get a little loaded resource (all data is stored on other servers, on ours only their location), with multifunctional search and api, about which I want to say a couple of words.
About api
Let's go back to VKontakte. All users of VKontakte are limited in functions and the design of each page is the same (maybe for the better, take at least liveinternet). API of such a system, which I described above, can allow to solve all these problems. The user can also sit on the central site or make your blog using api and its blog will not be like anything, it will be able to do anything in it, especially without bothering. API will not focus all people around a single service, but will allow developers to make their services based on given.
PS fig statement of thoughts probably, excuse me. Also, the idea is still damp and needs some work, but the concept is outlined. I would like to see your opinion in the comments
About social networks
I'll start from afar. Now social networks are very popular:
')
Take for example VKontakte (most of its structure is familiar to most). VKontakte has a huge amount of information concentrated in one place, which gives a number of drawbacks (difficult search, server load, etc.). In fact, VKontakte is created for sharing multimedia (photo, video and so on). But for each function of a vkotnakt there is a separate service that gives even more opportunities than a social network, an example would be youtube for video or flickr for a photo.
Idea
So, in general, the very idea: to create a service with a single authorization system, which has its own api for creating web applications. This service will store information about the user and his data (blog posts, videos, photos, etc.). Integrate into this semantic search service, associate it with a large number of sites and what will we get? We will get a little loaded resource (all data is stored on other servers, on ours only their location), with multifunctional search and api, about which I want to say a couple of words.
About api
Let's go back to VKontakte. All users of VKontakte are limited in functions and the design of each page is the same (maybe for the better, take at least liveinternet). API of such a system, which I described above, can allow to solve all these problems. The user can also sit on the central site or make your blog using api and its blog will not be like anything, it will be able to do anything in it, especially without bothering. API will not focus all people around a single service, but will allow developers to make their services based on given.
PS fig statement of thoughts probably, excuse me. Also, the idea is still damp and needs some work, but the concept is outlined. I would like to see your opinion in the comments
Source: https://habr.com/ru/post/26985/
All Articles