I’m a technical kinda guy, doing technical kinda stuff.

  • 0 Posts
  • 245 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle




  • Dave.@aussie.zonetoProgramming@programming.devWhen LLM gives you "{ }"
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    11 days ago

    Ollama released a new feature yesterday

    Ollama 0.5.1, yesterday : “Fixed issue where Ollama’s API would generate JSON output when specifying “format”: null”

    Ollama-rs 0.2.1: released 08/09/24.

    Gee I wonder why it doesn’t play nicely with the latest Ollama API which uses new/updated behaviour for an option 🤔





  • Why the fuck isn’t there just a simple status LED that is on the same circuit as the camera?

    Because cameras aren’t simple on-off devices powered by a single wire, that’s why. It’s always got power, and it’s turned “on” (send image data over the data bus) and “off” (do not send data) by software commands over the same data bus.

    So the most convenient solution is then have the camera IC have an output that can drive an indicator light. And as camera ICs are basically full computers in their own right, they can be reprogrammed so that they don’t turn on that output.

    End result is that you are much better off either having a physical cover over the camera lens, or having a USB camera that you can unplug.


  • , couldn’t the brokers just filter the period when i started clickning everything?

    They don’t care about the quality of an individual profile, it’s the quality of the aggregate data that’s important to them. If anything, your profile might be identified as an outlier compared to the average and simply discarded. They’re not going to look any further than that and try and “rescue” your data, they’ve got a million other profiles to sell to advertisers.





  • You’ve got the motive back to front.

    yah, let’s get rid of these cheap, easily manufactured and implemented dials and knobs

    In modern cars those buttons are an input to a body computer which then sends commands over the vehicle data bus to another module that performs the appropriate function. The touchscreen option is much cheaper once you have more than a few buttons to deal with.

    Buttons have different physical shapes, the little decal for the button on each one has to be printed and put on top, each one needs to be connected to power, each one needs to be slotted into the dash somewhere , each one needs to be backlit so you can use it at night, and the signal for each one has to be routed somewhere through increasingly bulky harnesses, etc etc.

    A touchscreen sits on the vehicle data bus and with a bit of software, sends whatever command is needed.

    Is it a great user experience to press fiddly buttons on a touchscreen while driving down a bumpy road? Fuck no. But it is definitely cheaper and less complicated for the manufacturer.


  • Effective advertising has a clear and simple visual language, and this is what UIs should strive for.

    Interfaces can be needlessly complex regardless of being flat or skeuomorphic.

    But flat interfaces still require mental effort to parse. Especially when the interface is complex and/or crowded and you’re trying to pick out active UI elements amongst decorations like group boxes/panels.

    Essentially, flat interfaces are currently popular because of touchscreen devices. Touchscreen devices have limited space and thus need simplistic UI elements that can be prodded by a fat finger on a small screen.

    But I don’t need a flat touchscreen-friendly interface on my non-touch dual 24" monitors with acres of screen real estate. I need an interface that nicely separates usable UI elements from the rest of the application window. That means 3D hints on a 2D screen, which allows my monkey-brain with five million years of evolved 3D vision the opportunity to run my “click the button” mental command as a background process.