Remember deep linking? That is, if you’ve ever done computing/science history. Deep linking was a nefarious act and for ultra brief periods (in some places) making a link (like this) was link stealing.

Basically, homepage links were a–ok, but deep links were bad, really bad, because customers skipped the front and arrived at the exact (product) page. Businesses died overnight (the hypo theory).

Deep linking is smartphone marketing lingo now and very much desired. My hunch is that something analogous to taking a screen shot will be the modern equivalent of that unworkable controversy.

Hopefully no one else cuts their plants in half. Experts only… but seriously, in an epistemological sense; many popular topics today are just like talking about the nature of trees.

The universe’s resiliency allows for contradictory stuff to be practical, or at least appear generalizable on the long–tail and convincingly so. Bananas are indeed fascinating.

Banana trees are kind of invincible. Here’s what happens if you chop a sufficiently radioactive one clean across the mid…

Some SSH options are worth tweaking when directly distributing code with git to multiple remotes. ConnectTimeout and BatchMode (optionally for automation). ControlMaster enables multiplexing for session sharing via sockets.

ForwardX11 no
Compression no
ConnectTimeout 3
ServerAliveCountMax 1
ServerAliveInterval 10

Host *
  ControlMaster auto
  ControlPersist yes
  ControlPath ~/.ssh/sockets/%r@%h-%p

%r@%h-%p translates to user@hostname-22.

Did you know that cPanel has a back end user–space API? I’ve yet to see a web front end user dashboard that’s reliable and consistent.

Some of you were curious. Text assistants and bots are booming, as shovelers seek the god oracle and magnum opus. Here’s the numbers for a naked robots.txt. Inferences, up to you.

1. Applebot/0.1 [20.1 MiB]
2. heritrix/3.4.0-20200304 [21.8 MiB]
3. YandexBot/3.0 [28 MiB]
4. GPTBot/1.0 [30.1 MiB]
5. IonCrawl [31.6 MiB]
6. CCBot/2.0 [40.6 MiB]
7. DataForSeoBot/1.0 [51.2 MiB]
8. SeznamBot/4.0 [58.6 MiB]
9. facebookexternalhit/1.1 [64.1 MiB]
10. Google-Read-Aloud [86 MiB]
11. PetalBot [91.3 MiB]
12. Barkrowler/0.9 [98.6 MiB]
13. SemrushBot/7~bl [141.1 MiB]
14. BLEXBot/1.0 [152 MiB]
15. AhrefsBot/7.0 [159.5 MiB]
16. MJ12bot/v1.4.8 [285.2 MiB]
17. bingbot/2.0 [373.4 MiB]
18. Googlebot/2.1 [535.2 MiB]
19. Bytespider [543 MiB]
20. DotBot/1.2 [806 MiB]
21. Amazonbot/0.1 [2.6 GiB]

I saw something peculiar the other day. Hallucination? The microsoft.com domain was serving up 192.168.1.0 and 192.168.1.1 as A records in a 7 address round robin.

That’s a spooky reminder to check your rebinding setup — that is, if you’re playing with fire (DNS).

For example, unbound with private-address and private-domain. Then test if DNS rebinding is possible.

Are the caches warmed up? vmtouch and fincore are two useful programs.

What do they do? Basically, one can peek at what’s been cached into memory. I somehow ended up re–looking into this today. The Linux kernel is intelligent.

Rule #1 of finding technical feeds; type ‘OPML’ into GitHub search. GitHub is like a social network for software engineers and I’m a conservationist of time.

Are you a safe kid? I’ve just had a memory of a past time in a library.