Urgent.News

What's breaking now, across thousands of outlets.

Tech

One night, one team, countless discussions and a lot of learning. This is definitely a night we will remember.

An overnight journey of brainstorming, building, learning, snacks, last-minute changes and memories that we will probably talk about for a long time. It was around 4:00 when our Hacktoberfest Hack Day began. There was excitement everywhere, and honestly, we were very thrilled. For most of us, this was a new experience. We were not just going to build a project; we were about to experience our…

On an overnight journey of brainstorming, building, learning, snacks, last-minute changes and memories, the Hacktoberfest Hack Day commenced at around 4:00. Participants were thrilled, as it marked their first overnight hackathon together. The team worked on a novel problem statement—developing a decentralized trust network for open-source contributions.

The initial challenge was selecting a problem statement. After about 30 minutes of exploration, they chose Problem Statement 07. They then spent nearly an hour understanding the problem, discussing potential solutions, and sharing ideas. With the decision made, they began building at nearly 10:30, feeling they were behind schedule.

Their goal was to create a shared trust network, allowing open-source projects to exchange information about contributors and suspicious activities. They also aimed to develop a unique trust-ranking system, evaluating contributor trust using mathematical calculations, previous records, reviews, and feedback. This system would help identify genuine contributors, ensuring new contributors weren't unfairly judged due to lack of experience.

The team divided tasks, with backend and frontend leads Yash and Rounak working on the dashboard. They collaborated closely, refining the PPT structure, researching how to explain their project, and discussing the technical approach. Numerous discussions took place, often leading to long conversations, but these discussions ultimately helped clarify their vision.

Amidst the work, there were snacks, burgers, stickers, and conversations about each other's experiences and other teams' projects. Mentors provided valuable insights, and the team also enjoyed refreshments like KurKure, Lay's, KitKat, Coke, and burgers. The most hectic period was between 5:30 and 6:30, when they finalized the PPT, resolved dashboard concerns, and uploaded project files to GitHub. Their hard work paid off, as they presented a complete solution they could demonstrate.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at dev.to →

More in Tech

A Project Skill Can Change APX Behavior With One Name

A skill name is a boundary, not just a label. In APX, a project-local skill with the same slug as a user-global or built-in skill wins. That is useful when a repository needs its own operating rules.

  • Project-local skill overrides user-global or built-in skill in APX
  • Create SKILL.md file in .apc/skills/ directory to customize workflow
  • Project-specific skill replaces global version, not merging with it

Why I Stopped Letting One Turn Give an Agent Two Orders

Why I Stopped Letting One Turn Give an Agent Two Orders I used to think duplicate delegation was a small prompting problem.

  • One turn should command only one action from an agent.
  • Guard records target agent and instruction per turn.
  • Follow-up flag corrects or extends instructions explicitly.

Getting Started with Keycloak - Building a Simple Login Page with Docker

Introduction Recently, it seems Keycloak is being used quite frequently. (According to my colleague) I hadn't tried it yet myself, so I decided to give it a simple try to see what it's all about.

  • Pull Keycloak Docker image and start container with docker run command
  • Access Keycloak admin console at http://localhost:8080 with default login
  • Create test user and client in admin console for demo purposes

Twelve Hours, Four Friends, and a Whole Lot of Coffee: Our Hack Day Journey

There’s a unique kind of chaos that only hits you at 3:00 AM in a room full of glowing screens and buzzing energy. That was us—Team CodeSins—deep into Hack Day Sonipat, wondering why on earth we…

  • Team CodeSins built puzzle in 12 hours
  • Pulkit led team through challenges
  • Camaraderie highlighted over final product

More from Sunday 1 November →