331–340 of 354 posts
After spending way too much time I got 9 degrees of separation. I did piggyback off of someone else's work with "Phinney". https://www.sixdegreesofwikipedia.com/?source=Lion%20Express... I found a ton of 5 degree paths and only a couple of 6 degree ones. Then I pulled out the "big guns" (the dead-end pages category). https://en.wikipedia.org/wiki/Category:Dead-end_pages_from_F...
After spending way too much time I got 9 degrees of separation. I did piggyback off of someone else's work with "Phinney". https://www.sixdegreesofwikipedia.com/?source=Lion%20Express... I found a ton of 5 degree paths and only a couple of 6 degree ones. Then I pulled out the "big guns" (the dead-end pages category). https://en.wikipedia.org/wiki/Category:Dead-end_pages_from_F...
Creator here. Six Degrees of Wikipedia is a side project I've been sporadically hacking on over the past few years. It was an interesting technical challenge and it's fun to play with the end result. Here's the tech stack: * Frontend: React (Create React App) * Backend: Python Flask * Database: SQLite * Web (frontend) hosting: Firebase Hosting * Server (backend) hosting: Google Compute Engine (it runs fine on a tiny…
How big does the SQLite database get? How do you maintain such great performance? (Other than indexes?)
Context: https://www.youtube.com/watch?v=MuDLw1zIc94
Addendum - I thought it was a really cool idea, and you made it look amazing! Well done!
Earlier quoted context omitted.
The downside of bidirectional seems to be that things like place names are linked via short paths through boring articles like "Census designated place" or "City"
The bi-directional nature of the search does not change the end result. It is simply a performance improvement.
Creator here. Six Degrees of Wikipedia is a side project I've been sporadically hacking on over the past few years. It was an interesting technical challenge and it's fun to play with the end result. Here's the tech stack: * Frontend: React (Create React App) * Backend: Python Flask * Database: SQLite * Web (frontend) hosting: Firebase Hosting * Server (backend) hosting: Google Compute Engine (it runs fine on a tiny…
Simple question I have is, are you hitting wikipedia api live? or you have dump of the wikipedia and running through it?
If running through dump do you update it regularly or how?
Thanks in advance.
Creator here. Six Degrees of Wikipedia is a side project I've been sporadically hacking on over the past few years. It was an interesting technical challenge and it's fun to play with the end result. Here's the tech stack: * Frontend: React (Create React App) * Backend: Python Flask * Database: SQLite * Web (frontend) hosting: Firebase Hosting * Server (backend) hosting: Google Compute Engine (it runs fine on a tiny…
Looks pretty cool. Simple question I have is, are you hitting wikipedia api live? or you have dump of the wikipedia and running through it? If running through dump do you update it regularly or how? Thanks in advance.
[1] https://github.com/jwngr/sdow/blob/f39398d112fecf7b993c64bd4... [2] https://github.com/jwngr/sdow#data-source
All I get for every search (no matter what terms) is: "Whoops... something is broken and has been reported. In the mean time, please try a different search."
My favorite mentioned which Wikipedia article had the longest article name:
Suzukake no Ki no Michi de "Kimi no Hohoemi o Yume ni Miru" to Itte Shimattara Bokutachi no Kankei wa Dō Kawatte Shimau no ka, Bokunari ni Nannichi ka Kangaeta Ue de no Yaya Kihazukashii Ketsuron no Yō na Mono (https://en.wikipedia.org/wiki/Suzukake_no_Ki_no_Michi_de_%22...)