Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
0
Comments
246
Joined
10 mo. ago

  • I can stop laughing at steamcmd.

  • I have a buddy that bought AR glass to play around with and actually do AR development. We taunt him all time time and ask him if he has perv'd on anyone today, even though we know he he leaves them at home. The technology is tainted.

  • I think you are missing the fact that our pensions are going to be shit or not exist entirely. A retirement fund has to be much larger to cover what Boomers and earlier did because they had good pensions.

  • I have some small apps that I use for testing deployments that just do busy work. I have looked through the code and made corrections, but an LLM coded most of it. Where is the line for them? They are on Codeberg already, do I pull them off?

  • How many people are going to get murdered in cold blood by police when they pull up with their guns drawn?

  • I don't think many Americans understand how much of the Country is forests. In Quebec everything past the river plains north of A40 or 138 is forests.

  • Whatabout licking deez nuts.

  • The system is wrong 25% of the time and will do the opposite of what you want.

  • BS, I have gotten HP printers to work on Linux with no problems.

  • We all know what they would be saying and doing if it was the other way around. They don't have beliefs, morals, or honor. Act accordingly.

  • That's 24 with Christmas and Halloween specials. Or a clip show, ugh.

  • Copper

    Jump
  • Your napkin math is the best we have. We will make all decisions based on it.

  • For real, users never give enough information and so many metrics are not measurable by a user. We take user's bug reports and match them to the backend telemetry to see exactly what happened.

    Worst is that to be GDPR compliant you have to be opt-in and can't hold the data forever. So data is hard to come by.

  • You have two options for shielding, one is shield the entire thing like we do with the ISS because people live there and radiation is bad for living cells. Two is to shield the smallest unitary entities to use the least amout of materials, like a shield per chip. This is physics not magic, radiation does not just go away. When everything add to launch weight it does not make sense. Redundancy systems also add to launch weight.

  • LEO is still protected by the atomsphere and magnetosphere fully. Geostationary orbits start to have issues.

  • My ISP bumped me up from 1GB to 3GB for free and I was like like great, can you upgrade all of my NICs and router ports to be higher than 1GB? Because you effectively gave me nothing.

  • I don't think you don't understand the difference between the amout of cosmic rays, which are basically any flying particle, on Earth compared to space. Small nodes would be dealing with multiple per cpu cycle. Multiple could be 1 million a second, I am trying to figure out a way to measure. It would be something like distance from atomsphere(rate of total particles) x probably of an object the size of a transitior getting hit(rate of collions). I could probably find the bit-flip rate for an off-the-shelf space resistant chip and infere the rate for the size I need, but there are other factors. A bit will not flip on every collision, shrinking transistors exponentially increases this.

  • They are not using 6nm process chips in the ISS. The computers themselves were made before that process existed. An off-the-shelf space hardened computer system uses 65nm process. Cosmic rays is a very general term, it covers basically everything that flies around in space, that includes sources like the sun, which is hammering everything in the solar system with rays. Outside of the atomsphere there are so many more cosmic rays that non-space hardened computers can not even make calculations. Combined with the difference between the bit flip rate when you make transistors 10 x smaller is also fucked up high. One CPU cycle will have enough erros to make the computer useless. It's a multi-faceted problem and when the largest limiting factor is weight & size, it can't be solved with scaling.

  • There is an unsolvable compute problem. The average PC on earth has multiple bit-flips a year from cosmic rays. The space hardened chips we use are 50nm and the chips used from inference are 4 to 6nm. 50nm is far more cosmic ray resistant than 6nm because of the transistor size. Are we supposed to think making H100s with a 65nm process is possible? The speed of light creates a die size limitation as well.