Lobsters: Rename vibecoding to llms (Greasemonkey script)
66 points by joshka
66 points by joshka
In the same vein, I have written this small Stylus CSS that moves the posts tagged videcoding to the bottom of the page, and colours the tag red:
.story .tag.tag_vibecoding {
color: var(--color-fg-accent);
}
.stories.list {
display: flex;
flex-direction: column;
}
.stories .story:has(.tag.tag_vibecoding) {
order: 1;
}
Mmm, reordering is interesting, though it’s visual-only (tab order is now out of whack). In my user styles I’ve reduced their opacity sharply (used to be .6, now trying .4):
.story:has(.tag_vibecoding) {
opacity: .4;
}
That would kinda collide with the default :visited styles, but I changed that to purple, as is traditional for the web.
That's a great idea thanks!
I replaced the tag coloring a separator:
.stories.list {
display: flex;
flex-direction: column;
.story:has(.tag.tag_vibecoding) {
order: 1;
}
/* Last non-vibecoding story */
.story:nth-last-child(1 of :not(.story:has(.tag.tag_vibecoding))) {
border-bottom: dashed 2px var(--color-box-border);
padding-bottom: 5px;
margin-bottom: 5px;
}
}
(And made order: 1 only apply to the front page: also uses .stories.list)
Why add bottom properties to the last non-vibecoding story? It’d be simpler to add top properties to the first vibecoding story:
.story:nth-child(1 of :has(.tag_vibecoding)) {
border-top: dashed 2px var(--color-box-border);
padding-top: 5px;
margin-top: 5px;
}
Negation of the rule right above was more natural to me :)
Yours is better so the separator is absent when there's no vibecoding story though!
I think eventually "LLM" will be the incorrect term. agent or agentic is probably the best fit. I still want to see ai news but not agentic news.
Tangential, I think lobste.rs needs a polling post type. There is no way to disagree with posts like this at a top level in aggregate, but we can aggregately agree?..
The "vibecoding" tag has succesfully encompassed "llms" and "prompt engineering" and now "agentic", which shows that it is stable and future-proof.
Was it successful? I think there is a great number of people who want to read and discuss LLMs or agents but don't necessarily want to checkout every vibecoded project along the way.
I'm in the boat of the people who think the "vibecoding" tag here is way too broad. Vibecoding is a very specific thing, and it being used as the "catch-all" tag for anything AI-related is bad, IMO.
While I agree, there is some sense in which we might want to avoid making it too narrow. You have "LLM was used in production of code the post is about", "the code the post is about is fully LLM-generated and the author cares not about quality", "LLMs were used in production of some figures in the post", and "LLMs were used in writing of the post itself". I think if you'd collect filtering wishes of lobste.rs readers, you'd need at least all these categories to be accurate enough. But should we really be that precise?
That is true, probably what I'm more annoyed about is the naming of it. If the "vibecoding" tag is supposed to be for just "AI/LLM usage in some way", it should be named to reflect that, rather than looking like it represents something more specific than it actually does.
I think most people who aren't interested in agents aren't interested in LLMs generally
There's a whole world outside of LLMs in the AI space :)
Wrong URL, should be https://greasyfork.org/en/scripts/597063-lobsters-rename-vibecoding-to-llms.
Should also be tagged meta.
I already used the “suggest” link next to the story timestamp to suggest adding the “meta” tag. If you suggest that too, Lobsters should apply the change.
I wish there were separate tags for the tech and culture topics. I've seen enough rants and grandstanding on the topic to last a lifetime.
I don’t plan to use it, but I upvoted because I feel this could save us a lot of heated debates!