HN user

binaryturtle

422 karma

Two Turtles, One, and Zero.

Posts0
Comments179
View on HN
No posts found.

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.

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.)

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! :-)

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 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)