Skip to content

Grok praises Hitler, gives credit to Musk for removing “woke filters”

Technology
54 35 0
  • Grok, Elon Musk's AI chatbot, seems to get right-wing update

    Technology technology
    13
    1
    182 Stimmen
    13 Beiträge
    12 Aufrufe
    A
    Yep. Pretty sure that was deliberate on Musk's (or his cronies) part. Imagine working at X and being told by your boss "I'd like you to make the bot more racist please." "Can you convince it that conspiracy theories are real?"
  • 129 Stimmen
    22 Beiträge
    73 Aufrufe
    N
    I can’t believe he knows anybody like that. You think you know somebody…
  • Software is evolving backwards

    Technology technology
    64
    1
    342 Stimmen
    64 Beiträge
    320 Aufrufe
    M
    Came here looking for this
  • 782 Stimmen
    231 Beiträge
    476 Aufrufe
    D
    Haha I'm kidding, it's good that you share your solution here.
  • 25 Stimmen
    9 Beiträge
    42 Aufrufe
    S
    I didn't care much about arc because it was chromium, but damn this is just bland and uninteresting compared to it
  • 21 Stimmen
    1 Beiträge
    11 Aufrufe
    Niemand hat geantwortet
  • 131 Stimmen
    67 Beiträge
    222 Aufrufe
    I
    Arcing causes more fires, because over current caused all the fires until we tightened standards and dual-mode circuit breakers. Now fires are caused by loose connections arcing, and damaged wires arcing to flammable material. Breakers are specifically designed for a sustained current, but arcing is dangerous because it tends to cascade, light arcing damages contacts, leading to more arcing in a cycle. The real danger of arcing is that it can happen outside of view, and start fires that aren't caught till everything burns down.
  • 1 Stimmen
    8 Beiträge
    36 Aufrufe
    L
    I think the principle could be applied to scan outside of the machine. It is making requests to 127.0.0.1:{port} - effectively using your computer as a "server" in a sort of reverse-SSRF attack. There's no reason it can't make requests to 10.10.10.1:{port} as well. Of course you'd need to guess the netmask of the network address range first, but this isn't that hard. In fact, if you consider that at least as far as the desktop site goes, most people will be browsing the web behind a standard consumer router left on defaults where it will be the first device in the DHCP range (e.g. 192.168.0.1 or 10.10.10.1), which tends to have a web UI on the LAN interface (port 8080, 80 or 443), then you'd only realistically need to scan a few addresses to determine the network address range. If you want to keep noise even lower, using just 192.168.0.1:80 and 192.168.1.1:80 I'd wager would cover 99% of consumer routers. From there you could assume that it's a /24 netmask and scan IPs to your heart's content. You could do top 10 most common ports type scans and go in-depth on anything you get a result on. I haven't tested this, but I don't see why it wouldn't work, when I was testing 13ft.io - a self-hosted 12ft.io paywall remover, an SSRF flaw like this absolutely let you perform any network request to any LAN address in range.