- 143comments
- 198comments
- 36comments
- 228comments
- 5comments
- 61comments
- 11comments
- 45comments
- 250comments
- 72comments
- 40comments
- 238comments
- 36comments
- 10comments
- 51comments
- 17comments
- 168comments
- 1comments
- 13comments
- 3comments
- 151comments
- 25comments
- 89comments
- —discuss
- 16comments
- 176comments
- —discuss
- 148comments
- —discuss
- 74comments
I made Ethos, an open-source tool to visualize the discourse on Hacker News. It extracts entities, tracks sentiment, and groups discussions by concept.
Check it out: https://ethos.devrupt.io
This was a "budget build" experiment. I managed to ship it for under $1 in infra costs. Originally I was using `qwen3-8b` for the LLM and `qwen3-embedding-8b` for the embedding, but I ran into some capacity issues with that model and decided to use `llama-3.1-8b-instruct` to stay within a similar budget while having higher throughput.
What LLM or embedding would you have used within the same price range? It would need to be a model that supports structured output.
How bad do you think it is that `llama-3.1` is being used and then a higher dimension embedding? I originally wanted to keep the LLM and embedding within the same family, but I'm not sure if there is munch point in that.
Repo: https://github.com/devrupt-io/ethos
I'm looking for feedback on which metrics (sentiment vs. concepts) you find most interesting! PRs welcome!
This is virtually identical to tools the US Department of Homeland Security uses across each social media platform and major website with comments to monitor sentiment and activities.
Congrats, I guess.
I was also told this by someone randomly while working at a coffee shop here in DC. Something about CGA.
Very interesting. LLMs open up space for transforming unstructured raw data into visualizations and dashboards. I made something just looking at “Who wants to be hired” posts.
https://hireindex.xyz/#stats
Does that use the "real" LinkedIn API or something else like Playwright?
What model does it use?
What vector database is it using?
Well done.
If I could suggest, please make green colors more distinct in sentiment split wheel, they seem to be very similar now.
Awesome idea! The entity tracking is very exciting, most interesting part imo
I think the budget is noticeable in the sentiment analysis unfortunately, the tags and entity recognition are good but the sentiment ratings themselves seem pretty sloppy.
I think it's mostly prompting, but I will be experimenting with this more. The prompt currently is garbage IMO
(Source: https://github.com/devrupt-io/ethos/blob/67670eb2855b84d389d...)
Garbage, why? That is the insightful bit you chose to omit. How would you do it instead?
It leaves a lot of interpretation to the model. For example it doesn't give any guidance on concept naming or disambiguation, which leaves all of that work to the JSON schema.
In my experience it's much more effective to reference key terms or ideas in the JSON schema and then explain those and their constraints in the system prompt.
This is one reason why people often think one model performs better than another for tasks they are both capable of. The real question IMO becomes, does porking all of that extra input prompt (a) eat too much context or (b) increase cost too much.
We will put an update on this in the future and post it in our blog, https://blog.devrupt.io/
This is really cool and something I've envisioned building for a long time!
There is a bug in the entity tracking. For the entity "github", it shows a positive sentiment. HN does NOT like GitHub (for reasons good or bad). If you click on it, it shows you stories about other seemingly unrelated stories.
https://ethos.devrupt.io/entities/github
Thank you. I believe this is because it's not properly aggregating the story title, content, and comment hierarchy. There are going to be cases where the LLM does a poor job of understanding the conversation, but I think right now the information isn't being sent to the prompt.
Right now it seems to be only using one level of the parent comment hierarchy.
(Source: https://github.com/devrupt-io/ethos/blob/67670eb2855b84d389d...)
any blog post anywhere that explains how all of this stuff works and the architecture etc?
We wrote this https://blog.devrupt.io/posts/introducing-ethos/
Jeffrey Epstein: 0.20% Positive! Lol.
Side note: this is cool, but the sentiment analysis could be a bit more sophisticated in v2.
I know I'm going against the HN hivemind a bit here, and I hope I don't get flamed too much for it - but I think that that Jeff Epstein fellow wasn't a very nice man.
guidelines link
I'm thinking about constantly getting bombarded with audible microwave voice messages for past couple years
Epstein was written in COBOL because of static analysis.
and how that's related?
I figured you were testing the analysis to see where it put you lol
no, I just straight up answered the question. it's fucking annoying, you know https://ieeexplore.ieee.org/document/9366412
The sentiment analysis is very interesting. I'm super curious what that looks like historically, going back to 2007.
I currently have it limited to this "epoch" date while I tweak the prompts, once I feel the prompt is done cooking I will be letting it go back to 2007. But, also, gotta keep the lights on somehow ;)
Also, hello fellow taylor.