• 1 Post
  • 97 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle

  • In my school they encouraged you to come up with techniques like this.

    You’re either very lucky and were in a school that went against established norms, or you’re young enough that you were taught the “new” math that boomers hate. Because this is the new math.

    Boomers, GenX, and elder millennials were primarily taught via rote memorization. You simply memorized the times tables, and committed “8*3=24” to memory. You didn’t calculate it every time. You just memorized the tables, regurgitated them ad nauseam to appease the teachers, and then referred to those memorized tables for any multiplication you needed to do.

    For reference, this is the times table I’m referring to. Our quizzes/tests required you to fill out the entire thing in less than 5 minutes:

    We had to fill this out multiple times per week. The goal of the time limit was to force you to memorize it, instead of calculating it out every time. You simply didn’t have time to calculate each one out. Then once you had it memorized, if you ever had to do 8*3, you would just refer to your memorized times tables for it.

    But the issue with this is that it doesn’t teach you how to actually do the math in your head, it just teaches you the times tables. You aren’t calculating it out each time, so you don’t develop any shortcuts or methods to make it easier. If a teacher ever saw you turn 9+7 into 10+6, they would bust out the red pen and start slashing. Even though 10+6 is undeniably easier to do in your head, the teachers weren’t concerned with that; They wanted to know that you had memorized what 9+7 is. These memes are primarily aimed at the millennials and GenX with ADHD, because they were the ones who got bored of rote memorization and started coming up with shortcuts (which then got docked points on their quizzes.)


  • Yup, this is what parents are complaining about when they say math has changed. Before, math was primarily about rote memorization. You just memorized that 9+7 is 16. There were multiplication tables you were expected to memorize and regurgitate ad nauseam. Sure you could count it out on your fingers, but that only works for numbers under 11. For anything above that, you just referred to your memorized addition, subtraction, multiplication, or division tables. But this also meant that numbers outside of those tables were really difficult to do in your head, because you were poorly equipped to actually calculate them out.

    Common core math is attempting to make math easier to do in your head, by teaching the concepts (rather than promoting rote memorization) and helping students learn shortcuts to avoid getting lost. 9+7 is 16, but it’s also 10+6 or 8*2, which are much easier to visualize in your head without counting on your fingers.


  • I first heard about it due to my buddy (a high school English teacher) complaining about how his incoming students were incredibly far behind in basic reading comprehension skills. We ended up having a pretty long talk about it, and he mentioned that all of his colleagues have noticed the same thing.

    I did some digging, and discovered that language teachers everywhere have basically been lamenting the fact that the upcoming generation just straight up doesn’t know how to interpret media when it falls outside of their personal algorithms. I ended up talking with another buddy of mine (a writer for a magazine) and he mentioned that they have started needing to change the way they write, because people have simply lost the ability to comprehend what they read. Skimming the first one or two paragraphs is the new norm, even for in-depth news articles. So they have to load as much content into the early paragraphs as possible.


  • Yeah I bought my N64 when GameStop was liquidating their stock to make room for the next gen stuff. It was like $50 for a refurb console, two controllers, and a few games. Plus games and peripherals were only like $3 each because they were trying to clear their inventory.

    I walked in with like $150, and walked out with a fully fleshed out console (four controllers, memory expansion pack, memory cards, etc) and a full library of games.




  • I tend to front-load my comments as much as possible, to try and avoid just that. Make the main point ASAP. But even then, there’s only so much you can do without sounding messy.

    For instance, I front-loaded the part about reader comprehension. All of the “why” is in later paragraphs. But even if they only read the first few sentences, they’ll at least get my overall point.

    It does make nuanced discussion impossible though. I work in a pretty specialized field (professional audio) with lots of snake oil myths about what will or won’t make your system sound better. There have been several times that I have seen people parroting this snake oil type stuff as if it is genuine advice. And often, this advice happens because the person only has a surface-level understanding of how audio works. Something sounds plausible, (and they don’t understand the underlying principles that would disprove it,) so they end up perpetuating the myth. So a lot of discussions boil down to “well kind of but not really” and people won’t bother reading anything past the “well kind of” part.



  • This is also due to a distinct drop in reader comprehension. One of the largest parts of reading comprehension is being able to infer the intended audience for a particular piece of work. You should be able to read a news article, see a commercial, read a comment, etc and infer who it is aimed at. And the answer is usually not “me”.

    People have become accustomed to having an algorithm that is laser focused to their specific preferences. So when they see something that’s not aimed at them it is jarring, and they tend to get upset. Instead of going “oh this clearly isn’t aimed at me, but I can infer who the intended audience is. I’ll move on.” Now they tend to jump on the creator with whataboutisms and imagined offense.

    Maybe you make a post about the proper way to throw a football. You’ll inevitably get a few “bUT wHaT abOUt WhEElcHaiR uSerS, I hAvE a baD ShoUlDer aNd cAn’T thROW SO wHaT abOUt me, I haTE FoOtbAll wHY aRe yOU SHowiNG tHIs to Me, etc” types of comments. It’s because those users have lost the ability to infer an intended audience. They automatically assume everything they see is aimed at them, and get offended when it isn’t.

    I have even noticed this started to affect the way media is written. Creators tend to make it a point to outright state their intended audience, just to avoid the negative comments.



  • You don’t need to run it on a pi. In fact, I’d actually argue against it; A pi will be underpowered if you’re ever needing to transcode anything. Transcoding is what Plex/Jellyfin does if your watching device can’t natively play the video. Maybe you have a 4k video, but you’re playing it on a 1080p screen. That video will need to be transcoded from 4k into 1080p for the screen to be able to display it. Or maybe the file is encoded using ACC (a fairly recent encoding method) which isn’t widely supported by older devices. This often happens with things like smart TVs (which often don’t support modern encoding and need to be transcoded even if the resolution is correct.)

    Basically, if you’re 100% positive that every device you’re watching it on will never need transcoding, then a pi is acceptable. But for anything else, I’d recommend a small PC instead. You can even use an old PC if you have one laying around.

    Or if you want to use a new machine, maybe something like an HP Elitedesk. They’re basically what you see in every single cubicle in every single office building. They’re extremely popular in corporate settings, which means there are a ton of used/refurbished systems available for cheap, because IT destroys the drives and sends the rest to refurb when they upgrade their fleet of PCs. So for the refurb you’re basically just paying the cost of an SSD they added in (to replace the one IT pulled out), plus whatever labor is associated with dusting it out and checking the connections to make sure they all work. You can pick up a modern one for like $250 on Amazon (or your preferred electronics store).

    Worth noting that the elitedesk generations are marked by a G-number, so google the model (like an EliteDesk G9, G7, etc) to see what kind of processor it has; Avoid anything with an intel 13th or 14th generation CPU, (they have major reliability issues) and check with Plex/Jellyfin’s CPU requirements list to see if it supports hardware accelerated transcoding. For Intel chips, look for QuickSync support.

    For storage, I’d recommend running a NAS with however many hard drives you can afford, and one that has extra ports for future expandability. Some NAS systems support Plex and/or Jellyfin directly, but the requirements for full support are tricky and you’ll almost always have better luck just running a dedicated PC for Plex. Then for playing, one of two things will happen. Either the device is capable of directly playing the file, or it will need to be transcoded. If it’s directly playing, the plex server basically just points the player to the NAS, and the player handles the rest. If it’s transcoding, the PC will access the NAS, then stream it to the player.

    As for deciding on Plex vs Jellyfin, that’s really a matter of personal preference. If you’re using Plex, I’d highly suggest a PlexPass sub/lifetime purchase; Wait until Black Friday, because they historically do a (~25% off) discount on their lifetime pass. Plex is definitely easier to set up, especially if you plan on streaming outside of your LAN.

    Jellyfin currently struggles from a lack of native app support; Lots of smart TVs don’t have a native Jellyfin app, for instance. But some people have issues and complaints (many of them justified!) with Plex, so if the FOSS sounds appealing, then consider Jellyfin instead. Jellyfin is also rapidly being developed, and many people expect it to have feature parity with Plex within a few years.

    And if you’re having trouble deciding, you can actually set up both (they can run in tandem on the same machine) and then see which one you prefer.

    And the nice part about using a mini PC is that you can also use it for more than just Plex/Jellyfin. I have the *arr suite running on mine, alongside a Factorio server, a Palworld server, and a few other things.



  • If you’re referring to the wavy pattern along the cutting edge, that’s not from the folding process. The hamon is added to the blade during the quenching process, by adding clay to the steel. The clay causes the covered steel to heat differently than the uncovered steel. That differential heating is what is visible as the hamon.

    It’s largely decorative, but does have function as it determines what part of the blade can be sharpened to an edge.


  • Yeah, Japanese steel wasn’t great, but they were working with what they had available at the time. Katanas were basically made out of iron dust, which had been melted into slag by filtering through charcoal. The resulting chunks of steel were basically straight up slag, not nice even ingots. So the steel they got was actually extremely high carbon in places, but that also meant it was brittle as hell, because those carbon pockets were prone to shattering.

    So the folding was invented, to even out the steel’s carbon content (just like how a Damascus steel blade has visible stripes, Japanese steel had invisible stripes of high and low carbon steel) and to lower the carbon content overall; Every time you heat for another fold, you’re evaporating some carbon. So the folding process took the steel from extremely high carbon pockets to a more evenly distributed carbon content.

    Now that modern steel processing exists, the only real reason to stick to the folding method is tradition. There’s no need to fold modern steel ingots because they’re already homogenous and can be produced at whatever carbon level you want.



  • This looks like it was a timing analysis attack. Basically, they’re trying to figure out which user did something specific. They match the timing of the event with the traffic from the user, and now they know which user did the thing.

    It can be fuzzed by streaming something at the same time, because now your traffic is way harder to time analyze when you have a semi-constant stream of data running. But streaming something over Tor is an exercise in patience, (and it’s not something the typical user will just always have running in the background) so timing analysis attacks are gaining popularity.