• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle

  • Mirodir@discuss.tchncs.detoProgrammer Humor@programming.devSus
    link
    fedilink
    arrow-up
    111
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Sure. You have to solve it from inside out:

    • not()…See comment below for this one, I was tricked is a base function that negates what’s inside (turning True to False and vice versa) giving it no parameter returns “True” (because no parameter counts as False)
    • str(x) turns x into a string, in this case it turns the boolean True into the text string ‘True’
    • min(x) returns the minimal element of an iterable. In this case the character ‘T’ because capital letters come before non-capital letters, otherwise it would return ‘e’ (I’m not entirely sure if it uses unicode, ascii or something else to compare characters, but usually capitals have a lower value than non-capitals and otherwise in alphabetical order ascending)
    • ord(x) returns the unicode number of x, in this case turning ‘T’ into the integer 84
    • range(x) creates an iterable from 0 to x (non-inclusive), in this case you can think of it as the list [0, 1, 2, …82, 83] (it’s technically an object of type range but details…)
    • sum(x) sums up all elements of a list, summing all numbers between 0 and 84 (non-inclusive) is 3486
    • chr(x) is the inverse of ord(x) and returns the character at position x, which, you guessed it, is ‘ඞ’ at position 3486.

    The huge coincidental part is that ඞ lies at a position that can be reached by a cumulative sum of integers between 0 and a given integer. From there on it’s only a question of finding a way to feed that integer into chr(sum(range(x)))



  • after leaving can’t join another for a year

    Can you fix this? There was enough misinformation floating around about this already when this feature went into beta.

    Adults can leave a family at any time, however, they will need to wait 1 year from when they joined the previous family to create or join a new family.

    it should say something like: “After joining, can’t join another for a year”




  • I’d argue that with their definition of bots as “a software application that runs automated tasks over the internet” and later their definition of download bots as “Download bots are automated programs that can be used to automatically download software or mobile apps.”, automated software updates could absolutely be counted as bot activity by them.

    Of course, if they count it as such, the traffic generated that way would fall into the 17.3% “good bot” traffic and not in the 30.2% “bad bot” traffic.

    Looking at their report, without digging too deep into it, I also find it concerning that they seem to use “internet traffic” and “website traffic” interchangeably.


  • Without knowing any specifics of the TOS or the exact setup beyond what I could gather in this thread: generally speaking they could still send you a bill through email or otherwise.

    After that, if you’re not paying up, they might be able to successfully get the money out of you through court regardless, depending on a few factors. What’s more likely for smaller sums is that they’ll just drop it and ban you though.

    IANAL of course.


  • I think the humor is meant to be in the juxtaposition between “reference” in media contexts (e.g. “I am your father”) and “reference” in programming contexts and applying the latter context to the former one.

    What does “I’m your father” mean if the movie is jaws?

    I think the absurdity of that question is part of said humor. That being said, I didn’t find it funny either.





  • I’m not really sure how to describe it other than when I read a function to determine what it does then go to the next part of the code I’ve already forgotten how the function transforms the data

    This sounds to me like you could benefit from mentally using the information hiding principle for your functions. In other words: Outside of the function, the only thing that matters is “what goes in?” and “what comes out?”. The implementation details should not be important once you’re working on code outside of that function.

    To achieve this, maybe you could write a short comment right at the start of every function. One to two sentences detailing only the inputs/output of that function. e.g. “Accepts an image and a color and returns a mask that shows where that color is present.” if you later forget what the function does, all you need to do is read that one sentence to remember. If it’s too convoluted to write in one or two sentences, your function is likely trying to achieve too much at once and could (arguably “should”) be split up.

    Also on a different note: Don’t sell your ability to “cludge something together” short. If you ever plan to do this professionally or educationally, you will sadly inevitably run into situations where you have no choice but to deliver a quick and dirty solution over a clean and well thought out one.

    Edit: typos


  • While I agree with you and also agree with the decision to not show it anymore, I do want to highlight this bit that you wrote:

    instead dad physically abuses the misbehaving child and nothing is ever resolved

    The positive thing is that it never (or so raraly that I wouldn’t remember) presented the strangling as anything good or helpful. Instead it was always presented as a shortcoming of his personality. Homer is mentally ill equipped to solve conflicts with Bart non-violently. Strangling him was his only outlet and (at least to attentive viewers) it was clearly and evidently damaging Bart’s development. This is for example demonstrated in a scene where Bart has such a trauma that he’s getting “strangled” by thin air when he thinks his dad would go for it.

    Also, with the knowledge that Bart is, to some extent, Matt Groening’s self-insert, that does raise some rather unpleasant questions.


  • I went and skimmed the paper because I was curious too.

    If my skimming is correct, what they do is similar to adversarial attacks on classifiers, where a second model learns to change as few pixels as possible to confuse a classifier into giving a wrong prediction.

    Looking at the examples of dogs and cats: They find pictures of dogs where by making only minimal changes, invisible to the naked eye, they can get the autoencoder to spit out (almost) the same latent representation as an image of a cat would have. Done to enough dog-images, this will then confuse the underlying diffusion model to produce latent representations of cat images when prompted to generate a dog. Edit for clarity: Those generated latent representations would then decode into cat images.

    If my thinking doesn’t fail me, this attack could easily be thwarted by unfreezing the pretrained autoencoder. In the paper that introduced latent diffusion they write that such approaches already exist. If “Nightshade” takes off, I’m sure those approaches would be refined and used. Even just finetuning the autoencoder for a few epochs first should be enough to move the latent representations of the poisoned dog images and those of the cat images they’re meant to resemble far enough apart to make the attack meaningless.

    Edit: I also wonder how robust this attack is against just adding an imperceptible amount of noise to the poisoned images.