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/)HA
Posts
1
Comments
234
Joined
2 yr. ago
  • I expect the trusted authorities would be selected by the server where the user account resides. I.e. if a server's admin does not recognize a certain authority, it would not show their verifications to users logged in to their server.

    It's possible that it could extend to user selections of trusted verifiers as well, but I think implementing that level of granularity would be more of pain than it's worth to Bluesky. Still, I could be surprised.

  • Revolt relies on community self hosting last I looked at it, which means it would never be a "mass" solution.

    Should Discord ever collapse (something I don't see in the near future), the free alternatives that I see benefitting would be XMPP and Matrix — though there's new contenders that could make name for themselves by then too.

  • The issue is a TSMC-made chip ended up inside a Huawei processor. They're not allowed to make chips for Huawei or other US-sanctioned entities since they use US tech inside their foundries.

    What happened here is that TSMC made chips for another Chinese company that gave them to Huawei (and is now on the sanctioned list as well as a result, but wasn't when TSMC made the chips). The problem for TSMC is if the US determines they should have reasonably known there was a risk the company they made the chips for would give them to Huawei.

  • From the article, it sounds like TSMC's part in this was just negligence as Huawei used a front company to make the order for them — like a 14-year-old getting an adult to make a booze purchase. If they get fined, it seems unlikely it would be for the maximum amount.

  • As another east-coaster, I feel comfortable saying there's a huge cultural difference in the industry between here and the west coast (and Silicon Valley specifically). It's a gap that's been growing wider for over a decade now.

    It used to be that everyone followed the Microsoft/Apple culture nationwide (and before them — IBM's). Then Google, Facebook, Twitter, and Silicon Valley startup culture took over the West.

  • Android @lemdro.id
    hamsterkill @lemmy.sdf.org

    Device makers hiding the SoC they are using is a terrible recent trend

    Rant incoming:

    This was spurred by having just read https://www.androidpolice.com/google-tv-streamer-questions-answered/ , particularly this bit:

    When I asked directly, a Google representative told me they couldn't confirm which chipset powers the Google TV Streamer — essentially, Google declined to answer.

    I've been noticing an increasing trend by device makers to not disclose the SoC their devices run on. I've been seeing it with e-readers, network routers, media streamers, etc.

    It's incredibly frustrating to have devices actively exclude important information from their spec sheet and even dodge direct questions from tech news reporters. Reporters shouldn't have to theorize about what chip is in a released device. It's nuts.

    If you're wondering why this infomation is important, it can be for several reasons. SoC vendor can have significant impact on the real world performance and security of a device. It also carries major implications for how open a device is as SoC vend