• 1 Post
  • 36 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • Yup. Rand() chooses a random float value for each entry. By default I believe it’s anywhere between 0 and 1. So it may divide the first bill by .76, then the second by .23, then the third by 0.63, etc… So you’d end up with a completely garbage database because you can’t even undo it by multiplying all of the numbers by a set value.












  • Make declaration of war a mandatory vote for every citizen. Anyone who votes “yes” (or illegally abstains) gets registered for the draft. Anyone who votes “no” is unregistered.

    I know it’s not really feasible because governments need to be able to react swiftly in times of war. But these days with computers and cell phones, there’s very little reason that the government couldn’t push a “go download our secure voting app/visit this link to cast your vote” notification via the emergency alert broadcasting system.


  • It isn’t compressible at all, really. As far as a compression algorithm is concerned, it just looks like random data.

    Imagine trying to compress a text file. Each letter normally takes 8 bits to represent. The computer looks at 8 bits at a time, and knows which character to display. Normally, the computer needs to look at all 8 bits even when those bits are “empty” simply because you have no way of marking when one letter stops and another begins. It’s all just 1’s and 0’s, so it’s not like you can insert “next letter” flags in that. But we can cut that down.

    One of the easiest ways to do this is to count all the letters, then sort them from most to least common. Then we build a tree, with each character being a fork. You start at the top of the tree, and follow it down. You go down one fork for 0 and read the letter at your current fork on a 1. So for instance, if the letters are sorted “ABCDEF…” then “0001” would be D. Now D is represented with only 4 bits, instead of 8. And after reading the 1, you return to the top of the tree and start over again. So “01000101101” would be “BDBAB”. Normally that sequence would take 40 bits to represent, (because each character would be 8 bits long,) but we just did it in 11 bits total.

    But notice that this also has the potential to produce letters that are MORE than 8 bits long. If we follow that same pattern I listed above, “I” would be 9 bits, “J” would be 10, etc… The reason we’re able to achieve compression is because we’re using the more common (shorter) letters a lot and the less common (longer) letters less.

    Encryption undoes this completely, because (as far as compression is concerned) the data is completely random. And when you look at random data without any discernible pattern, it means that counting the characters and sorting by frequency is basically a lesson in futility. All the letters will be used about the same, so even the “most frequent” characters are only more frequent by a little bit due to random chance. So now. Even if the frequency still corresponds to my earlier pattern, the number of Z’s is so close to the number of A’s that the file will end up even longer than before. Because remember, the compression only works when the most frequent characters are actually used most frequently. Since there are a lot of characters that are longer than 8 bits and those characters are being used just as much as the shorter characters our compression method fails and actually produces a file that is larger than the original.


  • but some other secure facility that maximizes the ability of these people to make whatever contribution to society they may be able to make to society.

    Yeah, I touched on that with my last sentence:

    It may be called something else in the future (like a long-term involuntary mental health facility,) but it’s still serving the same basic function while wearing a more friendly mask.

    There are two problems with that. The first is that “maximizing contribution to society” can easily be interpreted as “being forced to stamp license plates for 16 hours a day.” We already know this is a possible interpretation, because that’s how our system already interprets it. Either way they’re locked up against their will, and are being forced to perform labor to someone else’s benefit. The very nature of their confinement means that any contribution they make will be for someone else and not themselves. And the simple word for that is “slavery”. The second problem is that it’s still prison. We haven’t actually solved the prison problem at all in this scenario; We’ve simply given it a mask so we can say prisons have been abolished. Like if we don’t call them prisons, we can say we don’t have any prisoners.


  • Prisons will still be necessary for the most egregious and irredeemable criminals. The sad reality is that there are certain people who simply need to be sequestered from the rest of society for the general public’s safety, and no amount of rehabilitation or intervention will solve that. But that should be the exception, not the norm. The massive prison population is absolutely a problem, but it isn’t something that can be completely abolished. It may be called something else in the future (like a long-term involuntary mental health facility,) but it’s still serving the same basic function while wearing a more friendly mask.



  • Not only that; You have to pay for updates too. Supposedly it’s because Apple takes time to verify that the app is legit and not going to do nefarious things. So they don’t want a bad actor to get a legit app on the store, then later push an update that infects everyone with a virus.

    But apparently a company did a study and realized that app testing rarely made it past the main page, with testers spending ~15-20 seconds per app. They’d basically open it and if it looked like it did what it said, they didn’t bother digging any deeper.