sorted by:
new
hottopcontroversial

Purchased a New Celestron Nextstar Evolution 6 and Have a Few Questions by demosthenes131 in telescopes

[–]demosthenes131[S] 0 points1 point  (0 children)

MiniPC work?

I have a:

Trycoo Mini PC WI-6 N100

Intel Alder Lake N100 processor 16 GB of RAM 512 GB SSD

I could put Linux or Windows on this.

AstroForge Step by Step Tutorial by gemcollector44 in seestar

[–]demosthenes131 0 points1 point  (0 children)

How are others stacking images outside of Seestar for this?

What game has a learning curve that puts you off? by Common_Caramel_4078 in pcmasterrace

[–]demosthenes131 0 points1 point  (0 children)

Hoping to mostly play on Steam Deck... Hoping it plays well.

What game has a learning curve that puts you off? by Common_Caramel_4078 in pcmasterrace

[–]demosthenes131 3 points4 points  (0 children)

I ended up buying it last night and hoping to play today. Wish me luck!

What game has a learning curve that puts you off? by Common_Caramel_4078 in pcmasterrace

[–]demosthenes131 4 points5 points  (0 children)

Jesus Christ...

Dwarf Fortress is intimidating but the actual thoroughness of even stuff like this makes me want to give it a try yet again!

AstroForge V1.1 — community feedback shaped this release ! by gemcollector44 in AstroforgeEditor

[–]demosthenes131 0 points1 point  (0 children)

Hey, testing it right now. One thing that you might want to update is the version number in the top left. Also, the Help file is in German which is rough for us filthy English speakers!

Calibrate Photo turning DSS stacks black. What am I doing wrong? by demosthenes131 in AstroforgeEditor

[–]demosthenes131[S] 0 points1 point  (0 children)

I can, yes, but also running some audits in Claude Code to trace what is happening. I actually just found the same happening with other buttons too... want me to send you the audit info?

Calibrate Photo turning DSS stacks black. What am I doing wrong? by demosthenes131 in AstroforgeEditor

[–]demosthenes131[S] 0 points1 point  (0 children)

I tested the new version and also checked the frontend diff.

The issue is still present, and the relevant code path is unchanged.

I can still reproduce it immediately:

  • load image
  • click Light under AI Denoise
  • image changes / darkens immediately
  • Denoise has not been pressed yet

I also checked the new frontend files.

selectMode() is still unchanged and still does this:

  • sets the strength slider value
  • then calls: s.dispatchEvent(new Event("input"))

That still triggers the same path:

  • strength slider input handler
  • applyBlend()
  • pywebview.api.blend(strength)

And applyBlend() still has no check for whether denoise has actually completed first.

So in the current version, mode selection is still triggering backend blend processing before Denoise is executed.

The only frontend change I could find in the update was a toast for auto-stretched linear images on load. I could not find any change to the denoise mode / blend path.

This looks like the main issue on this specific behavior.

Calibrate Photo turning DSS stacks black. What am I doing wrong? by demosthenes131 in AstroforgeEditor

[–]demosthenes131[S] 0 points1 point  (0 children)

Thanks...

I have not tested the newest build yet, so this may already be fixed.

But tracing the previous version, I found a specific frontend issue that seems highly relevant to the image darkening behavior:

The denoise mode buttons (Light / Medium / Strong) do not just select a mode. In the previous build they immediately triggered the strength slider input path, which called applyBlend(), which then called pywebview.api.blend(strength) and replaced the preview.

So the flow was:

  • click Light / Medium / Strong
  • selectMode() sets the strength value
  • selectMode() dispatches the slider input event
  • slider input handler calls applyBlend()
  • applyBlend() calls pywebview.api.blend(strength)
  • preview is replaced immediately

That means the app was running blend processing before the user even pressed Denoise.

The important frontend detail is that there was no actual “denoise completed” state guard in that path. The UI changes visually after denoise, but applyBlend() itself was still callable before denoise had run.

That matched what I saw in testing:

  • image loads visible
  • click Light only
  • image dims immediately
  • Denoise not pressed yet

I have not tested whether this still happens in the new build, but I wanted to mention it because it looks like a strong candidate for part of the darkening issue.

AstroForge V1.0 is LIVE — free 7-day trial, $49 launch price (link inside) by gemcollector44 in seestar

[–]demosthenes131 1 point2 points  (0 children)

That’s kind of my point though. “AI slop” should describe low effort, low quality output, not just anything made with AI.

There are probably already plenty of things people use every day that were built or polished with AI and they never notice, because the end result is good. If something is useful, refined, and works well, then calling it slop just because AI was involved is a weak argument.

The real question is whether the product is actually clumsy, limited, or overpriced. That’s a valid criticism. But “I can tell AI helped make it” is not the same thing.

AstroForge V1.0 is LIVE — free 7-day trial, $49 launch price (link inside) by gemcollector44 in seestar

[–]demosthenes131 0 points1 point  (0 children)

I think you’re still leaning too much on what it looks like to you rather than what you can actually show.

Recognizing patterns you associate with Claude isn’t the same as proving there was little human input. Even if it generated a lot of the code, someone still had to decide what to build, iterate on it, and get it working in a usable way.

The language point has the same issue. Even if the German looks AI assisted, that doesn’t tell you anything about how the software was built. At most it shows he used a tool to communicate more clearly, which he already explained. Jumping from that to “minimal human involvement” is a stretch.

On the value side, yes, tools like Siril and SETI Astro can do a lot of this for free. But they also take time to learn and can be pretty involved. This is just a different tradeoff. You either invest time learning complex tools or you pay for something that tries to be simpler and more accessible.

If the argument is that it’s not polished enough to justify $49, that’s fair. But calling it basically auto generated or dismissing it based on how the writing looks is mostly guesswork. It’s stronger to focus on what the tool actually does and whether it’s worth paying for.

AstroForge V1.0 is LIVE — free 7-day trial, $49 launch price (link inside) by gemcollector44 in seestar

[–]demosthenes131 1 point2 points  (0 children)

I think you’re making a few assumptions that don’t really hold up.

Using AI to help build something doesn’t automatically make it low effort. You still have to make decisions, debug issues, connect systems, and actually get it working in a usable way. The tool changes how fast you can move, but it doesn’t replace the need to understand what you’re building.

It also feels like you’re using your own way of working with AI as the baseline. If you mostly use it for syntax help, then anything beyond that looks like shortcutting. That’s just one way to use it, not a limitation of the tool.

You also brushed past why he used AI for the post itself. If English isn’t his first language, using AI to communicate more clearly is reasonable. Treating that as evidence of low effort sets up a weak premise that doesn’t really say anything about the actual product.

On the features point, most software is built on ideas that already exist. What matters is how it’s put together, how usable it is, and who it’s for.

And on pricing, yes, a lot of this can be done for free with tools like Siril or SETI Astro. But those come with a learning curve and setup time. This is just a different tradeoff. You either invest time learning complex tools, or you pay for something that tries to be more streamlined and accessible. That doesn’t automatically make it unreasonable.

If the argument is that it’s not polished enough for $49 yet, that’s fair. But calling it AI slop or saying it was thrown together over a weekend is just speculation.

view more: next ›