Article: https://proton.me/blog/deepseek

Calls it “Deepsneak”, failing to make it clear that the reason people love Deepseek is that you can download and it run it securely on any of your own private devices or servers - unlike most of the competing SOTA AIs.

I can’t speak for Proton, but the last couple weeks are showing some very clear biases coming out.

  • morrowind@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    4 hours ago

    I think you’re confusing the two. I’m talking about the regular qwen before it was finetuned by deep seek, not the regular deepseek

    • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      I haven’t actually used that one, but doesn’t the same point apply here too? The whole point of DeepSeek is in distillation that makes runtime requirements smaller.

      • morrowind@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        47 minutes ago

        No cause I was already running regular (non-deepseek) qwen 14B, admittedly a heavily quantized and uncensored version, so I was just curious if it would be any better

        • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          41 minutes ago

          The big difference with R1 at least is that it is trained using reinforcement learning, and it gives you an explanation of how it arrived at a solution. I find the thinking bit is really fascinating cause it really reads like a train of thought. Here’s an example of what it outputs when I ask it to write a react component with a text input and a button:

          <think> Alright, the user asked for a React component that includes a text input and a button. I need to write this in a way that’s clear and functional.

          First, I’ll start by setting up the basic structure of a React component. I’ll import React and useState since we’ll need state management for the input value.

          Next, I’ll create a functional component called TextInputButton. Inside this component, I’ll use the useState hook to manage the text input’s value. The initial state can be an empty string.

          Then, I’ll define a handler function, handleChange, that updates the state whenever the user types into the input. This function will take the event object and set the new value using setTextInputValue.

          I also need a function to handle the button click. For now, I’ll use handleClick with an alert message as a placeholder. The actual functionality can be added later based on requirements.

          In the return statement, I’ll structure the JSX. I’ll include an input element of type text, binding its value to the state variable and attaching the handleChange function to the onChange event. This ensures that the state always reflects the current input value.

          Below the input, I’ll add a button element. On clicking this button, it will trigger handleClick. I’ll also give it a class for styling purposes, like ‘button’ which can be styled with CSS if needed.

          Finally, I’ll export the component so it can be used elsewhere in the application. I’ll make sure to include comments explaining each part for clarity. </think>

          Here’s a simple React component with a text input and a button:

          import React from 'react';
          import { useState } from 'react';
          
          function TextInputButton() {
            const [text, setText] = useState('');
          
            const handleChange = (event) => {
              setText(event.target.value);
            };
          
            const handleClick = () => {
              // Add your click handler logic here
              alert('Button clicked!');
            };
          
            return (
              <div>
                <input
                  type="text"
                  value={text}
                  onChange={handleChange}
                  placeholder="Enter text..."
                />
                <button onClick={handleClick}>Submit</button>
              </div>
            );
          }
          
          export default TextInputButton;
          

          This component:

          1. Uses useState to manage the input value
          2. Has a handleChange function that updates the state when the user types
          3. Has a handleClick function that currently just shows an alert (you can add your own logic here)
          4. Renders an input field and a submit button

          You can use this component in your application like:

          <TextInputButton />
          

          The input value is controlled through the text state variable, and you can access it using text. When the button is clicked, the handleClick function will execute whatever logic you need.