[–] 3 points 5 months ago

I use openrouter for my of my paid online calls, when setting up API keys you get to set a budget. Easy. It's also pre-paid so unless I turn on auto-charge for my credit card (which is off by default) it will never blow more than I've already loaded. Two layers of safety are better than one.

  • source
  • parent
  • context
  • [–] 9 points 5 months ago (1 child)

    That's why I refuse to use most cloud API keys. The API keys always default to take the money first. Anthropomorphic already has their money. They're not getting it back.

    I'm just a home user and worry that if my security slipped for one moment over my entire life, my keys would be leaked and I'd see a surprise $1k Google cloud bill.

  • source
  • parent
  • context
  • [–] 8 points 8 months ago

    Aye to make sure they can spy on us they've left us all vulnerable to everyone else as well. The NSA and their ilk covertly made sure everything was corrupted, as per the Snowden Files. They have their priorities all screwed up.

  • source
  • parent
  • context
  • [–] 9 points 8 months ago (1 child)

    What a friendly country! And people think i'm crazy when I try to avoid buying Chinese stuff as much as I can.

    Satellite communications giant Viasat was also compromised, allowing hackers to gain access to tools used by law enforcement to access the communications of others.

    Yeah let's keep installing surveillance backdoors guys it's safe surely.

  • source
  • [–] 1 point 8 months ago

    This unsung material, known as Ajinomoto Build-up Film (ABF), has become the invisible backbone of the AI revolution, enabling the cutting-edge performance and energy efficiency that powers today’s most advanced neural networks

    Exaggeration much? Sure, it might be an important component, but I doubt the industry will collapse overnight if they stop selling it. There are probably substitutes or alternative solutions.

    The article reads like AI slop. I wonder if this is some market manipulation thing?

  • source
  • [–] 14 points 8 months ago

    So while the world was worrying about the Red Chinese monopolising the rare-earths, a Japanese ramen company and a Japanese toilet manufacturer have quietly established a grip on chipmaking materials?

  • source
  • [–] 6 points 10 months ago

    free component libraries like shadcn/ui, daisyUI, and HyperUI killed Tailwind UI’s paid component business. shadcn/ui exploded in popularity by offering free, copy-paste components with no npm installation required

    ... the article makes a big thing about AI being the cause, and then says "oh yeah and this other thing too". Not obvious whether it would've happened without AI generated CSS as well.

  • source
  • [–] 4 points 10 months ago*

    It is a federation issue. Mbin made a change recently and I had to change some code in PieFed to stop this issue from occurring there. The Lemmy devs need to do the same, or Mbin needs to undo their change.

  • source
  • parent
  • context
  • [–] 1 point 10 months ago

    Glad I moved to Zen a while back, for the UI, but they seem to have their heads screwed on right. One upside here is that it'll breathe a lot of life into firefox forks...

  • source
  • [–] 7 points 10 months ago* (2 children)

    Not a federation issue. Limitation of Lemmy. Lemmy doesn't support link AND image in the same post "header". One or the other.

    You can do a custom thumbnail and a link OR you can do an image.

    And with either, you can put whatever the hell you want in the post body.

    But the "header" (can't really think of a better term, sorry) is image OR link.

    I've brought it up to the Lemmy devs that they desparately need to make this limitation clearer, at the very least in the Lemmy UI. They said they need to see an example of a better UI because they couldn't figure it out themselves. Can't make this shit up. Just clear out one when you fill in the other. Red warning message. Anything to make it fucking clearer. It shouldn't be tough, but here we are.

  • source
  • parent
  • context
  • view more: ‹ prev next ›