5,542 karma · joined February 27, 2013
It might, in fact, be that you are more successful with your approach. I have no idea. Congrats if so.
It's nice to see a person who actually acknowledges tradeoff.
For the curious, this seems to be his company: https://www.umh.app
So I'd say it's probably only a $56 contribution.
Anyway, I think it's all a fun marketing thing. A desk toy for folks with disposable income. I imagine they'll sell out, given the limited release and then they'll be on eBay.
This is a person with OpenAI labs, which created it. They cited their coworker who didn't post it themselves.
It's not exactly the same thing, of course, but still interesting the extent to which this type of content is viewed as the business opportunity for him.
But if you're a nurse and wear scrubs all the time, then it might become worth spending time upfront perfecting it.
And then he admitted that he cheated as a 16 year old in "random games" to boost his online rating. I can't find any instance of him providing a number of how many games he admits to cheating in, but the chess.com report alleged over 100, including when he was 17.
In reality, I don't think this is how it'll shake out. But it's a valid argument.
The other aspect that's missing from the discussion here is LEGAL. If Tidal is making money from stolen music -- although arguably they still are by offering it on a subscription basis -- then that opens them up to litigation. From that perspective, this may double both as risk-mitigation and also a marketing opportunity for them, would love an attorney to weigh in there.
(From the comments here, Spotify is the market leader and already pays out for AI generated music. But I can't say that independently.)
I think this needs more clarity. I can think of a lot of different ways AI is used in music today as a part of the song generation process and not sure whether or not this definition would apply to it. They specifically mention developments in "text-prompted generation" but if anything that confuses the issue more, for example what about training on specific music.
This isn't a comment on how expansive or narrow the definition should be, just that they need to spell it out more to allow for consistent application (to say nothing of enforcement). If someone uses ChatGPT for lyrics, but writes the instrumentals themselves, does this policy apply? I genuinely have no idea.
I'd like this not as a timeline scrub but as a back button.
I think it'd be worth slowing down when you have receive data for multiple pitches at once, which would also mean it wouldn't feel as slowed down at other times -- even if that means at some points you're further behind the real-time nature of the game.
I also wish it was more zoomed-in on the action, but I get why that's not in v1.
Far more importantly, you would not get billed for 2 minutes of work for this if you paid a developer to fix it. At best, half hour increments for the fix. But more likely, for the full hour. Also, in this comparison, the consultant is on call every day, morning, afternoon, evening, for whatever you wanted and will jump on the job immediately.
Another model might have used fewer tokens, but come up with a fix that was 1000 lines when the right fix was only 2 lines.
It doesn't have Claude Fable yet, so I went with GPT 5.5 Pro. And so I'd estimate it at 22 gallons of water used (different from consumed, of course). That's quite a lot! It amazes me how much the different use cases and models use dramatically different amounts of water. My takeaway from playing with that calculator has been the folks who talk about water usage are overstating the impact of chatbots, but not overstating when it comes to vibecoding.
The good thing is that competition should drive down how efficient these models are in the long run. This blog post makes me not want to run Fable because of the cost, and that incidentally also means selecting models that aren't as wasteful in terms of water and electricity.
That first sentence threw me off.
Anyway, I'm glad he spent the $12 because this blog post was highly informative.