@patcon Thanks for the Twitter details. Good to know there is an avenue. We will have to wait until August to see how our funding ideas pan out. As for the talk, there will be a recording, but I’m not sure when Eyeo will release it. I will definitely share it out though 🙂
Buy domains from Enom: A trusted registrar since 1997 with great prices, exceptional customer service, and 24/7 support. Over 20 million registered domains and counting. FIND YOUR DOMAIN NOW >>>
Will fire those over tonight. Thank you in advance for taking the time to review and answer. We’ve been heads down working on our talk. T-minus 2 hours until we talk about vTaiwan, g0v, Polis, and g0vNYC. 🙌🏾
@colinmegill@au Here are our questions. Thank you again! ```- Did vTaiwan add any additional features or make any changes to Pol.is?
- Do you have any examples of Pol.is projects using an authentication layer other than Twitter or Facebook?
- What tests did you set up to study the use/problems/limitations of Pol.is?
- Is vTaiwan running their own instance of Pol.is or using the hosted solution?
- Are we able to use the Pol.is API?
- Is there an open project roadmap for Pol.is?
Audrey and the g0v team were early adopters of the tool, gave us enormous amounts of helpful feedback. We were, at times, on a 24 hour loop of feature request and pushing code during the initial vTaiwan experiments
Yes. Alternativet in Denmark is an excellent example - they are a political party and their 11,000 members log into their system. pol.is has a system called `xid` for 'external id'. If you know who your people are, you can embed us and pass that to us to keep track of who is who.
Easiest answer is 'not for free and not for everything'. There is a lot of customization and control you can accomplish via the pol.is iFrame with data attributes - that's the way we've gone with the community based on requests and it's really quick. Basically no one is using the API, with the exception to maybe export data.
@colinmegill Thank you so much. This was incredibly helpful. One clarifying question around `xid` system. In our use case, we want to tie zip code to each user, since zip codes are not unique, how could we tie this to each user record? Would it still be through `xid` or a custom data attribute?