I think you missed the most important part. They wired a NEW neighborhood, that hadn't been previously wired. The major blockade to getting the last mile of fiber installed is usually right of way, both on utility poles (they are often owned by a competitor) and it's even worse when all the wiring is underground. Sometimes the old wiring in a neighborhood falls apart to the point where it needs to be completely replaced, and at that point you will probably see the "only one block gets gigabit" effect.
I've had strictly DSL in some for or other since early 2000, and I've rarely had "connectivity issues". The most notable times were first, when the local copper down the alley degraded to the point where POTS service gave up before DSL did (though this gave me my first lesson in how TCP/IP doesn't tolerate even 10% packet loss very well), and second when (at least three times on two lines!) someone re-punched the wires inside a breakout box incorrectly. There have also been times (usually after midnight) where I lose internet for a few minutes, probably when they force an update and reboot the modem. Oh yeah, and there was one incident where they sent a bad update to the remote terminal and bricked it (!), and couldn't get a replacement until the second day.
Those breakout box incidents were all after Uverse began, so either they had idiots upgrading their network (no old-school Bell System repairman would have done something so stupid), or they were intentionally trying to fuck with people who still had classic DSL. (which they were deprecating)
But five incidents over 17 years with at least seven different installs in two cities? Not bad. Certainly not the "daily issues" with Comcast that someone else in these replies mentioned.
"It was heartbreaking to see that some of our users were upset to learn about how we monetize our free service,"
Heartbroken because the users found out about it.
For example, two months ago I drove about two miles on a horribly bumpy dirt road. Two weeks later and I had a coolant leak. Turned out that a hose clamp had come loose. Hmm, I wonder how that could have happened?
Seriously, flying cars are probably the dumbest idea that just won't die.
I'm not quite old enough to have used FORTRAN. I grew up on BASIC and Z-80 assembly language on a TRS-80 (and a bit of HP BASIC on equipment at school), but when I went to college in 1982, they were using PL/I. The first semester was even on IBM equipment, but fortunately they got a VAX late in the semester, because I managed to screw up my JCL by trying to reformat it to be readable. I still don't know why it took DEC so long to add the UNTIL statement to their PL/I compiler.
Then I got into programming on the Macintosh, so I started using Pascal. Also, Turbo Pascal was a thing, and they were both UCSD variants. But one of the worst things to do is use Pascal and PL/I at the same time. (as in same era, not simultaneously) The function headers are syntactically backwards to each other.
I didn't even officially switch over to C until after 2000. I even have one program I use sometimes that started with code I originally wrote in college in PL/I, then ported to Pascal, then again ported to C.
robots.txt is intended to indicate what parts of a site should not be scanned recursively, often due for technical reasons such as generated content> It especially for sub-paths like
However, it was also not intended to be used to remove previously-archived content, as archive.org is currently using it. When an archived page changes status in robots.txt, they should note the first date that the status changed, then simply stop updating it until and if robots.txt re-allows it.
scanning and archiving are two different operations, and robots.txt is only intended to apply to the former.
DEFENSE! DEFENSE! DEFENSE! WELFARE! WELFARE! WELFARE! (throws chair)
Something like that, but now I have to compensate for all those caps (why yes, it is exactly like YELLING, how did you guess?) to make the lameness filter happy.
"The Avis WIZARD decides if you get to drive a car. Your head won't touch the pillow of a Sheraton unless their computer says it's okay." -- Arthur Miller