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.
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 notagentic 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?..
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 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.
abhin4v | 13 hours ago
In the same vein, I have written this small Stylus CSS that moves the posts tagged
videcodingto the bottom of the page, and colours the tag red:MatheusRich | 7 hours ago
I love how readable CSS gets when using :has
chrismorgan | 12 hours ago
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):
That would kinda collide with the default
:visitedstyles, but I changed that to purple, as is traditional for the web.ThinkChaos | 5 hours ago
That's a great idea thanks!
I replaced the tag coloring a separator:
(And made
order: 1only apply to the front page: also uses.stories.list)chrismorgan | 4 hours ago
Why add bottom properties to the last non-vibecoding story? It’d be simpler to add top properties to the first vibecoding story:
durrendal | 7 hours ago
Thank you, this is such a great QoL hack
atmosx | 10 hours ago
What I want to know is, did you vibe code that?
abhin4v | 9 hours ago
No, I didn't. I typed it with my bare hands till it worked.
LenFalken | 9 hours ago
I think eventually "LLM" will be the incorrect term.
agentoragenticis probably the best fit. I still want to seeainews but notagenticnews.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?..
gerikson | 9 hours ago
The "vibecoding" tag has succesfully encompassed "llms" and "prompt engineering" and now "agentic", which shows that it is stable and future-proof.
aleyan | 3 hours ago
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.
Sharparam | an hour ago
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.
tomsmeding | an hour ago
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?
Sharparam | an hour ago
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.
LenFalken | 8 hours ago
Very true! Yep, strong reasoning to keep what we have now.
singpolyma | 9 hours ago
I think most people who aren't interested in agents aren't interested in LLMs generally
LenFalken | 8 hours ago
There's a whole world outside of LLMs in the AI space :)
singpolyma | 8 hours ago
Sure, always has been. But most of that isn't what people are trying to avoid?
reezer | 7 hours ago
There also is an AI tag.
LenFalken | 6 hours ago
Mhm, between
aiandvibecodingI think we're in a good place.chrismorgan | 15 hours ago
Wrong URL, should be https://greasyfork.org/en/scripts/597063-lobsters-rename-vibecoding-to-llms.
Should also be tagged meta.
roryokane | 15 hours ago
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.
Gracana | 10 hours ago
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.
dbushell | 10 hours ago
motet-a | 15 hours ago
I don’t plan to use it, but I upvoted because I feel this could save us a lot of heated debates!