eskerda.com Report : Visit Site

Technical data of the eskerda.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host eskerda.com. Currently, hosted in United Kingdom and its service provider is Linode LLC .

the related websites

carlsonrezidor.com bournemouth.co.uk arkive.org ft.com allprint.co.uk monografias.com whitehouse.gov kantarworldpanel.com politicsresources.net un.org 

HTTP Header Analysis

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

DNS

HtmlToText

you are using an outdated browser. please upgrade your browser or activate google chrome frame to improve your experience. your daily cup of tea™ posts projects code powered by wp termlove codename maials march 6, 2017 leave a comment i’ve been busy working on something. it’s not finished so this is just a sneak peek. cmdbikes: a terminal client for citybikes november 23, 2016 leave a comment lo and behold cmdbikes , a client to get bike share information right at your terminal. you can install it by $ pip install cmdbikes looks good, but why? most of the time i spend on citybikes is either working on pybikes or the api but rarely using it, aka eating my own dog food. for a while i thought the api syntax was sufficiently straightforward to not even need an interface for a language. turns out i was wrong: the v2 syntax of the api has some caveats and having an abstraction over it helps make everything easier and cleaner. i first noticed this whilst attending an open data hackatiño organized by coruña dixital and gpul . even though i was invited to just be part of the jury, being in a room full of people coding made me want to join in on the fun and prompted me to start working on a telegram bot for citybikes (which i plan to release on the following weeks/months). it’s impossible to assume an api is going to have a perfect representation, so abstracting it in some way will always hide the ugly parts and will make building api consumers easier. there are already some interfaces for other languages but i haven’t find any for python, most probably due to the fact that requests is an ubiquitous library that makes things much easier. precisely for that reason i decided to create python-citybikes , an interface for the citybikes api that makes working with it a real pleasure. some things might change so i will keep it under 0.1 for a while. the cool part of python-citybikes is that it abstracts all code relating to requesting stuff and from the code point of view, all resources are accessed just when they are needed and saved for later reuse (though an update on the data can be forced). this snippet, for instance, gives you the first station of the first network on the api. import citybikes client = citybikes.client() # this will do a request to https://api.citybik.es/v2/networks a_network = next(iter(client.networks)) # this will do a request to https://api.citybik.es/v2/networks/foobar an_station = next(iter(a_network.stations)) # this will do no further requests len(client.networks) # neither will this len(an_station.stations) this one instantiates a network by its id import citybikes client = citybikes.client() bicing = client.network(client, uid='bicing') # this will do a request to https://api.citybik.es/v2/networks/bicing print(bicing) # this will not do further requests len(bicing.stations) another good thing of having an interface for an api is that it allows the addition of utility functions. in this case, i added a near function that will return resources based on distance to a given point. import citybikes # gives you 5 nearest stations on a given lat / lng lat, lng = 40.7831, -73.9712 client = citybikes.client() network = next(iter(client.networks.near(lat, lng))) stations = list(network.stations.near(lat, lng))[:5] see where this is going? the best way to assert that an interface for an api is useful is by writing a simple terminal client to play with the api, and that’s what cmdbikes is. even though it would be fairly easy to bundle cmdbikes together with python-citybikes, i have decided against it. this way i get to feel what’s like to install and use it separately. this is not the first time i think about writing a terminal client for citybikes. some years ago i did a live coding exercise on a talk at pycones 2014 precisely about that. although, since the talk was about pybikes, the exercise used pybikes and not the api directly. all in all, writing cmdbikes and python-citybikes has been a useful exercise. for a long time i’ve avoided learning the proper way to publish a package on pypi or writing things on python 3. turns out writing a proper package and publishing on pypi is not that difficult (at least anymore) and it’s straightforward to write new python 3 code that is compatible with python 2.7 (at least for a simple case like this). revisitando bicimad july 9, 2016 leave a comment hace dos años publiqué una “auditoria de seguridad” de bicimad . entrecomillado, porque no era tal. usando un par de herramientas a disposición de la mayoría salieron errores que no se deberían permitir en ningún proyecto público-privado . éso era sólo la punta del iceberg, se encontraron más gazapos , hubo amenazas , se escribieron artículos y, como es costumbre, se olvidó todo para dar paso al siguiente escándalo. de no ser por mi proyecto, citybikes , yo también me habría olvidado. para contextualizar, citybikes es un agregador de sistemas de bicicletas públicas y a día de hoy, es la fuente pública más utilizada para crear desde apps a proyectos de investigación que requieran datos sobre bicicletas públicas. ante la duda sobre si incluir bicimad al proyecto, mi decisión fue la de no hacerlo hasta que no se ofreciera desde el ayuntamiento o la empresa gestora de una fuente abierta y claramente licenciada de datos (para el que no lo sepa, algo conocido como “open data”). bien, han pasado dos años. ¿ha cambiado algo? la página de bicimad sigue mostrando el siguiente ridículo “mapa-imagen” . los datos sobre localización y disponibilidad de las bases (que son los que realmente importan) siguen sin ser públicos . ésto es un extracto de la propuesta en el portal de datos de madrid . información completa bicimad (no viable) resumen de la propuesta: “informacion completa bicimad ” fecha de recepción: 30/09/2015 propuesto por: ciudadano estado:no viable actualmente la aplicación bicimad de gestión del servicio público de bicicleta no dispone, en tiempo real, de la información que se solicita, por lo que actualmente no es viable que dicha información se publique en el portal de datos abiertos por cuestiones técnicas . creemos que en el plazo de un año, podríamos disponer, con la colaboración y apoyo de la emt, de una aplicación más enfocada a la actual política de transparencia en beneficio de todos. actualmente, ya se publica en el portal información sobre la bicicleta pública como la posición (georreferenciada) de las estaciones, las incidencias (syr), media de bicicletas disponibles diaria u usos diarios, tanto de abonados mensuales como ocasionales y el importe pagado en concepto de indicadores de calidad del servicio. no obstante, si tenemos previsto a lo largo de la primera quincena del mes de junio, publicar en el portal de datos abiertos una mayor información sobre bicimad. entre esta información estarían los datos completos de los gastos del ayuntamiento por este servicio. recientemente ha llegado una contribución a pybikes (una de las partes fundamentales de citybikes) que añade el sistema de bicimad. dado que, tras dos años, todavía hay excusas “técnicas” sobre la imposibilidad de abrir ésta fuente, no tengo más remedio que aceptar la contribución. al menos ahora bicimad dispone de una api y un mapa online , aunque sea a través nuestro, y sus usuarios podrán elegir entre la multitud de aplicaciones que ya funcionan con citybikes. a disfrutar. your browser does not support frames, big deal configuring the polaroid cube on linux (or anywhere) october 20, 2014 13 comments the polaroid cube is all fun and games until you see the only way to configure it is through a program for either windows or os x. fortunately that configuration program does not do anything fancy, it just edits the files setting.txt and time.txt that live in the root level of the sdcard. these files are read by the firmware of the camera when powered on, and can be edited by any text editor. the syntax is a bit sloppy. cube-v1.01 update:n <--- set this field to y before saving! format

