Sgtatham

> I do wish that there existed a forum for some of the discussions that used to actually happen on the cypherpunks list You may find some interested people in UK Crypto (but obviously I'm not suggestion you spam their list). (http://www.chiark.greenend.org.uk/mailman/listinfo/ukcrypto) > This group is comprised of people with a professional interest in the formulation and content of UK government policy on the provision, use and control of encryption products and services in the UK. It was formed in response to the 1996 announcement of UK policy on the provision of encryption services on telecommunications networks. > The mailing list is unmoderated, but only subscribed members can post. Please try and restrict postings to UK Encryption law and try not to stray onto general cryptology topics.

Tangential: 1. Simon Tatham is the author of PuTTY 2. In the early days of the web, many people's personal sites were hosted on shared computers (e.g. my first was on my university's DEC Ultrix system). The URLs started with a reference to the user's home directory. This page is hosted on a machine that has a page to lists all the user's home pages: https://www.chiark.greenend.org.uk/users.html 3. The home page has this awesome spam detector: If you want not to be able to send mail here in future, please send mail to [email protected].

or throw exceptional loops : https://www.chiark.greenend.org.uk/%7Esgtatham/mp/

Yes, guaranteed solvable minesweeper variants exist. https://www.chiark.greenend.org.uk/%7Esgtatham/puzzles/js/mines.html "The first square you open is guaranteed to be safe, and (by default) you are guaranteed to be able to solve the whole grid by deduction rather than guesswork. (Deductions may require you to think about the total number of mines.)" I don't know about the runtime though.

First resignation: http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2019…

http://www.chiark.greenend.org.uk/doc/cmucl-docs/compiler-hint.html is mostly applicable to SBCL last I checked. It gives an idea of what kind of cleverness the compiler can undertake.

I found this: http://www.chiark.greenend.org.uk/%7Esgtatham/puzzles/js/mines.html "you are guaranteed to be able to solve the whole grid by deduction rather than guesswork."

Everyone's internal ip range is likely to be similar. 192.168.[0|1|2].0/24 or 10.[0|1].[0|1].0/24 There are some projects that hold a registry of internal ips, for example: http://www.chiark.greenend.org.uk/ucgi/~ijackson/cam-grin?list=all If we all were on ipv6 it might help, but meh.

Some operating systems, including OS X, don't provide that script, but it's easy enough to just download it: http://www.chiark.greenend.org.uk/ucgi/~cjwatson/cvsweb/~checkout~/ope…

I think git-annex is pretty much the right answer if you are already a linux saavy person that expects a mature battle tested tool that integrates well with your existing linux workflow systems. It sits on top of git in a sensible discernible way. https://www.datalad.org/for/git-users Peoples non text data is going to be some form of indiscernible binary blob to whatever system is managing it. Think about what a diff looks like for a jpeg, excel file, or an audio file. http://docs.datalad.org/en/latest/metadata.html What about git-annex vs git-lfs? 1. """LFS Test Server is an example server that implements the Git LFS API. It is intended to be used for testing the Git LFS client and is not in a production ready state.""" 2. git-lfs seems to want to store your files in the github/microsoft cloud, its not really ready to be deployed inside an existing systems workflow? If you need to check a tickbox and just assume Atlassian/Microsoft has you covered it might be a good choice. 3. git annex has a ton of integrations with multiple backends - http://www.chiark.greenend.org.uk/doc/git-annex/html/special_remotes.h… 4. Poke around the git-annex website. I think you'll see a tool that's being used in a variety of workflows successfully for a decade plus. That's not true of really any of the other tools others have noted in this thread.