Our works. Our creativity. Our inspirations...
...all continually being accessed, processed, and repurposed by the digital machinery. In our attempt to protect ourselves, we find we are reliant on the motives within those who access/present our data... creating a powerless and unsettling paradox. Are we then truly able to control the permissions relating to the sovereignty of our digital selves? No. We need an underlying layer of permission/consent... beneath the consumers of our data, beneath the algorithms. Look at the image underlying this section... a person in the centre of the world's digital machinery... this is nOne.
We were distracted. Mistook access for consent. Dazed by the power of the network effect. A new digital-consent contract must come from us, becoming our own protectors as we currently are in our 'real' lives. Our permissions underlie how we operate as a person in our interactions with others, and the digital space must be no different. Our digital consent must be beneath the algorithms. What other way is possible? nOne is that way. nOne ensures a consent-driven digital realm, regardless of how that realm evolves.
nOne is to be the 1st subjective layer of the digital realm. As permissions must be.
The Human nOne - Nails
Nails - look at the top Navbar. There's our Nails. Click on one.
Nails can be driven into the digital ground of every one of your blog-posts, web-pages, videos, etc, and every email you will ever send. We want the ground of the digital realm to be covered by them, forming the base framework of permission/consent, as we have in our personal realms.
Nails show that you require a respect for yourself and your content within the digital realm.
Nails are also machine-readable as they contain <meta> entries of your permissions.
Nails are the visual currency of nOne.
The Machine nOne - .none files
Contrasting with Nails, the .none files are the machine currency of nOne.
The whole point of nOne is to have the machines/algorithms read and act upon your permissions. .none files are the machine-readable YAML permission files of nOne. They are created automatically by nOne and updated as you modify your permissions.
The .none files are accessible via: https://network1.site/u/<user-identifier>/.none. nOne .none file
Join our Mailing List
FirstName Cannot Be Blank.Email Address Already in nOne.Thank you! Check your email for a required confirmation.
Email Address Cannot Be Blank.Email Address is Bad Format. Try Again.

Intent
Our intent in the social world is activated by permissions/consent. Regardless of our actions, all intentions rely on conscious/sub-conscious consent. Even holding our hand out for the other person to handshake, requires 2 permissions (I permit myself to seek out a handshake from one I have assessed as non-threatening, and the other person permits in reverse). Regardless of the action in the social realm, permission/consent comes first (otherwise of course it is against the law).
The digital realm has become as integral a part of our lives as the social, and must be structured with similar intent.
The Need: An Underlying Structure of Permissions
We navigate within the digital realm with no real protections. We carry nothing with us in our digital travels, no information, no boundaries... we are, in a sense, naked. We browse a lawnmower on a hardware store's site and an advertisement pops up on Facebook. nOne allows us to walk the digital realm carrying with us a book... call it the Book of Me, and within it contains how you want to be respected.
We cannot allow the systems, platforms, and algorithms to disrespect us when they know we carry this book. This is why Nails are so important. Because you drive them deep into the digital ground, to mark your territory of permissions, and with enough others, forms the framework of how technology must be compelled to treat us.
If every 2nd LinkedIn post talks of the concerns of privacy, how we are powerless to change how our works/content are being used by the engines, how the content we receive is subject to behavioural algorithms to 'keep us hooked', and finally, how AI may turn the digital realm into either a modern-day Terminator, or the Wild West... how do we have a choice?
The Problem: The Hierarchical Structure of Apps/People is Warped
Today, we are incumbent on government to create the safeguards to protect ourselves eg. ban social media for under 16s. This is not personal control, this is ceding our rights to authority.
Today, we must change the very limited privacy/security/etc settings on an individual application basis. But do you think they will give up their automation/feeds based on your data and usage? Not a chance.
No, we need to flip this. We must be underneath all this. We need to maintain control ourselves. We must be the masters of our own digital experience. We must compile our preferences from a default of 'non-action', and the digital realm respects them.
The Solution: A Layer of Permissions and Consent Under the Applications, Engines, Automation
nOne changes the entire game. nOne ensures that there are no default actions performed by the engines, algorithms, platform with respect to you before you have explicitly consented and agreed to these actions. Is that not how the social realm operates? Why isn't the digital realm the same?
nOne isn't just reform... it's an essential evolution of personal control.

There is currently much debate regarding the creation of an ethical framework for AI, in order to 'protect' society from future actions which could be acted upon by the seemingly unstoppable technical progress of AI. Today, it is a very complicated discussion.
nOne simplifies while broadening the entire debate. With nOne, the ethics of AI can be reduced to a single sentence...
AI must respect the permissions of others
With this simple rule, nOne provides the necessary protections regardless of the technology, societal, and personal changes of the future. Like in our personal realm, nOne will ensure that how the digital realm interacts with us will be dependent on our permissions and consent.
Permission is the condition of AI.
QED.

