I derive the majority of my hobby satisfaction from getting stuff done, not enjoying the process of crafting software. We probably enjoy quite different aspects of tinkering! LLMs make me have so much more fun.
It’s not that hard. You would not expect 5 sec drift on phones that can sync time on the web at least once a day or once a week. A basic quartz crystal can keep time to within seconds per month of drift. High quality phones can do the same or better. Also the phone should keep track of system time as epoch time, and convert to local.
> Also the phone should keep track of system time as epoch time, and convert to local.
Yes, but imagine your local time is US Pacific time, but you have a phone intended to be sold in Mexico, so your phone only has Mexico time zones and MX Pacific Time has no DST. During part of the year, you can use automatic time sync, but during the summer, you disable automatic sync and set the clock so that the time displayed matches local time. Your epoch time is now an hour ahead of properly synched devices, but whatevs, your phone shows the right time and that's what counts.
Let's say 1.5tok/sec, and that your rig pulls 500 W. That's 10.8 tok/Wh, and assuming you pay, say 15c/kWh means you're paying in the vicinity of $13.8/mtok of output. Looking at R1 output costs on OpenRouter, it's costing about 5-7x as much as what you can pay for third party inference (which also produce tokens ~30x faster).
I hate the ad business model as much as the next person, but this is a pipe dream. Meta had ~$50b in revenue on ads last quarter, and 3.54b “daily active people” whatever that means. That’s in the order of $1/“dap”/week, and there is just absolutely no way any meaningful proportion of their userbase would be paying that much for these apps.
Is it relevant? It's writing about a pool for storing spent fuel, which is not a part of the actual reactor system.
This incident report says that the worker fell into a "reactor cavity" containing water and that there was a measurable amount of radiation detected in their hair after the initial clean-up. The two situations don't seem remotely compatible to me.
Yeah, no shit. But, come on, don't play dumb. By measurable, I obviously meant "above normal background". Something that shouldn't have been possible if, as described in the xkcd post, the water should have had less radioactivity than normal background. Combined with the fact that the post was literally about a different kind of pool than the one involved in the accident, it was reasonable to question whether the post was actually relevant.
I agree this was not a serious incident, and I never really though it was. (I'm extremely pro-nuclear, for the record.) But at the time I posted, the comment section was about 8 people posting the xkcd link at once (with no additional commentary), and few others reading it and saying "oh, no problem then", with literally nobody pointing out the discrepancies, or explaining exactly what a "reactor cavity" means in this context.
I find it highly informative that the required PPE for working in that location is a life jacket so you float in case you fall in, rather than a tether and fall arrest harness so that it's not possible to fall in.
300 CPM is nothing, background levels might be 150.
Background is probably a bit lower depending on where you're at. My counter went through airport security luggage scans 'cause they wouldn't let me wear it through the metal detector. It beeps for a few seconds and then comes out about a days' dose of natural radiation higher. The count was higher than 300 CPM, but obviously only shortly.
That poor bloke might stay at 300 (if ingested and he can't scrub it off) for a while but it's still not very discouraging long-term. Pilots have about that at cruising altitude.
He went back to work the next day. They don't provide much detail about the minor injuries but it seems that the biggest issue is maybe a bruised shin from the fall.
reply