Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)G
Posts
1
Comments
439
Joined
3 yr. ago

  • Same with RAM.

    Unfortunately, the RAM shortage is caused by a RAM component being diverted to specialized packages that can't easily be converted into normal RAM. So even a bubble bursting won't bring RAM onto the market.

  • definitely not for sensitive work.

    I would argue that desktop software capable of doing this (storing and using past pixel values to calculate some sort of output) violates the principle of least privilege, so that an OS that supports this kind of screensaver being possible shouldn't be used for sensitive data, even if that particular screensaver is disabled.

    Better to harden the OS so that programs (including screensavers) can't access and store the continuous screen output.

    That's one of the problems we have with Windows Recall. We don't even want the OS to have the capability, because we don't want that data being copied and processed somewhere on the machine.

  • If the screensaver is saving the information of what a pixel has been on average, there's all sorts of potential for leakage of sensitive information onto a part of the computer that shouldn't have that information.

  • Well if you want to read about the many battery chemistries currently in use in EVs, there's this article:

    https://insideevs.com/news/782685/all-ev-battery-chemistries-explained/

    As the article explains, there are several chemistries that have already come and gone, and the current models being sold use a few competing chemistries with their tradeoffs. Some of the up and coming chemistries are also already being mass produced.

    So whatever it is you mean by "leap," it sounds like it's already been happening in the last 15-20 years.

  • Visa/Mastercard requires all cardholders, cardholders' banks, merchants, and merchants' processors to follow the comprehensive set of rules for disputed transactions. That way the dispute process tends to be uniform across different banks and across different merchant/payment processors.

    The network sets the rules, while the banks implement those rules on behalf of the cardholder and the processor implements those rules on behalf of the merchant.

    So replacing the network will require a comprehensive replacement for the network's dispute resolution rules (assigning who is responsible for paying when certain things happens) and procedures (how a cardholder can initiate a dispute and how that gets resolved).

  • Or, if the app has the private key for decryption for the user to be able to see the messages, what's stopping the app from copying that decrypted text somewhere else?

    The thread model isn't usually key management, it's more about the insecure treatment of the decrypted message after decryption.

  • JPEG Organisation?

    The G in JPEG already stands for "Group."

  • Using space elevator technology (metal structural beams and metal guy cables) I think we can get things up to 100m geosynchronous "orbit" pretty easily.

  • Safety

    Jump
  • I'm giving some reasons why turning on or off location services at the OS level doesn't appreciably change battery life.

  • Safety

    Jump
  • You can turn off higher level location services at the OS level, but at the radio level the cellular network will always need a precise enough location to handle tower handoffs and timing issues between the tower and phone, as well as modern beam forming techniques where the tower "aims" the signal at the phone. The simple act of the phone communicating with a specific tower tells the phone where it is (sometimes with surprisingly high precision).

    911/emergency services also use more low level location techniques, but I'm pretty sure those functions don't get called unless you dial an emergency number.

  • 90GB of both RAM+NAND combined. I'm guessing most of it is actual persistent storage for all the stuff the infotainment system uses (including imagery and offline map data for GPS, which is probably a big one), rather than actual memory in the sense of desktop computing.

  • Everything else that you said seems to fit the general thesis that they're making a lot more money selling to AI companies.

    If those reasons were still true but the memory companies stood to not make as much money on those deals, I guarantee the memory manufacturers wouldn't have taken the deal. They only care about money, and the other reasons you list are just the mechanisms for making more money.

  • It's a very common complaint among people administering websites. This particular AI poisoning service seems to be directed at those people.

    So maybe it's not the majority of complaints about AI, but it's a significant portion of the complaints about AI from site administrators.

  • The Fediverse is designed specifically to publish its data for others to use in an open manner.

    Sure, and if the AI companies want to configure their crawlers to actually use APIs and ActivityPub to efficiently scrape that data, great. Problem is that there's been crawlers that have done things very inefficiently (whether by malice, ignorance, or misconfiguration) and scrape the HTML of sites repeatedly, driving up some hosting costs and effectively DOSing some of the sites.

    If you put Honeypot URLs in the mix and keep out polite bots with robots.txt and keep out humans by hiding those links, you can serve poisoned responses only to the URLs that nobody should be visiting and not worry too much about collateral damage to legitimate visitors.

  • What's crazy is that they aren't just doing this because they make more money with AI.

    No, they really are making more money by selling whole wafers rather than packaging and soldering onto DIMMs. The AI companies are throwing so much money at this that it's just much more profitable for the memory companies to sell directly to them.

  • That's why "bullshit," as defined by Harry Frankfurt, is so useful for describing LLMs.

    A lie is a false statement that the speaker knows to be false. But bullshit is a statement made by a speaker who doesn't care if it's true or false.

  • If I am reading this correctly, anyone who wants to use this service can just configure their HTTP server to act as the man in the middle of the request, so that the crawler sees your URL but is retrieving poison fountain content from the poison fountain service.

    If so, that means the crawlers wouldn't be able to filter by URL because the actual handler that responds to the HTTP request doesn't ever see the canonical URL of the poison fountain.

    In other words, the handler is "self hosted" at its own URL while the stream itself comes from the same URL that the crawler never sees.

  • In terms of usage of AI, I'm thinking "doing something a million people already know how to do" is probably on more secure footing than trying to go out and pioneer something new. When you're in the realm of copying and maybe remixing things for which there are lots of examples and lots of documentation (presumably in the training data), I'd bet large language models stay within a normal framework.

  • The hot concept around the late 2000's and early 2010's was crowdsourcing: leveraging the expertise of volunteers to build consensus. Quora, Stack Overflow, Reddit, and similar sites came up in that time frame where people would freely lend their expertise on a platform because that platform had a pretty good rule set for encouraging that kind of collaboration and consensus building.

    Monetizing that goodwill didn't just ruin the look and feel of the sites: it permanently altered people's willingness to participate in those communities. Some, of course, don't mind contributing. But many do choose to sit things out when they see the whole arrangement as enriching an undeserving middleman.