Meeting

7 min. for each company to answer the following, plus 3 min. each for Q&A

1. Each company’s primary aim. I.E.: Why you do what you do.
2. Each company’s vision / calling. How and what.
3. Markets or area of influence where we move. Who.

Clarifying questions on the 13 possibilities in the appendix?

Discuss any possibilities that seem viable, with the following guiding questions:

What are your company’s needs (gaps in technology, threats/hurdles)?

What are your company’s strengths that could be shared?

Next steps on collaboration possibilities?

Next meeting?

We can each indicate an interest level for each possibility—Yes, Maybe, or No

1. Producing a custom version of Android that facilitates monitoring and filtering.
2. Producing a common desktop and/or mobile browser friendly to monitoring and filtering.
3. Sharing blacklists, whitelists, or other categorization databases or tools if agreement can be reached on terms of use.
4. Combining already existing products into products that are even more comprehensive. For example, a person could use an ADAMnetworks router, Pluckeye for filtering, and Covenant Eyes for accountability on their main computer.
5. Creating standards so tools can interconnect more easily. For example, a common filtering language other than ABP (which was created for ads) might be useful in a variety of cross-product scenarios.
6. Sharing a common and reusable anti-tampering solution for desktop or mobile platforms.
7. Creating a suite of tests that measures filter and monitor quality. Such a tool would be useful to developers, and perhaps also to users looking for filters with a certain “severity.”
8. Lending technical expertise to reduce the overall workload (specializing rather than duplicating work). Major areas include the mobile platforms, various desktops, and browsers.
9. Creating a comprehensive, company-neutral website to advise people (especially Christians!) on technology options and recommendations for diverse audiences, not just parents. See http://filters.pluckeye.net/ as a beginning attempt at such a site.
10. Working with the National Center on Sexual Exploitation (or another coalition) to speak to Apple, Google, Microsoft, and Mozilla about the problems that their architectural limitations create for filters and people who want to use them.
11. Advising the Church so Christians can have a voice in shaping technical platforms.
12. Sharing news of interest in the technical landscape with each other. For example, we could create a chat channel, a mailing list, or a similar resource for sharing news relating to changes in platforms and networking protocols.
13. Praying together periodically (perhaps once a month or once a quarter) in order to demonstrate a fundamental commitment to unity and to the Body of Christ.