Advertisers pay for ads that don’t have impression data all the time. You can’t count how many people looked at a billboard or listened to your radio ad or paid attention to your televised ad.
A schema with response metadata (so responses that deviate from it fail automatically), plus a challenge question that's calibrated to be hard enough that the disruption of instruction following from prompt injection can cause the model to answer incorrectly.
Maybe I’m out of touch but why do you need an LLM to decide if there’s any work to be done? Can’t it just queue or schedule tasks? We already have technology for that that doesn’t require an LLM.
Totally valid for fixed, well-defined tasks — a cron job is cheaper and more reliable there. The LLM earns its keep when the heartbeat involves contextual judgment: not just "is there a task in the queue" but "given everything happening right now, what actually matters?" If the agent needs to reason about priority, relevance, or context before deciding what to surface — that's where the local model pulls its weight. If your agents only do fixed tasks, you're totally right, you don't need it!
The appviews are interchangeable; any appview will work with any PDS. Whatever appviews my followers and followees end up using, they'd still be able to see my posts, and I'd still be able to see theirs.
I don't think anyone one knows yet, nor does that answer need to be answered soon, or perhaps ever, bluesky can die and atproto can go on. They are not existentially tied together
>make revenue from that $20 than the electricity and server costs needed to serve that customer
Seems like a pretty dumb take. It’s like saying it only takes $X in electricity and raw materials to produce a widget that I sell for $Y. Since $Y is bigger than $X, I’m making money! Just ignore that I have to pay people to work the lines. Ignore that I had to pay huge amounts to build the factory. Ignore every other cost.
They can’t just fire everyone and stop training new models.
There's a trust built up over years (in this case, decades) by a news organization. In this case, Ars Technica. I don't trust the rando on the internet, but I do trust a news organization that has proven over the course of decades to release factual information.
Now that Ars Technica has been caught and admitted to using AI-generated material in its stories, I now have to question that trust. A week ago, I wouldn't have had to.
> Cloudflare Inc (NYSE:NET) shares rose more than 10% on Monday to $193.68, following a weekend surge in social media excitement around Clawdbot, an open-source AI agent built on Anthropic’s Claude. This jump comes despite the stock having fared poorly over the last month, according to InvestingPro data.
There's nothing in Tailwind that makes the craftsmanship dead, and your proposed solution with scoped styles somehow a revival of said craftsmanship.
Note how your solution literally depends on a build tool (Vue) to work. Whereas Tailwind can work with no build tools (tailwind build tools removes unused classes, and that's mostly it).
And then you go:
--- start quote ---
Juniors still come along and just do margin: 13px. In tailwind, they do m-[13px]. No difference. At least with CSS its centralized.
--- end quote ---
When your scoped CSS example is literally decentralized per-file CSS that has `margin: 5px` in it. That gets compiled into a meaningless `class-678x8789g` by the build tool.
> The people I've seen who are most excited over tailwind are generally those that would view frontend as something they have to do, not something they want to do.
reply