🌐 Wikis

• Read More About Crypto ID

• Read More About Push Notification Strategy

• Read More About Rust Ownership and Borrowing Rules

• Read More About AES256 CBC

• My playground

📚 blogs and books:

• https://rust-unofficial.github.io/patterns/

• https://github.com/steadylearner/Rust-Full-Stack/

• https://book.avr-rust.com/001-introduction.html

• https://nnethercote.github.io/perf-book/title-page.html

• https://rust-lang-nursery.github.io/rust-cookbook/intro.html

• https://smallcultfollowing.com/babysteps/

• https://lucumr.pocoo.org/

• https://www.lpalmieri.com/

• https://blog.yoshuawuyts.com/

• https://www.i-programmer.info/programming/theory.html

• https://www.i-programmer.info/babbages-bag/

• https://without.boats/blog/

📡 networking

🛠️ tools:

• tokio
• impl riker actor for each socket connection
• libp2p pub/sub stack based on tokio tcp and udp with borsh and serde
• zmq pub/sub socket for async I/O event streaming like audio and video
• rpc capnp
• hyper
• juniper gql

🎭 actor concepts:

libp2p stacks can be built on top of the ZMQ pubsub sockets over TCP or UDP which supports various socket protocols for streaming borsh or serde encoded data also each socket in ZMQ is an actor like riker in which:

• is a message passing concurrency model that avoids deadlocks and low level data races.
• the message queue of each actor is a tokio job queue channel to share Arc<Mutex<Data>> + Send + Sync + 'static between different parts of the app in multithreading contexts like solving the received async task inside the mailbox from other actors in tokio worker green threadpool.
• each actor can communicate with each other through pubsub message passing protocol in which the publisher actor can publish or broadcast a message with a specific topic and a message then an interested subscriber can subscribe to that topic and get the message to put in inside its mailbox to solve it by sharing it using tokio job queue channel inside its threadpool.
• with actor system we can schedule a task using tokio cron scheduler to be executed at a specific time inside a specific actor and from there the actor can do the rest by popping out the task from its message queue channel to solve it inside its threadpool.
• there is an event loop and a threadpool inside each actor in which it execute an async I/O task from the loop using tokio::select!{} once it gets solved by the flow of the code inside its threadpool which can be the tokio::spawn().
• actors on two different devices can call directly each other method using RPC pubsub pattern based on capnp protocol.

💡 concepts:

• distributed (replication and sharding) and decentralized concepts:
  • create best objective function to find the most rewarded (less cost actions) path in the network graph env (route planning) greedily using:
    • hybrid tech algorithms like NN, GA 🧬 and neurofuzzy(ANFIS)
    • gradient optimization methods like stochastic gradient descent
    • none gradient optimization methods like GA and FA
    • graph theory and heuristic search algorithms like DAG, dijkstras, floyd, bellman, DFS, BFS and A*
    • reinforcement learning algorithms like qlearning using mdp and bellman equation with off and on policy methods based on markov decision process and markov chain
    • other algorithms using greedy, dynamic programming, backtracking, divide and conquer, recursive and brute forcing methods
    • hashmap based algos like hash tables (DHT) to find closest peers to a specific range of key inside a replication like cassandra db and p2p nodes
  • search, db and routing engines like elastic, cassandra and p2p kademlia:
    • rpc capnp for actor method based communication on two different machines like calling between smart contract actors
    • tokio tcp and udp and jobq channels for sharing Arc<Mutex>: Send + Sync + 'static between actor threads in a same machine
    • actor tokio worker green threadpool and message queue for task and method broadcasting and scheduling to the pub/sub channels (tokio jobq, socket or rpc)
    • pub/sub and other zmq socket actors to broadcast from publishers to subscribers (m2m) using sockets
    • in libp2p peers can find each other using either mDNS (over LAN) or kademlia (over WAN)
    • in libp2p peers can communicate with each other based on pub/sub floodsub or gossipsub protocols on top of rpc capnp, tokio udp and tcp, websocket, webrtc, zmq like sockets (req/res, cli/srv or pub/sub) actors
• proxy, firewall, vpns, packet sniffer and load balancer like pingora, HAproxy, v2ray and wireshark for all layers concepts:
  • v2ray and tor protocols
  • decompress encoded packet
  • cpu task scheduling,
  • weighted round robin dns,
  • vector clock,
  • event loop
  • iptables
  • zmq pub/sub
  • simd divide and conquer based vectorization

🏗️ system

💡 concepts:

• compiler, vm using llvm and os
• streaming of async I/O events compression and ram (buffer) algos like deflate, lz4 and snappy
• data serialization codec and protocols like borsh, bson, serde, capnp and gql
• runtime
• video and audio codec, compressor and streamer like ffmpeg
• cryptography
• bridge between blockchains
• language binding like writing rust libraries insie lib.rs:
  • on top of apis of the compiled (.so) code in c like rust bindings to libsodium or coding c like syntax using extern, unsafe and mangle proc macro attribute to generate c shared objects, headers and libraries to load in other c based langs like swift iOS
  • to compile to .wasm and .so like NEAR and solana contracts

🤖 AI

💡 SSL (Self Supervised Learning) concepts:

• health improvement based on a pattern mining approach and semantic attributes like
  • predicting missing part of the unseen input based on the exact style of the input
  • reconstructing and labeling the unseen input based on the exact style of the input
• feature or representation learning and extracting from the data itself
• feature or representation selection using dimensionality reduction algorithms like GA, TSNE, PCA & VAE
• extracting semantic attributes from the input for 0/1/few/n-shot learning
• autoregressive based sequence modeling to predict the future based on past events and behaviors
• anomaly detection, 0/1/few/n-shot and meta learning
• solving catastrophic forgetting problem using MemTransformer instead of MANN with NTM architecture LSTM based
• FF algorithm as an alternative to gradient descent

🛠️ models and tools

• Transformers (https://arxiv.org/abs/2101.12037)
• SEER (https://arxiv.org/pdf/2103.01988)
• VAE & GAN
• BART (https://arxiv.org/pdf/1910.13461)
• VISSL (https://vissl.readthedocs.io/en/v0.1.5/)
• GNN (Graph Neural Network)
• MemTransformer (https://arxiv.org/pdf/2006.11527.pdf)
• Decision Transformer (https://arxiv.org/pdf/2106.01345v1.pdf)
• TransZero (https://arxiv.org/abs/2112.08643)
• DALLE-2 (https://arxiv.org/abs/2204.06125)
• CLIP (https://arxiv.org/abs/2103.00020)
• DayDreamer (https://arxiv.org/abs/2206.14176)
• Algorithm Distillation (https://arxiv.org/abs/2210.14215)
• You Only Live Once (https://arxiv.org/abs/2210.08863)
• Forward-Forward Algorithm (https://www.cs.toronto.edu/~hinton/FFA13.pdf)

💡 NLP concepts:

• 🛠️ preprocessing
  • tokenization
  • Lexicon Normalization(stemming & lemmatization)
  • lowercasing
  • stopwwords removal
  • padding
• 📄 vocabulary building, word embedding, vectorization, feature extraction and semantic analysis
  • BOW(ngram based with TF-IDF normalization)
  • Word2Vec(skip-gram & CBOW based)
  • GloVe
  • GPT
  • BERT
  • BART
• 📈 models and statistical results
  • ML models like SVM, Naive Bayesian, Random Forest and Logistic Regression
  • DL models like LSTM(MLP+CNN), Transformers and Attentions
  • classification confusion matrix