Skip to main content

Help Protect Child Information Privacy by helping Phora Group become a Chase Mission Main Street Grant Recipient!

As advocates of child privacy, we ask everyone in the ICS community to help us.  We are applying for 2015 Chase Mission Main Street grant and we need your vote.  As many of your know, our iPhora Touch technology is based on XWork /Domino and we would like to bring this technology to K-8 schools and ensure that students and teacher information is not be recorded and create iPhora Touch for Education.
 
Please read below the description on what we are doing.  Unfortunately, you need a Facebook account in order to vote, but every vote counts.  Let's help protect our kids privacy.
 
There are many cloud-based social collaboration products that offer free services to schools for teachers and students to use in their classrooms. The age-old adage "nothing is free" really does apply in this situation. Many of these "free" services come at the cost of privacy. Information that is shared and exchanged between students and teachers is collected and aggregated for corporations’ marketing use.. As advocates of child privacy, we want to provide schools with an alternative solution, one that keeps our students’ and teachers’ information private. We plan to utilize our iPhora Touch technology to create a K-8 collaboration system so that schools have a private and secure social platform in which teachers, students and their families can exchange and share information without being tracked and analyzed for marketing information. We plan to work with local elementary schools in our area and, with help from foundations, create and provide this platform to schools at no charge. We would like to use half the Chase Mission Main Street Grant towards developing this version of iPhora Touch: iPhora Touch for Education. So please help us make this become reality and vote for Phora Group.

go to: https://www.missionmainstreetgrants.com/b/67177

Comments

Popular posts from this blog

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a

The iPhora Journey - Part 4 - JSON is King - The How

  The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document.  However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo