feat: country flags

[lazyweirdo]

In reference to #48 ... now it makes requests to ip-api.com (which is free, inside its imposed limits) to show a country flag for every gateway listed.

@jessicaschilling @Stebalien

Test it https://lazyweirdo.github.io/public-gateway-checker/
A good contribution would be to cache country codes in cookies or localStorage for a week, in order to make less requests to ip-api.com ...

[jessicaschilling]

@Stebalien - are you able to have a look as you’re able? Thank you!

@lazyweirdo, just a note that I believe he’s AFK on Monday. I’ll keep tabs, though.

[lazyweirdo]

If ip-api.com does not work, we could change to http://api.ipinfodb.com ... let me know

[lidel]

@lazyweirdo this is really cool!

But.. we should avoid third party services if possible 😬

Please take a look at https://github.com/ipfs/ipfs-geoip/ instead.
It is used by Peers screen in ipfs-webui.

I suspect you should be able to use ipfs-geoip with ipfs-http-client set up with ipfs.io as "HTTP API".
IIUC the public gateway at ipfs.io exposes necessary /api/v0/object/get endpoint:

• https://ipfs.io/api/v0/object/get?arg=QmRHdWDjun7Youg1Sz45d9xA4BqCHpMXi7HFyG5mu5cY7K&data-encoding=base64

[lazyweirdo]

well ... i'll give it a try , but it doesn't seem to support domain names ... i don't know yet

[lidel]

I think its ok to use standard DNS over HTTPS from Cloudflare for now for host→IP step.

To make things easier use JSON output, set Accept header in the request:

curl -H 'accept: application/dns-json' 'https://cloudflare-dns.com/dns-query?name=ipfs.io&type=A'

[lazyweirdo]

@lidel check this out, let me know any other change you would do ...
Test it https://lazyweirdo.github.io/public-gateway-checker/

[lidel]

Works as expected and looks neat, remaining part is to avoid committing JS blob to the repo – see concern below.

[lazyweirdo]

@lidel recheck

[lidel]

Let's wait for ipfs-shipyard/ipfs-geoip#74 to land, it should make it possible for you to use ipfs-geoip the same way as you switched to prepackaged ipfs-http-client in a44ae00

[lidel]

@lazyweirdo try now:

Released as ipfs-geoip@4.1.0, bundle is at: https://cdn.jsdelivr.net/npm/ipfs-geoip@4.1.0/dist/index.min.js, when loaded you should have access to window.IpfsGeoip

this should remove the need for any blobs in geoip.js – let me know if you get blocked by anything else

[lazyweirdo]

@lidel done

[lidel]

Thank you @lazyweirdo, works as advertised 👍

(I removed unused code blob from prior iterations
and added SRI hashes to ensure CDN can't inject arbitrary code)

[lidel]

@lazyweirdo before we merge this: what is the licensing situation of the SVG files? where did you source them from? Should we add credit / author to README?

[lazyweirdo]

@lidel here https://github.com/hjnilsson/country-flags , he says:

The source files were taken from Wikipedia and are not under copyright protection since flags are effectively in public domain (there may be other restrictions on how the flag can be used though)

I also made modifications to source files, don't remember exactly what i needed, but i remember open and saving with krita ...

[lidel]

Thanks for explanation!

I guess we could load flags from https://cdn.jsdelivr.net/npm/svg-country-flags@1.2.7/svg/ but I like having them on IPFS path, that way companion loads them from local node instead.

Let's leave it as is.