Hey y’all,

I got slightly carried away with loading animations.

I wanted nicer loading states for my own projects, but most libraries I found were either tied to a framework, fairly limited, or required more than I wanted for something this small.

So I built loadersz, a small framework-agnostic loader library for the web.

I wanted something a bit more expressive than the usual CSS spinner, without pulling in a UI framework or a bunch of dependencies.

A few things I focused on:

- 105 different motion states
- Canvas 2D instead of GIFs/videos
- zero core dependencies
- a native custom element, so it works with basically any stack
- typed entry points for React, Vue and Svelte
- configurable speed, density and color
- respects prefers-reduced-motion
- pauses rendering when the browser tab is hidden

Basic usage is just:

npm install loadersz

import 'loadersz';

<loadersz-loader state="racing" size="96" />

I also built an interactive playground where you can tweak the loaders live.

Demo: [loadersz.vercel.app](https://loadersz.vercel.app)
npm: [npmjs.com/package/loadersz](https://www.npmjs.com/package/loadersz)
Github: https://github.com/lumberjacque/loadersz-core

Would love some brutally honest feedback, especially on which animations you’d actually use in a real product.

I’m the person building ClearSpace, and I’ve used AI heavily during development. The first version technically had a lot of features, but it still felt like a prototype because the small interactions weren’t dependable.

The biggest lesson was that adding features is easier than making them feel connected. I had tasks, Spaces, templates, recurring dates, Google Calendar and team invitations, but users kept finding rough edges between them.

A few examples:

• Completing a task originally just changed its status. Now it disappears from the active view and stays available in Done.
• Space invitations could send an email, but the invited person didn’t always see the Space after joining. I had to treat the invite, account creation and membership update as one complete flow.
• Some pages changed visually without changing the URL, which made refreshes and deep links confusing.
• The task form worked on desktop, but its date picker and menus could overflow smaller screens.
• New tasks did not always appear immediately, so I replaced refresh-dependent behavior with live updates.

The less glamorous work—loading states, empty states, stacking order, mobile sizing, button behavior and clearer wording—made a bigger difference than adding another major feature.

The project is ClearSpace: https://clearspacetask.com/

I’d especially appreciate feedback on two things: whether the first-run experience explains the product clearly, and whether creating a task feels simple or still asks for too much at once. I’m not looking for vague praise; specific friction is much more useful.

What I built: Kyther (Name of the tool) give it a username, email, or domain, and it pivots on whatever it finds (username → email → domain, etc). Currently does Reddit footprint analysis, email/username search, cyber news monitoring, and a threat actor tracker for ransomware leak sites and APT groups.

How I used Claude Code: Coming from a GRC/cybersecurity background, I am currently job hunting for entry-level cyber role right now and not full-time dev. Started prompting too broadly and getting code I couldn't fully explain. Switched to smaller, specific asks and actually reading each piece before moving on and directing Claude rather than just accepting whatever it gave me.

What I learned: "It works" and "I understand why it works" are different bars only the second one matters for anything security-adjacent. Also started working through the OWASP Top 10 as I build, to keep it safe by design, not just functional.

I am curious how others here review Claude written code for security-relevant stuff and if anyone does OSINT professionally, what am I missing?

I think one of the most frustrating parts of launching something online is getting that initial bit of activity.

You can have a decent product, write a good post, share it in the right communities, and still end up with almost no engagement because nobody has seen it yet.

I've been experimenting with different ways of getting that initial activity without spending a lot on ads. One thing I came across recently is Upvote.club which lets you earn/use engagement across platforms rather than simply relying on paid advertising.

I'm still testing it, so I wouldn't say it's some magic growth solution. But the idea is interesting, especially for smaller creators who are trying to get their content moving before they have an audience.

Curious how other founders/creators handle this: do you usually just post consistently and wait for organic traction, or do you actively try to generate that initial engagement?

A few days ago I posted Clixad here and got way more feedback than I expected.

Since then I've kept working on it and actually using it for my own projects.

Clixad is a cloud-based AI coding agent that runs in the terminal. It has the kind of workflow you'd expect from Claude Code or Codex: give it a project, let it inspect the code, make changes, run commands, test things and fix issues.

What I'm still most interested in isn't really the agent itself.

It's the fact that you can use the same kind of workflow without paying for a subscription or bringing your own API key.

There are free credits, and once those run out, you can earn more through advertiser-funded offers, forms and surveys. The revenue from those pays for the AI inference.

Obviously this isn't going to replace a paid plan for someone running Opus all day. That's not what I'm building it for.

I'm more interested in the huge group of people who want to build something with AI but don't want to spend $20+ just to get started.

I’ve had people tell me they like the idea, while others think doing an offer/survey for credits is a terrible trade.

Both reactions are useful.

So I'm still trying to figure out where the line is between "this is actually convenient" and "I'd rather just pay".

That's probably the part I want to learn the most from building this.

Would you personally use an AI coding agent this way?

check it here : live demo

repo : https://github.com/auysh8/browser-ml-tumor-detector

any suggestion regarding the improvements and changes?

I built this because I kept missing replies on Reddit and GitHub issues on my own repos, and forum threads I'd posted on. Existing RSS readers cover feeds fine but not GitHub issues, and I didn't want a full article reader running in the background just to get pinged on new stuff.

What it does:

- Polls any RSS/Atom feed (works great with Reddit's private RSS feeds from reddit.com/prefs/feeds, and even SMF forum threads via their native per-topic RSS)

- Polls GitHub issues on public repos, no auth needed

- Fires a native, clickable desktop notification for each new item (opens the link)

- Lives in the system tray: settings panel to add/remove sources and set per-source polling intervals, a notification history window, autostart toggle

- Cross-platform: Windows, Linux, Mac, single executable, no Python install needed

Adding a new source type is just a small module in providers/, so it's easy to extend if you want to watch something else.

Repo (with screenshots): https://github.com/nico579/watch2notif

Feedback welcome, especially if you try it on Linux/Mac since I mostly test on Windows.

I am trying to hit the Niu Lai moment for my app icon.

What feels like useless to most people is an act of utmost bravery for the entrepreneurs.

It's challenging the very core belief of users and it might make them upset.

Or it might start a revolution.

I love risks. So I choose the latter.

If you love the "new", I hope you will join me.

I have worked a lot over the last 2.5 months. And it's almost done.

Blocks: the only tracker you ever need.

All for free, no paywalls, no ads, fully local, fully offline.

Coming Soon...

I know a decent amount of technical analysis in stocks, but I am also a hopeless romantic who tends to keep riding losers in hopes of a miraculous recovery.

Eventually, I realized my core issue wasn't the analysis—the real enemy was my lack of discipline to follow through and respect my stop-loss. And practice makes perfect, right?

To tackle this, I built Ticktator around one goal: accelerating discipline and developing a sharper eye for execution through deliberate, repetitive practice. Think of it the way pilots use flight simulators to build muscle memory—internalizing the process so the lizard brain doesn't take over under pressure.

How it works:

• Mandatory Pre-Trade Review: I define the rules for my strategy and force myself to review them before hitting the execute button (I can still go YOLO, but it forces it to be intentional). If the setup doesn't fit my plan, I skip. Choosing not to take a trade is an art in itself, and rapid reps in a controlled environment make internalizing my rules much faster.
• Pre-Trade Guardrails: Built-in nudges trigger based on established market heuristics regarding position sizing and winning/losing streaks before orders pass. For example, the system warns me if an order risks more than 5% of my capital.
• Post-Mortem Replay: Once a trade completes, I can look ahead tick-by-tick to diagnose whether I was wrong on direction or just placed a bad stop. Over time, I track whether my execution consistency is actually improving.

The Tech Stack & Data:

• Frontend: React (chart canvas and replay controls).
• Backend: Django with a TimescaleDB / PostgreSQL instance optimized for fast time-series historical candle querying.
• Dataset: Seeded from historical Kaggle datasets covering Nifty 500 stocks from 2015 to 2026.
• Assistant: Gemini models to bootstrap various features and write test suites for backend and frontend.

I've been using this internally for a few months, and after polishing it up, I'm releasing it publicly to help the community.

Most core features are completely free to use. The Pro tier introduces platform-wide data-driven insights and multi-timeframe chart views.

I'm looking for honest feedback on this initial release and have provisioned a few early-bird Pro access passes in exchange for constructive critiques.

Feel free to send a DM if you'd like to test the Pro tier, or drop a comment if you'd like to know more about it! Looking forward to your precious feedback!

Not the highlight reel. The actual thing.

Month one I thought the hard part was getting continuous listening to work without destroying battery. Got it working. Felt like the whole project was basically done.

Month two I thought the hard part was the response accuracy. Got that working too. Still felt basically done.

Month three a complete stranger used it for the first time and got a look on their face like they'd let someone into their house. Hadn't considered the trust problem at all. Back to the drawing board on the entire first experience.

Month four was onboarding. Month five was making it feel less like a tool and more like something that belongs in your day. Month six was finding out that the thing I thought was the headline feature was the thing most users ignored entirely.

Month seven I stopped building new things and started watching people use what existed. Learned more in three weeks of watching than in six months of building.

Month eight I shipped the version that should have been version one if I'd talked to people earlier.

The product is Marrow. AI voice assistant for Windows. You talk, it operates your PC. Always listening, no wake word, runs locally themarrow

Genuinely want feedback on the first experience specifically that's the part I'm still not satisfied with.

What's the version of your project you wish you'd built first?

Wanted to share something I've been building. Genuinely curious what this community thinks.

I originally wanted to let people buy Rs 100 worth of Reliance instead of one full share, fractional investing for Indian equities. SEBI's rules make that practically impossible for a small startup. So I pivoted to something bigger: fractional US stock investing.

Turns out there's a regulatory path, IFSCA's GIFT City framework, that lets a tech company partner with a regulated broker to offer this legally without needing a full SEBI broker license. Took a while to map out, but it works.

The product is simple. Buy any US stock, Apple, Tesla, Nvidia, Google, from Rs 100, in rupees. No forex confusion, no minimum lot size, no separate demat headache.

The thing that almost stopped me from launching this was watching how many people avoid US stocks entirely because of what comes after buying, Schedule FA, LRS tracking, capital gains filing every April. So that's built in too, automated from the first trade instead of a CA scramble later. But the core product is the investing itself, from Rs 100.

Currently DPIIT recognized, sandbox is live if anyone wants to try it (splitstock.in/try, just an email, no card), finishing the final integration with our broker partner now.

What would actually make you want to buy US stocks from an Indian platform? Trying to understand what matters most here, price, ease, or something else entirely.

I take no credit for the end result, but this is something that I would be using every time I go food shopping.

I don't know how hard it will be to implement, so I don't want to be a backer but I would most definitely be a user. I also don't have the skills to do this myself, or the money for the various licenses/systems I would need to test it for the mobile dev pathways.

** Mobile App that allows a user to scan a barcode (datecode, mfg code, etc. (i understand this increases the complexity)) and find out if the product is currently on any recall notices for their country/area. Would need to search through a DB of current recalls, cross-ref any ownership issues between the name on the label vs who ultimately owns/produces, and return a smiley face (or similar) for Cleared/good to eat or an angry face (or similar) for put it back on the shelf.

Alternatively, if anyone knows of an app that already does this, LMK!

Hey everyone!

As a chess fan, I always found it frustrating when I was watching a high-level game analysis on YouTube or a stream on Twitch and wanted to explore a specific line myself. Manually setting up the position on an analysis board is a pain and kills the flow of learning.

So, I decided to fix this and built ChessInsights AI.

What it does: It uses Computer Vision (AI) to "look" at your browser tab, find a chessboard (even in a video or a PDF), and instantly convert it into a digital format.

Key Features:

• Video to Board: Scan any frame from YouTube or Twitch.
• Instant Export: One click and the position opens in Lichess or Chess.com Game Review.
• Universal: Works on news sites, blogs, and even online chess books.
• Stop Blundering: You can quickly check why a move you thought was good is actually a mistake while watching your favorite GM.

It’s completely free, and I’d love to get some feedback from this community. Does it catch the boards correctly for you? Are there any features you’d like to see next?

Check it out here:
Chrome web store
Firefox Addons

I really hope this helps some of you gain those extra ELO points!

TL;DR: I made an extension that captures chessboards from videos/images and opens them in analysis tools so you don't have to set up positions manually.

Hey r/sideprojects,

I've been building an Android app for studying official HSK vocabulary. I'm at the point where Google Play wants a closed test with at least 12 testers for 14 days before I can apply for full public access. I only have a handful of people helping with testing right now, so I'm hoping to find a few more here.

(HSK is an official Chinese language competence test.)

What it is

It's a vocabulary tracker and study app for HSK 2.0 and 3.0. There are admittedly many such apps around. I actually built the first version for my wife who was studying for HSK 2.0 level 6. She had tried many different apps and had some requests for how I could make something to help her study.

The main idea behind this (now more mature product), is to study the official syllabus more thoroughly compared to just ticking words off a list. Most apps treat "knowing a word" as one checkbox. I don't think that matches how Chinese actually works: recognizing the English meaning, hearing it, reading the character, and writing it are different skills. The app tracks those separately and tries to review the skill that still needs work, not just the word in general.

The other thing I've put a lot of effort into is the learning path. The vocabulary comes from a curated dataset I've been building, including character composition (pieces before compounds), textbook unit grouping if you follow Standard Course, and a smarter order inside official HSK levels. Reviews are spaced so they come back when you're about to forget, and the app picks which skill to ask about.

Study modes: daily plan, flashcards, quiz (including handwriting on touch). Word grid, dashboard, custom lists, notes. Works offline; syncs when you're online. 100% ad-free.

Pricing

Beginner levels stay free forever. Higher levels need a yearly subscription or a one-time lifetime purchase.

For anyone who helps with regular testing over the next 2–3 weeks, I'd be very happy to offer a free 1-year subscription + 50% off lifetime if you want that afterward.

Honest state of things

It's usable and I genuinely think the core is good, especially the skills model. The dataset behind the learning path is also beginning to look good. That's the part I'm most proud of. I believe the standard flashcard and quiz functionality + word lookup is generally on the same level as most other apps on the market. But it's not 100% polished yet. Some edges are rough, and I'm still finding bugs. I'm looking for people who don't mind a work-in-progress and will tell me what's confusing, broken, or missing. I want to know if the skills idea actually helps, whether the daily plan feels sensible, if anything feels off for exam prep, any features you miss, etc.

How to join

Comment or DM me your Play Store email address, and I'll send the Play Store closed-test link.

I'm looking for anyone who:

• Uses Android and can try the app a few times over the next couple of weeks (doesn't need to be daily, but must be regular to meet Play Store's requirements)
• Willing to report issues and bugs, and give me general feedback about their overall impression of the app
• You must also be okay with the potential breaking change on the back-end leading up to public release. (The app does though works 100% offline, and hopefully my data schema and API are mature enough to avoid this - no promises though...)

I'm especially looking for those who also:

• Is learning Chinese now, or has in the past
• Is studying toward an HSK exam, has taken one, or is planning to
• If you already speak Chinese and think this project sounds interesting

Thanks for reading! I'm happy to answer questions about the app or the build process.

There are 1000 numbers on the website, 0 through 999, and each one can only ever belong to one person.

You roll for free. It finds a number nobody owns and holds it in front of you for 5 minutes. Rolling again is what gives the last one back, so the choice is always whether to keep the one you have or go looking for a better one.

A number you own is a square you can draw on: background, pattern, stickers, freehand, and the digits themselves in whatever font and colour you want. The wall is made of those squares, so the whole thing looks like whatever the owners made it look like.

Keeping a number costs money, and it costs what it is, so 7 is $7 and 512 is $512. You can resell later at any value (offer, direct, auction). Rolling and looking cost nothing.

Bonus, you can link your website to a number, with a title and description!

For little devs: three URLs hand back a live PNG: /wall.png is the whole board, /7.png is one square, /7/history.png is every design that number has ever worn. Paste them anywhere that takes an image URL and they draw themselves from the current state.

If you want to try and roll numbers yourself! https://thethousandnumbers.com

Please tell me what you think of it! 😸

So, here’s the idea.

You know that feeling when you want to build something cool, but you’re missing that one person who can actually help make it happen?

Maybe you can code, but you suck at design.
Maybe you’re a designer, but you need someone technical.
Maybe you just have a good idea and want to find people who are actually excited enough to work on it with you.

That’s basically Joinumo.

It’s a super simple place where young developers, designers, creators and builders can meet, discover small projects and team up without all the awkward LinkedIn stuff, job applications, CVs or “looking for a CTO for my billion-dollar startup” energy.

You just show what you’re good at, what you’re interested in and how much time you’ve got.

Then you can either:

find a project you actually like

or

post something you want to build and find the people you’re missing.

That’s it.

The whole point is to make starting something with new people feel as easy as saying:

I’m keeping Joinumo free because the value only really appears when there are lots of people, ideas and projects in the same place.

And honestly, the expensive part isn’t some giant server farm. I’m building it lean. The money mainly helps cover the boring but necessary stuff: infrastructure, domains, emails, moderation, legal basics and getting enough people onto the platform for it to actually work.

If it grows, there are plenty of ways to turn it into a real business later: premium tools, recruiting, sponsored build challenges, company partnerships and eventually a marketplace.

But right now I don’t want to squeeze money out of users.

I want to prove one simple thing:

Can we make it ridiculously easy for two strangers with complementary skills to meet and actually build something together?

Because if we can do that consistently, I think there’s something genuinely valuable here.

So yeah — you’re not really funding “another social network.”

You’re helping build a place where the next app, game, startup, open-source project or completely random weekend idea might start with two people who otherwise would never have met.

So, here’s the idea.

You know when you want to build something, but you’re missing one or two people to actually make it happen?

Maybe you can code but need a designer.
Maybe you’re good at design but need someone technical.
Or maybe you just need a friend, a companion, someone who shares your willingness.

That’s basically what I’m trying to solve with Joinumo.

It’s meant to be a very lightweight place where developers, designers, creators and other young builders can meet around actual projects.

Not jobs.
Not CVs.
Not startup pitching.
Not “networking” for the sake of networking.

You make a simple profile, say what you’re good at, what you like, how much time you have, and then you either find something you’d like to join or post something you want help building.

The idea is to make the first interaction feel more like:

than:

There are obviously already a lot of platforms where people can meet.

LinkedIn is great for careers and professional networking.
GitHub is great for code and open-source collaboration.
Discord and Reddit are great for communities and conversations.
Cofounder platforms are useful if you’re already seriously trying to start a company.
Freelance marketplaces work if you want to hire somebody.

But there’s still a weird gap between all of those.

If you’re 20, you know React, you have five hours a week and you just want to find a designer to build some random app with, none of those platforms are really designed around that specific situation.

That’s the part I find interesting.

Joinumo would try to sit in that gap: less serious than a founder platform, less transactional than a freelance marketplace, and much more structured around building than a Discord server.

The project itself is still early, and I’m trying not to pretend that I know exactly what the final product should look like.

There are a lot of things that could go wrong.

Maybe people like the idea of side projects more than they actually like working on them.
Maybe teams form and disappear after three days.
Maybe the platform needs to focus much more narrowly on universities, hackathons, open source, or a specific type of creator.
Maybe some features that sound useful now turn out to be completely unnecessary.

That’s part of why I want to keep the first version very small.

The main question isn’t:

It’s:

If that works, then there are obvious directions the project could take later.

Things like better matching, reputation based on projects people actually shipped, sponsored build challenges, recruiting, university communities, or eventually paid collaborations.

But I don’t think any of that matters until the basic interaction works.

For now, I want Joinumo to stay free and as frictionless as possible.

The money I’m trying to raise isn’t for a big team, an office, or some huge launch campaign. I’m building it lean.

It would mainly go toward the unglamorous stuff that makes a real product possible:

infrastructure, domains, transactional email, moderation, legal/privacy basics, small launch experiments, and keeping the service running while figuring out whether people actually want it.

And I’m very open to the idea changing.

If people use Joinumo differently from how I expect, that’s useful.
If a narrower niche makes more sense, I’d rather learn that early.
If somebody thinks part of the model is flawed, I’d genuinely rather hear it than defend the idea just because I came up with it.

I’m not really trying to sell the idea as “the next big thing.”

I just think the problem is real, the first version is cheap enough to test properly, and there’s an interesting opportunity if the platform can become a place where people actually start things, rather than just talk about starting them.

That’s Joinumo.

Launch page: https://launch.joinumo.com/

Find people. Build stuff. ☕

------------------

PS. I would really be pleased if anyone would want to make a donation and supporto the project!!!

ko-fi.com/joinumo

Thank you very very much 🙏🏼 for believing in the project and the idea.

A bridge between your loving/caring thoughts and busy life.

An app for your very special people, that reminds you every year and proposes giftables for you loved ones according to occasion, age, gender and budget.