As we continue to evolve our new website, I will provide more regular updates to all of you visiting our site. Today’s topics are: improved search; much faster speed; and an open issue tracker.
For all of you who contacted us saying “I can’t find anything” on the site through the search box (the magnifying glass in the upper right corner of the screen), we’ve got some great news – it should now work! We tried two different search solutions for all our content before we moved on to a third solution that we find works well. Please do let us know if you are still having challenges finding content.
The site should now be much faster! We recently deployed some caching servers in front of our site and the speed should be dramatically improved for most all of the pages. This was very important to us as we want to provide the best user experience.
If you do find anything wrong with the new site, we have an open issue tracker on Github. You can visit the repository at:
https://github.com/InternetSociety/web-site-feedback
and the actual list of Continue reading

There are many reasons why proxies are implemented into an environment. Some can be put in place for security, others as load balancers for your systems. No matter the use, if you have a proxy in place, Red Hat Ansible Tower may need to utilize it. For a more in-depth look at what we will be doing in this post, you can visit our docs specifically on Proxy Support within Ansible Tower here.
In some instances, you might have Ansible Tower behind a load balancer and need that information added to your instance. Sessions in Ansible Tower associate an IP address upon creation, and Ansible Tower’s policy requires that any use of the session match the original IP address.
To allow for support of a proxy, you will have to make a few changes to your Ansible Tower configuration. Previously, this would have been done in a settings.py file found on your Ansible Tower host, but as of 3.2 you can now make these changes in the UI. To make these edits, you must be an admin on the instance and navigate to Settings, and then Continue reading
AT&T’s network on demand sounds a lot like a service Equinix launched last month.
The 2017 Indigenous Connectivity Summit (ICS) was the start of a critical conversation about how Indigenous communities can connect themselves to the Internet on their own terms. But it was just the beginning.
An extraordinary community of people came together: Indigenous-owned Internet service providers, community network manager/operators, researchers and policy makers, and Indigenous leadership. Their conversations outlined the benefits the Internet can bring to Indigenous communities, including self-determination, culture and language preservation, economic development, health, and education. These conversations are captured in the Indigenous Connectivity Summit Community Report, which also describes the unique challenges Indigenous communities face to gain sustainable connectivity and recommendations to address those challenges.
We hope that this report serves as a springboard to further Indigenous connectivity in North America and beyond. You can take part by visiting the Indigenous Connectivity page!
The post Community Report: Indigenous Connectivity appeared first on Internet Society.
Because containers often exist for only a brief period of time, this reduces the “attack vector.”
Here at The Next Platform, we’ve touched on the convergence of machine learning, HPC, and enterprise requirements looking at ways that vendors are trying to reduce the barriers to enable enterprises to leverage AI and machine learning to better address the rapid changes brought about by such emerging trends as the cloud, edge computing and mobility.
At the SC17 show in November 2017, Dell EMC unveiled efforts underway to bring AI, machine learning and deep learning into the mainstream, similar to how the company and other vendors in recent years have been working to make it easier for enterprises …
Google’s Vision for Mainstreaming Machine Learning was written by Jeffrey Burt at The Next Platform.
Bigleaf uses SD-WAN to connect cloud applications, not as an MPLS replacement.

Xerox fumbled the future when it invented and then ignored the personal computer. With the Macintosh, Apple created the personal computer the Xerox Alto might have been.
Apple is also fumbling the future—the Voice First future. Voice First simply means our primary mode of interacting with computers in the future will be with our voice. When Apple bought Siri it had a solid 5 year lead in voice control. Now Amazon’s Alexa and Google’s Assistant have not only caught Siri, but they’ve surpassed her.
The story of how Apple is fumbling the Voice First future is passionately told by Brian Roemmele in a great interview with Rene Ritchie in his Vector podcast Why Siri needs to be a platform.
Brian covers a lot of ground in the interview, but there are a few main themes: Voice First is the Future; Apple Fumbled Voice First; Engineering First Cultures Suck at Product; Apple Needs to Lose the iPhone Tax and Build Siri as a Platform.
In each section I paraphrase quotes Brian made in the interview to explain the theme. I think you'll find it fun and provocative. Brian is an interesting guy.
Poor quality data is a "silent killer" of service automation.
Check out the new Palo Alto Networks channel on SDxCentral for the latest in next-gen security for IoT, 5G, Cloud, and NFV.