[Ducky Software Research] Introducing NotPerfect-Sans (Developer Implementation Guide)

1a. Introduction:

Hi there,

Several months ago Ducky Software announced we were devloping a new research project. It launched yesterday and we created this blog post to provide more information about NotPerfect-Sans and the processes needed to apply for the beta so you can start using NotPerfect-Sans in your project. If you'd like to learn more about NotPerfect-Sans you can visit: this page and learn more. This page is for developers or brands who would like to apply. This document may at some points be technically complex however we have tried our best to make it more understandable and we hope you find it useful.

Let's get started

1b. Application Process Begins (Developers please read pre-application):

Before applying to use the beta of NotPerfect-Sans we kindly ask you read this section.

In this process of submitting an application the company or developer in question must be able to prove to ducky.software that they are operating there service in good faith and have proven they will continue to further operate in a responsible way and for a long period of time.

Let’s talk a bit more about what qualifies as “operating in good faith” in our eyes, for us this means:

• No excessive or unnecessary data collection (beyond what is needed to operate your service)

• Providing a high quality service

• Operating without predatory practices including but limited to: predatory contracts, racism, ableism, sexism, homophobia etc.

• A commitment to operate with fair pay and dignity to all

• A commitment to adequately credit all parties who have done work on the product(s) in a way that is accessible from the application it self

We feel these operating procedures are a more than fair assumption

2a. Crediting Expectations

Ducky Software expects to be fairly credited for the use of our projects and research, let’s talk more about this means for us.

• At least a line crediting “ducky.software” for “Use of NotPerfect-Sans font for OCR/Writing and Literacy”

• Ideally and if possible provide a link to the project

2b. Prove of commitment and active development:

We also require proof of commitment and active project development i.e. a submission to a major App Store. If the project is failing or is deprecated at some point in the future that is fine, we simply need prove of active development at the time of application.

2c. Healthy Software Development Practises

Your software may not be made with poor intent this including for the purposes of:

• To harvest Personally Indefinable Information in a dishonest way

• To contain malicious information, code or other forms of content

• To harvest credentials or information to that affect for a malicious purpose or activity

• To be created with the intent of collecting information for an enterprise or entity

• To be used by governments for illegal purposes or activities or to provide or facilitate a service for the purposes of the government

3. Protection of PII

You must be able to comply with local and federal laws for personal data protection in North America (US, CA, MX) or be able to proof you are going to attempt to meet these protections and documentations.

That’s it! Interested? Apply to join the beta: team@ducky.software