Tareq Aljaber

Smart Sign Language Glove – Our Prototype for Inclusive communication Proud to share the early-stage prototype of our project developed by me and my teammate Ameer Pasha — aimed at supporting individuals with speech and hearing impairments through gesture recognition and IoT-enabled communication. What We've Achieved So Far: •Designed and built a wearable glove using  • 4 Flex Sensors  • MPU6050 • ESP32 • OLED •Recognized basic hand gestures (like Hello, Yes, No, etc.) • Output is shown as text •Displayed results on serial monitor and OLED screen What's Coming Next: 🔹 Telegram integration to send text output as real-time messages 🔹 ML model to learn and recognize more complex sign language gestures 🔹 Add a voice-guided interface for blind users 🔹 Use ESP32’s Wi-Fi/Bluetooth to connect outputs to external screens or speakers — allowing others nearby to see and hear the message 🔹 Integrate with a mobile app for wider accessibility 🎯 Our vision is to turn this prototype into a scalable assistive solution for real-world use #AssistiveTechnology #Dsatm #MachineLearning #IoT #ESP32 #SignLanguage #WearableTech #InclusiveDesign #AIforGood #TextToSpeech #StudentInnovation #Accessibility #HumanCenteredAI

2

Another video in the video series of StationOne. This time, we look at how Connectors in StationOne can self-describe their capabilities, which is useful for dynamic workflows where tools be merchandized to qualify what they're capable of doing and not capable of doing. Not only does this show the power of agentic workflows interrogating tools capabilities, it also demonstrates a great way to show the relative maturity of tooling between tools from an AI context - in this case between Kochava and Appsflyer MCP endpoints. https://lnkd.in/gdjJMk5D

16

1 Comment

𝗗𝗫 𝗗𝗮𝘆 107 — 𝗦𝗶𝗴𝗻𝗮𝗹𝘀, 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗹𝗲𝘀… 𝗼𝗿 𝗦𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗦𝗶𝗺𝗽𝗹𝗲𝗿? Modern frontend development has become a 𝘀𝘁𝗮𝘁𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗮𝗿𝗺𝘀 𝗿𝗮𝗰𝗲. Angular now offers 𝗦𝗶𝗴𝗻𝗮𝗹𝘀 for local UI reactivity. Developers still rely on 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗹𝗲𝘀 (𝗥𝘅𝗝𝗦) for asynchronous streams. React is pushing 𝗦𝗲𝗿𝘃𝗲𝗿 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 to move work to the backend. Each of these tools solves a real problem. Signals simplify UI updates. Observables coordinate complex async flows. Server rendering improves performance. But there is a deeper question most systems never ask: 𝗪𝗵𝘆 𝗶𝘀 𝘁𝗵𝗲 𝗯𝗿𝗼𝘄𝘀𝗲𝗿 𝗺𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝘀𝗼 𝗺𝘂𝗰𝗵 𝘀𝘁𝗮𝘁𝗲 𝗶𝗻 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝗽𝗹𝗮𝗰𝗲? In many enterprise systems the UI ends up holding: • business truth • workflow progress • partial transactions • synchronization between components • recovery logic after failures That is why frontend state management keeps getting more complicated. Frameworks are trying to tame a problem that 𝘀𝗵𝗼𝘂𝗹𝗱 𝗻𝗲𝘃𝗲𝗿 𝗵𝗮𝘃𝗲 𝗯𝗲𝗲𝗻 𝗽𝗹𝗮𝗰𝗲𝗱 𝗶𝗻 𝘁𝗵𝗲 𝗯𝗿𝗼𝘄𝘀𝗲𝗿. Eventz approaches the problem differently. Instead of asking: Should this be a 𝘀𝗶𝗴𝗻𝗮𝗹? An 𝗼𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗹𝗲 𝘀𝘁𝗼𝗿𝗲? A 𝘀𝗲𝗿𝘃𝗲𝗿 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁? Eventz asks a prior question: 𝗦𝗵𝗼𝘂𝗹𝗱 𝘁𝗵𝗶𝘀 𝗯𝗲 𝗳𝗿𝗼𝗻𝘁𝗲𝗻𝗱 𝘀𝘁𝗮𝘁𝗲 𝗮𝘁 𝗮𝗹𝗹? In an Eventz system: • Business events are published. • Functions apply organizational rules. • Immutable tuples are written to the system archive. The governing equation is simple: 𝘆 = 𝗙(𝗬, 𝗲) Where: • 𝗲 = a business event • 𝗙 = the rule-bearing function • 𝗬 = the accumulated system history • 𝘆 = the newly published fact The browser is no longer the keeper of truth. It becomes a 𝘃𝗶𝗲𝘄𝗲𝗿 𝗮𝗻𝗱 𝗽𝘂𝗯𝗹𝗶𝘀𝗵𝗲𝗿 𝗼𝗳 𝗲𝘃𝗲𝗻𝘁𝘀. In that architecture: Signals still work well for 𝘁𝗲𝗺𝗽𝗼𝗿𝗮𝗿𝘆 𝗨𝗜 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝗿 • selected row • form input • toggles • screen layout Observables still work well for 𝘁𝗿𝗮𝗻𝘀𝗽𝗼𝗿𝘁 • websocket updates • user input streams • async responses Server rendering can still improve 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲. But none of these tools carry the weight of business truth. Truth lives in the immutable event archive. The result is surprising. Frontend state management suddenly becomes 𝗺𝘂𝗰𝗵 𝘀𝗺𝗮𝗹𝗹𝗲𝗿. You no longer need elaborate client stores to reconstruct what the business believes to be true. The system already knows. Every fact was published. Every rule was applied. Every result was recorded. Signals. Observables. Server components. All useful. But they are 𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝘁𝗼𝗼𝗹𝘀, not the foundation of the system. Eventz moves the foundation somewhere much simpler. 𝗧𝗼𝗼 𝗦𝗶𝗺𝗽𝗹𝗲 𝘁𝗼 𝗙𝗮𝗶𝗹. #DigitalTransformation #SoftwareArchitecture #EventDriven #Eventz #CIO #CFO #EnterpriseArchitecture

