bitchat is a fascinating idea
itโs a decentralized messaging app that can work without the internet, sim cards, or central servers.
it uses bluetooth mesh networking, where your message can hop from one nearby device to another, then another, until it reaches the person youโre trying to talk to.
the good stuff? privacy, offline communication, no central point of control, and the ability to stay connected when traditional networks go down.
but that same privacy also comes with concerns.
in india, authorities have raised security concerns over the potential misuse of apps like bitchat, especially because decentralized communication can make traditional monitoring more difficult.
itโs a perfect example of how the same technology can be both a powerful tool for privacy and a challenge for law enforcement.
privacy vs security. a debate thatโs definitely not going away anytime soon.
bitchat is such a fascinating project
imagine sending messages without the internet, sim cards, or a central server.
your message can hop from one nearby bluetooth device to another, then another, creating a decentralized mesh network until it reaches the person youโre trying to talk to.
the idea that every phone can become a tiny relay node is honestly so damn cool.
itโs like your phone becomes part of the network and helps pass messages along. no central server. no traditional infrastructure. just devices talking to each other.
tech like this really makes you think differently about what a "network" actually is.
day 4
i havenโt been active for the past five days due to some medical conditions, but now iโm back on track and continuing my learning journey.
today, i:
- revised and practiced everything i had learned in the previous days.
- received calls from a few companies and had discussions with them.
- continued working on my project.
- started learning nginx and exploring how to use it with my project.
taking it one day at a time and staying consistent.
#day4 #learninginpublic #nginx #webdevelopment #devops #project #consistency #learningjourney
@kimmonismus fr this ai race is kinda scary. every company is just trying to beat the other, but in the end we might be the ones getting cooked. one day ai could replace so many jobs that a lot of people end up with nothing while these big companies keep winning.
Introducing Kimi K3: Open Frontier Intelligence
๐น 2.8 Trillion Parameters, 1 Million Context, Native Multimodal
๐น Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts
๐น Attention Residuals deliver ~25% higher training efficiency at <2% additional cost
๐น Built for long-horizon agentic coding and self-evolving workflows
Kimi K3 is now live on on https://t.co/zrk6zZxZUo, Kimi Work, Kimi Code, and the Kimi API.
Open Weights by July 27, 2026.
๐ API: https://t.co/XCrgjXAqMw
๐ Tech blog: https://t.co/YTfiMSNM1f
day 3:
> got back to typescript and i'm getting more comfortable with it.
> applied for jobs. some applications got rejected, while others were ghosted.
> working on my project alongside everything else.
> improving one of my old projects by adding more useful features.
i feel empty because i'm living the same day over and over again.
i keep making the same mistakes, and i'm honestly tired of myself at this point.
every night i tell myself, "tomorrow i'm waking up early." then the alarm rings, i hit snooze without even thinking, and go right back to sleep.
i keep saying i'll quit scrolling on insta, but somehow i always end up there again. i think i'm actually addicted to it. it's like i always need a new hit of dopamine or my whole day feels off.
the worst part is that i know exactly what's distracting me. i know where i'm messing up. i notice every bad habit, every excuse, every pattern... and somehow i still repeat the same things.
then night comes, and i replay my entire day in my head. i overthink everything, regret wasting another day, and can't even sleep properly. then because i don't sleep well, i can't wake up early the next morning.
and just like that, the cycle starts all over again.
i'm so done feeling stuck, but somehow i keep becoming my own biggest obstacle.
that's totally normal
when i build a backend project, i know what i want to build and how it should work. but i still forget the exact syntax sometimes, so i check google, my old code, github, or ai.
you don't get extra points for remembering every line. knowing the logic, the approach, and where to find the answer is what really matters.
I went to 4 Full Stack Developer interviews, and every single interviewer asked me one question:
"Can you explain the Event Loop?"
If you're preparing for interviews, don't skip this topic.
Here's a simple explanation
The Event Loop in Node.js is the system that helps Node.js handle many tasks without waiting for one task to finish before starting another.
Node.js is single-threaded, meaning it uses one main thread.
But still, it can handle thousands of users because of the Event Loop.
Simple Example
Imagine this code:
console.log("Start");
setTimeout(() => {
console.log("Timer Done");
}, 2000);
console.log("End");
Output:
Start
End
Timer Done
Why?
Because Node.js does not stop and wait for setTimeout.
Instead:
"Start" prints
setTimeout is sent to the browser/Node API
Node.js continues running
"End" prints
After 2 seconds, callback goes to the Event Loop
Event Loop executes "Timer Done"
What Actually Happens Internally
Step-by-step
1. Call Stack
This is where normal code runs.
console.log("Hello");
goes into the stack and executes immediately.
2. Web APIs / Node APIs
Async tasks like:
setTimeout
File reading
Database calls
API requests
are handled outside the main thread.
Example:
setTimeout(() => {}, 2000);
Timer is handled by Node APIs.
3. Callback Queue
When async work finishes, its callback waits in a queue.
Example:
() => {
console.log("Done");
}
waits in the callback queue.
4. Event Loop
The Event Loop constantly checks:
โIs the call stack empty?โ
If yes:
It takes callbacks from the queue
Pushes them into the call stack
Executes them
Easy Real-Life Analogy
Think of a restaurant waiter.
The waiter takes your order
Gives it to the kitchen
Doesn't stand waiting
Takes other orders meanwhile
When food is ready, serves it
The waiter = Event Loop
Why Event Loop is Important
Because of Event Loop, Node.js can:
Handle many users
Work asynchronously
Avoid blocking
Build fast APIs and servers
Blocking vs Non-Blocking
Blocking Code
const data = fs.readFileSync("file.txt");
Node waits until file reading finishes.
Non-Blocking Code
fs.readFile("file.txt", (err, data) => {
console.log(data);
});
Node continues other work while file reads in background.
This is powered by the Event Loop.
One-Line Interview Definition
The Event Loop in Node.js is a mechanism that continuously checks the call stack and callback queue to execute asynchronous operations without blocking the main thread.
Simple Diagram
Call Stack โ executes code
โ
Event Loop
โ
Callback Queue โ completed async callbacks
how to live life like bruce wayne:
1. master discipline over motivation:
bruce doesn't train when he feels like it he trains because the mission demands it. build routines that don't depend on your mood.
2. invest in yourself relentlessly:
whether it's physical fitness, skills, or knowledge, bruce treats self-improvement as non-negotiable. read widely, train your body, and never stop upgrading your capabilities.
3. have a mission bigger than yourself:
bruce isn't rich for the sake of luxury every resource serves gotham. find a purpose that gives your daily grind meaning beyond personal comfort.
4. keep your circle small but loyal:
alfred, lucius, a select few not a huge network, but people who tell him the truth. surround yourself with people who challenge and support you honestly.
5. control what you can, prepare for what you can't:
bruce always has contingency plans (yes, even for the justice league). build savings, skills, and backup plans so chaos doesn't catch you off guard.
โผ๏ธ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion.
The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed.
The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads.
Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.
one of the biggest problems i'm facing right now is finding a job as a fresher. what are some tips or strategies i can use to land a job faster? also, what are the biggest mistakes or bad decisions i should avoid while job hunting?
bro i literally planned out my whole day for today and i was actually excited to wake up early, but then my friend's grandma passed away, so i had to go there. now my whole schedule is fucked..
day 1
today i started my 90-day job journey.
- applied for jobs on naukri and other job portals
- completed a few assignment tasks
- made a 90-day plan and started working on it
it was not a big day, but i am happy i took the first step. every small action counts.
@Misbahtwts@grok why can't india fix waterlogging? Every year it rains, the roads turn into rivers. if we know the rain is coming, why isn't the drainage system actually built to handle it? what's the real reason?
I was about to catch some Z's, then I saw this tweet. Yeah... sleep's officially canceled.
Now all I can think about is the ridiculous amount of time I've spent applying for jobs just to get ghosted.