Nice to see this here! I'm Sanjay Bhangar - I recently gave a talk about some of the history of the project and the technical architecture / setup at State of the Map, US (talk should be online soon).
This is essentially a long-running experiment in repurposing the OpenStreetMap software and architecture to map historical objects, with some modifications to handle dates: essentially, we generate vector tiles for the data and then use client-side filtering of the vector tiles to enable the time slider you see on the site.
Recently, we've been getting quite a lot of usage, and some folks mapping some areas really deeply, which is fantastic to see - of course, it all throws up very interesting questions, some of which are going to be harder to solve than others: we use OpenStreetMap's free tagging system, so a lot of these things would have to evolve as community consensus on tag usage, as OSM has.
As @nfgusedautopart says, it really is a big experiment .. all our code and discussions are open of course, and would love for you to contribute / jump in. This is the Github org: https://github.com/OpenHistoricalMap/
Code for our deploy process to deploy the website code as well as associated services like Overpass (query tool), Tasking Manager (tasking tool), etc: https://github.com/OpenHistoricalMap/ohm-deploy/ (uses Helm + Kubernetes for the deploy).
There's definitely some wild, fun problems in there - dealing with fuzzy dates, disputed historical facts, events .. though my favourite is likely the coastline problem: https://github.com/OpenHistoricalMap/issues/issues/329
Thanks for posting this here, and super happy to answer any questions if I'm able to.
That was in the example of the documentation frame-work, I believe - https://oxjs.org/#examples/oxdoc_tutorial - while highlighting how commenting / documentation works and the code there was purely example and not at all how the development style for the library is.
No, these sites are being blocked. I am on Airtel as well and things weren't blocked until yesterday. I think Reliance was the first to enforce the block - I believe they're also the ones who filed for the court order. It's really good to see this on the HN front-page, and hope there's more awareness / discussion. Blocking pastebin is a bit ridiculous :/ - the message one gets when one goes to any of the sites is just "This site has been blocked as per Court Orders", without any other explanation. Changing DNS servers does not work, so they are doing it at a different level.
this!!
I know this is a bit off in a tangent, but after spending a week with the Range API and contenteditable, the frustration is truly immense .. it is truly astounding that file upload and rich text editing, yes, two of the most basic things, are not really solved problems on the web.
It's amazing.
But also kind've exciting :)
uh.. and what if you're in India?
uhh .. apply for a Visa at your local consulate, hop onto a plane, go down to the library ... not very convenient, innit?
I'm sorry, but academic data walled up in closed journals (im sorry you live in a coccoon where you think everyone has a local university library) is malicious withholding of information - i dont imply that malice exists on the part of the scientist publication, but of the larger system - smug statements that data available only to experts will save the 'wise ones' from useless questions and let them do work or so, are, i think, retarded.
any-how, just my personal opinion.
This is essentially a long-running experiment in repurposing the OpenStreetMap software and architecture to map historical objects, with some modifications to handle dates: essentially, we generate vector tiles for the data and then use client-side filtering of the vector tiles to enable the time slider you see on the site.
Recently, we've been getting quite a lot of usage, and some folks mapping some areas really deeply, which is fantastic to see - of course, it all throws up very interesting questions, some of which are going to be harder to solve than others: we use OpenStreetMap's free tagging system, so a lot of these things would have to evolve as community consensus on tag usage, as OSM has.
As @nfgusedautopart says, it really is a big experiment .. all our code and discussions are open of course, and would love for you to contribute / jump in. This is the Github org: https://github.com/OpenHistoricalMap/
Fork of openstreetmap-website code-base: https://github.com/OpenHistoricalMap/ohm-website
Code for our deploy process to deploy the website code as well as associated services like Overpass (query tool), Tasking Manager (tasking tool), etc: https://github.com/OpenHistoricalMap/ohm-deploy/ (uses Helm + Kubernetes for the deploy).
Consolidated issues: https://github.com/OpenHistoricalMap/issues/issues
There's definitely some wild, fun problems in there - dealing with fuzzy dates, disputed historical facts, events .. though my favourite is likely the coastline problem: https://github.com/OpenHistoricalMap/issues/issues/329
Thanks for posting this here, and super happy to answer any questions if I'm able to.