• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle

  • instead of blocking advertising data, we should embrace it IMO.

    imagine a world where users shove so much information at these tools that they can’t even tell what’s real or not. camouflage works better when everyone participates.

    There’s an ad blocker that does exactly this. Called Ad Nauseam. Chrome blocked it from their store super fast, then blocked it from being installed in Chrome from 3rd party sites, then blocked known versions of it from being manually installed in developer mode. I used to run it set to a low percentage - if I “clicked” every ad they’d know to throw my data out, but if I click say 3% of them…






  • With the introduction of protected mode it became possible for programs to run in isolated memory spaces where they are unable to impact other programs running on the same CPU. These programs were said to be running “in a jail” that limited their access to the rest of the computer. A software exploit that allowed a program running inside the “jail” to gain root access / run code outside of protected mode was a “jailbreak”.

    I still miss the narrow window in which you could make use of paging without technically being in protected mode. Basically there was like one revision of the 386 where you could set the paging bit but not protected mode and remain in real mode but with access to paging meaning you got access to paging without the additional processor overhead of protected mode. Not terribly useful since it was removed in short order, but neat to know about. Kinda like how there were a few instructions that had multiple opcodes and there was one commercially distributed assembler that used the alternative opcodes as a way to identify code assembled by it. Or POP CS - easily the most useless 80086 instruction, so useless that the opcode for it got repurposed in the next x86 processor.










  • Except I couldn’t. Because a person being influenced by an artwork and then either intentionally or subconsciously reinterpreting that artwork into a new work of art is a fundamentally different thing from a power hungry machine learning algorithm digesting the near entirety of modern humanity’s art output

    The big differences there are whether it’s a person or a machine and just how much art one can digest as inspiration. Again, reference my example of a commission above - the main difference between a human and an AI making it is whether they look up a couple dozen examples of each element to get a general idea or 100 million examples of each element to mathematically generalize the idea, and the main reason the number of examples and power requirements need to be so different is that humans are extremely efficient pattern developing and matching machines, so efficient that sometimes the brain just fills in the pattern instead of bothering to fully process sensory inputs (which is why a lot of optical illusions work).

    to churn out an image manufactured to best satisfy some random person’s text prompt.

    At a level, “churning out an image to best satisfy some random person’s” description is essentially what happens when someone commissions a work or when producing things to spec as part of some project. They don’t generally say “just draw whatever you are inspired to” and hope they like the result. This is the thing that AI image generators are specifically good at, and is why I say it’s about protectionism for a class of workers who didn’t think their jobs could be automated away in whole or in part.

    But we’re not just talking about automating someone’s job.

    Except you are, you are just deeming that job “someone’s dream career” as though that changes whether or not it’s a job that is being automated in whole or part. Yes, it’s going to hurt the market for commissioned art works and the like. Again, upset because those jobs are supposed to be immune to automation and - whoopsie - they aren’t. Join the people in manufacturing, or the makers of buggy whips.

    We’re talking about automating someone’s passion.

    Literally no one is going to ban or forbid anyone from creating art because AI art exists.


  • This is problematic at best and flat out dishonest thievery at worst.

    You could say that about literally all art - no artist can name and attribute every single influence that played even the smallest effect on the work created. Say I commissioned an image of an anime man in a french maid uniform in a 4 panel pop art style. In creating it at some level you are going to draw on every anime image you’ve seen, every picture of a french maid uniform, every 4 panel pop art image and create something that’s a synthesis of all those things. You can’t name and attribute every single example of all of those things you have ever seen, as well as anything else that might have influenced you.

    Whereas a work made by a person that is dirivitive or parody has actual work and thought put into it by an actual person.

    …and this is the crux of it - it’s not anything related to the actual content of the image, it’s simple protectionism for a class of worker. Basically creatives are seeing the possibility of some of their jobs being automated away and are freaking out because losing jobs to automation is something that’s only supposed to effect manufacturing workers.

    Even if it is dirivitive it’s unique in some way simply by virtue of being made by a person.

    Again, the argument is it’s nothing to do with the actual result, but with it being done by an actual human as opposed to a mere machine. A pixel for pixel identical image create by a human would be “art” by virtue of it being a human that put each pixel there?


  • That analogy was chosen for a reason. Ada was originally developed by DOD committee and a French programming team to be a programming language for Defense projects between 1977 and 1983 that they were still using at least into the early 2000s. It’s based on Pascal.

    It was intended for applications where reliability was the highest priority (above things like performance or ease of use) and one of the consequences of that is that there are no warnings - only compiler errors, and a lot of common bad practices that will be allowed to fly or maybe at worst generate a warning in other languages will themselves generate compiler errors. Do it right or don’t bother trying. No implicit typecasting, even something like 1 + 0.5 where it’s obvious what is intended is a compiler error because you are trying to add an integer to a real without explicitly converting either - you’re in extremely strongly-typed country here.

    Libraries are split across two files, one is essentially the interfaces for the library and the other is it’s implementation (not that weird, and not that different than C/C++ header files though the code looks closer to Pascal interface and implementation sections put in separate files). The intent at the time being that different teams or different subcontractors might be building each module and by establishing a fixed interface up front and spelling out in great detail in documentation what each piece of that interface is supposed to do the actual implementation could be done separately and hypothetically have a predictable result.