binaryturtle

Like one time? It is like any other API. You look it up, study the parameters (in this case you need to look up in which register is what argument expected) and off it goes.

The site loads somewhat, burns 100% CPU non-stop, I can't really click any of the buttons. I guess it's not for me. :)

Never paid a cent, never will pay a cent. I have my principles.

It may put me at a disadvantage when it comes to quickly slop something together? But so far the free-to-use chat bots do as well for my needs.

With the title I was expecting some notes about DeluxePaint, but it was still a nice read nonetheless. Wish you much success with the game! :-)

I've made a brainf** interpreter in C, from scratch. I didn't use any "AI" though. Does it still count? :)

Maybe I should remove the following bit of code from my profile?

    if [ "$SESSION_TYPE" != 'remote/ssh' ]; then
     if [ "${TERM_PROGRAM}" != 'tmux' ]; then 
      ( if [ $[RANDOM % 10] == "0" ]; then fortune -n 40 -s; else echo "Hi, $(whoami)!"; fi ) | cowsay | lolcat && printf '\n'
     else
      if [ "${TMUX_PANE}" == '%0' ]; then 
       fortune | cowsay -f small | lolcat && printf '\n'
      fi
     fi
    fi

It's a whole chain of interpreters firing up (sub-shells, Perl for the cow, Ruby for the lol, I think.) :D

But what would life be without a little bit of fun?

Still the same. I guess it's some sort of wild anti-bot stuff basing on the user agent?

/edit

Yes, as confirmed with cURL, using my browser's "User Agent": 410 blocked. Using some other "User Agent" and it passes along the data. Pretty silly, IMHO.

I'm just seeing a "410 Gone" error on the linked site (same happens to the parent URL too).

I'm waiting for the second version (supposedly has a better number of RJ45; that's where the "One" was a bit limited and an extra switch would have been required in the setup)

And that's why we educate others and let them know about their options. You have to start somewhere.

If it's a "router" and you can't install a OpenWRT on it, then it's an absolute no-brainer to not to buy it.

I recall, back in the AmigaOS days, we kept the documentation inline with the code. E.g. you had your exported API function in a shared library code's .c file, with the documentation right above it sitting in a special formatted comment. Easily kept in sync (code wasn't that convoluted back then either.) Afterwards, during the build phase, the documentation (for other developers) was extracted on-the-fly. There was a fixed format/style and the documentation was compact and actually useful too.

(aka "autodocs", for those who remember the term)

I learned something new. That also explain why it was a quote and I didn't found the quoted part in the news item itself. :)

For the price tag I would have expected something bigger and more imposing (at least twice the size.)

I duckduckgo'ed "nose gear collapse" earlier and it seems it may be an issue that's more common than expected? At least there were lots of images of airplanes with broken front wheels and the nose touching the floor.

Thanks for the quick summary.

cloudflare blocked. :-(

No, I appreciate posts that call out actual AI usage that has not been disclosed properly. I often have trouble already detecting them, so hearing other people calling things out and point out why, this is very useful for me to update my knowledge how to smell those out.

I'm also very hesitant to release any new works (code, artworks, etc.) to the public. I usually release code under the GPL or AGPL, but I don't think any of those choices are properly respected by the AI crawlers, and subsequent "mixing into" those models.

Multiple times I got partially broken "citations" of GPL licensed code out of the models as answers to basic research questions (aka prompts) w/o any mentioning of the original license applied to the code. Just adding some random bugs every 10th line doesn't make it not a direct derivate. Image generators happily generated Sonics or Bart Simpsons (w/o directly prompting for that either). No mentions that those are copyrighted characters either.

Well… I know plenty people in my circle affected by this. Just have a slightly outdated system you simply can't afford to update: it's way to easy to get cut off like this. IMHO, a rather systematic discrimination of poorer people.

I can no longer access any website that's "protected" by Cloudflare. As soon a website enables that stuff… "Shoot, another one bites the dust." I wonder if the website owners realise at all how many actual users they lose by this sort of "protection."

And so it starts… modern robot machinery wiping out all humans? And for now they make it look like random accidents?

Sci-fi aside: We probably will see a slow but very steady increase of such events in the coming years with more unnecessary automation applied everywhere.

"new", just means "new entries" (in no specific order), but "newest" suggest some sorting/ ranking. If it's the very same why would it need two different words? :) It's like people often confusing the words "art" and "artwork".

Anyway… the URL first becomes visible once you hover over the link (assuming a browser that shows the link target)/ or click on the "New" entry. If you don't know beforehand that the "New" link turns into a "newest" URL… one only can make an educated guess. Sure, I assumed it may be the same, but could have been there's some actual more obscure "Newest" somewhere too… the way the question / poll was asked it didn't feel like this was about the first top most link on the site. Hence my query for proper clarification.

Hope that clears it up. :-)

I only have "new" here, and not "newest". Am I missing something?

The PI5 was a real downgrade for me with its lack of proper hardware h264 decoding as in the earlier versions (playing back h264 is my primary use case.) I will buy a PI6, if that comes back, else I stay with my reliable, and passively cooled, PI3.

> …charging them with violating sanctions law by directly or indirectly making economic resources available to EU-sanctioned entities…

I guess that's why.

It's not gmail accounts, but "services" (?) hosted on Google's cloud. Basically I see X.X.X.X.bc.googleusercontent.com addresses in the "Received" header fields, e.g. "22.185.141.34.bc.googleusercontent.com"

When doing a WHOIS on that IP we'll get a contact address for abuse reports: "google-cloud-compliance@google.com", but sending anything there, returns an error that the user doesn't exists.

I'm receiving daily about 20 to 30 spam mails from google servers. I'm sorting them into a separate SPAM folder for the "fun" of it.

Who to contact? How to make Google stop? Where to report the abuse of their services? I can't find out. The whole service is basically a big <bleep> off and "we don't want any contact."

Maybe I also need to publish some article, so it can be published here on HN? Maybe that could give it some traction for someone at Google to look into it?

I have no idea which distro to choose actually. Too much choices and it's not clear why one should be better than the other. For some distros it feels more like it's one-man projects for bragging rights. It's also a bit hard to put trust in that.

I want to resurrect an older Mac mini with an installation of a Linux distribution, but choosing a suitable distro is the first step I struggle with. Only thing I know is that it won't be an Ubuntu setup. :-)

I do run Linux-based systems in various forms already: OpenWRT on the router, an older Debian VM —which I just messed up a few days ago by trying to uninstall a wallpaper package which took down the whole desktop environment for some reason— and Raspbian on the PI.

But on some days I feel maybe I just should go for FreeBSD. But it may have similar (to a lesser extend) issues like Haiku with proper up-to-date software, especially in the web browser department? I previously dabbled with Haiku and this was its main issue. The OS itself is pretty nice though.

Sometimes it helps to test. Which I just did. :-)

Actually the compiler (at least clang) warns about this:

    $ gcc -W -Wall test.c -o test
    test.c:8:7: warning: multiple unsequenced modifications to 'a' [-Wunsequenced]
            a = a++ + ++a;
                 ^    ~~
    1 warning generated.

The undefined behaviour stems from the fact that "a" is modified multiple times between the "sequence points" (so it's irrelevant to the actual problem that this happens with ++, --, pre-, or, post-, or in which order) We only can modify the variable safely once on the right side without entering bizarro world.

A construct like this certainly can be confusing.