I don't understand this.

Don Knuth is a Christian, as he sometimes mentions in talks or things he's written. He also wrote this book which discusses each 3:16 verse in the bible http://www.amazon.com/3-16-Bible-Texts-Illuminated/dp/089579...

Thank you for answering my question.

A white American being Christian is so common that I wonder why the original poster felt that this was worth emphasizing.

As Knuth himself acknowledged in "Things a Computer Scientist Rarely Talks About", it's rare among CS researchers.

From that link:

> Is SRC used to develop itself? No. That would be silly.

From Git's Wikipedia page:

> The development of Git began on 3 April 2005. The project was announced on 6 April, and became self-hosting as of 7 April.

You're kinda missing the point: this project is designed around a single user maintaining a linear history for a single file. Using it for a project would be a weird impedance mismatch.

That's not to say I find SRC compelling... in the slightest. Just that you'd never use SRC to track a project.

You're right, I was mostly just being snarky - but, that said, the source of SRC (sigh - what a terrible name, as others have said) is, in fact, just one Python file, so I suppose you could arguably use SRC for it.

I don't find it at all compelling either.

Hah. I just looked at the src (heh) - you're right, one file. I take back my argument.

If esr wants to fetishize a time when Real Programmers took patches over nntp and applied them in rcs, then by god he should go all in and self host the thing!

ESR is not the only contributor to SRC, check the log. So no, SRC would be the wrong tool.

Also reproduced on 10.9.5 -- you would think that there's sometone at Apple looking at this forum and at hannob's bashcheck and that it would get tested. I guess there will be a 1.1 version of the update soon?

The Americans should probably fear bugged Russian processors too, right?

We are more afraid of counterfeit china-fabbed ASICs; even the US military has been burned by these. With more fabbing done in china, I guess the problems could get worse.

Well yeah, if they were to buy made-in-russia processors. Which is very unlikely.

Maybe he's trying to get you to bite on the database so that he can extort some money out of this.

hmm, it's an advertisement for those who may want the database file. the zip file contains a read.me file which has a bitcoin address in it, offering the DB for 1 BTC.

I don't think that this post should be on HN.

Yea, this is exactly what I said in another thread.

an you were right :)

Did some investigation:

* The tar file (cnet.com.tar) is 489MB.

* Unpacked it's 536MB

* No database

* Around 30,000 files

* READ.ME has a promise of a copy of the database if you send this person 1BTC (not publishing their name here)

* Based on directory structure, looks like this is a release from 06/12 of this year

* Looks like the site is based on Symphony?

>READ.ME has a promise of a copy of the database if you send this person 1BTC

Sounds legit.

Virtual machine...

And a competitor to you would be Follow Up Then which does what you do, I think. (http://fut.io/) I've used it for a very long time, but just switched to the snooze button in Streak. It's slick.

There is also our product, FollowUp.cc (https://followup.cc). We've been around for a little over 7 years!

Thanks for doing this, it is greatly appreciated. The list of offenders with screenshots is nice, but what would be really useful is a table that is sortable and filterable so that people (i.e. me) can find out if any of our vendors are offenders. Also, a JSON API would be slick too. Just ideas.

Soon :)

Why not just slap Varnish in front of that and be done?

That would be the end goal - but since all users get cookies there's not obvious "I'm anonymous" vs "I'm a signed-in-user" differentiator I can use to control whether to cache or serve live.

It'll happen, shortly, but the fastest solution was to re-deploy on a scaling platform.

When a user is logged in, use a Vary: Cookie header, when a user is not logged in, leave that off. Set the expiration time as appropriate.

Which brings the next question... why not use Github for authentication?