Ranking Alexa Global: # 1,770,428
Server:Apache/2.4.7 (Ubuntu...
X-Powered-By:PHP/5.5.9-1ubuntu4.22
The main IP address: 104.131.59.210,Your server United States,New York City ISP:Digital Ocean Inc. TLD:org CountryCode:US
The description :whizzy.org on code and gadgets. ubuntu desktop goings on. friday 19th may 2017 tweet ubuntu desktop newsletter i’m going to start a weekly newsletter style update to keep people abreast of what’s been...
This report updates in 21-Oct-2018
Created Date: | 2005-09-29 |
Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host whizzy.org. Currently, hosted in United States and its service provider is Digital Ocean Inc. .
Latitude: | 40.71993637085 |
Longitude: | -74.005012512207 |
Country: | United States (US) |
City: | New York City |
Region: | New York |
ISP: | Digital Ocean Inc. |
HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.7 (Ubuntu) containing the details of what the browser wants and will accept back from the web server.
Content-Length: | 45009 |
X-Powered-By: | PHP/5.5.9-1ubuntu4.22 |
Content-Encoding: | gzip |
Vary: | Accept-Encoding |
Keep-Alive: | timeout=5, max=100 |
Server: | Apache/2.4.7 (Ubuntu) |
Connection: | Keep-Alive |
Link: | |
Date: | Sun, 21 Oct 2018 10:27:03 GMT |
Content-Type: | text/html; charset=UTF-8 |
soa: | cheryl.ns.cloudflare.com. dns.cloudflare.com. 2029127632 10000 2400 604800 3600 |
txt: | "v=spf1 include:_spf.google.com ~all" |
ns: | cheryl.ns.cloudflare.com. kirk.ns.cloudflare.com. |
ipv4: | IP:104.131.59.210 ASN:14061 OWNER:DIGITALOCEAN-ASN - DigitalOcean, LLC, US Country:US |
mx: | MX preference = 20, mail exchanger = aspmx2.googlemail.com. MX preference = 20, mail exchanger = aspmx3.googlemail.com. MX preference = 20, mail exchanger = aspmx4.googlemail.com. MX preference = 20, mail exchanger = aspmx5.googlemail.com. MX preference = 10, mail exchanger = alt1.aspmx.l.google.com. MX preference = 10, mail exchanger = alt2.aspmx.l.google.com. MX preference = 0, mail exchanger = aspmx.l.google.com. |
whizzy.org on code and gadgets. ubuntu desktop goings on. friday 19th may 2017 tweet ubuntu desktop newsletter i’m going to start a weekly newsletter style update to keep people abreast of what’s been going on with ubuntu desktop as we move to gnome shell and build the foundations for 18.04 lts. here’s the first instalment: friday 19th may 2017 gnome we’re on to the last few mir ( https://wiki.ubuntu.com/maininclusionprocess ) reviews for the packages needed to update the seeds in order to deliver the gnome desktop by default. we still have some security questions to answer about how we deal with updates to mozjs/gjs in an lts release (where mozjs has a support period of 12 months but we need to offer support for a full five years). this is being looked at now, but for 17.10 we are set. we are aiming to have the seeds updated next week, and this will be the first milestone on the road to a fantastic gnome experience in 17.10 artful. we’ve been fixing bugs in the ambiance & radiance themes to make them look crisp on gnome shell. http://www.omgubuntu.co.uk/2017/05/install-improved-ambiance-gnome-theme we’ve also triaged over 400 gnome shell bugs in launchpad to allow us to more easily focus on the important issues. we have been working on removing ubuntu’s custom “aptdaemon” plugin in gnome software in favour of the upstream solution which uses packagekit. this allows us to share more code with other distributions. livepatch https://www.ubuntu.com/server/livepatch livepatch delivers essential kernel security updates to ubuntu machines without having to reboot to apply them. as an ubuntu user you can sign up for a free account. we’re working on integrating livepatch in to the supported lts desktops to provide a friendly way to setup and configure the service. this week we started to investigate the apis provided by the livepatch services so we can report livepatch activity to the user, obtain an api key on behalf of the user & set up the service. work has also started on the software-properties-gtk dialogs (aka software & updates in system settings) to add the options required for livepatch. qa added upgrade tests from zesty to artful for ubuntu and flavours. working on making all these tests pass now so that everyone will have a solid and reliable upgrade path. work is being done on the installer tests. this will extend the current installer tests to check that not only has the install completed successfully but that all desktop environment is working as expected, this had previously been covered with manual tests. package updates gstreamer is now at 1.12 final in 17.10. chromium: stable 58.0.3029.110, beta 59.0.3071.47, dev 60.0.3095.5 libreoffice 5.3.3 is being tested. cups-filters: 1.14.0 snapd-glib: 1.12 snaps more gnome applications are being packaged as snaps. there is still some work to do to get them fully confined and fully integrated into the desktop. we’re working on adding snap support to gtk’s portals to allow desktop snaps to access resources outside their sandbox. we will start tracking the snaps here: https://wiki.ubuntu.com/desktopteam/gnome/snaps in the news interview with ken vandine on the gnome desktop in ubuntu: http://www.omgubuntu.co.uk/2017/05/ubuntu-switch-to-gnome-questions-answered there’s also a survey running to get feedback on some extensions which could be shipped with ubuntu desktop: http://www.omgubuntu.co.uk/2017/05/ubuntu-desktop-gnome-extensions-survey-1710 this was picked up by the linux unplugged podcast as their headline story: http://www.jupiterbroadcasting.com/114701/that-new-user-smell-lup-197/ tweet posted by will cooke / may 19, 2017 / 8 comments / posted in uncategorized retrieving user profile data from login with amazon on alexa tweet in my previous post about how to add oauth to your alexa app in 10 minutes a couple of people commented that they couldn’t actually access the users information once they had linked their account. i didn’t actually try and access any of the user information because the only user of my skill is me, and i already know my name and email address. nevertheless, i had a quick play with it over the weekend and here’s a simple skill to show you how to access the user’s profile information from a python skill running in aws lambda. first of all you need to make sure your skill is set up to use login with amazon. i’ve covered this for smart home skills here but it works just the same for normal skills. you also need to make sure your skill is configured to use the scopes “ profile ” and “ postal_code “. this is done in the configuration tab in the developer console for your skill: the interaction model for this skill is as follows: { "intents": [ { "intent": "amazon.helpintent" }, { "intent": "amazon.cancelintent" }, { "intent": "amazon.stopintent" }, { "slots": [ { "name": "options", "type": "options" } ], "intent": "greetintent" } ] } the custom slot type “options” is: first name last name post code email address user id and the sample utterances are: greetintent tell me my {options} greetintent what is my {options} and here’s the code (also on github here ): #!/usr/bin/python import requests def build_speechlet_response(title, output, reprompt_text, should_end_session): return { 'outputspeech': { 'type': 'plaintext', 'text': output }, 'card': { 'type': 'simple', 'title': "greeter", 'content': output }, 'reprompt': { 'outputspeech': { 'type': 'plaintext', 'text': reprompt_text } }, 'shouldendsession': should_end_session } def build_response(session_attributes, speechlet_response): return { 'version': '1.0', 'sessionattributes': session_attributes, 'response': speechlet_response } def get_user_info(access_token): #print access_token amazonprofileurl = 'https://api.amazon.com/user/profile?access_token=' r = requests.get(url=amazonprofileurl+access_token) if r.status_code == 200: return r.json() else: return false def handle_end(): return build_response({}, build_speechlet_response("session ended", "goodbye!", "", true)) def launch_request(access_token): session_attributes = {} card_title = "welcome" if access_token is none: speech_output = "your user details are not available at this time. have you completed account linking via the alexa app?" reprompt_text = "" should_end_session = true else: user_details = get_user_info(access_token) if user_details is none: speech_output = "there was a problem getting your user details." should_end_sesion = true else: print user_details speech_output = "hello "+user_details['name'].split(" ")[0]+"! i know all about you now. we can be friends!" reprompt_text = "what can i tell you about your user information? first name, last name, email address or postcode?" should_end_session = false return build_response(session_attributes, build_speechlet_response( card_title, speech_output, reprompt_text, should_end_session)) def intent_request(intent_request, access_token): intent = intent_request['intent'] intent_name = intent['name'] if intent_name == "greetintent": if access_token is not none: user_details = get_user_info(access_token) if user_details is none: query_type = false else: query_type = intent['slots']['options']['value'] else: return handle_end() if query_type == "post code": speech_output = "your post code is "+user_details['postal_code']+"." elif query_type == "first name": speech_output = "your first name is "+user_details['name'].split(" ")[0]+"." elif query_type == "last name": speech_output = "your last name is "+user_details['name'].split(" ")[1]+"." elif query_type == "email address": speech_output = "your email address is "+user_details['email']+"." elif query_type == "user id": speech_output = "your user id is "+user_details['user_id']+"." else: speech_output = "something went wrong. goodbye." card_title = "what i know about you" return build_response({}, build_speechlet_response(card_title, speech_output, none, true)) if intent_name == "amazon.helpintent": print "help intent" card_title = "no help available!" speech_outp
https://www.whizzy.org/wp-content/uploads/2017/02/ubuntu-logo-tn.png
https://www.whizzy.org/2011/02/
https://twitter.com/intent/tweet?url=https%3a%2f%2fwww.whizzy.org%2f2016%2f12%2fhowto-add-oauth-to-your-alexa-smart-home-skill-in-10-minutes%2f&via=8none1&related=8none1%3awill%20cooke
https://www.whizzy.org/2010/09/
https://www.whizzy.org/category/google-maps/
https://www.whizzy.org/2009/05/
https://www.whizzy.org/2016/12/howto-add-oauth-to-your-alexa-smart-home-skill-in-10-minutes/#comments
https://www.whizzy.org/#dialtones
https://www.whizzy.org/2009/06/
https://www.whizzy.org/wp-content/uploads/2016/12/authurl.png
https://www.whizzy.org/2016/09/unity-7-low-graphics-mode/
https://www.whizzy.org/#extras
https://twitter.com/intent/tweet?url=https%3a%2f%2fwww.whizzy.org%2f2017%2f02%2fcisco-7941-asterisk-and-sip%2f&via=8none1&related=8none1%3awill%20cooke
https://www.whizzy.org/2011/09/
https://www.whizzy.org/page/7/
thekelleys.org.uk
omgubuntu.co.uk
phil.lavin.me.uk
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: WHIZZY.ORG
Registry Domain ID: D107641280-LROR
Registrar WHOIS Server: whois.google.com
Registrar URL: http://domains.google.com
Updated Date: 2018-09-29T17:11:46Z
Creation Date: 2005-09-29T11:47:42Z
Registry Expiry Date: 2019-09-29T11:47:42Z
Registrar Registration Expiration Date:
Registrar: Google Inc.
Registrar IANA ID: 895
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6502530000
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Contact Privacy Inc. Customer 1241750676
Registrant State/Province: ON
Registrant Country: CA
Name Server: KIRK.NS.CLOUDFLARE.COM
Name Server: CHERYL.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2018-10-21T10:38:55Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
REFERRER http://www.pir.org/
REGISTRAR Public Interest Registry
SERVERS
SERVER org.whois-servers.net
ARGS whizzy.org
PORT 43
TYPE domain
DOMAIN
NAME whizzy.org
HANDLE D107641280-LROR
CREATED 2005-09-29
STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
NSERVER
KIRK.NS.CLOUDFLARE.COM 173.245.59.192
CHERYL.NS.CLOUDFLARE.COM 173.245.58.83
OWNER
ORGANIZATION Contact Privacy Inc. Customer 1241750676
ADDRESS
STATE ON
COUNTRY CA
REGISTERED yes
The following list shows you to spelling mistakes possible of the internet users for the website searched .