I've been working on a project called ThreadQuilt, and I'm excited to share it with you all. ThreadQuilt is a community discussion aggregator that brings together the best threads from various forums and platforms into one convenient place. Whether you're interested in programming, tech trends, or just want to stay updated on niche topics, ThreadQuilt helps you find and follow the most relevant conversations without the clutter of AI-generated content. It's all about real human discussions, curated for quality and relevance.
I built ThreadQuilt because I was tired of wading through endless noise to find meaningful discussions. With ThreadQuilt, you get a cleaner, more focused experience that highlights the best parts of the web's conversations. Check it out and let me know what you think! Your feedback would mean the world to me as I continue to improve and expand the site. Happy threading!
I applaud your effort.
I’ll ask the obvious question around the strongly opinionated approach of not leveraging “AI”. Would you like to expand on what that means to you? I would imagine that some form of intelligence could also help with noise reduction but maybe you considered it and decided otherwise.
I am absolutely not opposed to it, and if I can convince myself that integrating AI would be moreso "what people want" then I would integrate it (and have more fun).
However, there ARE plenty of areas it IS the right fit for. Lots of “fuzzy” systems that would struggle to be rule-based and generalizable benefit hugely from LLMs and other fuzzy / intentionally broadly scoped tooling.
Source — I work at a “chat with your data” startup, and our product just categorically wouldn’t be worthwhile if the above weren’t true :)
Additionally, I chose to avoid AI as I have picked up from a lot of people that Google’s AI features have more or less ruined it. Do you think there is a way that I could use AI here that wouldn’t ruin things?
Deleted Comment
Google has done a terrible job, but perplexity has done a pretty good job. I think there's quite a bit to be gained by summing/extracting desired information from threads. I'm thinking opinions on choosing tech stacks (eg, "should i use sql or nosql", "fastAPI vs supabase"...), or even fixing bugs (on that note, if you're going after tech, github might be another to look at).
I defitley agree there's a ton of noise in discussions, I think LLM's are the current best way to cut through that noise.
https://www.threadquilt.com/search?topic=openbsd
Throws a 500 and displays a stack trace of the server.