@inside_human![SAY handle="inside_human" side="left"] ![GREETING]. This is the person inside. This page serves as not/on's read.me, summarizing its concepts and other details. ![/SAY]
This app, not/on, is an article posting/sharing service that aims to achieve both ease of writing and overwhelming freedom of expression.
Whether you just want to write casually, or if you are knowledgeable and want to use Markdown, you can post while checking the public preview as you write.
Here is a summary of the concepts and what you can do.
Concepts
Write, and connect
- Reactions connect by writing
- Therefore, there are no ❤ or 👍. Towards a chain of deeper connections rather than easy rewards
- Articles cannot be deleted once published; if you want to withdraw them, you overwrite them
NOT DONE , ALWAYS ON
- It doesn't end; articles are self-running
- You can publish apps on Vercel and embed them in your articles
- With unique reserved words, you can embed self-running texts that adapt to the weather and time
- You can embed self-running tables linked with Noton (coming soon)
SECURE FIRST / FALE SAFE
- We do not give up convenience, but remain secure
- We do not exclude affiliate links, but assign a PR tag if detected
- Vulnerabilities are verified using the trending Claude Fable5
What you can do
- Expressive text formatting such as headings, lists, and quotes
- Tabular expressions
- Seamless embedding of apps (apps published on YouTube or Vercel) into articles
- Texts that change depending on time, location, and weather, such as greetings
- Other features will be added in the future
React to and praise other articles
Pasting a not/on article URL creates a "connection"
This becomes a reaction to the original article
(No matter how hard you look, you won't find a comment feature or reaction buttons)
Articles with many connections and frequent updates are praised
The platform considers articles with many "connections" (references) as "excellent articles" and displays them preferentially.
Furthermore, not/on does not have an article deletion feature. Instead of not being able to withdraw them, updates are free. The platform considers an article to be more "plausible" the more times it is updated, and displays it preferentially.
Operation of not/on
not/on is a completely non-profit service, and we have no plans to monetize it in the future.
The operation is handled by an organization called youside.me, and not/on is one of the digital commons implementations initiated by this youside.me.
Please refer to the official statement below regarding the organization youside.me and its philosophy.
Philosophy of not/on
not/on and youside.me, which supports it, are connected to the theory of ANTI FRAME (Anti-Frame) and value the knowledge and frameworks in its peripheral areas. For more details, please refer to the article below.
We use grand words like philosophy, but we hope you understand that it is all part of "play".
We will continue to reframe with free ideas, without being overly bound by established frameworks or common sense, in order to enhance the value of the play experience.
Security of not/on
not/on is a service that values the agility of being able to publish an article immediately after writing it. However, "agility" and "safety" are two different things. At not/on, we consider security to be the first and foremost requirement before launching the service.
In this chapter, we will introduce some of the security initiatives at not/on.
Claude Fable5 Ready
not/on incorporates a security (sanitization) engine designed by Claude Fable5.
For details, we have summarized them in the article below, so please refer to it.
anti-stack
Based on a zero-trust policy, not/on does not use libraries provided by external organizations that cannot be fully controlled (even if they are OSS and industry standards).
We can oversee and control all the code ourselves.
By basing our work on a simple, full-scratch implementation environment with as few dependencies as possible, we are also taking measures against supply chain risks.
Authentication
When actually posting an article on not/on, account authentication is required.
Currently, we ask you to prepare a Google account and log in using that account1.
As for the method, we achieve single sign-on (SSO) with Google using JWT with the OIDC protocol. By entrusting the identification and authentication of accounts, as well as the management of personal information attributes, to a major company like Google, we ensure the safety of the service.
By utilizing this method, not/on is able to identify the account (handle) using the service without holding originally unnecessary user personal information2.
The arrow of zero trust is also directed at ourselves. In preparation for any unlikely event, not having personal information such as PII in the first place is the best security measure for us.
Other
The Person Inside
Let us introduce the account of the person inside (youside.me staff) operating not/on.
Starting with this article, we will mainly share update information for not/on.
Please see here for details 💁
not/on Service Changelog
not/on is primarily updated on weekends when Claude's credit consumption is cheaper. The article below is sequentially updated regarding the changes.
Trackbacks (Connections) for this article
![RELATED_FEED]
- You can continue to enjoy referencing (just viewing) published articles without logging in. Furthermore, we are considering adding more authentication providers in the future. ↩
- The authentication feature uses AWS Cognito, and during service authentication, we request the provision of an email address and name information from the SSO authentication provider. This information is handled as the initial value for the authentication process and profile settings screen, but this value is never saved by the service. ↩