iPigeon.institute « Made with Google » PidginKit TalkBox Actions Privacy Policy and Terms of Service.

iPigeon.institute User Privacy Policy

The mobile app, web app, and scripting actions, and content of products produced of the organisation fall under several to many various licensing agreements at the time of this writing, May 2019. Given such circumstances, and on account of scaled delivery timelines in mind, a conservative user privacy policy is requisite in order.

The licensors and open-source development projects I'd been indebted to may (or may not) collect user data in the form of cookies.

It has been the ethos of this .institute web and mobile app and digital accessory production foundry that offering user data, metrics, usage information, system info, and user feedback is a productive manner with which to establish an efficacious development ecology, within the digital foray of the internet, which is the basis of much of our communications today, and from here forth, as well.

Some of the products produced of iPigeon.institute and umbrella companies will fall under the following additional privacy policy:

This product is intended for academic and scholastic learning environments. As such, and at that, or consideration, the product will be updated along an astute development project architectural fundamental underpinning, aimed at burgeoning a much-standardized threshold of user intelligence based upon Google Mobile Services and Android Open Source Project's code-scripting, libraries, and Multi-Device Management protocols, as the end-user receives them [the user interface and experience through Google Actions developer through « Made with Google » by iPigeon.institute and supporting cooperative efforts.

As such, the expectations upon the end-user and developer(s) are bound by United States of America Federal Trade Commission by-lines and rules; particularly the Children's Online Privacy Protection Act of 1998, 15 U.S.C. 6501–6505, pertaining to rules regarding online interactions involving children under the age of 13 years. 

iPigeon.institute aims to produce digital products, services, and elsewise (such as hardware) which will be suitable for users of various discrete age groups, while providing a suitable backdrop of learning, lifestyle, and technology that is delivered with an aspiration towards artisanship and hand-crafted authenticity.  

Thanks for using products by iPigeon.institute.

mbed'ing the Google Assistant Services (gRPC) Software Development Kit on to your Google AIY Voice Kit 2.0 Raspberry Pi Zero WH board from Target.

curl -sSL https://~`/•^°\=✓*bwip!!.com/installSlædeAeffe.™pac | sudo bash

???? {something like that, maybe}

The point is to develop the single threaded processor as a Complex Instruction Single Compute CISC processor (perhaps ad hoc usage somewhat)

to manage the various duties that the board can field and relay as far as sensory I/O and for the voltage required to push or throttle the calibration of the compressor/envelope signals in some notion of that the Google Assistant API - which is a massive undertaking of interfacing capabilities in libs and process-scripting of requiring all of Google's API repositories in being suited on-hand for the controller device as a « self-hosted » full server interface.

Important: this librarybwipp/>∆ is known as « gRPC » on GitHub or similar Unix / Linux architecture sort repository.

This sort of purpose in enterprise développent is otherwise known as a .icu (colloquially), of general Top Level Domain web app development.

=>< =>< =>< =>< =>< =>< =>< =>< =<> =>< =0/*6

  # Perhaps, 1st of all, port scan (ioctl?) [Check]

      # the mbed board; perhaps at platformio.org (best

          # site for embedded device platforming, frameworks

         # and as a lib / script / proc - subtype

       # « customizing » (tryna) purpose about IoT device board

     # purchases in slædd'nAeFFé™ multivariate distributions

   # to bwipp pigeon around, see what's bwi-bwippsies

   

                   /`~/•^°\==✓°`* bwippzsi*'ieezz<_ span="">

Cooooooo- wu-WuWU wroooóoooooóoo....

=>< =>< =>< =>< =>< =>< =><% •°√~\•^°/=~'* bwi√p¶sie$*:-/

    # « | »

     is

    

« %7c »

in

  tcp/udp ipv4/v6 in the address line.

  # # in case your browser features a command-address line as for the

Straight Line | | delineator separator thing, as for UTF-8

=><=><=><=><=><=><=><=><=><<=

At some point, it's back to the instructions for doing the development board mbed thing of getting it working or better.

=>< =>< , =>< =>< =>< =>< =>< =>< =>< =>< =><

Creating a Virtual Environment

  in

Python 3.3(+) 

     with

          Lib/venv

         

The 'venv' module.

Invoking the virtual environment is important to previz the middle ground between scripting code and commands (libs / firmware flashing) in to the embedded device.

# # you'll need to know the path to your desired destination device, which isn't an off-hand easy thing to simply stated or claim, and as well pull it off like bwipp-si*ezzz.

=>< =>< =>< =>< =>< =>< =>< =>< =>< =>< =>< =>< =>< =

Okay, perhaps not, though. Not Python, I'd decide - for this one. I find some of the syntax in Python to be contrary to some of my efforts at understanding scripting and coding, as a musician at heart. I'm planning on going with a Java embedded platform.

Update: May 6th, 2019:

Instead of continuing to try to SSH in to the Voice Kit 2.0 as a first-off consideration, I purchased a mini-HDMI to HDMI cable at Fry's Electronics; a warehouse electronics specialty store. I was pleased to see the results when I plugged it in and booted up the system - a complete Linux operating system contained within the small Google Cardboard Voice Kit.

The home screen of the Google AIY Voice Kit 2.0 - a complete Linux operating system in and of itself

Check out my newer blog posts to see progress I've made on a concept for the AIY Voice Kit 2.0 embedded platform based on Dialogflow - a conversational interface for Google Cloud Developers.