u/Imaginary_Drawer7827

Hey everyone,

We built **StrikeSense** for creators, streamers, editors, and YouTubers who want to avoid copyright claims, muted VODs, takedowns, and demonetization caused by music.

StrikeSense is a Windows desktop app that monitors your system audio, recognizes music, checks copyright risk, and warns you when a track may not be safe to use.

The goal is simple: catch risky music before you upload, publish, or go live - not after the damage is already done.

It can be useful if you:

* make YouTube videos or Shorts
* stream on Twitch or YouTube
* edit client videos
* use background music in content
* want an extra safety check before publishing

StrikeSense shows whether music looks **cleared / not cleared / unknown**, so you can make faster and safer decisions while creating content.

You can check it out here:

[https://strikesense.net\](https://strikesense.net/)

If you create content and want to reduce the risk of copyright problems, StrikeSense might be useful for your workflow.

Hey everyone,

We built StrikeSense for creators, streamers, editors, and YouTubers who want to avoid copyright claims, muted VODs, takedowns, and demonetization caused by music.

StrikeSense is a Windows desktop app that monitors your system audio, recognizes music, checks copyright risk, and warns you when a track may not be safe to use.

The goal is simple: catch risky music before you upload, publish, or go live - not after the damage is already done.

It can be useful if you:

• make YouTube videos or Shorts
• stream on Twitch or YouTube
• edit client videos
• use background music in content
• want an extra safety check before publishing

You can check it out here:

https://strikesense.net

If you create content and want to reduce the risk of copyright problems, StrikeSense might be useful for your workflow.

Hey everyone,

We built StrikeSense for creators, streamers, editors, and YouTubers who want to avoid copyright claims, muted VODs, takedowns, and demonetization caused by music.

StrikeSense is a Windows desktop app that monitors your system audio, recognizes music, checks copyright risk, and warns you when a track may not be safe to use.

The goal is simple: catch risky music before you upload, publish, or go live - not after the damage is already done.

It can be useful if you:

• make YouTube videos or Shorts
• stream on Twitch or YouTube
• edit client videos
• use background music in content
• want an extra safety check before publishing

StrikeSense shows whether music looks cleared / not cleared / unknown, so you can make faster and safer decisions while creating content.

You can check it out here:

https://strikesense.net

If you create content and want to reduce the risk of copyright problems, StrikeSense might be useful for your workflow.

Hey everyone!

I’m developing Iron Cross, a dark browser-based grand strategy game about managing a fictional industrial state.

The beta is playable now: https://iron-cross.net

You can start a match, manage your economy, politics, laws, diplomacy, armies, wars, events, and try to dominate the map. I attached some screenshots from the current build.

The game is still rough, so I’m looking for honest feedback from strategy game players — especially on gameplay flow, clarity, balance, bugs, UI, army control, and what feels confusing after starting a match.

Any feedback or improvement ideas are very welcome.

Hey everyone!

I’m developing Iron Cross, a dark browser-based grand strategy game about managing a fictional industrial state.

The beta is playable now: https://iron-cross.net

You can start a match, manage your economy, politics, laws, diplomacy, armies, wars, events, and try to dominate the map. I attached some screenshots from the current build.

The game is still rough, so I’m looking for honest feedback from strategy game players — especially on gameplay flow, clarity, balance, bugs, UI, army control, and what feels confusing after starting a match.

Any feedback or improvement ideas are very welcome.

If you find any bugs, you can report them either in the comments or through the feedback page on the website.

I’m a software engineer, probably somewhere between mid-level+ and senior, and recently I’ve been using tools like Codex for a large part of my work - including complex tasks.
It saves me a lot of time, makes me more efficient, and in many cases it even suggests cleaner or better implementations than I would have written manually at first.
My workflow has changed a lot. Instead of writing every line of code myself, I now spend more time defining the task clearly, reviewing the implementation, checking the diff, testing the logic, making adjustments, and preparing merge requests.
On one hand, this feels incredibly powerful.
On the other hand, it feels weird. Sometimes I wonder if this can lead to degradation as a developer, because I’m writing less (almost 0) code by hand than before. I still understand and review what gets built, but the process is completely different from how software development felt even a year ago.
I’m also building my own projects, and AI has become a huge part of that as well. Things that used to feel unrealistic for one person to build now feel possible.
A year ago, this workflow would have sounded almost impossible. Now it feels like reality.
I’m curious how other developers see this.
Do you think using AI this heavily makes you a weaker developer over time, or is this simply the next stage of software engineering?

Hey everyone,

I recently built a small tool called Pain Signal: https://pain-signal.com

The idea is simple: instead of brainstorming startup ideas from scratch, it helps find repeated complaints, pain points, and product opportunities from real market signals.

It’s mainly for indie hackers, SaaS founders, and developers who want to validate ideas before spending months building.

Still early, but I’d really appreciate honest feedback.

Would love if you could check it out and tell me what feels useful, unclear, or missing.

For a long time, I thought product ideas came from brainstorming.

But lately I’ve started to think that the better approach is almost the opposite: don’t search for ideas, search for frustration.

A lot of useful product signals are already public:

— Reddit complaints
— bad app reviews
— GitHub issues
— forum threads
— comments under competitor products
— “why does nobody solve this?” type posts

The interesting part is not one random complaint.
The interesting part is when the same pain appears again and again across different places.

That usually tells you a few things:

— the problem is real
— people already understand the pain
— current solutions are not good enough
— there may be a market gap
— the wording people use can help with positioning

I’ve been experimenting with this for SaaS validation and even started building a small tool around it called Pain Signal (pain-signal,com).

The idea is simple: collect complaints, find repeated patterns, and turn them into possible product opportunities before wasting months building something nobody asked for.

Still early, but this approach feels much more grounded than just asking “what should I build?”

Curious how others here validate ideas before writing code.

Do you mostly rely on interviews, Reddit/reviews, competitor research, or just instinct?

been trying to find better ways to come up with saas ideas because just asking chatgpt gives the most generic stuff ever

what worked a bit better for me is looking at actual complaints instead of brainstorming from zero. reddit, app reviews, github issues, product hunt comments etc. if the same problem keeps showing up in different places it feels way more real

tested pain-signal,com for this yesterday and it was kinda interesting. you put in a niche and it pulls signals/complaints and turns them into ideas + competitor gaps. not saying its perfect but it gave me a few angles i probably wouldnt have thought of

curious if anyone else does idea research this way or do you mostly just build from your own problems?

been trying to find better ways to come up with saas ideas because just asking chatgpt gives the most generic stuff ever

what worked a bit better for me is looking at actual complaints instead of brainstorming from zero. reddit, app reviews, github issues, product hunt comments etc. if the same problem keeps showing up in different places it feels way more real

tested Pain signal for this yesterday and it was kinda interesting. You put in a niche and it pulls signals/complaints and turns them into ideas + competitor gaps. not saying its perfect but it gave me a few angles i probably wouldnt have thought of

curious if anyone else does idea research this way or do you mostly just build from your own problems?

I’m starting to think the best SaaS ideas are not really “invented”.

They’re found in places where people are already annoyed.

I’ve been testing this recently by looking through Reddit threads, Product Hunt comments, app reviews, GitHub issues, and support-style complaints.

It’s kind of surprising how often the same patterns repeat.

People don’t usually say “I want a SaaS for X”.

They say stuff like:

• why is this so confusing
• why am I paying for this
• this should be automated
• I hate doing this manually
• is there an alternative to this

Those are usually much better signals than just asking AI for ideas.

I’m playing around with PainSignal for this because it does a lot of the scanning/clustering automatically, but the bigger point is the method itself.

Start with complaints first.
Then think about products.

Has anyone else tried finding ideas this way?

I’m starting to think the best SaaS ideas are not really “invented”.

They’re found in places where people are already annoyed.

I’ve been testing this recently by looking through Reddit threads, Product Hunt comments, app reviews, GitHub issues, and support-style complaints.

It’s kind of surprising how often the same patterns repeat.

People don’t usually say “I want a SaaS for X”.

They say stuff like:

• why is this so confusing
• why am I paying for this
• this should be automated
• I hate doing this manually
• is there an alternative to this

Those are usually much better signals than just asking AI for ideas.

I’m playing around with PainSignal for this because it does a lot of the scanning/clustering automatically, but the bigger point is the method itself.

Start with complaints first.
Then think about products.

Has anyone else tried finding ideas this way?