Of course, that is a centralized option, but, otherwise, the application could not function fully without it.
Or could it?
- You can do it with tags (for example put a tag with
x<longitude>y<lattitude> - You can use fields in the json_metadata and search/filter on it with AskSteem. Distance is easy its just
sqrt( |x1 - x2|² + |y1 - y2|² )(assuming earth is flat)
Another thing... please serve it as a single page app. It needs to work with file://, IPFS, DAT, etc. You will need to use #s in your routes.
@heimindanger Thanks for your advice. Yes, this is a good idea, I implemented the SPA version and uploaded it to ipfs: /ipns/dtrip.app/
I want to make the choice of the node and the ability to work only on it.
To filter objects on a map, it would be better to use a country, it seems to me that it would be more rational, publications may contain different or multiple objects, not only points.
I think in the future, there will be no problems with filtering and aggregation of objects by json_metadata field. EOS and GOLOS blockchains already have a MongoDB plugin, most likely the http standard of the interface will be developed soon, which will be able to run along with the node and this will solve the problem. AskSteem is also a centralized solution, then why is it better than the service developed specifically for my application?
@heimindanger is a homophobe, remind him it's 2018 and people are people.
Would you believe anyone who calls someone else a "fag" in a derogatory way?