A list of open sourced backend repositories which integrate into The All Seeing Eye (and it's API)

This was inspired by the following events

• The choice that was made integrate RoCleaner's userlist into TASE's API.
• The plan to switching to an alternative human-reviewal system.
• The presence of banlists, such as RCR and RoLock
• The presence of condo providers who have been found in data breaches.

Table Of Contents

Anything past Index 2 should be useful for developers or people wanting to check out the source.

Index	Section	Description
1	Table Of Contents	All sections of the README guide.
2	Information	Information of how ExAPI will be used on TASE
3	Bases	Templates for ExAPI "extensions"
4	Extensions	Provider implementations built from the bases

Information

Reliability Grading

Reliability grades is a minimal feature of ExAPI that can indicate to a user how reliable a source (or it's owner) is.

Grades are usually formatted in {XX} on the frontend, but can also be formatted as single letter to indicate only the source.

APIs can filter scan results found in ExAPI by reliability grades if needed.

S Grades

S grades are only able to be applied as a one letter grade and cannot be applied in TASE ExAPI definitions.

This grade means that the source's information was made by TASE. Sources with an S rank also require flagged users to have certain knowledge knowledge that they are participating in sexual activities.

Conversion endpoints under this ranking must also use one of the following:

• A method of verification that is considered concrete evidence (such as OAuth or another method of verification where the server knows it can accurately link a user between accounts)
• Manual user linking so long the user admits or has undeniable proof of being linked to that account.

Owner Reliability

An owner's reliability grade is based on their history of behavioral standards and actions.

Source Reliability

The source's reliability grade is based on how accurate it is to verify a user is in the database or how accurate it's results are.

Appeals

Appeals by default will be handled by The All Seeing Eye, but the provider can override this by a value provided in their API, so long one of the following is true about the provider and/or it's bans:

• Has valid reasoning to mark the flags as unappealable.
• The provider has an appeal outlet.

Privacy

Lists that originate from data breaches or any other sources made to grab information (otherwise known as an archive) are only allowed to give the following information:

• Username Handles
• Provided

Bans

TASE official bots should only be authorized to take action against if the following is true:

• The source is officially vetted by TASE API Maintainers.
• The user is marked moderate or unsafe.
• The server owner allows for this action to happen.

For services not officially recognized as official, you should follow a ruleset like this too.

Bases

Name	Language	Customizability Level
Elysia	Typescript	Very Easy

Extensions

Tags

Emoji	Definition
✅	Officialy verified/vetted by TGP
🔓	API is publically usable

Private APIs can only be requested by The All Seeing Eye and it's API.

Repositories

ID	Name	Base	Tags
ferns	Ferns Databreach	Elysia	🔓 ✅