Simret.exe
128 subscribers
511 photos
47 videos
230 links
It’s just a chill space where I share my dev moments, ML/backend projects, and things I learn along the way. I started this to stay committed and grow with others. If you vibe with that, open your laptop and let’s figure out tech together 💻🧚‍♀️
Download Telegram
Forwarded from Robi makes stuff (Robi)
Welp, here it is . Moat or bloat

Effectively a very harsh standard for grading the "Introducing X" posts we see in "the telegram community"

under review means not enough data, moat means peak ( only 2 projects so far ) float means alright but needs work and bloat means needs work.

Dont be mad at me demo 😂 its also roasting me

https://mob.robi.work/
❤1😁1
This media is not supported in your browser
VIEW IN TELEGRAM
⏳ Day 10/60 Building SafePay

A long, good day: half research, half code.

I studied 4 Ethiopian payment gateways (Chapa, ArifPay, SantimPay, AddisPay) and found they differ on test access, cancelling, webhook security, and status names. So I built a universal adapter framework that lets SafePay plug into any of them, and moved the provider's own details (reference IDs, raw status) into new database fields.

I also added a verify-before-trust rule: a webhook never decides a payment's status, SafePay asks the provider to confirm first. To test it without real money, I built an in-memory fake provider, and the automated tests pass.

X post

Next: connecting Chapa in test mode.

#60Days #Consistency
❤6🔥3
Good morning everyone 😊😊

Have a Good Day❤️❤️

@Simret_exe
❤2😁2
Forwarded from Atomic izzy
I built Fayda MCP, a Python library for connecting AI agents to Fayda eSignet identity verification.

• Start verification and track its status.
• Retrieve identity and age-check results.

pip install fayda-mcp

GitHub: https://github.com/izzy-Ti/fayda-mcp

If you find it useful, give the repo a star!⭐️



*Still in development

@Atomic_izzy
Media is too big
VIEW IN TELEGRAM
⏳ Day 11/60 Building SafePay

The most exciting day so far: SafePay talked to a real payment gateway.

I built the first real adapter, for Chapa, in test mode with no real money. SafePay creates a Chapa checkout page, I paid with a Chapa test card, and SafePay asked Chapa what happened and translated the answer into its own status, going from pending to succeeded.

X post

Next: checkout sessions, so a merchant can start a Chapa payment through SafePay's own API.

#60Days #Consistency
🔥5⚡1
Good 🌃 night 🌙 fams
❤2👍1
Forwarded from Eyu Devs
Getting a job is the new "you won an iPhone 13 pro" scam 😁🤣
Media is too big
VIEW IN TELEGRAM
⏳ Day 12/60 Building SafePay

Today SafePay got its front door: a checkout session endpoint. A merchant sends an amount and an invoice number, SafePay asks Chapa to create a payment page, and the merchant gets the link back. The request needs an Idempotency-Key, so if a merchant retries, SafePay returns the same session and never creates a duplicate payment or calls Chapa twice.


X post

Next: reading the real result from Chapa and updating the payment's status.

#60Days #Consistency
🔥5
kilopal HQ
I am starting this challenge: "Day X Until I Get Into YC."
👀Something big is Coming👀🤯🤯
🔥5
Good morning everyone ☺️❤️

Have a good Saturday ☺️☺️❤️
❤2
Forwarded from EthioDeploy
EthioDeploy.com has been accepted into the Claude startup program
👏2
Media is too big
VIEW IN TELEGRAM
⏳ Day 13/60 Building SafePay

The customer paid, but does SafePay know?

Today SafePay learned to ask Chapa what really happened. When a merchant checks a payment, SafePay verifies it with the provider, then moves it through its states, pending to processing to succeeded, with a history row for each step, and sends the merchant one signed webhook.

Checking again changes nothing and sends nothing twice. The status comes only from Chapa's own answer, never from a browser redirect or an unverified message.

X post

Next: receiving Chapa's own webhooks safely.

#60Days #Consistency
❤4
Forwarded from Sapphire Builds.
Announcing Vitra v0.2.3: The Universal Visual Runtime & Spatial Version Control Engine

I built Vitra, an open-source visual runtime, deterministic layout engine, and spatial version control system. It formalizes UI design into an open Visual Abstract Syntax Tree (AST), provides a Git-compatible content-addressable object store for user interfaces, maintains bidirectional real-time synchronization with Penpot and Figma, and exposes a native Model Context Protocol (MCP) server enabling autonomous AI agents to inspect, audit, build, and version software interfaces with mathematical precision.

Key Features

- Deterministic Visual AST & Object Store: Typed, immutable scene nodes with spatial layout metrics, typography, and fills, backed by a content-addressable DAG using SHA-1 object hashing and zlib-compressed trees.

- True Spatial Version Control: Full Git semantics for design files (init, add, commit, log, branch, checkout, merge). Features a true 3-way AST merge engine that automatically resolves non-overlapping structural and property changes.

- Embedded Web Studio & Zero-Dependency CLI: Single standalone native executable compiled with Bun. Serves an interactive canvas web studio and sync server directly from binary memory with zero external assets required on disk.

- Bidirectional Penpot & Figma(experimental) Live Sync: Seamless bridge connecting open design tools to code repos. Includes a hosted Penpot plugin with millisecond WebSocket synchronization directly mirroring canvas edits into your local AST.

- Headless Quality & WCAG Auditing: Automated continuous integration engine calculating WCAG 2.1 AA/AAA contrast ratios, geometry boundary overflows, and minimum touch target surface validations.

- Multi-Target Production Code Generation: Transpiles the Visual AST directly into idiomatic React with Tailwind utility classes, native Apple SwiftUI view hierarchies, and semantic HTML5/CSS.

- Zero-Dependency Bitmap & Vector Export: Headless vectorization pipeline compiling text to mathematical SVG paths, rasterizing pixel-perfect PNGs via an embedded WebAssembly engine without requiring external system font libraries or npm dependencies.

- AI-Native Model Context Protocol (MCP): 20 native JSON-RPC tools and pre-packaged agent skills installable directly into Claude Desktop, Cursor, and Antigravity (npx skills add ruhamabek/Vitra) for autonomous interface engineering.

Core Tech Stack

TypeScript, Bun, Yoga Layout, W3C Design Tokens, WebAssembly, OpenType, Resvg(Rust) , WebSocket, Lucide, React, Tailwind CSS, Model Context Protocol (MCP).

GitHub Repository: https://github.com/ruhamabek/Vitra
Website: https://vitra-ten.vercel.app/
License: AGPL-3.0
Forwarded from Mahi's Diary
ሰላምን እተውላችኋለሁ፥ ሰላሜን እሰጣችኋለሁ፤ እኔ የምሰጣችሁ ዓለም እንደሚሰጥ አይደለም። ልባችሁ አይታወክ አይፍራም።


የዮሐንስ ወንጌል 14:27

መልካም ሰንበት ❤️

@my_dev_diary
❤1
ጥቅምት 01/02/2019 ዓ.ም
❤4🥰2
Media is too big
VIEW IN TELEGRAM
⏳ Day 14/60 Building SafePay

SafePay can now receive Chapa's own webhooks.

Today SafePay got its own door for Chapa's webhooks, which means a public endpoint anyone can knock on, so security came first. Every request must carry a valid signature, or it is rejected with a 401 and logged in an audit table that stores only a hash of the body.

Even a correctly signed message that says "paid" cannot change a payment, because SafePay always asks Chapa directly what really happened and updates from that answer.

X post

Next: reconciliation, so SafePay catches payments whose webhook never arrived.

#60Days #Consistency
❤4👏1
Forwarded from Code and Thought (جنة)
You will lose a lot if you don't have money, but the first thing you lose is your freedom.


There is no such thing as ኩሩ ደሀ
💯3
Have a Great Week✨✨

@Simret_exe
🥰2😐1