The order of priority for most people is: 1\ output quality 2\ latency 3\ cost. I will always pays more money if output quality is significantly better and latency is worth the tradeoff. There's also enough cost optimization strategies for applied AI applications that token cost rarely outweighs unless it's a SIGNIFICANT difference (e.x. 100-200% more).

Err I just tried this with Claude and it responded: "Drive — you need the car at the car wash."

:)

There's nothing novel in this article. This is what every other AI clickbait article is propagating.

This is dumb. The solution for all music platforms should be to add a label for AI-generated tracks or artists so users clearly can disambiguate. It's frivolous to prevent someone from enjoying a piece of art whether AI or human. Furthermore, the line is blurred between what constitutes human vs AI development of music. Most producers today use pre-packaged samples, sequencers, and tracks to generate derivatives. Sure, they might manually have to mess around with Ableton to do so, but the line is already blurred.

I suspect the problem is scale. AI slop can be churned out at an unprecedented rate, and Bandcamp is not a big company, but they'd have to host and serve all of that stuff nonetheless.

Agreed that is a valid problem, though it's solvable and IMO worth solving.

Solid OSINT methodology here. The 10x AS path prepending is the most interesting detail to me b/c typically you'd see prepending used to de-prioritize a route, which raises the question: was this about making traffic avoid CANTV, or was it a side effect of something else?

A few thoughts: - The affected prefixes (200.74.224.0/20 block → Dayco Telecom) hosting banks and ISPs feels significant. If you're doing pre-kinetic intelligence gathering, knowing the exact network topology and traffic patterns of critical infrastructure would be valuable. Even a few hours of passive collection through a controlled transit point could map out dependencies you'd want to understand before cutting power. - What's also notable is the transit path through Sparkle, which the author points out doesn't implement RPKI filtering. That's not an accident if you're planning something (you'd specifically choose providers with weaker validation). - The article stops short of drawing conclusions, which is the right call. BGP anomalies are common enough that correlation ≠ causation. But the timing and the specific infrastructure affected make this worth deeper analysis.

Would love to see someone with access to more complete BGP table dumps do a before/after comparison of routing stability for Venezuelan prefixes in that window.

?

I'd love to swap notes - hmu at dev@locunity.com !

Super cool! We are doing the same thing in California: https://locunity.com/

I don't think the root cause here is AI. It's the repeated pattern of resistance to massive technological change by system-level incentives. This story has happened again and again throughout recent history.

I expect it to settle out in a few years where: 1. The fiduciary duties of company shareholders will bring them to a point of stopping to chase AI hype and instead derive an understanding of whether it's driving real top-line value for their business or not. 2. Mid to senior career engineers will have no choice but to level up their AI skills to stay relevant in the modern workforce.