Forwarded from AM Kaweesi
A vibrant, high-quality image of a young Ugandan person sitting in a modern, comfortable cafe. They are holding a smartphone and smiling as they interact with the AfuChat app. The phone's screen is clearly visible, showing the AfuChat interface with its distinct blue and white theme, chat bubbles, and maybe even a notification from AfuAl. The background is softly blurred, keeping the focus on the person's happy engagement with the app."
❤1
Forwarded from Rust-Script
autogitignore v0.1.2 is in crates.io you can install it with cargo
[repo] -it's OSS
i was about to release pre built binaries but issue every where until then rust people can try.
[repo] -it's OSS
i was about to release pre built binaries but issue every where until then rust people can try.
🔥1
Forwarded from Dagmawi Babi
This media is not supported in your browser
VIEW IN TELEGRAM
Obama as a cat 😭
😁6
Bruce Lee once said
I am experiencing this right now in programming world
I don't fear a person who practiced 1000 styles
I fear a person who practiced 1 style 1000 times
I am experiencing this right now in programming world
🤣6✍1
Have you wondered why localhost starts with http:// and your deployment starts with https://?
If you’re learning web dev, this difference shows up pretty early—and it feels confusing at first. Like… why is my local app “insecure” but the moment I deploy it, everything suddenly has a lock 🔒?
Let’s break it down without the boring textbook vibes.
Localhost is just you talking to yourself
When you use http://localhost:3000, your browser is talking to your own machine.
No internet involved
No strangers listening
No Wi-Fi snoopers
No attackers in the middle
It’s literally:
Because of that, encryption doesn’t really matter. Setting up HTTPS locally also means dealing with certificates, keys, warnings, and general pain—so most dev tools just keep it simple and use HTTP.
And that’s totally fine.
Deployed apps live in the wild
Now compare that to a deployed app.
Your request goes:
That’s a lot of places where someone could:
Read your data
Modify it
Pretend to be your server
So production apps use HTTPS:
Data is encrypted
Server identity is verified
Browsers trust it
Users feel safe
That little lock icon actually matters here.
HTTPS doesn’t mean “this site is perfect”
Quick reality check:
HTTPS only means:
Your connection is secure in transit
It does not mean:
The backend has no bugs
The site can’t be hacked
The app is “well written”
You can have:
❌ Bad code over HTTPS
❌ Secure connection to a broken app
Still, HTTPS is non-negotiable in production.
Can localhost use HTTPS?
Yep. You can do:
https://localhost
People usually do this when:
Testing auth (cookies, OAuth)
Working with payments
Mimicking production closely
But for normal development? 👉 HTTP on localhost is completely okay
The simple takeaway
localhost → HTTP (safe enough, fast, easy)
Deployed app → HTTPS (required, secure, trusted)
HTTP isn’t “bad” — it’s just not meant for the public internet
Once you deploy, encryption stops being optional.
And that’s the whole story—no mystery, no magic 🔐
If you’re learning web dev, this difference shows up pretty early—and it feels confusing at first. Like… why is my local app “insecure” but the moment I deploy it, everything suddenly has a lock 🔒?
Let’s break it down without the boring textbook vibes.
Localhost is just you talking to yourself
When you use http://localhost:3000, your browser is talking to your own machine.
No internet involved
No strangers listening
No Wi-Fi snoopers
No attackers in the middle
It’s literally:
browser → your computer → browser
Because of that, encryption doesn’t really matter. Setting up HTTPS locally also means dealing with certificates, keys, warnings, and general pain—so most dev tools just keep it simple and use HTTP.
And that’s totally fine.
Deployed apps live in the wild
Now compare that to a deployed app.
Your request goes:
your device → ISP → routers → servers → data centers → server
That’s a lot of places where someone could:
Read your data
Modify it
Pretend to be your server
So production apps use HTTPS:
Data is encrypted
Server identity is verified
Browsers trust it
Users feel safe
That little lock icon actually matters here.
HTTPS doesn’t mean “this site is perfect”
Quick reality check:
HTTPS only means:
Your connection is secure in transit
It does not mean:
The backend has no bugs
The site can’t be hacked
The app is “well written”
You can have:
❌ Bad code over HTTPS
❌ Secure connection to a broken app
Still, HTTPS is non-negotiable in production.
Can localhost use HTTPS?
Yep. You can do:
https://localhost
People usually do this when:
Testing auth (cookies, OAuth)
Working with payments
Mimicking production closely
But for normal development? 👉 HTTP on localhost is completely okay
The simple takeaway
localhost → HTTP (safe enough, fast, easy)
Deployed app → HTTPS (required, secure, trusted)
HTTP isn’t “bad” — it’s just not meant for the public internet
Once you deploy, encryption stops being optional.
And that’s the whole story—no mystery, no magic 🔐
👍2🔥2
Dcode
Have you wondered why localhost starts with http:// and your deployment starts with https://? If you’re learning web dev, this difference shows up pretty early—and it feels confusing at first. Like… why is my local app “insecure” but the moment I deploy it…
0kb/s
Tele keeps showing us miracles
Tele keeps showing us miracles
😁2😭1
This media is not supported in your browser
VIEW IN TELEGRAM
If tele compete this competition, they'll be champion
Dcode
If tele compete this competition, they'll be champion
But fr tho
If there is bad ux competition
What u gonna do
If there is bad ux competition
What u gonna do