One of the programming languages we use at iCog Labs is MeTTa

let me share u about it ☺️

What is MeTTa?

MeTTa is an experimental open-source programming language developed by SingularityNET for Artificial General Intelligence (AGI). It is designed to represent knowledge, perform logical reasoning, and build intelligent systems that can learn and adapt.

Why MeTTa?

Combines symbolic reasoning with AI.
Supports knowledge representation and inference.
Enables self-modifying and adaptive programs.
Flexible and expressive for building AI agents.
Designed specifically for AGI research and development.

How MeTTa Thinks Differently

In traditional programming languages like Python, we usually store data and then write code that knows how to use that data. Knowledge and logic are separate.

For example, to represent that Socrates is a human, we might write:

Python

facts = {
    "Socrates": "Human"
}

print(facts["Socrates"])  # Human

Or using classes:

class Human:
    pass

socrates = Human()

In MeTTa, you don't think in terms of variables, dictionaries, or classes. You simply state the knowledge itself.

MeTTa

(Human Socrates)

That's it.

The expression directly represents the fact "Socrates is a Human." There is no dictionary to look up or class to instantiate. MeTTa treats knowledge as relationships and facts, making it much more natural for reasoning and AI systems.

MeTTa at first might look confusing but trust me you'll get used to it

and there are AI agents like Omegaclaw mostly developed using MeTTa

How is ur night fam ❤️

Btw EthioLink is down 😭

Coz of this railway only on month free tier 😤

So I just bought credit on GCP(Google cloud provider) 💪 and im gonna host my projects there.

I will let u know how it goes. good bye free tier😘

Monday again

Have a wonderful week ❤️

Now Ethiolink is up and working again as I told you I used GCP to deploy it 💪

How i did it?

EthioLink have to things one a server to accept http requests from users for profile customization and a worker always listens for jobs in different places

So I separated them into two components

1,Deployed on Cloud Run. Handles user interactions with the bot subscription checks, category/job-type/experience preferences, all saved to the DB. Fully serverless, scales automatically, webhook connected directly to Telegram.

2,Runs on a dedicated Compute Engine VM as a persistent background daemon (managed by systemd, so it auto-restarts and survives reboots). Listens across many source channels, rewrites , posts to the main channel, and DMs matched subscribers based on saved preferences.

Infra
Single Docker image, pushed to Artifact Registry, run two different ways for the two components. Same setup will host future projects too.

Wtf it is 4 AM already 😴

Nothing beats the feeling of watching your project live and annoying ☺️

Why the team im supporting lose this wc 😭

France was playing like they never seen a ball before 😡

So today the long waited debate will be settle down right? 😃

Saka or Messi

See u on Sunday

England is shit 🤬

Good night

Sleep tight 😴

Claude: “this project will probably take 3 months to complete”

Me: