binaryturtle

A few really nice buttons there, indeed. :)

I may have missed one by looking at this huge dump, but NONE of the "buttons" I saw there actually looked/felt like a button. Something I can feel that I press it down and it gives proper visual feedback, like a little 3D effect.

I'm old-school. :)

My SSD only reports as 121 GB. Dunno why it's such an odd size.

With 21,647,615 MiB (~20.64 TiB) written. Reporting as 99 (down from initial 100?) in the normalised value, but the normalised value hasn't changed since I first checked in 2015, so maybe it doesn't work? The wear leveling is at 180 (down from initial 200?), and the threshold at 100, so still ~80 to go until expected EOL. I'm losing between 1 and 2 points per year at the current rate.

I'm also hoping for another 10 years at least. *knock-on-wood*

It's the typical Cloudflare error where it tells you "Your browser sucks", not sure what a screenshot would help. :)

There's a survey link. Not sure it works as Cloudflare blocks me from accessing it. Oh the irony, having my opinion as EU citizen about an EU issue blocked by some silly US company.

I want some birds too!

I'm running my own home server on an old 2014 Mac mini, 24/7 basically. It both has a SSD and a HDD (old "Fusion" disk type of machine, but I use both parts separately, the SSD part for the OS, the HDD part for the data.)

A few days ago the HDD had its 100,000 Power_On_Hours anniversary. :) According to SMART this is way past the expected/ designed life time of the disk (the normalised value reports "1" since a few years when the disk hit about 42,000 Power_On_Hours)

So you never know. It either works or it doesn't. You have backups for the worst case.

F.ex. in the case of flyers or other smaller print products: You will not print one product for one customer at once, but many at once (e.g. from different customers), that will share a sheet. So, e.g., you print 1000 of everything, aka 1000 sheets. If a customer needs 2000 they get two spots on the sheet. If a customer wants 4000, they get 4 spots. Now, if a customer needs less than 1000, they still need one spot for the 1000. For that customer this still will be way cheaper than doing a separate small series print.

Site doesn't work for me (older Firefox). Looks like there's no CSS and some Javascript error (probably makes it bail out loading the CSS?)

Many years ago I worked in the printing industry. F.ex. a client wants 100 products of something (e.g. posters or flyers), usually it was more cost effective to produce a 1000 (or more) and then throw away 900 the client didn't need. Obviously a huge waste of material.

BlitzBasic(2) was also great. Hacked together bunch of games with it. Huge fun.

I wonder how many people may have gotten an actual heart infarct because of that. There may be a person out there that may be dead as a result.

It's entirely irresponsible of Amazon to even display such values to the user.

There's a weird "Cloudflare" captcha on that site. I can't get past that either. :)

Oh well… the article probably hasn't anything useful or important to say anyway. Time to move on.

Article needs registration.

Just flash OpenWRT to them? :) (a script could prepare a matching default config)

In the same scene there's also a 24h clock. The movie was way ahead of its time (pun intended). :-)

The 10h clock is also used in the scenes where a worker madly adjusts the hands to keep the moloch running.

I wonder if there's a project like there's OpenWRT for routers, just for vacuum robots? Where you just can buy some device form a normal online shop, then flash your custom firmware, and off you go with a privacy respecting fellow that doesn't film you and doesn't send everything to some US or Chinese cloud. :)

(I still use a traditional vacuum here, because all the privacy and snooping aspects of those robot thingies.)

I always encode my AAC with VBR. Why wouldn't you, right? I guess I'll stick to apple or fdkaac for now.

As long we still have DCF77…

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)