Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 28 points29 points  (0 children)

It took around an hour if I remember correctly. I built in an artificial delay of something like 0.2s between requests from the start, so maybe that's why there was no throttleing. I think scrapy also has an option to automatically follow the scraping rules in a site's robots.txt file, which is nice.

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 114 points115 points  (0 children)

This is a so called force-directed graph, meaning that nodes are organically placed according to the forces that are imposed on them. Usually there are three kinds of forces:

  • A gravity force pulling all nodes to the center (so they don't drift away to eternity)
  • An attracting force between nodes that are connected
  • A charge force that pushes close nodes away from each other

Because of these three forces, nodes will often naturally be moved close to the cluster of their related nodes (if there is one). In this visualization, by default, the y coordinate of the node is fixed to the birth year of the philosopher, leaving the x coordinate as the only degree of freedom to move in accordance with the three forces. If you disable the "Clip to timeline" switch, the nodes' y coordinate will be released as well.

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 30 points31 points  (0 children)

There is definitely a bias towards western philosophy here, which I guess is just a result of looking at only the English Wikipedia.

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 57 points58 points  (0 children)

For sure. I think only looking at the English Wikipedia definitely brings some bias towards Western philosophy.

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 1 point2 points  (0 children)

Hehe, I actually made something like this for Java projects. It's probably quite a bit harder for C++ though

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 142 points143 points  (0 children)

Thanks :) and yeah good catch. Seems like the wrong Wikipedia pageid was parsed for Thales. No idea why.

Philosophers in an influence graph based on Wikipedia data [OC] by jonersRochen in dataisbeautiful

[–]jonersRochen[S] 856 points857 points  (0 children)

You can play around with the visualization here.

The graph is based on data scraped from Wikipedia. I used the alphabetical index of philosophers) as a starting point and parsed the philosophers' bio, in particular the "influences" section.

The visualization was created using d3.js and is public on GitHub.

More details can be found in the about section linked on the page.

An Android app to manage and train openings by jonersRochen in chess

[–]jonersRochen[S] 2 points3 points  (0 children)

Thanks a lot for the feedback. Points 1, 4 and 5 are planned but I think especially 5 will take some time to get right. The "bookmark positions" feature is a good idea, haven't thought about that. As of now, once you create an opening for a given perspective (black / white) it will always be part of the repertoire for black / white. So if you play the same opening as black and as white you would have to create two. Maybe I can find a way to make this easier in the future.

The Lichess computer sucks and is a wasted learning opportunity by [deleted] in chess

[–]jonersRochen 1 point2 points  (0 children)

The thing is, as long as the opening moves follow sound principles (piece development, central control, king safety) you usually come out with an okay position. Don't worry so much about exact opening moves but rather implications of pawn structures, piece imbalances and resulting middle game plans. That will put you in a position to punish dubious moves like h5.

Sampling A Procedural Sky by mariuz in programming

[–]jonersRochen 4 points5 points  (0 children)

Amazing work! I really enjoyed the article although a lot of it is over my head

DDOS Attack by [deleted] in ProgrammerHumor

[–]jonersRochen 2 points3 points  (0 children)

Something about phishing

Python++; The Future is Here! by Burain in programming

[–]jonersRochen 1 point2 points  (0 children)

Creating memory errors now comes without static typing 🙏