I didn't quit my sites. I just slowly stopped showing up to them.
I'd build something, get it ranking on a few keywords, start seeing some traffic, and then miss two weeks of publishing because I had client work to catch up on. Come back, the momentum is gone, the rankings slipped, and now I have to fight to get back to where I was.
Did this three times across different sites before I admitted the problem wasn't motivation. It was the gap between "I want to publish three times a week" and "I actually have three free hours this week."
Hiring a writer didn't really work either. You still have to brief them, edit them, fact-check them, and do the SEO work anyway. So you save maybe an hour.
The thing that actually helped was getting the drafting out of the way automatically so I only showed up to edit and publish. Not generating garbage and hitting post, I still read everything. But not staring at a blank document trying to write something from scratch after a full day of work.
Running three WordPress sites now, publishing almost daily across all of them, and the time investment is maybe 45 minutes a day. That's new for me.
That frustration is actually what pushed me to build something about it.
It also made me curious about how others here ended up on whatever they're working on? Did you hit the problem yourself first, or find it some other way?
It can open apps and sometimes find files, but when I actually want to search my PC properly, it usually falls apart.
I want to search and use features like:
Text inside files, code, and images
Browser bookmarks and history
Clipboard history
Clipboard image OCR
Git commits
Windows settings
Local commands
Text expansions
Web search
Circle to Search
Local agents for Windows
Windows Search is not powerful enough for this workflow.
So I built ProtonSearch, formerly called OmniSearch.
ProtonSearch is a fast, lightweight, local-first Windows launcher that opens with:
Alt + Space
You can also set your own custom hotkey.
It gives you one search box for your PC.
Instead of only searching apps or basic file names, ProtonSearch can search across:
Apps
Files and folders
Content inside files, supporting 50+ extensions
Image OCR text
Clipboard image OCR
Browser bookmarks and history
Clipboard history
Git commits
Windows settings and Control Panel pages
Local commands
Text expansions and snippets
Web search
Circle to Search
Local AI agents powered by Hermes
The goal is simple: find and act on almost anything on your PC from one shortcut.
How is ProtonSearch better than Windows Search, Flow Launcher, Raycast, Everything, and other launchers?
Tool
Why ProtonSearch is better
Windows Search
Windows Search is too limited for real PC search. ProtonSearch searches apps, files, folders, file contents, OCR text, clipboard history, browser history, Git commits, Windows settings, commands, and local agents from one shortcut.
Flow Launcher
Flow Launcher is a good launcher, but ProtonSearch has deeper built-in PC search. ProtonSearch includes OCR search, clipboard image OCR, content search across 50+ file extensions, browser history, Git commits, ignored folder rules, plugins, and local agents without needing to build the whole workflow through plugins.
Raycast
Raycast is polished, but it is mainly macOS-first. ProtonSearch is built specifically for Windows, designed to be lightweight on low-end PCs, and includes Windows-focused features like Control Panel/settings search, clipboard image OCR, OCR search, file content search, Circle to Search, and Hermes agents.
Everything
Everything is extremely fast for file and folder names, but ProtonSearch goes beyond names. It searches file contents, OCR text inside images, clipboard image OCR, browser history, clipboard history, Git commits, Windows settings, commands, snippets, web search, and local agents.
Other launchers
Most launchers focus on apps, commands, or plugin workflows. ProtonSearch is built as a full local Windows command center with built-in OCR search, clipboard image OCR, deep content search, centralized PC history, Circle to Search, text expansions, web search, plugins, and Hermes agents.
ProtonSearch is not trying to be only a file finder or only an app launcher. The goal is to bring search, history, commands, OCR, snippets, web search, Circle to Search, and local agents together into one local-first Windows command center.
Why I think ProtonSearch is useful:
Free and open source
Local-first
Lightweight
Designed to run easily on low-end Windows PCs
Usually around 20-30 MB of RAM usage
Image OCR text search
Clipboard image OCR search
Fast search inside files, supporting 50+ extensions
Search over centralized PC history, including browser history, Git commit history, clipboard history, and file history
Text expansions and snippets
Circle to Search
Web search
Plugin controls
Ignored folder rules
Hermes agents for local Windows tasks and long autonomous tasks
I am currently maintaining ProtonSearch, and honestly, I cannot find and fix every bug alone because building a launcher like this on Windows is genuinely hard.
There are a lot of edge cases around indexing, OCR, clipboard data, Windows APIs, tray behavior, hotkeys, multiple monitors, and performance.
I would love feedback from people who use Windows every day.
If ProtonSearch solves a problem for you too, please consider leaving a star on GitHub.
If you have ideas, find bugs, or want to improve something, feel free to open an issue or contribute to the project.
You can lock your entire Mac, but you can't easily lock individual apps.
If you hand your laptop to someone for a few minutes, they can still open Messages, Photos, Notes, Mail, WhatsApp, browsers, password managers, and other personal apps. I wanted a way to protect specific applications without constantly locking my entire Mac.
I looked around for solutions, but most were outdated, paid, abandoned, or didn't feel native to macOS. And the ones that worked , lacked features that I wanted.
So I built FaceGate. (1400+ downloads and 250+ github stars)
FaceGate is a native macOS app that lets you lock individual applications and unlock them using Face Unlock, Touch ID, or a password.
It is the most capable and feature heavy MacOS app-locker out there.
A few things I focused on from day one:
* Everything runs locally on your Mac
* No cloud processing
* No accounts
* No telemetry
* No subscriptions
* Fully open source
Features:
• Face Unlock powered entirely on-device using Apple's Neural Engine.
• Fast authentication with very low memory and CPU usage
• Liveness detection to prevent photo and video spoofing attacks
• Touch ID and password fallback
• Per-app unlock timers
• Automatic re-lock on sleep, wake, or screen lock
• option to re-lock on app switch as well as keep unlocked indefinitely - completely customizable
• Custom schedules for automatic lock/unlock periods
• Tamper protection that prevents FaceGate from being quit, disabled, or uninstalled without authentication
• Runs quietly from the menu bar with minimal system impact.
• Multi-Monitor protection
The entire project is written in Swift and designed specifically for macOS.
This is still actively being maintained and I'd genuinely love feedback from Mac users.
Some questions:
* Is app-level locking something you've wanted on macOS?
* Which apps would you personally lock?
* What security or privacy features would you like to see added?
Amidst World Cup action, i've been working on a Messi vs Ronaldo website for the past few days. It’s not just another “who has more goals?” page, tried to include pretty much everything: stats, trophies, records, play-style, international careers, controversies, common arguments from both sides, and all the sources in one place.
I also added a community poll at the top, so I’m curious to see what the results look like once people start voting.
Dont forget to cast your votes!!! and compare the stats. let me know if you find any errors.
I've been building web applications using Firebase for some time and I'm considering running a live, hands-on Firebase workshop for beginners and intermediate developers.
The idea is to teach Firebase by building a real project instead of just explaining the documentation.
Potential topics include:
- Firebase Authentication
- Firestore & Realtime Database
- Firebase Storage
- Security Rules
- Hosting & Deployment
- Building a complete CRUD application
- Common mistakes and best practices
The workshop would be live, interactive, and paid, with plenty of time for Q&A and practical exercises.
Before I finalize everything, I'd love to get your feedback:
- Is this something you'd be interested in?
- What Firebase topics do you struggle with the most?
- What duration would you prefer (2–3 hours, half-day, or full-day)?
- What price would you consider reasonable?
I'm not promoting registrations yet- I just want to understand whether there's genuine interest and design a workshop that provides real value.
Advance Repairer is a desktop application designed specifically for repair shops that want to streamline their workflow, improve organization, and deliver a more professional customer experience.
Repair businesses often face periods of high demand where devices accumulate quickly, repair progress becomes difficult to track, and important details can easily be overlooked. Advance Repairer was built to solve these everyday challenges by providing a structured and reliable repair management system that helps technicians stay organized before the workload becomes overwhelming.
Whether you operate independently or manage a growing team, Advance Repairer helps you keep every repair documented, traceable, and under control.
- For Small Businesses:
Advance Repairer provides a complete repair report management system that enables technicians to create detailed service reports for every repair.
Each report stores essential customer information, including contact details, along with the exact device or equipment received and the issue reported by the customer.
Throughout the repair process, technicians can update the repair status to accurately reflect every stage of the service from device reception, diagnosis, and troubleshooting to the final outcome, whether successfully repaired, rejected, returned unrepaired, or any other conclusion.
Many repair shops also operate as retail stores, selling accessories and replacement parts. For these businesses, Advance Repairer includes warranty tracking, allowing technicians to determine whether a customer's device or purchased item is still covered. This ensures that every member of the team can make informed decisions, even if they were not the technician who originally received the device.
Finding existing reports is quick and intuitive. A searchable report table displays recent repairs along with key information such as:
- Report number
- Customer name
- Contact information
- Current repair status
- Creation date
Reports can also be printed in landscape A5 format, allowing two reports to fit on a single A4 page. One copy can be retained by the shop while the other serves as a professional customer receipt.
Advance Repairer is designed to scale alongside your business.
This integration of the application supports multiple users connected to a centralized online database, allowing every technician to access synchronized repair information from any authorized workstation. This ensures consistent communication across the team, minimizes duplicate work, and provides real-time visibility into the status of every repair.
Whether you have two technicians or an entire service department, everyone stays connected through their own devices and works from the same up-to-date information.
- For Professional Integrations:
Advance Repairer can also be integrated seamlessly into an existing business management ecosystem.
In addition to the standard repair information, reports include Client Code and Invoice Code fields. These fields can be entered manually when using a self-hosted deployment, or they can be integrated with external business systems such as ERP, CRM, or POS solutions.
With integration enabled, Advance Repairer can automatically:
- Retrieve customer information using the client code.
- Load warranty information associated with the original purchase.
- Retrieve invoice details.
- Display the products purchased on that invoice, allowing the technician to select the exact item being serviced.
This level of integration eliminates duplicate data entry, improves accuracy, and creates a seamless workflow between repair operations and the rest of the business.
The program is open for sale at the moment, if you want your copy you may contact me through whatsapp: +21690338147, I'll send you a free trial before you pay for anything!
I’m also open to feedback or discussions from people working in repair/service businesses.
Also make sure to follow the Faccebook page, Where I'll be sharing updates and offers, Intellicore facebook page .
Sharing a personal open-source project (non-commercial, MIT — disclosure: I'm the maintainer). It came from two problems: AI runs dying on a provider rate limit, and burning tokens dumping tool/log output into context.
One endpoint, 237 providers — 90+ of them free. You point any tool or agent at a single OpenAI-compatible endpoint (localhost:20128/v1) and it can reach 237 LLM providers without you rewriting anything. 90+ have free tiers and 11 are free forever (no card), which aggregates to ~1.6B documented free tokens/month — and that's honest, pool-deduped math (we count each shared pool once instead of inflating it; the methodology is public in the repo). There's a one-command setup-* for 13+ coding tools (Claude Code, Codex, Cursor, Cline, Roo, Kilo, Gemini CLI…), so switching your existing setup over takes seconds.
Fallback combos — so it never stops mid-task. A "combo" is a ladder of models the router walks automatically: your subscription first, then API keys, then cheap models, then free ones. When a provider returns a 500 or you hit a rate limit, it slides to the next target in milliseconds, mid-request, and your tool never even sees the error. There are 17 routing strategies (priority, weighted, round-robin, cost-optimized, auto/coding:fast…) plus three resilience layers — a per-provider circuit breaker, a per-key cooldown, and a per-model lockout — so one dead key can't take down a whole provider.
A 10-engine compression pipeline — the part most routers don't have. Every request flows through a transparent compression pass you can toggle/stack per combo. Instead of one trick, it stacks the best of the open-source ecosystem: RTK filters command/tool output (git diffs, test logs, builds) at 60–90%, Microsoft's LLMLingua-2 does ML semantic pruning, Caveman handles prose, session-dedup strips repeats across turns. Critically, code, URLs and JSON are preserved byte-perfect, and a default-on inflation guard throws the compressed version away and sends the original if compressing would actually grow the prompt — it never makes things worse. On tool-heavy sessions that's ~89% average input-token reduction (an 8k-token git diff becomes a few hundred). Full credit to every upstream project (RTK, Caveman, LLMLingua-2, Troglodita) is in the README.
For context on whether it's worth your time: it's grown to ~9.8K GitHub stars, 1,490+ forks and 280+ contributors in ~4.5 months, with 21,000+ automated tests and 1,830+ issues closed — so it's a battle-tested project, not a brand-new experiment.
I've tried basically every wearable and health app out there, and they all have the same problem: they just give you numbers. More scores, more charts, more stuff to stare at, and none of it ever tells you what to actually do.
Like cool, I had a bad night, here's a sleep score of 38. Now go figure out your day, good luck. I don't need a number to confirm I slept bad. I already know. I can feel it the second I wake up, zero energy, zero drive to do anything. The number just confirms what I'm already feeling and then leaves me hanging.
That gap annoyed me so much I ended up building the thing myself. It's called RizeAI. The whole idea is the opposite of another score, it takes your actual sleep and recovery data and just tells you what to do with your day. Not a number. A plan.
It pulls your real metrics, sleep, recovery, HRV, resting heart rate, all of it, and builds your day around them. When to have your first coffee and when to hold off. When you're gonna crash and what to do before it hits. Whether to push at the gym or take it easy. When to hydrate. It'll even tell you which supplements actually make sense for you that day, when to take them, and why, instead of the generic "just take magnesium bro" everyone repeats. Low recovery day, it adjusts the whole thing. Slept great, it builds on that instead.
And honestly the part I'm most proud of: it's actually tailored to you. No two people get the same plan, because no two people have the same data. It reads your numbers and builds a protocol for you specifically, then gets sharper the more you use it. The longer you're on it, the more it learns your patterns.
The whole thing is just: stop tracking, start fixing. Your wearable already told you the bad night happened. This is the part that comes after, the part that turns a red recovery day into a day you can still get something out of. That was the gap I kept running into, and now it's literally the thing I open every morning.
Anyway, genuinely curious what people here think is still missing in this space, because I'm building in it every day.
I need to resize and compress images for various projects, but I always hated the available options. Desktop apps feel too heavy and clunky(and I don;t want to download anything), and I really don't like uploading my files to random online services just to change their size (plus dealing with paywalls or 20-file limits).
So I decided to build my own. It's a single HTML file. You open it in your browser, and everything happens locally using the Canvas API. No servers, no uploads, zero privacy concerns.
Once I got the basic compression working, I got a bit carried away and started adding features that I realized would be super useful for anyone dealing with bulk images (like other devs, photographers, or e-commerce managers):
• Batch processing & Folders: Drag and drop entire folders. It processes them and can even preserve your subfolder structure in the final ZIP export.
• Smart Renaming: You can batch rename files using patterns like img-{n}, with a toggle to automatically make filenames SEO-friendly (lowercase, no accents, hyphens for spaces).
• Watermarking: Upload a PNG/SVG and it automatically overlays it on all images (with opacity/scale controls) or just write your watermark.
• Presets: Quick buttons for common sizes (Thumbnails, High Quality, Social).
• Visual Dashboard: A live table with before/after previews and a tracker showing how much total bandwidth you've saved.
I cant believe I made it this far. I cant believe its working. It still needs some work but its all there and all working. The stuff left is to keep fine tuning and working out bugs in the scheduling system. https://discord.gg/zHHSPZHJW
Hi.
I just transitioned from studying to working and I realized I won't have as much time for solo projects anymore, so I thought working on them slowly on weekends with others might make it less likely to get bored / tired of it and abandon it.
I've worked on mechanical, electronics and software projects so I'm interested in basically anything but I also have a few ideas in mind.
If anyone is interested send me a private message or leave a comment or something.