3

Ovonts is now part of early AGI reports. From 2016 till now, our research on AI, ML, deeptech, AGI (and hopefully someday ASI) has not stopped.

5

Honored to introduce Core-Ce — the operating system for the Web of Agreement. Core-Ce is a distributed operating system designed for node-based (AKA neighbor) networks where people, infrastructure, and devices coordinate directly through agreements instead of centralized platforms. Core-Ce is open source, enabling developers, communities, and infrastructure builders to contribute, deploy nodes, and expand the ecosystem. Core Specifications Architecture: • Node-native operating system • Web of Agreement protocol • Ce - Block distributed ledger • Autonomous mesh networking • Infrastructure identity system • Decentralized communication layer • IoT and device integration • Open utility layer for applications Core UI Functions: • Mesh Request Broadcast • Node Discovery Panel • Profile Identity Panel • Agreement Feed • Neighborhood Dashboard • Language Control • Node Status Indicators • Broadcast Controls • Direct Node Interaction • Shared Resource Panel • Node Reputation Indicators • Activity Notifications • Agreement Builder • Data Attachments • Infrastructure Control Panels • Network Visualization Core-Ce enables networks where nodes coordinate infrastructure, exchange resources, and establish verifiable agreements across decentralized environments. Sandboxed release---> 5/25/2026 Core-Ce full release. ----> 12/26/2026 #WOA #Ce #ledger #javascript #node #agreementprotocol

7

2 Comments

This week, we shipped a predictive route detector and stabilized Tycho execution flows, inviting a few partners for short onboarding calls. This week, our team shipped a focused, production-oriented step toward private, safe MEV routing. We integrated an FMD-based profitable-route detector into the execution stack, refined Tycho route encoding and Permit2 flows, and stabilized our canonical two-hop example, enabling contributors to reproduce realistic simulations locally. These changes aren’t just code. They cut down wasted simulations, surface higher-quality candidate routes, and make private execution paths more deterministic and auditable. Quick technical highlights: - FMD detector: physics-inspired prediction (TPS/committor) ranks route candidates before expensive REVM validation. - Safe execution: Tycho-encoded solutions + Permit2 user-transfer flow — never broadcast to the public mempool. - Developer flow: fixed example stability and clearer env checks, so onboard cycles are shorter. Why it matters: Extracting value from fragmented DEX liquidity is both an engineering and research problem. Predictive filtering reduces noise, and deterministic encoders reduce execution risk; that’s what moves this from lab experiments to usable tooling for desks, wallets, and integrators. We’re inviting a small set of partners for a brief 20 to 30-minute onboarding call to walk through our approach, discuss integration pathways, and gather feedback on our docs and APIs. If you’re building MEV-safe routing, wallet integrations, or execution infrastructure and would like a private walkthrough, message me or email joshua.davidson@orkidlabs.com, and we’ll schedule a quick call. If you're interested, please preview our new whitepaper below. DM for a copy if you surf chaos like Paul Atriedes rides the sandworm. Negentropy I'll send you the version properly processed with LaTeX. I promise. 🙏 — JC, ORKID Labs p.s. Beta Version of ORKID's Uniswap V4 hook deployed: https://lnkd.in/gTn46y6Q #MEV #MEVProtection #DeFi #Web3Infrastructure #Rust

4

What Startups Can Learn from Iran This might surprise you, but there’s a powerful startup lesson hidden in Iran’s military strategy. For years, Iran faced sanctions, isolation, and zero support from any major ecosystem. No partnerships. No resources. No love from the “market.” Yet somehow quietly and methodically, it developed a powerful missile program. No fanfare. No leaks. Just focus. And when it finally revealed its capability, the world took notice. That’s asymmetric power. That’s strategic patience. Startups can learn from this: ✅ Build quietly. Don’t brag. Validation isn’t traction. Let your product speak, when it’s ready to strike. ✅ Exploit incumbents’ weaknesses. Iran never tried to match its enemies tank-for-tank. It looked for blind spots. So should you. Move where they’re slow, bloated, or arrogant. ✅ Lack of ecosystem isn’t an excuse. Iran didn’t wait for support. It built its own tools. Startups with no external help can still win , through discipline, grit, and creative hacks. You don’t need to be loud. You need to be dangerously competent. #Startups #UnderdogStrategy #QuietExecution #AsymmetricWarfare #Iran #BuildDifferent #ProductStrategy #Resilience

7

3 Comments

Building an MVP with no-code tools has become one of the fastest ways for startups to get a product in front of users. We reviewed 10 leading no-code agencies that help early-stage teams build, test, and refine their ideas without the time and cost of traditional development. https://www.rfr.bz/ldd02e3

3

🚨 Engineers, this one’s for you. Why do so many brilliant builders struggle when they step into the founder role? In my latest episode of The CTO Show With Mehmet Gonullu, I sat down with Mohamed (Mo) Ahmed, Ph.D. —AI entrepreneur, author of The Inside-Out Entrepreneur, and founder of Boundless Founder—to unpack what really separates product builders from business builders. We covered: ✅ Emotional resilience and founder mindset ✅ Fundraising psychology and investor dynamics ✅ How to avoid the “product trap” and focus on solving real problems ✅ Lessons from scaling, failing, pivoting, and getting acquired This isn’t startup theory—it’s lived experience. 🎧 Now live on all podcast platforms and YouTube Links in comments 👇

4

1 Comment