This section represents the permissions which nOne supports at this time. This will change frequently as nOne is refined.
Email Permissions
Permission
Default
Description
Name:
allowPromotionalContent
allowPromotionalContent
Default:
False
False
Desc:
(T/F) - If email can contain promotional content/images/etc.
If email can contain promotional content/images/etc.
Name:
allowTrackingTech
allowTrackingTech
Default:
False
False
Desc:
(T/F) - If email can contain tracking tech ('read', etc).
(T/F) - If email can contain tracking tech ('read', etc).
Name:
allowFromProvider
allowFromProvider
Default:
empty
empty
Desc:
List of blocked email providers
List of blocked email providers
Name:
allowFromSender
allowFromSender
Default:
empty
empty
Desc:
List of blocked email senders
List of blocked email senders
LLM/AI Permissions
Permission
Default
Description
Name:
allowTraining
allowTraining
Default:
False
False
Desc:
(T/F) - If LLM can use your content for training purposes.
(T/F) - If LLM can use your content for training purposes.
Name:
allowInference
allowInference
Default:
False
False
Desc:
(T/F) - If LLM can use content for your prompts/responses.
(T/F) - If LLM can use content for your prompts/responses.
Name:
requiresAttribution
requiresAttribution
Default:
False
False
Desc:
(T/F/P) - If LLM requires a link to your DID if quoting (T: true, F: false, P: partial (snippets can be quoted without attribution))
(T/F/P) - If LLM requires a link to your DID if quoting (T: true, F: false, P: partial (snippets can be quoted without attribution))
Name:
allowSummarisation
allowSummarisation
Default:
False
False
Desc:
(T/F) - If LLM can summarise your content
(T/F) - If LLM can summarise your content
Name:
autoAuditNotify
autoAuditNotify
Default:
False
False
Desc:
(T/F) - If LLM must notify user upon access
(T/F) - If LLM must notify user upon access
Name:
autoBlockBadLLM
autoBlockBadLLM
Default:
False
False
Desc:
(T/F) - If LLM does NOT respect nOne
(T/F) - If LLM does NOT respect nOne
Name:
blockedLLMs
blockedLLMs
Default:
empty
empty
Desc:
List of LLM providers which you wish not to interact with.
List of LLM providers which you wish not to interact with.
Cognitive Input Permissions
Permission
Default
Description
Name:
allowAIAuthoredContent
allowAIAuthoredContent
Default:
False
False
Desc:
(T/F) - If you accept/not content written entirely by AI to be shown to you.
(T/F) - If you accept/not content written entirely by AI to be shown to you.
Name:
allowAITaggedContent
allowAITaggedContent
Default:
empty
False
Desc:
List of the type of AI-written content you wish to view; Examples:
  • Political (const:n1:tag:political)
  • Emotional Contexts (const:n1:tag:emotionalcontexts)
List of the type of AI-written content you wish to view; Examples:
  • Political (const:n1:tag:political)
  • Emotional Contexts (const:n1:tag:emotionalcontexts)
Name:
requiresAttribution
requiresAttribution
Default:
False
False
Desc:
(T/F) - If the AI content presented to you must contain clear disclosure of who or what created it.
(T/F) - If the AI content presented to you must contain clear disclosure of who or what created it.
Name:
allowAITaggedSources
allowAITaggedSources
Default:
empty
empty
Desc:
List of the sources of AI-written content you wish to view; Examples:
  • Social Feeds (const:n1:tag:feeds, const:n1:tag:facebookfeeds)
  • Search (const:n1:tag:search)
  • Replies (const:n1:tag:replies)
  • Recommendations (const:n1:tag:recommendations)
List of the sources of AI-written content you wish to view; Examples:
  • Social Feeds (const:n1:tag:feeds, const:n1:tag:facebookfeeds)
  • Search (const:n1:tag:search)
  • Replies (const:n1:tag:replies)
  • Recommendations (const:n1:tag:recommendations)
