You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, when a client opens a campaign site, the number of signatures is requested from the API. This leaks the IP addresses of all visitors to the API provider. It would be nice if, instead, the server-side of the front-end would make this request.
(Sorry if ended up posting this in the wrong repo)
The text was updated successfully, but these errors were encountered:
just to be clear: the API provider is the same as the provider for the API collecting signatures (ie us).
This being said, I agree it's a difference to know the IP address only of the ones that agree (that submit) vs. every visitor
it's possible/trivial to fetch that counter from your website. The easiest is probably to have a cronjob that query the counter every few min and store it
(same url we use from the widget) https://api.proca.app/api?query=query%20getCount ...
As the widget is potentially embedded in a lot of different CMSes, I can't think of a way to provide a universal solution without some extra work on your side.
What about:
you add a cronjob (running evry x minutes) that curl the counter api and saves the json in a place your web server can serve
we add a param "counter_api" that would use the url of the json file on your web server
it's a difference to know the IP address only of the ones that agree (that submit) vs. every visitor
👍 this is what I wanted to target
What about:
* you add a cronjob (running very x minutes) that curl the counter api and saves the json in a place your web server can serve
* we add a param "counter_api" that would use the url of the json file on your web server
Sounds like a good and reasonable solution to me. However, I can not speak for an organization ...
At the moment, when a client opens a campaign site, the number of signatures is requested from the API. This leaks the IP addresses of all visitors to the API provider. It would be nice if, instead, the server-side of the front-end would make this request.
(Sorry if ended up posting this in the wrong repo)
The text was updated successfully, but these errors were encountered: