I take this opportunity to shame GitHub for completely ignoring the mobile experience in their own Android app. The project's README is pages upon pages of largely blank space. In general, the app does not render mermaid diagrams and does not allow for zooming in, so smaller pictures are unusable. Even if you access pictures directly in a repo's source, you still can't zoom in. iPython Notebooks, which are extremely common in data science, are an "unsupported file type" and are not rendered.
Contributors: GCSS had the original idea. JPP tried to talk him out of it. JPP did the first literature search but GCSS lost it. GCSS drafted the manuscript but JPP deleted all the best jokes. GCSS is the guarantor, and JPP says it serves him right.
Haha yeah pretty wild how easily you can see the data is fake by the repeating numbers (refresh the page the progress goes back in time constantly) + watch for restarts. They say they happen but 0 data correlates the log messages. Just a replay of old data or being fed by an llm so they convince people they are open
Same here. 5.5 would sometimes oneshot relatively complex models even without MCP. Opus, however, even with Fusion 360 MCP access would usually make comically bad models. It seemed that Opus tried to reason through the problem while GPT would come up with a general plan of using whatever tools were available to solve the problem. In chat, it would use the available Python and trimesh. It was also the only time I had ChatGPT work on something for over 30 min without giving up.
reply