Skip to content
Türkçe

(Protokol Taslağı)

Protocol Draft

One of the sub-projects of Memoristik is to develop a protocol that enables access to databases from anywhere.

It is crucial to allow users to filter their data by creating schemas.

Let's illustrate with an example,

Using the "theMe" system, any individual or organization can enter their public and partially private data.

(For now, let's use the example of a Company/Organization to diversify examples with more data.)

Here, we can initially use a predefined schema, and let our sample schema be as follows:

{Source:Schema Name:Username:KYC:Contact:Logo/Avatar}

One of the important parts here is the "Source" name. Since the project's goal is not to centralize, anyone can create different sources in similar structures. Users can use multiple sources to access data.

(An issue that needs to be decided and clarified by developer communities is how the "Username" might be. It could be a solution similar to the email system, like "username@source," or it could be directly "username". While the second option provides convenience for end-users, preventing conflicts would require serious effort. In such a case, all source servers must synchronize "Usernames" among themselves.)

After entering data into our schema, in an environment where any user can access these databases using the "gel" infrastructure, when they type {@username}, communication will be established with the person who has that username.

Let's explain this with a few examples.

When we create an identity for "flipboard," it will appear on the predefined schema somewhat like this:

{Memoristik:predefined identity:flipboard:(KYC approved by flipboard)KYC:flipboard/predefined:flipboard}

When we enter KYC, Contact, and Logo data, thanks to communications between schemas, pulled data will reach end-users, and the "Full Name, Contact Information, and Logo" of "flipboard" will be visible.

In any form, for example, written on social media like this,

Sample 1

It will be seen by users using the predefined schema like this,

Sample 2

All information added to the database can be quickly accessed via links generated in the outputs.

For example, accessing a website can be done with a usage like {@flipboard/web}, sending an email with {@flipboard/email}, or accessing chat environments with {@flipboard/chat}, if created by the username holder.

Schemas can also be distributed across sources. For instance, default information can be stored in one source while contact details are kept in another, or custom schemas can be created and left to the users' preference.

User tracking will also be as per their specified preferences.

For example, any user can do the following:

Show the Logo and add a link to the Web address where {@username} is mentioned, other information can remain in the background, I can access it if needed.

Also, when clients using the project infrastructure are employed, only necessary data is extracted from individuals. For example, an email software can access {@username/email/encryption key} data and use them to send emails.

Meanwhile, individuals tagged in any environment can receive notifications or restrict the notifications they want to receive, they can add queries similar to these:

Query Examples

Only receive notifications from:

  • Authors using sources I find reliable,
  • Real persons with KYC approval,
  • Those I'm following,
  • etc.