• 23 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2024

help-circle

  • This smells like bullshit. The AI was giving responses. If it was truly DDoS or wifi it wouldn’t have been able to answer the query at all. What happened here was the AI wasn’t giving responses as rehearsed before, it skipped ahead steps it.

    Even if true, kinda a rudamentary mistake for a multi billion dollar company to make. How did you not think people would show up with your product to record you unveiling the new product.

    But the audience for this product will eat up this explanation.


  • Does it already support the legion go 1?

    Do the disconnected controllers work along with fps mode?

    I am an idiot and I answered my question about the detarchable controllers and fps mode a month or so ago when I was giving steamos a try on my LeGo 1. Yes they work, so I guess in a way yes it is supported. I just do not know if valve has officially stated anywhere that they include it in the “offical supported devices” line up.

















  • – Boot b3a9a949f8d1499fb0404672a02d2e34 – Mar 11 21:04:21 arch systemd[1]: Starting Network Name Resolution… Mar 11 21:04:21 arch systemd-resolved[1296]: Positive Trust Anchors: Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16 Mar 11 21:04:21 arch systemd-resolved[1296]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.a rpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test Mar 11 21:04:21 arch systemd-resolved[1296]: Using system hostname ‘arch’. Mar 11 21:04:21 arch systemd-resolved[1296]: mDNS-IPv4: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. Mar 11 21:04:21 masonarch systemd-resolved[1296]: mDNS-IPv6: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers.