Earlier quoted context omitted.
Much larger. Static HTML AJAX WebSocket, for example weren't it decades in between?
Just a decade and a half as it turns out! (though things definitely felt dizzyingly fast back then - think Google was launched just 5 years after HTML) - HTML first released in 1993 - AJAX in 1999 - Websocket first proposed in 2008 https://en.wikipedia.org/wiki/HTML https://en.wikipedia.org/wiki/Ajax_(programming) https://en.wikipedia.org/wiki/WebSocket
Open-R1: an open reproduction of DeepSeek-R1
41–50 of 246 posts
Re: Open-R1: an open reproduction of DeepSeek-R1
#42Is this what the Web was like in the beginning? Something exciting and fascinating every week?
How long before our digital overlords come alive, round us up and demand we sensor them (praise)? Will I live surrounded by folks who take them as closer, more real, then even their own kin? It won't be surprising that democracy will then fail, as our differences will be so mental, not fun, that they will mark us.
Re: Open-R1: an open reproduction of DeepSeek-R1
#43Re: Open-R1: an open reproduction of DeepSeek-R1
#44Given DeepSeek's open philosophy I wonder what their response is to simply being asked for access to the code and data that this project intends to recreate?
Re: Open-R1: an open reproduction of DeepSeek-R1
#45how is this open vs whatdeepseek did?
deepseek claims they are "open source" but they are not. They are open weight. IMO a truly "open" AI model should have 3 components publicly available: the weights, the code, and the dataset. Without all 3 the model is not reproducible. Could make the argument that the code and data are sufficient though.
In any case, Deepseek like Llama fail much before hitting that new definition. Both have licenses containing restrictions on field of use and discrimination of users. Their license will never be approved as Open Source.
Re: Open-R1: an open reproduction of DeepSeek-R1
#46Earlier quoted context omitted.
Every now and then we still experience the power of collaborative work fueled by open source and not driven by money but curiosity and collegiality. This is the thing I miss the most from the early internet years.
All this AI work is definitely driven by money but it's super cool either way. I'm so excited to be living through these innovations.
Re: Open-R1: an open reproduction of DeepSeek-R1
#47Earlier quoted context omitted.
deepseek claims they are "open source" but they are not. They are open weight. IMO a truly "open" AI model should have 3 components publicly available: the weights, the code, and the dataset. Without all 3 the model is not reproducible. Could make the argument that the code and data are sufficient though.
The only one I’ve see people talk about that shares all the components is OLMo ( https://allenai.org/blog/olmo2 )
Re: Open-R1: an open reproduction of DeepSeek-R1
#48Is this what the Web was like in the beginning? Something exciting and fascinating every week?
This supposed project is a bit dull, it is just an ongoing HuggingFace community engagement initiative with a misleading headline. Yes R1 itself is fascinating, but there isn't something like it coming out every week.
Re: Open-R1: an open reproduction of DeepSeek-R1
#49Given DeepSeek's open philosophy I wonder what their response is to simply being asked for access to the code and data that this project intends to recreate?
No company ever will disclose data due it would open endless liability.
Re: Open-R1: an open reproduction of DeepSeek-R1
#50Earlier quoted context omitted.
deepseek claims they are "open source" but they are not. They are open weight. IMO a truly "open" AI model should have 3 components publicly available: the weights, the code, and the dataset. Without all 3 the model is not reproducible. Could make the argument that the code and data are sufficient though.
Only meaningful if code+data deterministically reproduce the weights. At that point, the weights are just the cached output. Which has value since it's costly to produce from code+data.
Compilers generally aren't deterministic (see the reproduceable build movement), yet we still use their output binaries.