wolfgang42

> Cable cars are a symbol of San Francisco, a major tourist attraction, and an indelible feature of the city’s cultural and historical landscape. [...] While SPUR doesn’t recommend changing SFMTA’s role in cable car operations, the agency may wish to explore options to generate additional revenue from the cable car system or seek supplemental support from the city’s budget, given the outsized expense of providing cable car service and the unique value this mode brings to the city as a cultural attraction. SFMTA already acknowledges the special status of cable cars by pricing them differently from other modes and by excluding cable car service from some of its passes and fare discount programs.

Apart from that, I suspect the per-service-hour figure is particularly misleading for cable cars and removing one cable car from the schedule would free up significantly less than $871: there is a significant fixed overhead (from power usage and cable wear) to having the system running at all, regardless of how many cars are on it.

1: https://codelibrary.amlegal.com/codes/san_francisco/latest/s... 2: https://www.cablecarmuseum.org/60th_Anniversay.html

Looking at the list of options on [2], your observed 1-in-5 Clipper taps seems within the realm of plausibility; there are a lot of ways to pay for Muni that aren’t visible to fellow passengers. In particular, out-of-towners who plan to ride Muni a lot are likely to get a MuniMobile (or, for the old-fashioned, paper) pass; and a ticket to any Chase Center event also counts as a Muni day pass. You also mentioned monthly passes (I know a lot of people who get them from their company’s commuter benefits), and there’s also transfers: not only are “single ride” fares valid for 2 hours, but if you board after 8:30pm you can’t tap again, because Clipper can’t handle it and you’ll be double charged!

[1] https://www.sfmta.com/projects/paying-your-fares-keeps-us-mo... [2] https://www.sfmta.com/getting-around/muni/fares

- My understanding is that OCSP stapling stops leaks, because the browser can get OCSP data from the server instead of needing to fetch it separately.

- Last I heard, Firefox was in the process of removing OCSP responder checks (precisely for privacy reasons) in favor of CRLite-based revocation checks—are you sure they didn’t remove whatever setting you’re referring to from the UI because it’s no longer relevant?

[1] You “update” by overwriting the entire file. This is remarkably fast and means that there’s no overhead/tracking for empty space, but it does mean you probably want this to be a fairly rare operation.

I rolled my own cdb reader library for a project a few years ago, and wrote up my notes on the format and its internals here: https://search.feep.dev/blog/post/2022-12-03-cdb-file-format

> there are about 230 billion* links that need visiting

> * Thanks to arkiver on the Archive Team IRC for correcting this number.

Also when running the Warrior project you could see it iterating through the range. I don't have any logs handy since the project is finished but they looked a bit like

  https://goo.gl/gEdpoS: 404 Not Found
  https://goo.gl/gEdpoT: 404 Not Found
  https://goo.gl/gEdpoU: 302 Found -> https://...
  https://goo.gl/gEdpoV: 404 Not Found

  const template = ({name}) => `hello ${name}`;
  const n1 = template({ name: 'joe' });

- Confusing and buggy UI causing clerks to duplicate or mis-enter transactions

- Inventory getting “stuck” in branches after the product was discontinued; the attempt to remove it hid the inventory but caused its value to reappear on the books again each accounting period

- Failing touch screens entering spurious purchases overnight

- Incomplete rollback of distributed transactions

- Byzantine failures during hardware replacement causing multiple transactions to be assigned the same ID and overwrite each other

- Fujitsu employees with unaudited write access to the production database making one-off modifications

- The point of sale system simply telling the clerk to give too much change back to the customer

There’s no “one bug” here; the main failure was that those responsible continued to dismiss any problems as users being either in error or outright malicious, despite massive amounts of evidence that the system had technical flaws. Better quality software would have reduced the problems, but no system is bug-free and in many cases very little effort was made to identify the root causes of problems, much less to prevent similar ones from happening again.

[1] https://www.judiciary.uk/wp-content/uploads/2019/12/bates-v-...

A brief and reductive explanation: The Religious Society of Friends (colloquially “Quakers”) are a religious movement (nominally Christian, in practice often agnostic) which originated in England circa 1650. A core part of the theology is that God might speak to anyone, so worship generally consists of sitting around in silence until someone hears from Him and stands up to repeat the message, hence why the article is drawing parallels between that practice and Zen Buddhism.

They had no idea that <form><input></form> is all built in to the browser and you can make GET and POST requests without any frontend code. (Not that this is a new problem, <a onclick="document.location='...'"> has been a thing for decades at this point...)

It’s not that simple: this command already exists, it’s called `shred`, and as the manual[1] notes:

The shred command relies on a crucial assumption: that the file system and hardware overwrite data in place. Although this is common and is the traditional way to do things, many modern file system designs do not satisfy this assumption.

[1] https://www.gnu.org/software/coreutils/manual/html_node/shre...

You may be thinking of Brendan Eich? Berners-Lee is famous for HTML, HTTP, the first web browser, and the World Wide Web in general; as far as I know he had nothing to do with JS.

Self-plug: I run such a search engine (for programmers) in my living room, at <https://search.feep.dev/>. I don’t spend a ton of time maintaining it, so I’m interested to see what someone really dedicated could do.

[1] I wrote a 2004-vs-2014 comparison, and things have only gotten better since then: https://search.feep.dev/blog/post/2022-07-23-write-your-own

You can compile Mini vMac without checksum verification (either yourself or with the variations service[1]), which will allow you to use unknown or completely custom ROMs, though you need to be aware that it patches the ROM (it doesn’t emulate the original floppy hardware; instead it pokes a custom driver in where the original one ought to be) so if your ROM doesn’t line up with the original you will have problems with random chunks being overwritten.

I’ve done this so I could use Mini vMac to learn assembly language: the Mac has the convenient property that pixels on the CRT are 1:1 the contents of a chunk of RAM at a fixed offset, so you can get very immediate visual feedback about what your program is doing. I just set up an assembler to dump raw machine code and named it "Mac128K.ROM" and Mini vMac picked up on it fine.

[1] https://www.gryphel.com/c/minivmac/var_serv.html - though since Paul Pratt disappeared a few years ago nobody is quite sure how the server is staying up

TLDR: it seems like they don’t want to, but there was enough uproar when they tried to stop that they reluctantly brought them back, behind a dubious clickthrough agreement which asserts “should I distribute this file for the purpose of LLM training, Stack Overflow reserves the right to decline to allow me access to future downloads.”

Personally I’m also a fan of https://github.com/pugjs/pug , which is an alternate syntax for HTML that I find easier to work with when I need the full power of HTML but don’t want a thicket of angle brackets.