3 ms·
Couple of thoughts: 1. To avoid making a loss due to map costs, sites may have to create a source of revenue which scales in proportion to the amount of maps u
by billysielu 8y ago
Couple of thoughts:
1. To avoid making a loss due to map costs, sites may have to create a source of revenue which scales in proportion to the amount of maps used. Advertising? Google Advertising?
2. It seems quite easy to attack someone by linking to their map content on social media. Loads of traffic = loads of cost. So sites may need to consider devising a 'mapping cost defense' of some sort.
- IanCal 8y agoI don't think 2 would work, we use static maps and they only work based on the site they're loaded from. They won't even work on our dev instance because I've not whitelisted the domain. Unless lots of people are going to your actual site, of course.
- elyobo 8y agoI have a project which runs a variety of sites for our network - currently ~900 different domains. Restricting keys by domain name is not really practical for us.
- IanCal 8y agoA list of 900 isn't really a huge problem, is it? Do they share anything common (many x.mycompany.com)? You can use wildcards.
- elyobo 8y agoMany do, but not all, and even then just wildcarding the common bits would leave it pretty much wide open. Maybe if they allowed regular expressions then it could be targeted reasonably closely, or if there was an API I could use to generate the keys then I could provision specific credentials for each site...