• 0 Posts
  • 367 Comments
Joined 3 years ago
cake
Cake day: November 4th, 2023

help-circle



  • This is exactly it.

    When you run your AI in the cloud you are trading some privacy and security, as well as higher operating expenses, for convenience and lack of upfront cost. This is no different than any other cloud service.

    Go back a decade and everybody said cloud is the only future, companies will throw their servers in the garbage, etc. Now a lot of companies have moved workloads back on premises because the simple fact is the cloud provider is buying the same servers and has to pay the same price for them you are just paying for that and also for their profit and overhead.

    There’s also the simple fact that even the best models have proven unsafe to be turned loose without human intervention. So if you have to have a human reviewing the output anyway, why pay a boatload more for slightly better output?

    I just hope when this bubble pops there isn’t some taxpayer bailout. Let OpenAI go bankrupt if that’s what it takes. Let the idiots who financed data centers with blank checks lose their shirts. There needs to be a lesson for the next bubble.


  • If you build a tool and in the process of building it it causes harm, that should be on you. If some model under development hacks into another company, the developer should be held criminally and civilly liable.

    If you build a tool and someone else uses it to cause harm, that person is 100% liable. It is not your responsibility to prevent your tool from being able to cause every possible harm.

    If you build a tool and someone else uses it as intended, but it malfunctions and causes harm, the developer should be liable for that just like any other product liability situation.

    Think of it like a riding mower. If I bypass the safety systems and point it toward my neighbor’s house and it runs over their dog, that’s on me not the manufacturer. But if I am riding along and suddenly it knocks me off the top and keeps going on to the neighbor’s yard and runs over their dog, that is on the manufacturer for building an unsafe mower.




  • Do you want to explain to a thirteen year old how it’s not a big deal if someone is passing around realistic nudes of them that were AI-generated?

    No of course not. But how’s that different than when one of her classmates takes Photoshop 101? What do you tell the 13yo whose face is photochopped onto a porn star? Same thing.

    I’m 100% with you that it sucks, and I’m not convinced generative AI has done much of anything useful to outweigh its societal and resource costs.
    You could require all cloud AI to embed tracking data in each image, so when little Johnny nudify’s his classmate we can trace who made the image. But lots of cloud AI companies are outside the USA. And that won’t affect local models.



  • Honestly this seems like a waste.

    If there was some free community edition of this I’d deploy it at our org. But I can promise you that I couldn’t get $1 approved for buying a browser, not when there’s plenty of free options.

    The other thing- contact us for demo- I mean this with all respect but FUCK OFF WITH THAT SHIT. That’s what companies do so they don’t have to list their million-dollar price tag, and/or want to size up how much they can rip you off for before quoting you. You want people to buy this, make it transparent.


  • Honestly I think this whole conversation is stupid.

    It’s always been possible to photoshop a celebrity’s face onto a pornstar’s naked body. That’s been a thing for decades.

    So you talk about guardrails to prevent AI from doing this, and you use the word ‘safety’- I don’t think that word means what you think it means.

    To me, AI ‘safety’ is not accidentally creating an AI that will find a bunch of 0day exploits and use them to destroy the Internet. Making AI not spit out spicy pics has nothing to do with ‘safety’.

    So if an AI model can spit out a naked pic of someone, honestly, I really don’t care. It’s shitty for sure, but if the big companies block it (which they probably can’t) some little operator will spring up and fill the gap.


  • Agree 100%.

    It’s the same thing with undocumented immigrants in the USA. They are an easily exploited underclass, they required no rights because if there’s conflict you just report them to ICE and away they go. As such they will work in awful conditions for shit pay.

    Maybe the solution is to enforce the immigration regs and penalize employers who hire undocumented people. Maybe the solution is to relax the immigration regs and encourage undocumented workers to stand up for themselves. I think the former is more likely because you’re not pushing through a cultural barrier.




  • I’m surprised. This actually has teeth.

    host of companies, including Cognizant, Infosys, Capgemini, Tata, Wipro and HCL.

    Many of these companies literally have the business model of letting you replace your expensive American tech people with cheaper foreign ones, either importing them as H1B or offshore remote.

    “Since 2009, just these companies alone have requested almost 3 million foreign workers. They’ve received over 230,000 H-1B visas approvals and over 100,000 permanent labor certifications…”

    I promise you there weren’t 3 million jobs that NO American tech workers were qualified for. There wasn’t 230k or 100k either.

    What there was, is 3 million positions that the companies didn’t want to pay American salaries for.

    So they post the job like ‘experienced tech needed. Must know (laundry list of 20 different systems) intricately. 10+ years experience preferred. Starting salary $45k’ and they get no applications because that skill set requirement is a $100k-$200k position. So they claim there’s no Americans to do the job and get H1B approval.



  • Most smartphones encrypt the majority of their storage these days.

    This means there are two states the phone can be in.

    BFU, or Before First Unlock, is the most secure. When you power on the phone it has just enough software in unencrypted storage to come on, initialize its hardware, start some background processes, and display an unlock screen. This is the most secure state for the phone. When you type in your password, the password itself decrypts the actual key which is used to decrypt the main storage. Without that password, the data is essentially useless as it cannot be decrypted. Also, most phones are now set up so that if you try the wrong password 10 times, it will erase the main storage encryption key which means the data is completely unrecoverable forever. In general, it doesn’t matter what you can exploit BFU because there’s very little running to exploit and the storage encryption key is usually stored in a secure enclave, that is a special part of a chip that is designed to resist tampering.

    Once you type in your password the first time, the phone is AFU, or After First Unlock. The key to access main storage is held in memory, it is being actively used to read and write from that storage as software is running on the phone like email, background apps, etc. The prompt to unlock the phone looks exactly the same, but in reality the phone is in a much less secure state. There’s plenty of software, both system and apps, running for you to try to exploit.

    The point here is that if you set the phone to regularly reboot, or to reboot if you haven’t logged in in a day or two, each time it reboots it switches back to BFU state.

    And so if some government agency has arrested you and seized your phone, you want that reboot to happen because if the phone automatically reboots before they manage to get into it, it becomes much much harder for them to get in.