Clickjacking is one of those everything works security problems that teams ignore because nothing crashes, nothing burns, and monitoring stays green. And that s exactly why it survives.
Your API can be flawless, your backend locked down but if your UI can be framed, a user can be tricked into clicking real actions through someone else s page. Approvals, settings, payments, permissions. All valid. All invisible.
We re asking because we never found an answer we truly loved.
Ours usually came in as screenshots, emails, Slack messages, support tickets and by the time they reached the product team, half the context was already gone. Also what after collecting the feedback? How do you communicate it back to your users? Everything eventually felt disconnected.
Hey everyone I m excited to share NextCV, a web tool I built to help students, freshers, and professionals create ATS-friendly resumes without design headaches.
What is NextCV?
NextCV helps you generate clean, modern resumes that actually pass Applicant Tracking Systems (ATS) used by companies.
I built a markdown editor that lets you start writing instantly and collab in real-time just by sharing a link.
No account, no setup. Click write share. Anyone with the link can edit with you live, with cursors visible in real-time (kinda like FigJam but for markdown).
There s a special kind of security failure that doesn t come from complex exploits or zero-days. It comes from your API politely introducing itself to the entire internet: Hi, I m nginx 1.18.0. This isn t advanced hacking. It s basic fingerprinting and it s how attackers decide whether you re worth attacking at all. Exposing server versions turns vulnerability scanning into shopping with a checklist: tech, version, CVE, automate. Teams forget this because it s boring, not because it s hard. No alerts. No crashes. Just a quiet little header waiting for the wrong person to notice. I added this check to Rentgen because people don t forget hard things they forget obvious ones. And those are the ones that usually bite first.
Hey everyone No CS background. Started vibe coding 3 months ago. 16+ hours daily. 15 billion tokens later I'm still learning. Then two things happened: 1. The leaderboard service I was using went silent. No updates, no response. 2. I realized all my work would disappear in 30 days. So I decided: "I'll just build it myself."
Claude Code deletes your session history after 30 days. Your work disappears. Unless you track it. CCgather preserves your journey.
That's CCgather not to track limits, but to preserve the journey. Every token you spend is proof of something proof that you're building, learning, doing the work. Features: Global Leaderboard See where you stand worldwide AI-Translated Community Write in your language, read in yours Levels & Badges From Rookie to Immortal Activity Heatmap Visualize your patterns
