nocarrier.co.uk Report : Visit Site

Technical data of the nocarrier.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host nocarrier.co.uk. Currently, hosted in Singapore and its service provider is CloudFlare Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called cloudflare containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

toggle navigation ben longden home speaking contact me! anonymous login register lost password decentralising the social network october 14, 2014 uncategorized no comments facebook , personal , social , tildeclub read in facebooks rise to the number two spot out in the list of the most popular websites in the world is proof that there is a huge demand out there for the social network. a way of being able to share snippets of your lives with friends and family in a way that they can consume as and when they want to. the social network has replaced emails and letters. it has fundamentally changed the way that we communicate with each other. i have always been rather uneasy about a centralised social network. my issue with it is that those snippets of my life, the announcement of when i first became a dad, my daughters first day at school, when i became a dad again, all of those little bits of information – they build up a picture. a profile. a statistic. a thing that can be sold by the social network for real money, so that the purchasers can place an advert in front of me. i don’t care much for privacy settings. why would corporations who sell my data to other people ever be interested in supplying a free to use and completely private system? the centralised model cannot be trusted to keep any of your information private, or restricted to being viewed only be a small group of people. everything that i share, i share with the knowledge that it could be seen by anyone. over the years there has been a number of attempts to get in on the social network space. many have tried and failed to take on facebook as the go to social network – but none have really been successful in being anything more than another centralised content distribution channel that uses facebook to try and drive traffic in. today, trying to take on facebook as another centralised social network is a bit like treading on google’s lawn in the web search space (although i am encouraged by what duckduckgo are doing in that area). diaspora is one of the first attempts at the decentralising social content. users register with a local hub (or with the right technical know how, can host their own ‘pod’). there is no central store of information. the pods are able to communicate with each other so there’s no centralisation of your data. the barrier to entry however is that it’s just not as slick as the facebook experience (though if you’re interested, you can sign up to the uk pod here and check it out). metcalfe’s law states that the value of a telecommunications network is proportional to the square of the number of connected users of the system. there’s simply not enough people on it that would make it likely that i might find my own friends and family on there. diaspora claim to have a million users (total). facebook has an order of magnitude more, standing tall at 1.32 billion (monthly active as of june 2014). it’s clear that the network that facebook built has considerable value. a uk company, ind.ie is building heartbeat. a decentralised network as part of a much larger plan to free data from ownership by large corporations. as we’re on the wrong side of the beta launch of this new network, it remains to be seen what impact it is going to have. the largest barrier i can see to the adoption of a decentralised social network is user experience. facebook is so compelling because it’s so easy. fill out a form, find your group of friends and you’re done. decentralisation necessitates that you either sign up with a centralised point of presence (a ‘pod’ in diaspora), or you pay to host your own server for yourself or your family. the barrier to entry is automatically higher. as a life long fan of computers (i started coding on my commodore 64 as soon as i was able), i have fond memories of spending some time at the local university learning to use their vax/vms system. it was some form of bsd (i don’t remember exactly) but i do remember that the ‘social network’ really just consisted of those who happened to be logged in to the same server as i was. we could chat – using irc, or the write command. leave messages using email and distribute content by setting up a website in our home directory. this is why the tildeclub experiment appealed to me. of course it’s not a social network. it’s just a low powered linux server that a bunch of geeks / nerds / enthusiasts are messing around with and sharing content with each other. i would love to see the day where i had a slick experience like facebook – but i had control over my own data. being able to provision a social network for my family (and friends) to use, and being able to link my server up to others to form a true social network of computer servers. free from being the product. free from advertising. expanding zoom march 6, 2013 uncategorized 14 comments there’s been some recent discussion on the hal-discuss mailing list around the ‘zoom’ concept for embedding resources, which has prompted me to start exploring this area a little further with a view to potentially writing up a specification that can be applied to any media type that define a way of embedding resources. this blog post mostly serves as a narrative to document my own ideas and learnings and to collect comments and recommendations from others in order to arrive at a proposal that will work for (almost!) everyone. at its most simple level, clients need a way of being able to take an existing resource with defined link relations and zoom (or expand) the current resource to include them in the response. this is primarily to avoid a second round trip to the server in order to retrieve the resource representation that the client is interested in seeing. to illustrate the problem, i have provided an example (for the sake of brevity, i have only included relevant parts of the resource representation). { "_links" : { "http://.../rels/detail" : { "href" : "/example/1/detail" } , "http://.../rels/misc" : { "href" : "/example/1/misc" } , "self" : { "href" : "/example/1" } } } { "_links": { "http://.../rels/detail": { "href": "/example/1/detail" }, "http://.../rels/misc": { "href": "/example/1/misc" }, "self": { "href": "/example/1" } } } in the above example, imagine a scenario where the client that has requested this representation is actually interested in the resource found at the ‘http://…/rels/detail’ link relation. the client now has to make a second request to the server in order to get at the data it needs. we can alleviate this by using a feature of the media type known as embedding – however it is impractical to embed every linked resource every time. we must provide a way of allowing the client to specify the resource it is interested in – and this is ‘zoom’. if we allow the ‘zoom’ (or ‘z’) parameter in the query string to be reserved for this purpose, we can request that the server embeds the link relation by performing a get request on ‘http://…/example/1?zoom=http://…/rels/detail’. the server would then be given the instruction to embed the resource and return it all in the response. { "_embedded" : { "http://.../rels/detail" : [ { "_links" : { "self" : { "href" : "/example/1/detail" } } , "firstname" : "ben" , "lastname" : "longden" } ] } , "_links" : { "http://.../rels/detail" : { "href" : "/example/1/detail" } , "http://.../rels/misc" : { "href" : "/example/1/misc" } , "self" : { "href" : "/example/1" } } } { "_embedded": { "http://.../rels/detail": [ { "_links": { "self": { "href": "/example/1/detail" } }, "firstname": "ben", "lastname": "longden" } ] }, "_links": { "http://.../rels/detail": { "href": "/example/1/detail" }, "http://.../rels/misc": { "href": "/example/1/misc" }, "self": { "href": "/example/1" } } } if we wanted to embed two items, the zoom query parameter may accept multiple link relations separated by commas, i.e., http://…/example/1?zoom=http://…/rels/detail,http://…/rels/misc. the hal format also supports curie style links to shorten the length of link

