pscircle --output=pncircle.png --dot-radius=3 --output-width=3200 --output-height=2000 --tree-font-size=20 --tree-font-face=cuprum --cpulist-show=0 --background-image=/tmp/noise.png

More complete script may look like

noise ++ && pscircle --output=/tmp/pscircle.png --dot-radius=3 --output-width=3200 --output-height=2000 --tree-font-size=20 --tree-font-face=cuprum --cpulist-show=1 --toplists-font-face=cuprum --background-image=/tmp/noise.png && nitrogen --set-zoom-fill /tmp/pscircle.png


Meshroom is a free, open-source 3D Reconstruction Software based on the AliceVision framework.

As We May Think

Berners-Lee wrote a proposal in March 1989 for “a large hypertext database with typed links”. Although the proposal attracted little interest, Berners-Lee was encouraged by his boss, Mike Sendall, to begin implementing his system on a newly acquired NeXT workstation. He considered several names, including Information Mesh, The Information Mine or Mine of Information, but settled on World Wide Web.

By Christmas 1990, Berners-Lee had built all the tools necessary for a working Web: the HyperText Transfer Protocol (HTTP) 0.9, the HyperText Markup Language (HTML), the first Web browser (named WorldWideWeb, which was also a Web editor)

Web was originally read-write.

next browser

I just had to take the hypertext idea and connect it to the Transmission Control Protocol and domain name system ideas and—ta-da!—the World Wide Web … Creating the web was really an act of desperation, because the situation without it was very difficult when I was working at CERN later. Most of the technology involved in the web, like the hypertext, like the internet, multifont text objects, had all been designed already. I just had to put them together. It was a step of generalising, going to a higher level of abstraction, thinking about all the documentation systems out there as being possibly part of a larger imaginary documentation system.

Berners-Lee is one of the pioneer voices in favour of net neutrality, and has expressed the view that ISPs should supply “connectivity with no strings attached”, and should neither control nor monitor the browsing activities of customers without their expressed consent.

And the first page

^ Note the weird html source of this pages (missing head, body tags)


Starting in 1963, Ted Nelson developed a model for creating and using linked content he called “hypertext” and “hypermedia” (first published reference 1965)

1968, Engelbart demonstrated a hypertext interface to the public for the first time, in what has come to be known as “The Mother of All Demos”.

In 1992, Lynx was born as an early Internet web browser. Its ability to provide hypertext links within documents that could reach into documents anywhere on the Internet began the creation of the Web on the Internet.

# Still kicking in 2019
lynx -nocolor -use-mouse

In 1995, Ward Cunningham made the first wiki available, making the Web more hypertextual by adding easy editing, and (within a single wiki) backlinks and limited source tracking. It also added the innovation of making it possible to link to pages that did not yet exist.

The Firefox Add-On Hyperwords which has been developed in cooperation with Doug Engelbart and Ted Nelson gives Web surfers the ability to issue many commands on any text on the web, not only pre-written links—a return to what users could do 40 years earlier with Doug Engelbart’s NLS.

As We May Think

The world has arrived at an age of cheap complex devices of great reliability; and something is bound to come of it.

Vannevar Bush july 1945 issue

The memex would provide an “enlarged intimate supplement to one’s memory”. The concept of the memex influenced the development of early hypertext systems (eventually leading to the creation of the World Wide Web) and personal knowledge base software. The hypothetical implementation depicted by Bush for the purpose of concrete illustration was based upon a document bookmark list of static microfilm pages and lacked a true hypertext system, where parts of pages would have internal structure beyond the common textual format. Early electronic hypertext systems were thus inspired by memex rather than modeled directly upon it.

ffmpeg scene detection

ffmpeg -hide_banner -i "$file" -an \
-filter:v "select='gt(scene,0.2)',showinfo" \
-f null \
- 2>&1

More complex version (detection is the same), that shall produce a lil timeline/stats like

/media/b/data/trailers/Captain.mkv timeline
average clip length: 1.06221 seconds
103 clips, 1 min 56 s 641 ms

Note: ffmpeg scene detection filter fails prety much every time, needs replacement with something better.

Update: The old way, abusing x264 debug info, unfortunately the results are in frames

ffmpeg -i "$file" -vf scale=100:100 -sws_flags neighbor -an -pix_fmt yuv420p -f yuv4mpegpipe - 2>/dev/null | x264 - --demuxer y4m --bframes 0 --min-keyint 10 --scenecut 45 --preset superfast --crf 30 --threads 1 -v --output /dev/null 2>&1 | grep scene

Ffmpeg only version, still abusing x264 (unclear on how to pass parameters to x264, -preset ultrafast not working for example)

ffmpeg -v debug -an -i "$file" -vf scale=100:100 -sws_flags neighbor -c:v libx264 -f null - 2>&1 | grep "scene cut at" | cut -d ' ' -f 7 | uniq


Increasing detection threshold with -sc_threshold 90 might detect fade-in/fade-out situations, but will also place I frames in the middle of long shots.

diff -y Captain.txt Captain90.txt 
1                                 | 2
36                                  36
                                  > 57
                                  > 59
63                                  63
534                               | 269
                                  > 397
                                  > 505
                                  > 601
611                                 611
                                  > 711
720                                 720
                                  > 723
                                  > 726
729                                 729
                                  > 732
                                  > 735
738                                 738
842                                 842
854                                 854
                                  > 856
901                                 901
                                  > 950

Openbox menu item height

Nope, but one could use shadow for that

menu.items.font: shadow=y:shadowtint=0:shadowoffset=15

Cube volume





about / github / jekyll /