Skip Navigation
InitialsDiceBear„Initials” ( by „DiceBear”, licensed under „CC0 1.0” (
Posts 1
Comments 808
EVs Could Last Nearly Forever—If Car Companies Let Them
  • I can confirm Samsung appliances are complete trash. Every single one I've owned has either died or had a non-replaceable part fail within a couple years. We had a Samsung fridge at one point and one of the door switches failed. No big deal right, easy to replace? No, apparently Samsung used some kind of custom switch instead of the bog standard cherry contact switch that basically everything and everyone has used for decades, and it's no longer being manufactured.

  • X11 + OpenGL window resizing issues
  • This is a wild guess but you probably need to rerender the framebuffer when you get the resize event. I'd expect most libraries/frameworks/engines would take care of that for you, but if you've rolled your own using the base X11 and OpenGL libraries you might need to set that up. X11 has a lot of strange quirks due to its network centric design.

  • Embarrassing coal
  • It depends. There's a lot of areas in coal country that are deeply conservative in part because conservative politicians promise to protect coal jobs and to disrupt renewables. That of course varies by location, but E.G. Texas which has a large oil company presence is going to have a lot of conservative voters who are anti-renewable because they've made their career working in the petroleum industry. So while not every conservative is going to be against solar, quite a lot of them are.

  • Embarrassing coal
  • That can delay things, but ultimately it will be the US against the rest of the world and no amount of subsidies will be able to offset that. We're already seeing the early stages of that with China having invested heavily in solar. Cheap Chinese made solar panels are starting to drive the cost of solar installs down and China is still ramping up. Between the public backlash against fossil fuels on one side, and increasing economic pressure on the other eventually they'll cave and phase the subsidies out.

  • Embarrassing coal
  • Ultimately this is how renewables win. Not because people are pushing for them, but because they're cheaper and easier. In order to reach that point we do need a certain number of early adopters that are using renewables because it's the right thing, but we'll eventually hit a tipping point where it costs you more to use non-renewables and the migration becomes self-sustaining at that point.

  • Neuralink looks to the public to solve a seemingly impossible problem
  • It's important to distinguish between lossy and lossless algorithms. What was specifically requested in this case is a lossless algorithm which means that you must be able to perfectly reassemble the original input given only the compressed output. It must be an exact match, not a close match, but absolutely identical.

    Lossless algorithms rely generally on two tricks. The first is removing common data. If for instance some format always includes some set of bytes in the same location you can remove them from the compressed data and rely on the decompression algorithm to know it needs to reinsert them. From a signal theory perspective those bytes represent noise as they don't convey meaningful data (they're not signal in other words).

    The second trick is substituting shorter sequences for common longer ones. For instance if you can identify many long sequences of data that occur in multiple places you can create a lookup index and replace each of those long sequences with the shorter index key. The catch is that you obviously can't do this with every possible sequence of bytes unless the data is highly regular and you can use a standardized index that doesn't need to be included in the compressed data. Depending on how poorly you do in selecting the sequences to add to your index, or how unpredictable the data to be compressed is you can even end up taking up more space than the original once you account for the extra storage of the index.

    From a theory perspective everything is classified as either signal or noise. Signal has meaning and is highly resistant to compression. Noise does not convey meaning and is typically easy to compress (because you can often just throw it away, either because you can recreate it from nothing as in the case of boilerplate byte sequences, or because it's redundant data that can be reconstructed from compressed signal).

    Take for instance a worst case scenario for compression, a long sequence of random uniformly distributed bytes (perhaps as a one time pad). There's no boilerplate to remove, and no redundant data to remove, there is in effect no noise in the data only signal. Your only options for compression would be to construct a lookup index, but if the data is highly uniform it's likely there are no long sequences of repeated bytes. It's highly likely that you can create no index that would save any significant amount of space. This is in effect nearly impossible to compress.

    Modern compression relies on the fact that most data formats are in fact highly predictable with lots of trimmable noise by way of redundant boilerplate, and common often repeated sequences, or in the case of lossy encodings even signal that can be discarded in favor of approximations that are largely indistinguishable from the original.

  • Google Search’s “udm=14” trick lets you kill AI search for good
  • I feel like Google is trying to speedrun killing their search service. It was already significantly shittier lately just because of all the sponsored bullshit and SEO spam, but this rush to cash in on the AI fad has really destroyed the last utility it had.

  • Neuralink looks to the public to solve a seemingly impossible problem
  • The implication of a 200 to 1 algorithm would be that the data they're collecting is almost entirely noise. Specifically that 99.5% of all the data is noise. In theory if they had sufficient processing in the implant they could filter the data down before transmission thus reducing the bandwidth usage by 99.5%. It seems like it would be fairly trivial to prove that any such 200 to 1 compression algorithm would be indistinguishable in function from a noise filter on the raw data.

    It's not quite the same situation, but this should show some of the issues with this:

  • /e/OS Is Better Than Android. You Should Try It
  • Honestly the short 5 year from original release till EOL thing really fucking annoys me, but it's literally every phone on the market. I've looked, it's impossible to find a phone that doesn't force you to replace it every few years unless you go to a plain dumb phone that only supports voice calls and maybe basic SMS with no apps. That's just a nonstarter in this day and age.

    Even alternative Android firmware like GrapheneOS and /e/OS are dependent on the stock firmware releases by the phone manufacturer so when the manufacturer goes EOL and stops releasing updates your alternative installs also are effectively EOL.

    The only solution to this problem I've seen that seems like it has a chance is Linux Phone OS, but it still has several problems that make it unusable for most people (biggest one probably being that it provides absolutely terrible battery life).

  • /e/OS Is Better Than Android. You Should Try It
  • Technically you're correct, but it's effectively the same thing since I've literally never used NFC for anything besides contactless payment and initial phone setup when migrating from an older Android phone to a newer one. For most people NFC is synonymous with contactless payment.

  • /e/OS Is Better Than Android. You Should Try It
  • You know that if someone skims your card and makes a fraudulent purchase, you will likely be able to get your money back, right?

    Sure but it's a major pain in the ass. Every time it happens I have to cancel my current cards, request a new one, find all the services I'm currently paying with the now cancelled card and update them to a different card while I wait for the replacement, and then maybe remember to swap them back when the new card shows up. It doesn't happen constantly but if I use cards to pay they seem to get skimmed about once every year or two.

    What do you think will happen if someone exploits a 0-day in GPay to do this? How could your bank know the purchase was fraudulent? At least with a card it is obvious that this can happen.

    Literally never happened before, but same way they know a credit charge is fraudulent, I tell them. Also if someone found a 0-day in GPay I wouldn't be the only one complaining of fraudulent charges, they'd be flooded with complaints.

    If you care about "secure" payments that much, why not use cash?

    Because that's a pain in the ass. I don't care about "secure" payments, I care about not having to spend days dealing with the aftermath of it. Paying with cash means I need to constantly go to ATMs to withdraw money, and if I'm doing that my odds of getting my card skimmed actually go up so it doesn't even protect my from that.

  • Greater Idaho movement: 13 counties in eastern Oregon have voted to secede and join Idaho
  • I'm trying to decide if this would be a net positive or negative.

    Looking at the congressional districts for Oregon and Idaho it looks like about 5 or 6 districts that are all Republican controlled. Currently Idaho has two congressional districts that both lean heavily Republican. Shifting 5 or 6 Republican congressional seats from Oregon to Idaho I don't see making a significant difference to Congress.

    Looking at things in the Senate both Idaho senators are Republican and adding more Republican districts won't really change that in any meaningful way. On the flip side both of Oregon's Senators are currently Democrats and I can't imagine removing a bunch of Republican voters from the state would do anything but reduce the chances of one of those Senate seats getting flipped.

    I'm not really seeing any way in which this would help Republicans or hurt Democrats other than just by generally strengthening each party's hold on its respective state.

  • /e/OS Is Better Than Android. You Should Try It
  • Not my entire payment record but certainly everything I use my phone to pay for. I'm willing to give Google some of my info as long as I'm in control of what info I'm giving them. Everything I do on my phone is too much. If a 3rd party offered a NFC payment app I'd happily use that over GPay, but until that exists GPay is the only option. Ultimately GPay is safer than using actual credit cards because it's more resistant to skimming. The extra security outweighs the loss of privacy in this specific case. I'm not happy about that but there doesn't seem to be a better alternative at this time.

  • /e/OS Is Better Than Android. You Should Try It
  • Ultimately the real solution to a lot of these problems is likely to be a Linux phone OS. It's something being actively worked on, but it's still only half baked and I wouldn't recommend anyone daily drive a Linux phone. Maybe in a few more years it will reach a state where it's actually usable.

    One thing that would help a lot is if some company stepped up to provide a platform agnostic NFC payment solution that worked on both iOS and Android. As far as I'm aware if you want NFC payment you have exactly one choice depending on your OS, and both Apple and Google brick NFC if you root your device.

  • /e/OS Is Better Than Android. You Should Try It
  • Unfortunately the fact that NFC can't be used on anything that's rooted anymore is kind of a deal breaker. If I could use google pay and my normal banking apps with GrapheneOS I would switch to it today.