osinkolu /
Umoja-Hack-Africa-2022
#Umoja Hacks. This repo contains team solo's best solutions for the umoja hackathon 2022 hosted on Zindi, it is the combined effort of Fajamila Oluwadunsin, Okewunmi Paul and Olufemi Victor.
Loading repository data…
iamlalu05 / repository
Solo is a futuristic gaming e-commerce website built solo using HTML, CSS, Bootstrap, and PHP. It features animated game cards, a responsive layout, and a glowing neon UI. Users can browse featured games, simulate purchases, and register accounts — all styled with immersive design and smooth transitions. Perfect for showcasing fullstack development
Solo is a solo-built, responsive gaming store website designed to simulate a sleek online shopping experience for gamers. It blends bold visuals, smooth animations, and functional backend logic to showcase my skills in full-stack web development and creative UI design.
Solo-Gaming-Store/ ├── index.html ├── bill.php ├── db.php ├── images/ │ ├── cod.jpg │ ├── rdr2.jpg │ └── coldwar.jpg └── README.md
Muntasir Mohamed Tariq
Graphic Designer | Web Developer | Aspiring Software Engineer
📍 Akkaraipattu, Eastern Province, Sri Lanka
📧 support@sologames.com
🔗 LinkedIn • GitHub
This project is for educational and portfolio purposes only. Commercial use is not permitted without permission.
Selected from shared topics, language and repository description—not editorial ratings.
osinkolu /
#Umoja Hacks. This repo contains team solo's best solutions for the umoja hackathon 2022 hosted on Zindi, it is the combined effort of Fajamila Oluwadunsin, Okewunmi Paul and Olufemi Victor.
souptik-samanta /
Chaos Compiler is a custom CoreXY-Cartesian hybrid 3D printer with Klipper on a Pi 4, multicolor printing, auto bed leveling, and a servo that kicks your prints off the bed. Built from scratch in India, on vibes and budget.This project was made possible thanks to the Hack Club Infill Grant, a YSWS by Alex Ren. mostly designed by me solo
pravinxdev /
Cloak is a secure, lightweight CLI tool to manage your development secrets locally — no cloud, no hassle. Store, retrieve, and manage secrets across projects with encryption and ease. 🔐 Perfect for solo devs, indie hackers, and teams who value speed, simplicity, and security.
xiaoyu24501 /
LocalGantt is a local-first agile project management tool designed for indie hackers, solo founders, and small teams. Manage projects with interactive Gantt charts and burndown charts, while keeping all data fully local and private. LocalGantt supports project import/export for easy sharing, backup, and migration across devices and teams.
NILKANTHABAG /
PUBG Data Description In a PUBG game, up to 100 players start in each match (matchId). Players can be on teams (groupId) which get ranked at the end of the game (winPlacePerc) based on how many other teams are still alive when they are eliminated. In game, players can pick up different munitions, revive downed-but-not-out (knocked) teammates, drive vehicles, swim, run, shoot, and experience all of the consequences -- such as falling too far or running themselves over and eliminating themselves. You are provided with a large number of anonymized PUBG game stats, formatted so that each row contains one player's post-game stats. The data comes from matches of all types: solos, duos, squads, and custom; there is no guarantee of there being 100 players per match, nor at most 4 players per group. File descriptions data.csv - 151MB Data fields DBNOs - Number of enemy players knocked. assists - Number of enemy players this player damaged that were killed by teammates. boosts - Number of boost items used. damageDealt - Total damage dealt. Note: Self inflicted damage is subtracted. headshotKills - Number of enemy players killed with headshots. heals - Number of healing items used. Id - Player’s Id killPlace - Ranking in match of number of enemy players killed. killPoints - Kills-based external ranking of players. (Think of this as an Elo ranking where only kills matter.) If there is a value other than -1 in rankPoints, then any 0 in killPoints should be treated as a “None”. killStreaks - Max number of enemy players killed in a short amount of time. kills - Number of enemy players killed. longestKill - Longest distance between player and player killed at time of death. This may be misleading, as downing a player and driving away may lead to a large longestKill stat. matchDuration - Duration of match in seconds. matchId - ID to identify matches. There are no matches that are in both the training and testing set. matchType - String identifying the game mode that the data comes from. The standard modes are “solo”, “duo”, “squad”, “solo-fpp”, “duo-fpp”, and “squad-fpp”; other modes are from events or custom matches. rankPoints - Elo-like ranking of players. This ranking is inconsistent and is being deprecated in the API’s next version, so use with caution. Value of -1 takes the place of “None”. revives - Number of times this player revived teammates. rideDistance - Total distance traveled in vehicles measured in meters. roadKills - Number of kills while in a vehicle. swimDistance - Total distance traveled by swimming measured in meters. teamKills - Number of times this player killed a teammate. vehicleDestroys - Number of vehicles destroyed. walkDistance - Total distance traveled on foot measured in meters. weaponsAcquired - Number of weapons picked up. winPoints - Win-based external ranking of players. (Think of this as an Elo ranking where only winning matters.) If there is a value other than -1 in rankPoints, then any 0 in winPoints should be treated as a “None”. groupId - ID to identify a group within a match. If the same group of players plays in different matches, they will have a different groupId each time. numGroups - Number of groups we have data for in the match. maxPlace - Worst placement we have data for in the match. This may not match with numGroups, as sometimes the data skips over placements. winPlacePerc - The target of prediction. This is a percentile winning placement, where 1 corresponds to 1st place, and 0 corresponds to last place in the match. It is calculated off of maxPlace, not numGroups, so it is possible to have missing chunks in a match. Link-https://www.kaggle.com/c/pubg-finish-placement-prediction/
TraXIcoN /
This repository is for the UGAHACKS X hackathon (Participated as a solo hacker)