Comments URL: https://news.ycombinator.com/item?id=47147282

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46522843

Points: 2

# Comments: 0

I'm using it right now to work on practicing vocalizing my ideation, which is a huge component of technical interviews that leetcode doesn't cover.

It integrates seamlessly into leetcode.com and sits on your screen as a little "rubber duck."

LeetDuck is automatically configured to proactively ask you a random behavioral question at the start, respond to runs and submits, and ask you about the time and space complexity when you successfully complete the problem.

Let me know what you guys think! Is this actually something other people would use too?

Comments URL: https://news.ycombinator.com/item?id=46513935

Points: 2

# Comments: 0

Great minds think alike! Mine is leetcodewrapped.com.

Did you guys hit the graphql endpoint as well?

> The OPs seems to be more cumulative lifetime stats rather than just this past year, for a lot of the slides.

I disclose that the last 5 slides are lifetime stats in my readme:

"Note: The last 5 slides are not necessarily specific to 2025 because of leetcode's graphql api only allows querying up to 20 of the latest submissions from an unauthenticated user.

However, if you pass a LEETCODE_SESSION cookie (obtained from leetcode.com, open dev tools -> application -> cookies) with your request you can query all of your accounts submissions. You could also use the calendar endpoint query all of your submissions in the past year, and thus create a much more nuanced leetcode wrapped. (ex: You struggled with this problem the most in 2025.)"

I may try to tackle this via an extension with no server side logic if I have some free time later this week, would certainly be a cooler final product. Only caveat is users would have to manually install the extension from a github repo (too scary for most people) or the chrome web store, which may add too much friction for most people.

> Fun how it goes the opposite compared to the real security implications.

You're spot on, it is pretty interesting. I suggested the extension purely to bridge that trust gap, especially if it's verified by the Chrome Web Store. If the extension is designed to strictly avoid calling any external APIs (other than leetcode graphql), it makes exfiltration impossible, ensuring the cookie never leaves the user's browser

Comments URL: https://news.ycombinator.com/item?id=46183952

Points: 28

# Comments: 11

Something I've been tinkering on that I thought I would share with y'all. Let me know what you guys think!

It's open source if anyone wants to contribute as well: github.com/collinboler/leetcodewrapped

Comments URL: https://news.ycombinator.com/item?id=46172102

Points: 1

# Comments: 1