URL analysis for eskerda.com

https://eskerda.com/thinkpad-conky-config/
https://eskerda.com/codename-maials/
https://eskerda.com/arduino-nes-gamepad/#comments
https://eskerda.com/codename-maials/#respond
https://eskerda.com/revisitando-bicimad/
https://eskerda.com/#setting
https://eskerda.com/arduino-nes-gamepad/
https://eskerda.com/demos/dungeon
https://eskerda.com/polaroid-cube-on-linux/
https://eskerda.com/polaroid-cube-on-linux/#comments
https://eskerda.com/a-mule/#respond
https://eskerda.com/auditoria-bicimad/
https://eskerda.com/bsp-dungeon-generation/
https://eskerda.com/categorizing-citybikes-data-feeds/#respond
https://eskerda.com/projects/

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: ESKERDA.COM
Registry Domain ID: 1796854933_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.ovh.com
Registrar URL: http://www.ovh.com
Updated Date: 2017-03-15T11:00:46Z
Creation Date: 2013-04-26T16:06:12Z
Registry Expiry Date: 2018-04-26T16:06:12Z
Registrar: OVH
Registrar IANA ID: 433
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS104.OVH.NET
Name Server: NS104.OVH.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-10-01T02:39:02Z <<<

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 OVH

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =eskerda.com

  PORT 43

  TYPE domain

DOMAIN

  NAME eskerda.com

  CHANGED 2017-03-15

  CREATED 2013-04-26

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS104.OVH.NET 213.251.188.148

  NS104.OVH.NET 213.251.128.148

  REGISTERED yes

Mistakes

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