URL analysis for nocarrier.co.uk

https://nocarrier.co.uk/tag/personal/
https://nocarrier.co.uk/wp-login.php?redirect_to=http%3a%2f%2fnocarrier.co.uk%2fdecentralising-the-social-network%2f
https://nocarrier.co.uk/code-review-karma/#comments
https://nocarrier.co.uk/decentralising-the-social-network/
https://nocarrier.co.uk/tag/json/
https://nocarrier.co.uk/2008/11/
https://nocarrier.co.uk/rest-and-the-hypermedia-constraint/
https://nocarrier.co.uk/tag/azure/
https://nocarrier.co.uk/tag/xml/
https://nocarrier.co.uk/writing-restful-clients/
https://nocarrier.co.uk/tag/conference/
https://nocarrier.co.uk/tag/rest/
https://nocarrier.co.uk/2010/11/
https://nocarrier.co.uk/tag/tildeclub/
https://nocarrier.co.uk/tag/development/
joindiaspora.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
nocarrier.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 25-May-2018

Registrar:
Paragon Internet Group Ltd t/a Tsohost [Tag = UKWEBHOSTING]
URL: http://www.tsohost.co.uk

Relevant dates:
Registered on: 26-Jan-2005
Expiry date: 26-Jan-2019
Last updated: 25-May-2018

Registration status:
Registered until expiry date.

Name servers:
jill.ns.cloudflare.com
seth.ns.cloudflare.com

WHOIS lookup made at 14:17:08 29-Dec-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS nocarrier.co.uk

  PORT 43

  TYPE domain

DOMAIN

SPONSOR
Paragon Internet Group Ltd t/a Tsohost [Tag = UKWEBHOSTING]
URL: http://www.tsohost.co.uk
Relevant dates:

  CREATED 26-Jan-2005

  CHANGED 25-May-2018

STATUS
Registered until expiry date.

NSERVER

  JILL.NS.CLOUDFLARE.COM 173.245.58.122

  SETH.NS.CLOUDFLARE.COM 173.245.59.142

  NAME nocarrier.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .