jillesvangurp.com Report : Visit Site

Technical data of the jillesvangurp.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host jillesvangurp.com. Currently, hosted in Netherlands and its service provider is PCextreme B.V. .

HTTP Header Analysis

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

DNS

HtmlToText

skip to content www.jillesvangurp.com yet another blog menu me work about scroll down to content posts posted on march 6, 2017 the people graph social networks have been all the rage for over a decade now. in the past years, facebook has consolidated their leadership in personal networking and linkedin has become the undisputed leader of business networking. a side effect of this consolidation is that business models have also consolidated, leaving out a lot of potential applications and use-cases that do not fit the current models. both facebook and linkedin have business models that focus on monetizing their respective social graphs through advertising. linkedin also monetizes search, analytics, and recruiting. to protect their data and business, they have largely cut off api access for third parties. consequently, building third party applications that use these networks has become very hard, if not impossible. at the same time, building a new social network has become harder due to the fact that most people already have their social networking needs covered by the existing offerings. most wannabe new social networks face the ’empty room problem’, where they don’t become interesting until enough users are using it. inbot was founded on the idea that sales is fundamentally a social process where building relationships and trust between people is the key to success. yet, customer relationship management (crm) systems used today by most salespeople are anything but social. crm is mostly used to manually keep track of conversations with customers. relationship data is shared only within the sales team, and when sales people change jobs, all aggregated data in the crm is left behind and they take their social network with them. marketing automation has emerged as a software-based mechanism to help companies to generate leads in a more automated fashion. the problem with it today is that the spam and noise generated by these applications is deafening, and making everyone harder to reach. initially, inbot started out as a disruptive play to make crms find and provide links to new business opportunities. over time, we realized that we should focus solely on social lead generation, and decouple it from teams and companies that crm vendors target. since last august, we have rolled out a community that we hope will one day rival that of linkedin but yet works very differently. continue reading “the people graph” posted on january 9, 2017 2084 – dodging a dystopian future 2084 – dodging a dystopian future some thoughts on surveillance technology, the broader impact on society, and my attempt to predict the future. i wrote this up over the past few months and finally decided to click publish a few days ago. posted on medium. so, please go there and do the usual sharing, liking, commenting, etc. there if you feel like it. posted on august 26, 2016 september 20, 2016 running elasticsearch in a docker 1.12 swarm my last blog post was on running consul in docker swarm . the reason i wanted to that is because i want to run elasticsearch in swarm so that i can use swarm service discovery to enable other containers to use elasticsearch. however, i’ve been having a hard time getting that up and running because of various issues and limitations in both elasticsearch and docker. while consul is nice, it feels kind of wrong to have two bits of infrastructure doing service discovery. thanks to christian kniep’s article , i know it can be done that way. however, i actually managed to do it without consul eventually. since it is completely non trivial to do this, i decided to write up the process for this as well. assuming you have your swarm up and running, this is how you do it: docker network create es -d overlay docker service create --name esm1 --network es \ -p 9201:9200 -p 9301:9301 \ elasticsearch -des.network.publish_host=_eth0_ \ -des.discovery.zen.ping.unicast.hosts=esm1:9301 \ -des.discovery.zen.minimum_master_nodes=2 \ -des.transport.tcp.port=9301 docker service create --name esm2 --network es \ -p 9202:9200 -p 9302:9302 \ elasticsearch -des.network.publish_host=_eth0_ \ -des.discovery.zen.ping.unicast.hosts=esm1:9301 \ -des.discovery.zen.minimum_master_nodes=2 \ -des.transport.tcp.port=9302 docker service create --name esm3 --network es \ -p 9203:9200 -p 9303:9303 \ elasticsearch -des.network.publish_host=_eth0_ \ -des.discovery.zen.ping.unicast.hosts=esm1:9301,esm2:9302 \ -des.discovery.zen.minimum_master_nodes=2 \ -des.transport.tcp.port=9303 there is a lot of stuff going on here. so, lets look at the approach in a bit more detail. first, we want to be able to talk to the cluster using the swarm registered name rather than an ip address. secondly, there needs to be a way for each of the cluster nodes to talk to any of the other nodes. the key problem with both elasticsearch and consul is that we have no way to know up front what the ip addresses are going to be of swarm containers. furthermore, docker swarm does not currently support host networking so we cannot use the external ip’s of the docker hosts either. with consul we fired up two clusters that used each other and via its gossip protocol, all nodes eventually find each other’s ip addresses. unfortunately, the same strategy does not work for elasticsearch. there are several issues that make this hard: the main problem with running elasticsearch is that similar to other clustered software it needs to know the where some of the other nodes in the cluster are. this means we have need a way of addressing the individual elasticsearch containers in the swarm. we can do this using the ip address that docker assigns to the containers, which we can’t know until the container is running. alternatively, we can use the container dns entry in the swarm, which we also can’t know until the container is running because it includes the container id. this is the root cause of the chicken egg problem we face when bootstrapping the elasticsearch cluster on top of swarm: we have no way of configuring it with the right list of nodes to talk to. elasticsearch really does not like having to deal with round robin’ed service dns entries for it’s internal nodes. you get a log full of errors since every time elasticsearch pings a node, it ends up talking to a different node. this rules out what we did with consul earlier where we solved the problem by running two consul services (each with multiple nodes) that talk to each other using their swarm dns name. consul is smart enough to figure out the ip addresses of all the containers since it’s gossip protocol ensures that the information replicates to all the nodes. this does not work with elasticsearch. dns entries of other elasticsearch nodes that do not resolve when elasticsearch starts start up, causes it to crash and exit. swarm won’t create the dns entry for a service until after it has started. the solution to these problems is simple but ugly: an elasticsearch service can only have one node in swarm. since we want multiple nodes in our elasticsearch cluster, we’ll need to run multiple services: one for each elasticsearch node. this is why in the example above, we start three services, each with only 1 replica (the default). each of them binds on eth0 which is where the docker overlay network ends up. finally, elasticsearch nodes rely on the ip address that nodes advertise to talk to each other. so, the port that it advertises needs to match the service port. it took me some time to figure it out but simply doing a -p 9301:9300 is not good enough: it really needs to be -p 9301:9301 . therefore each of the elasticsearch services is configured with a different port. for the http port we don’t need to do this so we can simply map port 9200 to a different external port. finally, the services can only talk to other services that already exist. so, what won’t work is specifying es.discovery.zen.ping.unicast.hosts=esm1:9301,esm2:9302,esm3:9303 on each of the services. instead, t

URL analysis for jillesvangurp.com

http://www.jillesvangurp.com/tag/new-publication/
http://www.jillesvangurp.com/2006/06/10/xdocdiff/comment-page-1/#comment-58993
http://www.jillesvangurp.com/tag/imho/
http://www.jillesvangurp.com/page/2/?id=30%00%27%7c%7csleep%283%29%26%26%271
http://www.jillesvangurp.com/tag/subversion/
http://www.jillesvangurp.com/tag/versionmanagement/
http://www.jillesvangurp.com/tag/ubuntu/
http://www.jillesvangurp.com/tag/photography/
http://www.jillesvangurp.com/tag/nokia/
http://www.jillesvangurp.com/tag/beer/
http://www.jillesvangurp.com/2016/05/25/functional-tests-and-flakyness/#more-1782
http://www.jillesvangurp.com/2015/03/03/how-to-rename-an-index-in-elasticsearch/
http://www.jillesvangurp.com/tag/academic/
http://www.jillesvangurp.com/2017/03/
http://www.jillesvangurp.com/work/photo-galleries/

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: JILLESVANGURP.COM
Registry Domain ID: 108312158_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.eu
Registrar URL: http://www.openprovider.com
Updated Date: 2017-12-15T10:20:47Z
Creation Date: 2003-12-15T09:25:18Z
Registry Expiry Date: 2018-12-15T09:25:18Z
Registrar: Hosting Concepts B.V. d/b/a Openprovider
Registrar IANA ID: 1647
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +31.104482297
Domain Status: ok https://icann.org/epp#ok
Name Server: V1.PCEXTREME.NL
Name Server: V2.PCEXTREME.NL
DNSSEC: signedDelegation
DNSSEC DS Data: 49144 8 2 C1713729AD1E75608548C6C116D91896FBB373B2DBEF4A73E683783399A23353
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-05-10T16:46:26Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR Hosting Concepts B.V. d/b/a Openprovider

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =jillesvangurp.com

  PORT 43

  TYPE domain

DOMAIN

  NAME jillesvangurp.com

  CHANGED 2017-12-15

  CREATED 2003-12-15

STATUS
ok https://icann.org/epp#ok

NSERVER

  V1.PCEXTREME.NL 93.180.70.53

  V2.PCEXTREME.NL 217.115.199.215

  REGISTERED yes

Mistakes

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