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

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

help-circle



  • And holy shit does their algorithm latch onto any minor interest in their content.

    Accidentally tapped on a floor tiling video the other day, three days of tiling and handyman videos jammed into my feed and me pressing the “not interested” button on every single one.

    Facebook, I am there for the rare post from my 150 or so friends and family. That’s it. Nothing else.

    The reason we don’t use it anymore is because actual posts from real humans we know are buried under a torrent of shit. Sometimes their posts take days to surface leading to all sorts of chain-mail posts on how to “get your feed back”. None of which work because the whole business model is about jamming sponsored shit down your throat.



  • Starlink sats have enough transmit power and receive gain to use normal cellular frequencies with a normal antenna on the phone side.

    You might think it’s a long way to space, but a few hundred kilometres of direct line of sight to your cellphone antenna isn’t that much more to overcome compared to say, 25 km to a cell tower on the ground.

    The biggest hurdle was getting a few thousand satellites into orbit so that coverage and availability is there.


  • Mainly when you are building a single-purpose , “appliance” device and you have the bare minimum of RAM/storage available. You just want to get the board powered up and initialised and then jump to your application.

    So you build a kernel with only the correct drivers you need, you skip initrd, you skip initscripts and (lord forbid) systemd, you just jump straight to your program, with possibly busybox available if you need debugging.

    Edit: I’m talking more about building it from scratch here, not LFS. Regarding security issues, you then “only” have to deal with kernel exploits, with a limited surface as you have limited modules linked, and exploits in your application.









  • 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.



  • 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.