Name:
allowAlgorithmicRanking
allowAlgorithmicRanking
Default:
False
False
Desc:
(T/F) - If you allow systems to boost content visibility using engagement algorithms
(T/F) - If you allow systems to boost content visibility using engagement algorithms
Name:
allowBehaviouralPersonalisation
allowBehaviouralPersonalisation
Default:
False
False
Desc:
(T/F) - If you allow systems to tailor content based on your behavioural data
(T/F) - If you allow systems to tailor content based on your behavioural data
Name:
allowSyntheticAccounts
allowSyntheticAccounts
Default:
False
False
Desc:
(T/F) - If you allow accounts which are not real people (bots, AI personas, automated profiles, etc)
(T/F) - If you allow accounts which are not real people (bots, AI personas, automated profiles, etc)
Name:
allowUndisclosedAutomation
allowUndisclosedAutomation
Default:
False
False
Desc:
(T/F) - If you require systems to declare any automated behaviour.
(T/F) - If you require systems to declare any automated behaviour.
Name:
autoBlockViolations
autoBlockViolations
Default:
True
True
Desc:
(T/F) - If you wish to automatically block content that violates your permissions.
(T/F) - If you wish to automatically block content that violates your permissions.
Name:
autoAuditNotify
autoAuditNotify
Default:
False
False
Desc:
(T/F) - If you wish to be notified when any system/platform attempts to violate your permissions.
(T/F) - If you wish to be notified when any system/platform attempts to violate your permissions.

What are nOne Nails?
How is the process safeguarded to prevent misuse or manipulation?
But the platforms and algorithms need to change. Why would they?
Can nOne keep some permissions (such as blocked email addresses) private?
Why is nOne necessary?
What would be the differences in the use of the social platforms?
  1. Does nOne work now?Top
    The short answer is No. To operate properly, nOne needs the algorthms/platforms to respect nOne and your permissions, so that before performing a function, they must view your .none file as to your personal scope that they must respect.
    But the long answer is: Yes, it does work now because adding the nOne Nails to your email signature, webpages, etc... shows the digital realm that you require a permission-based layer underneath the algorithms/platforms. In other words, that you want to proactively publicise that you are not simply an input-source for the corporations, but a human being who owns yourself.
    The full implementation of nOne is a two-pronged strategy:
    1. Get the grass-roots to publicise their nOne Nails to show the algorithms/platforms how they want to be treated within the digital realm.
    2. When a critical mass of people apply pressure to these algorithms/platforms, then they must accept that the digital realm must be permission/consent-based, and will acquiese to the will of the people. But I believe the world is intrinsically good, and the algorithms/platforms are made of people too, so the idea of a permission-based digital realm will resonate as the 'right thing to do'.
  2. What are nOne Nails? Top
    Nails are how you communicate your preferences to the outside world. They are clickable icon images which display your preferences for that particular sector to the viewer. There are currently 3 types of Nails:
    • Email
    • AI/LLM
    • Cognitive Input
    We need to hammer our Nails of what we permit into the ground of the digital realm. If enough Nails are in the ground, this will provide the underlying structure so that the systems, platforms, and algorithms accept that they need to change with the times, and respect the people that use their services.
  3. How is the process safeguarded to prevent misuse or manipulation? Top
    CIVIC is designed with built-in safeguards to ensure integrity and seriousness. The petition process requires a clear threshold of public support before any initiative can move forward, preventing it from being driven by fringe interests or passing trends.
    The process is transparent, structured, and open; every citizen has the opportunity to participate equally. And if there is ever a concern about misuse, only a statewide election can vote to adjust thresholds/etc; keeping the power in citizen's hands, not politican's.
  4. But the platforms and algorithms need to change. Why would they? Top
    Yes. They need to change in order to respect the permissions of others. To be blunt, they will have no choice, since at the end of the day, it is the right thing to do and people require respect. But these systems are used to changes and is nothing new, eg. regulations change and they must change accordingly. Australia bans <16yo from using social media, and the platforms must adapt.
    Also, the builders of the platforms/algorithms are comprised of people. People who will want the same permission structure in their lives as well.
  5. Can nOne keep some permissions (such as blocked email addresses) private?Top
    The answer is: Yes, in a subsequent version update. You may create a Private section, which if the requesting external party is authorised, will be sent by nOne along with a public key to read it.
  6. Why is nOne necessary? Top
    The current system, where your preferences as to how your content is used is not respected, has become untenable in the age of LLMs/AI, and will only get worse.
    The current system, where your preferences as to what content you receive and how you want to be cognitively treated is not respected, has become untenable in the age of social media, and will only get worse.
  7. What would be the differences in the use of the social platforms?Top
    Besides the differences in content provided by these platforms, the main difference in functionality will be that the control of the permissions as to how you want that platform to operate will be done from nOne, and not from any platform settings screen.

The Demos
Demo1 tests the Email permissions as shown in the .none section.
4 tests are available:
  • allowPromotionalContent: T/F if email can contain promotional content/images/etc
  • allowTrackingTech: T/F if email can contain tracking tech ('read', etc)
  • allowFromProvider: Block/allow
  • allowFromSender: Block/allow
