I'm working on adding an API and WhatsApp integration to my scam / AI detection tool - https://legitornot.co.za
Readit News7237139812 commented on Ask HN: What Are You Working On? (December 2025) · Posted by u/david927
Scam SMS and AI detection from screenshots, primarily for South Africa - hoping to make it available via WhatsApp soon.
No real monetization plans yet - just experimenting / improving the detection at the moment.
I’ve been working on https://stagify.io
— an AI tool that lets real estate agents and photographers instantly stage empty rooms with realistic furniture.
Traditional virtual staging usually takes 24–48 hours and costs $20–50 per image. Stagify does it in seconds while keeping everything MLS-compliant (it doesn’t modify walls, floors, or windows).
It’s been fun building it as a solo indie hacker — I’m using Rails 8, Nuxt 3, and AWS for the backend. Right now I’m focused on getting my first 100 paying users in Canada before expanding to the US.
Nice! I'm working on a similar thing focused on the South African market
I've recently started building out the image -> video feature.
My nights and weekends project at the moment is a virtual staging tool for real estate agents.
I'm focusing on the South African market (I know a bunch of agents and I've noticed an increase of very obviously ChatGPT generated images on property listing websites)
My hope is that I can own a nice slice of the listing marketing workflow:
- Creating great, but realistic staging images for listing websites - Improve property descriptions and copy
There is some early interest from agents, hoping to start marketing properly this week!
Deleted Comment
Location: South Africa
Remote: Yes, preferred
Willing to relocate: Possibly - with assistance
Technologies: JavaScript/TypeScript, Node.js, GCP, Kubernetes, Docker
Résumé/CV: https://docs.google.com/document/d/1pKnSWG0aWLrmIRyNrbkAvWHD... or https://www.linkedin.com/in/shivanmoodley/
Email: mshivanc@gmail.com
I'm a really passionate engineer/leader with a mix of experience across insurance, payroll and SaaS. I've worked in large corps and startups, with a few freelancing stints along the way. I'm always hacking on my own stuff in the background and looking for interesting problems. Good at working with really high ambiguity and figuring things out.
7237139812 commented on How to prioritize tasks? jimmyislive.dev/posts/how... · Posted by u/jimmyislive
I tried something similar a while back. It made me feel like I was doing really we;; at prioritising my work, but it's honestly a hard thing to do well and without over-engineering prioritisation.
These days I just have a list of weekly objectives (TODOs), and a daily list of things that I'm "doing". The doing list is based mostly on gut feel about what's important right now, and is in part - based on what my team / the business feels is important right now.
All the things in the weekly objective list are always high priority / important, if it isn't, then it doesn't go on a list.
> Though not a perfectly applicable example, we can see that the English language, due to its rules and formalization, does not have a single word that describes the complexity behind the feeling of “Schadenfreude”. This is an inherent constraint in the English language as it pertains to its translation to German.
Except English does have such a word and the author literally linked to its dictionary entry in an English dictionary.
OP here. I think it serves as a loanword, but I concede that linking to an _English_ dictionary can blur the point I was trying to make. Edited for clarity, thanks!
I always have trouble parsing the Seemingly Wrong Thing That I’m Redefining writing style, so I’m not sure my comment is germane.
It seems like OP is saying to communicate about technical matters in a way that is not obscured by jargon and distracting minutia. That is generally good advice, and has an ancillary benefit that explaining deeply technical matters in plain language usually deepens the explainer’s understanding.
There is a less charitable interpretation where this is just “I talk to the customers so the engineers don’t have to!” dreck, in which case, Be Less Click Thirsty.
OP here - I think your interpretation (the former) is pretty spot on. I also think the less charitable interpretation is not _exactly_ wrong. The title and repetition of "Be Less Technical" are definitely not devoid of "click thirst" - but the content is intended to be more in line with "we need to find ways to talk to each other, irrespective of whether we talk to customers or compilers".