Abstract reflections on the interaction of social networks
Despite the fact that for a fairly large number of Internet users 90% consists of only one VKontakte (Facebook, Odnoklassniki - underline), I think no one builds any illusions that any social network (at least in the near future). future) will gain a sufficient number of users and acquire such functionality that the entire Internet community will decide in amicable that “Fiddler is not needed, native” and abandons all other social networks / services. In many ways, this separation is even convenient.
Agree that the social graphs of different networks are very different due to the fact that each of them provides different functionality and, accordingly, users on them do different things. However, from the user's point of view, a little mutual integration would not hurt them. What I mean by this integration, and what benefits it might have gained from this company, will be discussed.
I’ll consider Twitter, Facebook / VKontakte and Last.fm as concrete examples.
')
VKontakte has recently introduced the microblogging function, after which the walls of users have become like Twitter with what you know . Good or bad - this issue in the discussion will be left out. Take it for granted. It is logical to assume that similar functionality will be used in a similar way. It also seems logical that the user using the same features will create about the same content. That is, writing about something on his wall, he is likely to write the same thing on Twitter and vice versa. A similar situation may arise with a wall on Facebook. In this regard, it would be nice when writing a message on your wall, say, to have some “Tweet it too” checkbox. Or, on Twitter, "Post on Facebook".
Often I have seen people listen to music mainly on VK. It is quite logical - there you can find music for every taste, it does not require hard disk space, only a more or less stable channel. Here comes the stage Last.fm. Agree, it would be interesting, say, directly from the VC to have access to the charts of users. But what would be really convenient here is scrobbling for VC. Of course, there is already Last.fm in VKontakte, but as an application, and this is something completely different.
In the opposite direction: I put some composition on Last.fm on my favorite list. It would probably be nice to share this news with friends in other networks - there are a lot of those who may be interested in this.
If I express a desire to go to any event at Last.fm, it would be nice to also be noted in the corresponding meeting on Facebook / VK, if such exists and vice versa.
This list goes on and on. If you add to the above networks YouTube - even longer.
I think the first thing that comes to mind is various extensions / add-ons for browsers or corresponding widgets on websites. However, the ability to stick a widget is far from everywhere, and add-ons are inconvenient because they need to be searched and installed. For each browser on each device from which you are going to go online. And on someone else's computer they may simply not be. Meh. It would be much more convenient to have all this out of the box, not to depend on the browser.
Of course, some of the above are already implemented to some extent. Say, last.fm has the opportunity to tweet or post on Facebook'e the upcoming concert. However, if I want to report this significant VKontakte event, then I have to resort to the old, like the world, copy-paste. Naturally, even without the “Like” button, we used to live somehow, but it’s somehow easier and more comfortable with it, isn't it?
Those who are familiar with OOP and at least heard about design patterns know that sometimes it is better to spend more time and write more code that can then be taken and used than reinventing the wheel every time. Thus, if we develop a standard for exchanging information between the profiles of the same user in different networks, we will no longer depend on the developers who add the “Like” button, but believe that “Tweet” is not needed here, but about VKontakte with its "I like it" did not hear.
To begin with, it is necessary to “link” the accounts of different networks. The process might look something like this: A @ X sends a request for a bundle of B @ Y, after which B must confirm that yes, A is me, but on network X. Yes, yes, about the same thing happens when you specify one e-mail as additional.
Next comes the question of how to link the various functions. When I think about it, I have an association with Obj-C / Cocoa's IBOutlet. Of course, the analogy is strained, but we are still considering only an abstract model, so some inaccuracies are forgivable. In fact, we have “sockets”, which we can combine in various ways (limiting ourselves, of course, to common sense). What kind of "sockets" can this be:
Text:
Multimedia: the same as with the text, but in addition it is necessary to provide the possibility that the direct display of this content is impossible there. In this case, there should be additional sockets like “post a link to the content”. For last.fm and the like - “I'm watching / listening to X”.
There may also be sockets “Allow access to X”. They can serve for situations such as the above-mentioned display of a personal charts with Last.fm next to the list of audio records of the user VKontakte, etc.
On the other side of these sockets, we will most likely need an appropriate handler. For example, Twitter will have to use the analog twitlonger.com for too long messages. Last.fm - process the message about the song you are listening to. And on Facebook / VKontakte, for example, convert links to a YouTube video or image that this link links to.
After the accounts are connected and the sockets are connected, the question arises: how will the user use this? Let for each outlet there will be a certain object with which it will be logically connected and will be displayed in a block specially allocated for sockets next to this object.
On the example of Twitter: next to Favorite / Retweet / Reply there will be “Like” and / or “Like” buttons - depending on whether we tied your Twitter account to your Facebook or VKontakte account or both. And next to the Tweet button, there are ticks "Post on Facebook" and / or "Write on the wall", etc. Here, “Like” is associated with the “separate tweet” object, and “Post on ...” with the “Tweet” button.
Or an example: the ability, when uploading photos to Facebook, immediately duplicate them on VKontakte. Or tweet one of them or a whole album.
The advantages are quite obvious - the influx of users from other networks. Given that their orientation is different (except for Facebook-VKontakte), they are in different niches and are unlikely to interfere with each other. On the contrary, they will acquire opportunities that they did not originally have. Since this interaction involves not complete, but only partial integration at the level of some basic functions, the number of visits will not fall, because for the full functionality will need to go to the site.
If an attempt is made to get into a foreign niche (for example, the already mentioned introduction of VKontakte microblogging), users will have an alternative that. definitely good.
Agree that the social graphs of different networks are very different due to the fact that each of them provides different functionality and, accordingly, users on them do different things. However, from the user's point of view, a little mutual integration would not hurt them. What I mean by this integration, and what benefits it might have gained from this company, will be discussed.
I’ll consider Twitter, Facebook / VKontakte and Last.fm as concrete examples.
')
For starters - specific examples of some inconveniences.
VKontakte has recently introduced the microblogging function, after which the walls of users have become like Twitter with what you know . Good or bad - this issue in the discussion will be left out. Take it for granted. It is logical to assume that similar functionality will be used in a similar way. It also seems logical that the user using the same features will create about the same content. That is, writing about something on his wall, he is likely to write the same thing on Twitter and vice versa. A similar situation may arise with a wall on Facebook. In this regard, it would be nice when writing a message on your wall, say, to have some “Tweet it too” checkbox. Or, on Twitter, "Post on Facebook".
Often I have seen people listen to music mainly on VK. It is quite logical - there you can find music for every taste, it does not require hard disk space, only a more or less stable channel. Here comes the stage Last.fm. Agree, it would be interesting, say, directly from the VC to have access to the charts of users. But what would be really convenient here is scrobbling for VC. Of course, there is already Last.fm in VKontakte, but as an application, and this is something completely different.
In the opposite direction: I put some composition on Last.fm on my favorite list. It would probably be nice to share this news with friends in other networks - there are a lot of those who may be interested in this.
If I express a desire to go to any event at Last.fm, it would be nice to also be noted in the corresponding meeting on Facebook / VK, if such exists and vice versa.
This list goes on and on. If you add to the above networks YouTube - even longer.
Implementation
I think the first thing that comes to mind is various extensions / add-ons for browsers or corresponding widgets on websites. However, the ability to stick a widget is far from everywhere, and add-ons are inconvenient because they need to be searched and installed. For each browser on each device from which you are going to go online. And on someone else's computer they may simply not be. Meh. It would be much more convenient to have all this out of the box, not to depend on the browser.
Of course, some of the above are already implemented to some extent. Say, last.fm has the opportunity to tweet or post on Facebook'e the upcoming concert. However, if I want to report this significant VKontakte event, then I have to resort to the old, like the world, copy-paste. Naturally, even without the “Like” button, we used to live somehow, but it’s somehow easier and more comfortable with it, isn't it?
So how can this be done?
Those who are familiar with OOP and at least heard about design patterns know that sometimes it is better to spend more time and write more code that can then be taken and used than reinventing the wheel every time. Thus, if we develop a standard for exchanging information between the profiles of the same user in different networks, we will no longer depend on the developers who add the “Like” button, but believe that “Tweet” is not needed here, but about VKontakte with its "I like it" did not hear.
A little more about how it might look.
To begin with, it is necessary to “link” the accounts of different networks. The process might look something like this: A @ X sends a request for a bundle of B @ Y, after which B must confirm that yes, A is me, but on network X. Yes, yes, about the same thing happens when you specify one e-mail as additional.
Next comes the question of how to link the various functions. When I think about it, I have an association with Obj-C / Cocoa's IBOutlet. Of course, the analogy is strained, but we are still considering only an abstract model, so some inaccuracies are forgivable. In fact, we have “sockets”, which we can combine in various ways (limiting ourselves, of course, to common sense). What kind of "sockets" can this be:
Text:
- Post X on another resource too
- Share X on another resource (de-facto retweet)
Multimedia: the same as with the text, but in addition it is necessary to provide the possibility that the direct display of this content is impossible there. In this case, there should be additional sockets like “post a link to the content”. For last.fm and the like - “I'm watching / listening to X”.
There may also be sockets “Allow access to X”. They can serve for situations such as the above-mentioned display of a personal charts with Last.fm next to the list of audio records of the user VKontakte, etc.
On the other side of these sockets, we will most likely need an appropriate handler. For example, Twitter will have to use the analog twitlonger.com for too long messages. Last.fm - process the message about the song you are listening to. And on Facebook / VKontakte, for example, convert links to a YouTube video or image that this link links to.
After the accounts are connected and the sockets are connected, the question arises: how will the user use this? Let for each outlet there will be a certain object with which it will be logically connected and will be displayed in a block specially allocated for sockets next to this object.
On the example of Twitter: next to Favorite / Retweet / Reply there will be “Like” and / or “Like” buttons - depending on whether we tied your Twitter account to your Facebook or VKontakte account or both. And next to the Tweet button, there are ticks "Post on Facebook" and / or "Write on the wall", etc. Here, “Like” is associated with the “separate tweet” object, and “Post on ...” with the “Tweet” button.
Or an example: the ability, when uploading photos to Facebook, immediately duplicate them on VKontakte. Or tweet one of them or a whole album.
And what's up with this network?
The advantages are quite obvious - the influx of users from other networks. Given that their orientation is different (except for Facebook-VKontakte), they are in different niches and are unlikely to interfere with each other. On the contrary, they will acquire opportunities that they did not originally have. Since this interaction involves not complete, but only partial integration at the level of some basic functions, the number of visits will not fall, because for the full functionality will need to go to the site.
If an attempt is made to get into a foreign niche (for example, the already mentioned introduction of VKontakte microblogging), users will have an alternative that. definitely good.
Source: https://habr.com/ru/post/112783/
All Articles