Divyanshu

115 posts

Divyanshu banner
Divyanshu

Divyanshu

@DivyanshuVortex

Free Radical ⚛️ github : https://t.co/IIs3SuUpFD

Moon Katılım Ocak 2025
125 Takip Edilen77 Takipçiler
Divyanshu
Divyanshu@DivyanshuVortex·
Let’s focus on building some great projects now and keep moving forward. btw start working.
English
0
0
1
16
Divyanshu
Divyanshu@DivyanshuVortex·
😒
Divyanshu tweet media
QME
0
0
0
61
Divyanshu
Divyanshu@DivyanshuVortex·
The person selected for GSoC just joined the Discord today , they weren’t previously present in the community.
GIF
English
2
0
3
210
Divyanshu
Divyanshu@DivyanshuVortex·
How this dude able to make 569 PR in 385+ multiple Open source repo. within 7 days !!
Divyanshu tweet media
English
2
0
2
207
Divyanshu
Divyanshu@DivyanshuVortex·
@adxtyahq @Amank1412 Bro i have more than 30 pr merge but two ghost contributor who just clone the repo in end of march got selected without any pr ....
English
0
0
0
297
aditya
aditya@adxtyahq·
seeing people with 0 PR's get into GSoC while guys like @Amank1412 with 15+ merged PRs don’t get what they deserve yeah… life’s not fair sometimes
Aman@Amank1412

rejected.

English
33
7
238
15.9K
Divyanshu
Divyanshu@DivyanshuVortex·
@code_kartik What should I improve? I’m not sure where I fell short—30+ PRs, top contributor for months, active throughout. Yet some selected profiles show little to no visible contributions,clone the repo in end of march. Looking for clear guidance on what to work on next.
English
1
0
2
184
Kartik
Kartik@code_kartik·
Congratulations to everyone who have been accepted in gsoc 2026 orgs 🎉 Also people who have not been accepted take it as learning as I think it is also valuable.
English
4
0
146
2.6K
Anas
Anas@Anas_founder·
Developers, what matters more? -Skills -Degree -Experience
English
122
2
91
4.1K
RAKSHIT Yadav
RAKSHIT Yadav@rakshit_yadav19·
@AtharvaXDevs @Tanishqstwt I have like 30+ pr merged was contributing since last 4-5 months in that org had good bonding with mentor had reviewed the proposal mentor liked it also build a prototye for it everything for going perfect then on result day saw a guy was selected with zero contributions
English
1
0
3
80
Atharva
Atharva@AtharvaXDevs·
this is special post for my homie @Tanishqstwt we both were prepping and contributing gsoc toghether since early jan. he was top 5 contributor in palisadoes with 12+ pr merged and was so active in community as well. but unfortunately palisa didn’t come this year we even tried keploy(they even announced projects list on slack, but didn’t came), owasp(too high competition) then i started moving my focus on lfx but i also got rejected there too. then we again started contributing in same project after list announcement we were almost same hand in hand in the org also he was contributing to one more org openbus something. he applied for those two orgs and i applied only one(which was common) unfortunately only i got selected and he got rejected in both orgs, i was so broke cuz i have seen his efforts very closely, i just wanted to say that something big is waiting for my bro! just move on & chin up bhai we gotta move to lfx term2. you have so much potential and you are working tremendously hopefully something big coming on the way. guys do follow my friend @Tanishqstwt he is doing crazy work in devops, open source and all. please do check his work as well and if anyone is hiring in my networking pls blindly hire him i am vouching :)
English
21
0
115
4K
Divyanshu
Divyanshu@DivyanshuVortex·
GSoC 2026 update: Not selected. Months of consistent effort—contributions, proposal, iterations. Result: not selected. Mind went blank. Hard to process seeing some selected profiles with almost no visible activity. In the end, results matter—hard work isn’t always visible.
English
1
0
2
128
Divyanshu
Divyanshu@DivyanshuVortex·
@tusharnjamdade @sahitya_twt Bruhh , ig you didn't like your mental peace btw here : Open gsoc website -> inspect -> network tab -> user-profile/format=json -> response tab -> check program key ??
English
0
0
1
515
Sahitya
Sahitya@sahitya_twt·
to all those who applied for GSoC'26, and are not getting that JSON thingy, don't stress out, a lot of deserving peeps are not getting it, and it does not mean you are rejected don't stress out and wait for tomorrow, there are still chances, best of luck congrats to everyone who got that thing
English
2
1
21
2.6K
em herrera
em herrera@EmilyHerrera·
I am hiring interns.
English
104
2
244
19.1K
Sahitya
Sahitya@sahitya_twt·
suddenly my engagement on LinkedIn just shooted up lot of new connection reqs, profile visits... wtf! my last post was 2 months back
English
3
0
20
3.8K
Divyanshu
Divyanshu@DivyanshuVortex·
@calcom is not open source anymore
Bailey Pumfleet@pumfleet

Open source is dead. That’s not a statement we ever thought we’d make. @calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core @calcom codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

English
0
0
0
22
Dhairyashil
Dhairyashil@dhaiiryashiil·
🚨 BREAKING: @calcom is not open source anymore
Bailey Pumfleet@pumfleet

Open source is dead. That’s not a statement we ever thought we’d make. @calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core @calcom codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

English
8
0
33
3.4K
Sahitya
Sahitya@sahitya_twt·
@calcom is gone closed source today but you all can still contribute to it since only commercial and enterprise features that only apply to Cal.com as a managed service have been removed. All free features remain in Cal.diy.
Sahitya tweet media
English
2
0
6
211
Divyanshu
Divyanshu@DivyanshuVortex·
University mid-exams can be considered the best break
English
1
0
2
156

Keşfet

@rakshit_yadav19 @swarnitghule @adxtyahq @Amank1412 @Harish_521 @code_kartik @Anas_founder @AtharvaXDevs