今日已更新 246 条资讯 | 累计 21112 条内容
关于我们

标签：#git

找到 1127 篇相关文章

开源项目

🔥 OpenMOSS / MOSS-TTS - MOSS‑TTS Family is an open‑source speech and sound generatio

GitHub热门项目 | MOSS‑TTS Family is an open‑source speech and sound generation model family from MOSI.AI and the OpenMOSS team. It is designed for high‑fidelity, high‑expressiveness, and complex real‑world scenarios, covering stable long‑form speech, multi‑speaker dialogue, voice/character design, environmental sound effects, and real‑time streaming TTS. | Stars: 2,051 | 53 stars today | 语言: Python

2026-05-28 原文 →
开发者

Copilot helped me deploy my passion project to the App Store

What I Built I’ve always had a love-hate relationship with technology. In college, I majored in computer science and took classes ranging from electrical engineering to human-computer interaction. From soldering transistors on a physical circuit board to designing UI/UX experiences, I’ve touched many layers of the computing stack—and I’m constantly mind-blown by every new piece of the puzzle I learn. However, my experience as a user of technology before studying it was very different. In middle school and high school, my phone made me feel anxious, stressed, and cynical. I felt lonely on social apps and isolated when I deleted them. I remember some summer days in middle school spent alone in my bedroom watching YouTube, where I was recommended extreme dieting videos. Back when I had no idea what an algorithm was, I still knew I was being harmed by them. By my sophomore year of college, I had deleted Instagram and TikTok and turned off YouTube recommendations. While this protected me from harmful and extreme content, I also missed important life updates from my close friends and family. After taking a web development class and learning how to build a basic card layout, I decided to try building my own social app: Lumira. My goal was simple. I wanted to create a mobile, personal feed of photos just from my friends and family, curated by their genuine interests and sorted by time. Demo https://youtube.com/shorts/DwbVU_LFOc0?si=9H5zPovzIbbW8t-i https://apps.apple.com/us/app/lumira/id6737853449#information The Comeback Story Lumira was born out of 3:00 AM manic coding sessions in my college apartment. This was my first fully end-to-end deployed and distributed application—and it was rocky. My code was chaos. My files were unorganized, and I followed no real patterns, but the thing that motivated me to keep going was that it somehow kind of just worked. I remember the sense of accomplishment I felt the first time I connected to my Firebase backend and saw a photo successf

2026-05-28 原文 →
AI 资讯

I Built Sổ Lãi, a Practical Profit Tracker for Vietnamese Online Shops

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built I built So Lai , a local-first profit tracker for small online shops in Vietnam. The goal is simple: help a seller answer the question they often cannot answer from platform revenue alone: Is my shop actually profitable after product cost, marketplace fees, shipping subsidies, discounts, ad spend, returns, and pending COD? So Lai is not trying to be a full POS, CRM, or inventory suite. It focuses on the painful middle layer that many small sellers still manage through scattered spreadsheets: Product cost by SKU Orders from Shopee, TikTok Shop, Facebook, Zalo, or livestream sales Platform fees, shipping cost, vouchers, and discounts Ad spend by channel and SKU Return/cancellation status COD received vs. pending Net profit by order, product, and sales channel The app runs locally with Node.js and JSON storage, so it does not require paid APIs or cloud setup. GitHub repo: https://github.com/klauski24/so-lai Demo Run locally: git clone https://github.com/klauski24/so-lai.git cd so-lai npm start Open: http://127.0.0.1:4182 What the demo shows: A Vietnamese-language dashboard called Sổ Lãi Shop profile setup Clear explanation of where the numbers come from CSV import for products, orders, and ad costs Manual order entry Profit analysis by channel and SKU Alerts for loss-making products, high COD pending, and high return rate CSV and Markdown report export Screenshots are included in the repository: so-lai-desktop.png so-lai-mobile.png The Comeback Story The first version was too vague. It started as an English-named dashboard called ProfitLens . It had some useful calculations, but it did not feel practical yet. The biggest problems were: The app used Vietnamese currency but had an English product name. There was no place to define the shop. It was not clear where the data should come from. The dashboard looked like a demo, not something a seller could actually use. I reworked the project into So

