obituary_latte

The animation is confusing...is one trip to the end and back the 1B iterations? I thought maybe they were counting up and once the slowest reached the end they would all stop but that didn't seem to be it. Maybe if it did (and there was a counter on each showing how many bounces they made), it'd be a little more clear.

Interesting nonetheless.

Not natively. There is other firmware out there, though, that allows such functionality. Depending on where you live, it may be illegal to even try, though, hence the native firmware locking out such use (you can record or visualize but not save/replay).

Probably as enforceable as any other EULA. Windows surely has similar language. I'd guess that somewhere buried deep in the agreements, or somewhere, it says they can audit your usage somehow. Does it ever happen? I'd be curious to know.

Wonder why it seems like all QT5 are "no help wanted"...

Agreed. Interesting that Yahoo was your choice. I may try it as well (have experimented with DDG and Bing a bit, but haven't used Yahoo since it was the only option back in the day).

Off topic (sorry), but has the quality of searches been on a steady decline over the last year or two? If I'm not just imagining things, wonder if it is because they changed the algo or if there is too much noise for the algo to work well anymore. Frustrating nonetheless...

IF configured away from the defaults:

By relying on the default keepalive limit, NGINX prevents this type of attack. Creating additional connections to circumvent this limit exposes bad actors via standard layer 4 monitoring and alerting tools.

However, if NGINX is configured with a keepalive that is substantially higher than the default and recommended setting, the attack may deplete system resources.

In the article one of the attendants says "I hit stop on Pump 3 and nothing happens" so they are at least seeing the pump is on and running. Whatever is happening must be either locking the attendant out or is leaving the attendants machine in a bad state with the pump running switch "on" so to speak. I wonder if it's actually NFC. It'd be interesting to see what a Flipper Zero would come up with.

There are multiple mentions of "extraterrestrial super islands", is this a mistranslation of the Meissner effect? Great term nonetheless.

Strangely, I get a Russian IP address for an answer when I query 1.1.1.1 for archive.is:

    ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐
    └─(12:32:59)──> nslookup archive.is 1.1.1.1                                                                          ──(Wed,Aug02)─┘
    Server:        1.1.1.1
    Address:    1.1.1.1#53

    Non-authoritative answer:
    Name:    archive.is
    Address: 89.253.237.217

    ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐
    └─(12:38:12)──> nslookup archive.is 1.0.0.1                                                                          ──(Wed,Aug02)─┘
    Server:        1.0.0.1
    Address:    1.0.0.1#53

    Non-authoritative answer:
    Name:    archive.is
    Address: 89.253.237.217

    ┌─(~/Projects/malware/triangulation)(ruby-2.5.0)────────────────────────────────────────────────────────────────────(c@c:s001)─┐
    └─(12:38:14)──> whois 89.253.237.217                                                                                 ──(Wed,Aug02)─┘
    % IANA WHOIS server
    % for more information on IANA, visit http://www.iana.org
    % This query returned 1 object

    refer:        whois.ripe.net

    inetnum:      89.0.0.0 - 89.255.255.255
    organisation: RIPE NCC
    status:       ALLOCATED

    whois:        whois.ripe.net

    changed:      2005-06
    source:       IANA

    # whois.ripe.net

    inetnum:        89.253.232.0 - 89.253.239.255
    org:            ORG-RL31-RIPE
    netname:        RU-RUSONYX-NET6
    descr:          Network for Rusonyx infrastructure
    country:        RU
    mnt-lower:      MNT-RUSONYX
    mnt-routes:     MNT-RUSONYX
    admin-c:        VZ1716-RIPE
    admin-c:        VZ1717-RIPE
    tech-c:         VZ1716-RIPE
    status:         ASSIGNED PA
    mnt-by:         MNT-RUSONYX
    created:        2018-10-10T09:53:33Z
    last-modified:  2018-10-16T12:37:40Z
    source:         RIPE # Filtered

    organisation:   ORG-RL31-RIPE
    org-name:       Rusonyx, Ltd.
    country:        RU
    org-type:       LIR
    address:        5th st. Yamskogo Polya, 9, office 19
    address:        125040
    address:        Moscow
    address:        RUSSIAN FEDERATION
    phone:          +74951370701
    fax-no:         +74951370701
    mnt-ref:        RIPE-NCC-HM-MNT
    mnt-ref:        MNT-RUSONYX
    mnt-by:         RIPE-NCC-HM-MNT
    mnt-by:         MNT-RUSONYX
    abuse-c:        AD11015-RIPE
    created:        2006-08-18T09:59:51Z
    last-modified:  2022-10-06T11:18:08Z
    source:         RIPE # Filtered

    person:         Viktor Zverkov
    address:        P.O. Box 19
    address:        127137, Moscow, Russia
    address:        Rusonyx ltd.
    phone:          +7 495 5089959
    nic-hdl:        VZ1716-RIPE
    mnt-by:         MNT-RUSONYX
    created:        2017-09-20T11:29:16Z
    last-modified:  2022-07-05T14:00:10Z
    source:         RIPE

    person:         Viktor Zaytsev
    address:        P.O. Box 19 , Russia
    address:        127137, Moscow
    address:        Rusonyx ltd.
    phone:          +7 495 5089959
    nic-hdl:        VZ1717-RIPE
    mnt-by:         MNT-RUSONYX
    mnt-by:         AM65535-MNT
    created:        2017-09-20T11:54:54Z
    last-modified:  2018-08-02T17:21:31Z
    source:         RIPE

    % Information related to '89.253.232.0/21AS41535'

    route:          89.253.232.0/21
    descr:          RUSONYX-RU
    origin:         AS41535
    mnt-by:         MNT-RUSONYX
    created:        2017-11-24T09:34:37Z
    last-modified:  2017-11-24T09:34:37Z
    source:         RIPE

    % This query was served by the RIPE Database Query Service version 1.107 (DEXTER)

Not sure why this would be happening (looks like at least one other person in the thread is seeing same result).

I get the same result when I query 1.1.1.1 or 1.0.0.1 for archive.is:

    ┌
    └─(12:32:59)──> nslookup archive.is 1.1.1.1 
                                            
    Server:  1.1.1.1
    Address: 1.1.1.1#53

    Non-authoritative answer:
    Name: archive.is
    Address: 89.253.237.217

    ┌
    └─(12:38:12)──> nslookup archive.is 1.0.0.1
                                            
    Server:  1.0.0.1
    Address: 1.0.0.1#53

    Non-authoritative answer:
    Name: archive.is
    Address: 89.253.237.217

Wonder why that is happening...

You don't have to "hazard a guess", one of their engineers gave you their email address in that other thread. They also invited you to their discord. Have you tried talking to someone directly at the source?