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

  • 0 Posts
  • 8 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle
    • Algorithm shows a preview of a chaotic scene where the content isn’t easily identified.
    • You open / interact / linger on it to figure out what is happening before identifying it as something you don’t want to look at.
    • Algorithm detects increased interaction and happily serves up more.

    I play a little game with Instagram sometimes. I click on one (1) thirst trap bikini girl post in the search reel. Then I see how many times I have to press the little 3 dot menu and pick “not interested” on allllll the other thirst trap bikini girl posts that immediately appear.

    I generally have to press “not interested” about 15 times before my feed reverts to only having bikini girl thirst traps once every 20 or so posts.





  • The smaller end is RJ12, the bigger end is RJ45.

    The question is, what are you trying to do with it? RJ12 is/was typically used for telephone connections, RJ45 for Ethernet. Generally speaking, they don’t mix.

    If your plan is to connect a computer to a RJ12 socket on the wall, that’s not going to work. If you’ve been told the socket on the wall is “the internet”, you’re likely going to need a modem in between that socket and your computer.



  • I was talking more about unwrap causing a panic rather than calling the actual panic macro directly. Rust forces the programmer to deal with bad or ambiguous results, and what that is exactly is entirely decided by the function you are calling. If a function decides to return None when (system timer mod 2 == 0), then you’d better check for None in your code. Edit: otherwise your code is ending now with a panic, as opposed to your code merrily trotting down the path of undefined behaviour and a segfault or similar later on.

    Once you get to a point where we are doing the actual panic, well, that is starting to just be semantics.