YJL

Sudoku is a game, generator, solver, and statistics calculator. It has command-line options and well-documented manual page, plus nice UI to play.

In game, you can save or load board, request a hint which might even give you which digit to try, it can also solve the board if you have given up.

Sudoku was released in 2005-07 by Michael Kennett into public domain, continued by Peter Spiess-Knafl on 2015-02-12, written in C with ncurses, running on Windows and Unix-like, currently git-61e3f39 (2015-03-13, post v1.0.4 (2015-02-28)).

I accidentally found this Commit Message Generator while I was trying to find a guideline for writing commit message which I had read long time ago. It is an open source hosted on GitHub and you can read all funny commit messages at once. I am not really sure if those messages are real or not, some really look like just made-ups.

This website actually inspires me of an idea. GitHub has an API to retrieve specific commit's metadata, other hosting providers' API probably can do the same or just scrape via HTTP interface of version control system. What if you can submit a URL of a commit on GitHub to an application, so you can have real cases which you can actually access to original repository.

You can up vote or down vote of a commit message, isn't that great? Anyone up to creating one of such website or is there already one around?

I just saw this Bullshit Generator Python script in usenet. This is perfectly making sense to create a such generator, maybe some people did use this way to write. Who knows?

Here is three sample paragraphs:

The bug-free operation is registered in an architecture. A client-side function is received by a toolkit. An aggregator identifier from an asynchronous entity integrates with the owner algorithm. The private customization from the aware object is generated by the end-point. Before all, an Internet is operational. The module triggers the approach entity. If needed, a service-oriented communication supersedes the object. The performant acknowledgment retrieves the respective event.

A native data scenario from an orchestration inherits from the asynchronous directory where a genericity subscribes to an AJAX value. A backbone overwrites an orchestration extracted from an application. The Web 2.0 is controlled by an ontology that aggregates the usage derivation rule. A major Internet is installed on a business-driven object. The OO approach registers a RSS feed. The available event is unaffected. The Web 2.0 cookie is installed on an approach. The source is controlled by the IP address that triggers the controller Internet.

The auto-regulated registry is populated by an availability. A next-generation granularity is collected by the operational object. Nevertheless, the logic leader is monitored by the Java work accessed by the official toolkit. A compatible server is responsible for the algorithm. The entity on top of a Web page globally relies on a service provider that is OO when an operational aggregator built from the schema is prime. The secondary end-point on top of the orchestration is authorized by the practice. An object look-and-feel is controlled by a thread. An open actor covers the Java-based encapsulation.

I have no idea what above they are about. :-)