< ^ txt
Thu Jul 8 06:00:01 EDT 2021
========================================
Slept from eleven to seven.
Woke briefly a couple times in the night (once when power briefly went out).
Mostly cloudy until late afternoon then becoming partly cloudy.
Showers and scattered thunderstorms in the morning, then scattered showers and thunderstorms in the afternoon.
Highs in the upper 70s.
Southwest winds around 5 mph shifting to the northwest early in the evening.
Chance of precipitation 80 percent.
Work
----------------------------------------
- check main office cameras for vandalism
Done.
- review pfSense 2.5.2 release
Done, but I'm going to hold off a while before upgrading. It does purport to fix the horrible multi-WAN port forwarding bug.
Heidi called me, briefly, and I gave my condolences for her loss.
Forty-five-minute walk at lunch.
A few raindrops, a few moments of sunshine.
Humid, but not excessively hot.
Saw mourning doves, chipmunks, a little white butterfly, pigeons, a small bunny, and a deer.
Several broken branches from yesterday's storms.
Home
----------------------------------------
A little more sorting and purging for the potential move.
```
-- inky ~ $ mail
[…]
Message 9:
From root@inky.paulgorman.org Thu Jul 8 03:27:01 2021
Subject: Anacron job 'cron.daily' on inky.paulgorman.org
[…]
/etc/cron.daily/logrotate:
error: error accessing /var/log/nginx: Permission denied
error: error accessing /var/log/nginx: Permission denied
error: failed to rename /var/log/nginx/access.log to /var/log/nginx/access.log-20210708: Permission denied
-- inky ~ $ sudo logrotate -f -d /etc/logrotate.conf
[…]
rotating pattern: /var/log/nginx/*log forced from command line (10 rotations)
empty log files are not rotated, old logs are removed
switching euid to 997 and egid to 995
considering log /var/log/nginx/access.log
log needs rotating
considering log /var/log/nginx/error.log
log needs rotating
rotating log /var/log/nginx/access.log, log->rotateCount is 10
dateext suffix '-20210708'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
error: error accessing /var/log/nginx: Permission denied
glob finding old rotated logs failed
rotating log /var/log/nginx/error.log, log->rotateCount is 10
dateext suffix '-20210708'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
error: error accessing /var/log/nginx: Permission denied
glob finding old rotated logs failed
[…]
-- inky ~ $ sudo -u nginx ls /var/log/nginx/
ls: cannot open directory /var/log/nginx/: Permission denied
-- inky ~ $ ls -lh /var/log | grep nginx
drwx--x--x 2 root root 4.0K Jun 1 20:24 nginx
-- inky ~ $ sudo getfacl /var/log/nginx
getfacl: Removing leading '/' from absolute path names
# file: var/log/nginx
# owner: root
# group: root
user::rwx
group::--x
other::--x
-- inky ~ $ sudo setfacl -m nginx:rwx /var/log/nginx
-- inky ~ $ sudo getfacl /var/log/nginx
getfacl: Removing leading '/' from absolute path names
# file: var/log/nginx
# owner: root
# group: root
user::rwx
user:nginx:rwx
group::--x
mask::rwx
other::--x
```
Didn't realize the Inform I played with in college was so new at the time.
https://kottke.org/21/07/from-text-adventures-to-modern-interactive-fiction
https://inform-fiction.org/
https://if50.substack.com/
https://if50.substack.com/p/1993-curses
> > Nelson’s game would take over the IF newsgroups as players who thought they’d seen the last of the great text adventures discovered a worthy modern successor. “Congratulations,” wrote one poster: “Its almost like having Infocom back.” It helped that the game had so many nooks and crannies and puzzles, endless puzzles, that at least some of them were bound to be stumpers for any given player. Hint requests and discussion of the game proliferated, and dominated the newsgroups through the rest of 1993 and 1994: so much so there was a half-hearted proposal to split it all off into a dedicated new group, rec.games.curses, just so there’d be enough oxygen to talk about anything else.
> The other big thing Nelson did with Curses is build a compiler for the Infocom virtual machine so that players and designers could create their own text adventures. Kind of like Dante importing the classic epic into the vernacular. Everybody could now do it themselves.
> That juncture — a compelling world, an obsessed and supportive community, and (there’s no better way to put this) the means of creative production — have proved over and over again to be the secret formula for building something beautiful and new in art.
> As popular as Curses was, the Inform language would come to have an even larger impact on interactive fiction history. It had at first been more of “an assembler with delusions of grandeur,” with code written close to the virtual metal of the Z-machine. That machine, of course, had been designed to run text adventures, so even a Z-code assembler was far more efficient for the purpose than higher-level but more general languages. But as Nelson kept improving Inform, it began to evolve more elegant features for efficiently crafting simulated worlds. By the release of version 5 in summer 1994 (just as its author was at last defending his PhD), Inform had become powerful and stable enough for others to start building ambitious projects of their own; Inform 6, appearing two years later along with a readable and elegant manual, would become the definitive version.
https://computer.rip/2021-07-07-dial-1-800-flowers-dot-com.html
> This issue broke for toll-free numbers basically the same way it did for local numbers. The FCC issued an order in 1993 stating that it must be possible to "port" toll-free numbers between inter-exchange carriers. Unlike local numbers, though, there was no inherent or obvious method of allocating toll-free numbers (the former geographical and carrier mappings were not widely known to users). This encouraged a completely "open" approach to toll-free number allocation, with all users pulling out of a shared pool.
> If this sounds a touch like the situation with DNS, you will be unsurprised by what happened next. A new class of entity was created which would be responsible for allocating toll-free numbers to customers out of the shared namespace, much like DNS registrars. These were were called Responsible Organizations, which is widely shortened to RespOrgs.
> The post-1993 system works basically like this: a business or other entity wanting a toll-free number first requests one from a RespOrg. The RespOrg charges them a fee and "assigns" the telephone number to them by means of reserving it in a shared database called SMS/800 (the SMS here is Service Management System, unrelated to the other SMS) [5]. The RespOrg updates SMS/800 to indicate which inter-exchange carrier the toll-free number should be connected to. Whenever a customer calls the toll-free number, their carrier consults SMS/800 to determine where to connect the call. The inter-exchange carrier is responsible for routing it from that point on.
> In practice, this looks much simpler for many users as it's common (particularly for smaller customers) for the RespOrg to be the same company as the inter-exchange carrier. Alternately, it might be the same company or a partner of a VoIP or other telephone service provider. So many people might just use a cheap online service to buy a toll-free number that points at their local (mobile or office perhaps) number. They don't need to know that behind the scenes this involves a RespOrg, an inter-exchange carrier, and routing within the inter-exchange carrier and service provider to terminate the call.
> The situation of DNS registrars has been subject to some degree of abuse or at least suspicious behavior, and the same is true of RespOrgs. It is relatively easy to become a RespOrg, and so there's a pretty long list of them. Many RespOrgs are providers of various types of phone services (carriers, VoIP, virtual PBX, etc.) who have opted to become a RespOrg to optimize their ability to assign toll-free numbers for their customers. Others, though, are a bit harder to explain.
> Perhaps the most infamous RespOrg is a small company called PrimeTel. War-dialers and other telephone enthusiasts have long noted that, if one dials a selection of random toll-free numbers, you are likely to run into a surprising number of identical recordings. Often these are phone sex line solicitations, but sometimes they're other types of content that is uninteresting except for the fact that it appears over and over again on large lists of telephone numbers. These phone numbers all belong to PrimeTel.
> Many words have been devoted to the topic of PrimeTel and most notably an episode of the podcast Reply All. I feel much of the mystique of the issue is undeserved, though, as I believe that one fact makes PrimeTel's behavior completely intuitive and understandable: 47 CFR § 52.107 forbids the hoarding of toll-free numbers.
> That is, toll-free numbers are a semi-limited resource with inherent value due to scarcity, particularly those in the 800 NPA as it is viewed as the most prestigious (unsurprisingly, PrimeTel numbers are more common in 800 than in other NPAs). This strongly suggests that it should be possible to make money by speculatively registering toll-free numbers in order to resell them, as is common for domain names. However, the FCC explicitly prohibits this behavior, largely by stating that toll-free numbers cannot be held by a RespOrg if there is not an actual customer for which the number is held.
> So PrimeTel does something that is pretty obvious: in order to speculatively hold toll-free numbers, it acts as customer for all of those numbers.
> Since it's hard to come up with a "use" for millions of phone numbers, PrimeTel settles for simple applications like sex lines and other conversation lines. It helps that PrimeTel's owners seem to have a historic relationship to these kinds of operations, so it is a known business to them. Oddly, many of the PrimeTel "services" don't seem to actually work, but that's unsurprising in light of the fact that PrimeTel is only interested in the numbers themselves, not in making any profit from the services they connect to. From this perspective, it's often better if the services don't work, because it reduces PrimeTel's expenses in terms of duration that callers stay on the line.
Servings: grains 6/6, fruit 2/4, vegetables 2/4, dairy 1/2, meat 0/3, nuts 1/0.5
Brunch: orange, two bean and tomato tacos, coffee
Afternoon snack: banana, cucumber
Dinner: cheese curls
127/74
< ^ txt