Skip to content

No JS, No CSS, No HTML: online "clubs" celebrate plainer websites

Technology
205 120 851
  • 1 Stimmen
    1 Beiträge
    12 Aufrufe
    Niemand hat geantwortet
  • 295 Stimmen
    31 Beiträge
    175 Aufrufe
    A
    I have a rough idea of their efficiency as I've used them, not in professional settings but I wager it would not be too different. My point is more that it feels like the rugs are finally starting to get pulled. This tech is functionnal as you said, it works to a point and that point is enough for a sizeable amount of people. But I doubt that the price most people are paying now is enough to cover the cost of answering their queries. Now that some people, especially younger devs or people who never worked without those tools are dependant on it, they can go ahead and charge more. But it's not too late, so I'm hoping it will make some people more aware of that kind of scheme and that they will stop feeding the AI hype in general.
  • Google kills the fact-checking snippet

    Technology technology
    13
    150 Stimmen
    13 Beiträge
    72 Aufrufe
    L
    Remember when that useless bot was around here, objectively wrong, and getting downvoted all the time? Good times.
  • 71 Stimmen
    12 Beiträge
    64 Aufrufe
    C
    Because that worked so well for South Korea
  • The AI girlfriend guy - The Paranoia Of The AI Era

    Technology technology
    1
    1
    6 Stimmen
    1 Beiträge
    13 Aufrufe
    Niemand hat geantwortet
  • 21 Stimmen
    41 Beiträge
    138 Aufrufe
    W
    that's because phone makers were pumping out garbage chargers with bare minimum performance for every single phone, isn't it?
  • Small (web) is beautiful

    Technology technology
    6
    1
    0 Stimmen
    6 Beiträge
    38 Aufrufe
    fredselfish@lemmy.worldF
    Will do thank you.
  • 1 Stimmen
    8 Beiträge
    40 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.