Ikram | Veiled DevπŸ§•
117 subscribers
155 photos
22 videos
3 files
67 links
Channel Dedicated to share my ups and downs, setbacks and milestones. Place were I jornal, post my thoughts, share useful tech related stuffs....

Aim: Continues Growth πŸ“ˆ

Resources Channel: https://t.me/Challenge_MeIkram
Download Telegram
Wait a minute, I forgot that tomorrow is a WeekendπŸ₯ΉπŸ€—! 😐

@veiledDev14
❀2πŸ‘1😭1
Bro acting thoughπŸ’ͺ
Daycare: Man... 🀨What is wrong with you?πŸ™„(Imagine she was a black American)

Complete EGO shatter πŸ˜‚πŸ˜‚πŸ€£
🀣2
Forwarded from Sapphire Builds. (Ruhama B.)
Announcing Docklet v0.0.1: A Lightweight Desktop Client for Docker

I built Docklet, an open-source desktop application designed to provide a fast, minimal interface for managing Docker containers and images locally.

Key Features
- Real-Time System Metrics: Displays aggregate host CPU load, active container counts, and system memory consumption.
- Container Management: Start, stop, and delete containers with one-click actions and view active port mappings..and more.

Platform Support & Downloads
Pre-compiled standalone binaries are available on the GitHub Releases page and landing page:

- Linux: Universal x86_64 binary built against glibc 2.35 (compatible with Ubuntu, Debian, Fedora, Arch, and Mint).
- macOS: Universal binary supporting both Apple Silicon (M1/M2/M3/M4) and Intel processors.
- Windows: 64-bit standalone executable.

Websitehttps://docklet-ochre.vercel.app
GitHub Repository: https://github.com/ruhamabek/Docklet
πŸ‘2
Doctors with out Engineers are 'Bahilawi Hakim'.

No hospital without Civil
No X-ray,no other tools with out Mechanical, Electrical, Mechatronics, Software engineers

And they say we save lives ha...🧐

@veiledDev14
😁8
This media is not supported in your browser
VIEW IN TELEGRAM
Now this is called real Machine Learning😎
😁6
Forwarded from KeyCodes (MΔ©ftΓ£h)
I used to build roadmaps for myself, rush through them, might skip the fundamentals, and end up lost in TUTORIAL HELL.

Too many resources without structure actually KILLS your progress.

So, I built the exact thing I always needed:
A centralized, interactive manual taking you from COMPLETE BEGINNER β†’ SENIOR FULLSTACK AI ENGINEER across 7 phases, with real projects at every phase .

Here is how it keeps you LOCKED IN:

STOP JUMPING AHEAD
➀ Topics unlock step-by-step as you complete each milestone.
TRACK UR PROGRESS
➀ GitHub login, saved progress, deep-work hours, and your own timeline.
ALL THE BEST RESOURCES IN ONE PLACE

➀ I brought together The Odin Project, Full Stack Open, Seefun's 90 day Backend Mastery, and Kidus's ML into one space.

➀ YouTube videos placed in each node

I built this for myself, but there's no reason to keep it to myself.

Whether u're a complete beginner or already deep into development, there's something here for u.
Share it with someone who might find it useful!

LINK

@KeyCoodes
πŸ•Š3πŸ”₯1
Forwarded from ISNAD
We are officially LIVE! πŸŽ‰

Alhamdulillah, we’re excited to announce the launch of Weam (ΩˆΨ¦Ψ§Ω…), a platform designed to help local residents and visitors easily discover and explore the city.
Weam puts everything you need right at your fingertips.

Key Features:

πŸ•Œ Masjids & Prayer Spaces: Find nearby locations and check jam'ah times with "Near Me."

🍽️ Halal Dining: Discover top local halal restaurants and cozy cafes.

πŸ›οΈ Shops & Services: Support Muslim-owned businesses, clothing stores, bookshops, and daily services.

🀝 Help Us Map the City!
Building this directory is a community effort. Map your favorite spot or business for FREE in under 2 minutes:

1️⃣ Go to https://weam.isnaad.tech/
2️⃣ Click "+ Add a Place"
3️⃣ Submit the name, location, and category!

πŸ“Œ Note: We are currently in beta testing and continuously improving.

Try it out today, leave your mark, and share the link with family and friends! πŸš€

#Weam #MuslimDirectory #DigitalAddis #smartcity #AddisGuide #IsnadTech #isnaad_tech
❀2πŸ”₯1πŸ‘1
Can You Perform a POST Operation Using a GET Request?🧐


Back when I was attending my 2nd year at A2SV, I was minding my own business when I overheard one of our mentors and his colleague talking about system design. His colleague had an upcoming system design interview and was preparing for it. Our mentor had already secured a full-time position at Bloomberg, so he was sharing some advice and helping him prepare.
Then I heard something that caught my attention.(Fast forward, they are both in Bloomberg now)
His friend asked:
β€œIt’s possible to do a POST request using a GET request, right?”

I was like, wait what?😳 That question stuck with me.

How is that possible? And more importantly, why shouldn’t we do it?
That curiosity eventually led me to dig deeper into how HTTP actually works.

πŸ’»The Mechanics: How GET Can Act Like POST

At the wire level, an HTTP request is just a text block sent over a network socket. The server receives the text, reads the verb at the beginning, and decides how to parse the incoming data.

app.get("/create-user", (req, res) => { 
const { name, email } = req.query;
// Insert into database

createUser(name, email); res.json({ message: "User created" });
});

Now a client sends:
GET /create-user?name=Alex&email=alex@example.com HTTP/1.1
Host: api.example.com


The backend reads the query parameters:
req.query.name
req.query.email


and inserts them into the database.
So even though the HTTP request is:

GET /create-user

the operation performed by the application is a create operation.

Data via Query Parameters:
A GET request can attach payloads directly into the URL query string. If a backend handler reads req.query and inserts those values into a database, a GET request has effectively performed a create operation (POST).

Payloads in GET Bodies: While unorthodox, the HTTP specification does not strictly forbid a body inside a GET request. If a server framework parses the body of a GET request and executes a data-altering query, it creates or updates records identical to a POST or PUT request.

πŸ™…β€β™€οΈWhy You Should Avoid Using GET for POST Operations
While technically feasible, bending HTTP semantics creates severe architectural and security risks:

1️⃣URL Logging and Leakage: Query parameters are logged in plaintext across browser history, web server access logs, load balancers, and CDN networks. Passing sensitive creation payloads (passwords, PII, tokens) inside a GET URL exposes data to third-party loggers.

2️⃣Aggressive Caching: CDNs and browsers assume GET requests are idempotent and safe to cache. If a GET endpoint creates a database resource, edge servers might serve a cached response instead of hitting your backend, causing silent data failure.

3️⃣Pre-fetching and Crawlers: Search engine web crawlers and browser pre-fetching engines automatically follow GET links. If a GET request mutates state, a search crawler indexing your web app could unintentionally trigger database modifications or account deletions.

4️⃣Violation of Idempotency: According to RFC 9110, GET is defined as a safe method intended purely for retrieval without side effects. Breaking this contract leads to unpredictable behavior in distributed microservices and API gateways.

✍️prepared it using AI

@veiledDev14
❀1πŸ•Š1