ul data-relation-list – social networking without a central server

At the time of writing this blog has almost no readers but I keep on blogging and this post is in English as I have an idea I think is timed well, knowing that social networking is established in the population and major companies in social networking are experiencing privacy issues.

Let’s say we all started blogging on our own web site instead of using social networks from commercial partners. I have made a scheme to implement a bidirectional list of relations that can be implemented on any website and it is possible to send and accept or deny relational requests using an API.

I have called the concept ul data-relation-list as it consists of an unordered list in html that is maintained by the webmaster’s server. I wrote about the concept using different terms in a previous post.

The concept is relying on html and the implementation of a standard API to handle requests for adding. If the sites you have in your list of relations implement feeds you can have a view that gives you status updates from all the sites in the list and we can start following each other in a new way not relying on the commercial actors in social networking.

See the readme on GitHub. Feel free to contribute by implementing the concept in various languages.

Webmaster friend protocol

I have been thinking about social networking and without mentioning social networks, I want to make the idea of a bidirectional mutual friendship to apply for webmasters. And anyone can become a webmaster. I think of bloggers.

What if there was a protocol for sending a friendship request to a blog from a different blogger? And how could it look?

I have an idea and I want to call it «webmaster friend protocol». WFP.

The idea is that a website must include its friends in such an unordered list as below in the example:

The example contains one friend.

A friend request is sent to a blog from a different blog on an api in json to a WFP endpoint which is an HTTP API that has three routes: request (POST), response(POST) drop(POST) and list(GET).

Request receives an HTTP post and to send a friend request one can send a json object for instance as such:


{
sender: "http://www.perandersen.no"
rss: "http://www.perandersen.no/feed/"
responseAddress: "http://wpf.perandersen.no"
}

Let’s say I sent this to a service you have installed at the address http://www.yourblog.com/wpf/request

When you were ready, through a front end, you could accept or decline. Let’s say you accepted. Your server would then contact my endpoint which was included in the request as http://wpf.perandersen.no and it could be sent as a JSON POST as such:


{
reply: "accepted",
friendList: http://www.yourblog.com
}

At this point, there should be a link in the unordered list in both directions between our websites and both servers could poll each other in case of cheating. Else drop should be called by one of the parties to drop the friendship.

In this way, your friendlist will be bidirectional, distributed and you can syndicate news from all your friends in a feed as such as made in social networks from commercial parties today. At the same time you are in control of the content and if you want ads the income from the ads will come directly to you and not a commercial third party.

This is a new though in my mind but if I don't drop the idea I will try to implement the WPF concept on my own blog. I might have to find a different name.