2026-05-28 原文 →
AI 资讯

GitHub Suspended My 2-Year Developer Account — Here’s What I Learned

𝗚𝗶𝘁𝗛𝘂𝗯 𝗦𝘂𝘀𝗽𝗲𝗻𝗱𝗲𝗱 𝗠𝘆 𝟮‑𝗬𝗲𝗮𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗔𝗰𝗰𝗼𝘂𝗻𝘁 — 𝗛𝗲𝗿𝗲’𝘀 𝗪𝗵𝗮𝘁 𝗜 𝗟𝗲𝗮𝗿𝗻𝗲𝗱 A few days ago, something happened that genuinely shook me as a developer. My GitHub account, KelvCodes, which I had used and built on for over 2 years, got restricted unexpectedly. At first, I thought it was a mistake that would be resolved quickly. I had experienced a temporary restriction before that was lifted within a short time, so I assumed this would be similar. But this time was different. Suddenly, I lost access to years of work and history tied to my developer identity: · 60+ projects · 110+ stars · 50+ followers · client work · collaborations · repositories connected to applications and opportunities For context, GitHub was not just a coding platform for me. It had become part of my professional identity as a software engineer. My resume linked to it. Applications linked to it. Opportunities came through it. In fact, some people literally looked at my GitHub profile before deciding to work with me. That's what made this experience difficult. The Emotional Side Nobody Talks About When developers lose access to an account, people often think: "Just create another account." But when you've spent years building a reputation, consistency, commit history, projects, and credibility under one identity, it doesn't feel that simple. It feels like losing a digital portfolio you carefully built over time. And honestly, for a moment, I felt stuck. Do I wait endlessly for support? Do I pause my work? Do I rebuild everything from scratch? What I Decided After thinking about it deeply, I realized something important: I cannot pause my growth waiting for a platform decision. So I made the decision to continue building. I created a new GitHub account: 👉 https://github.com/kelvinagyareyeboah And while I still hope my old account may eventually be restored, I'm no longer allowing the situation to stop my momentum. Lessons I Learned From This Your skills matter more than one platform Platforms are important

2026-05-28 原文 →
AI 资讯

From a Forgotten Multiplayer Prototype to a Chaotic Hidden-Object Game — Reviving WhatUsee 🚀

GitHub Finish-Up-A-Thon Challenge Submission There’s something strangely emotional about reopening an old unfinished game project. Especially one that once felt like “the next big idea” at 2 AM during a hackathon 😭 You open the folder expecting nostalgia… …and instead find: broken UI random commits duplicated code missing assets unfinished features and functions named things like test2_final_REAL.js That’s exactly what happened when I reopened WhatUsee . A multiplayer browser game I originally started building as a fun experimental idea. At first, it wasn’t meant to become anything serious. It was just a simple concept: “What if players had to race against each other to identify hidden objects inside chaotic images?” That tiny idea slowly turned into a real-time multiplayer hidden-object game. And honestly? At the beginning, building it was insanely fun. 💡 The Original Idea Behind WhatUsee Most multiplayer browser games focus on: shooting drawing trivia racing But I wanted something different. Something that created those chaotic: “WAIT I SEE IT—NO WAY 😭” moments. The idea was simple: Players join a room together. An image appears. Somewhere inside that image is: a hidden object an animal a logo a random item or something cleverly camouflaged And everyone races to identify it before the timer ends. Fast reactions. Visual focus. Pure multiplayer chaos. That became WhatUsee . At first, the project was extremely small. Just: Socket.IO basic image display simple guessing and a rough scoreboard No polish. No proper lobby. No smooth UI. But even in that early state… …the game already felt fun. And that’s what made me continue building it. 😭 Then The Project Slowly Got Abandoned Old unfinished WhatUsee multiplayer game interface with basic UI and minimal styling Like most side projects… life happened. College work. Burnout. Other responsibilities. Random unfinished ideas. And slowly, WhatUsee became: “that project I’ll definitely finish later.” The game technically worked.

2026-05-28 原文 →
← 上一页 下一页 →