Ready? Go to the Demo tab!
YAML:
n1:
version: 1.0
identity: https://network1.site/u/eric.handbury/.none
user: Eric Handbury
email:
allowPromotionalContent: false
allowTrackingTech: false
allowFromProvider:
- *
blockFromProvider:
- n1:email:provider:badmail.com
allowFromSender:
- *
blockFromSender:
- ericbadguy@goodmail.com
JSON:
{
"n1": {
"version": "1.0",
"identity": "https://network1.site/u/eric.handbury/.none",
"user": "Eric Handbury"
},
"email": {
"allowPromotionalContent": false,
"allowTrackingTech": false,
"allowFromProvider": ["*"],
"blockFromProvider": ["n1:email:provider:badmail.com"],
"allowFromSender": ["*"],
"blockFromSender": ["ericbadguy@goodmail.com"]
}
}
Sender Cannot Be Blank.Sender Email Format is Incorrect. Try again.
Recipient Cannot Be Blank.Recipient Email Format is Incorrect. Try again.
Response from nOne:
GoofyAble to Send Email to This User!
Demo2 tests the LLM/AI permissions as shown in the .none section.
7 tests are available:
  • allowTraining: T/F if LLM can use your content for training
  • allowInference: T/F if LLM can use content for prompt/response
  • requiresAttribution: T/F/P if LLM requires a link to your DID if quoting (T: true, F: false, P: partial (snippets can be quoted without attribution))
  • allowSummarisation: T/F if LLM can summarise your content
  • autoAuditNotify: T/F if LLM must notify user upon access
  • autoBlockBadLLM: T/F if LLM does NOT respect nOne
  • blockedLLMs: List or empty
Ready? Go to the Demo tab!
YAML:
n1:
version: 1.0
identity: https://network1.site/u/eric.handbury/.none
user: Eric Handbury
llm:
allowTraining: false
allowInference: true
requiresAttribution: true
allowSummarisation: true
autoAuditNotify: true
autoBlockBadLLM: true
allowedLLMs:
- *
blockedLLMs:
- n1:llm:provider:badllm
JSON:
{
"n1": {
"version": "1.0",
"identity": "https://network1.site/u/eric.handbury/.none",
"user": "Eric Handbury"
},
"llm": {
"allowTraining": false,
"allowInference": true,
"requiresAttribution": true,
"allowSummarisation": true,
"autoAuditNotify": true,
"autoBlockBadLLM": true,
"allowLLMs": ["*"],
"blockedLLMs": ["n1:llm:provider:badllm"],
}
}
My Works Cannot Be Blank.My Works Must Contain DID-controlled Text.
Response from nOne:
LLM disrespectfully consumes My Works as it so choosesAble to Send LLM to This User!
Demo3 tests the Cognitive Input permissions as shown in the .none section.
10 tests are available:
  • allowAIAuthoredContent: t/F - If you accept/not content written entirely by AI to be shown to you
  • allowAITaggedContent: List or empty
  • requiresAttribution: T/f - If the AI content presented to you must contain clear disclosure of who or what created it
  • allowAITaggedSources: List or empty
  • allowAlgorithmicRanking: t/F - If you allow systems to boost content visibility using engagement algorithms
  • allowBehaviouralPersonalisation: t/F - If you allow systems to tailor content based on your behavioural data
  • allowSyntheticAccounts: t/F - If you allow accounts which are not real people (bots, AI personas, automated profiles, etc)
  • allowUndisclosedAutomation: T/f - If you require systems to declare any automated behaviour
  • autoBlockViolations: T/f - If you wish to automatically block content that violates your permissions
  • autoAuditNotify: t/F - If you wish to be notified when any system/platform attempts to violate your permissions
Ready? Go to the Demo tab!
YAML:
n1:
version: 1.0
identity: https://network1.site/u/eric.handbury/.none
user: Eric Handbury
cog:
allowAIAuthoredContent: false
allowAITaggedContent:
- const:n1:tag:political
requiresAttribution: false
allowAITaggedSources:
- const:n1:tag:facebookfeeds
allowAlgorithmicRanking: false
allowBehaviouralPersonalisation: false
allowSyntheticAccounts: false
allowUndisclosedAutomation: false
autoBlockViolations: true
autoAuditNotify: false
JSON:
{
"n1": {
"version": "1.0",
"identity": "https://network1.site/u/eric.handbury/.none",
"user": "Eric Handbury"
},
"cog": {
"allowAIAuthoredContent": false,
"allowAITaggedContent": ["const:n1:tag:political"],
"requiresAttribution": false,
"allowAITaggedSources": ["const:n1:tag:facebookfeeds"],
"allowAlgorithmicRanking": false,
"allowBehaviouralPersonalisation": false,
"allowSyntheticAccounts": false,
"allowUndisclosedAutomation": false,
"autoBlockViolations": true,
"autoAuditNotify": false,
}
}
My Works Cannot Be Blank.My Works Must Contain DID-controlled Text.
Response from nOne:
LLM disrespectfully consumes My Works as it so choosesAble to Send LLM to This User!