|
|
|
|
|
|
by verdverm
131 days ago
|
|
|
I get the concept, but why is this interesting to HN? The page has very little about how it works (security / trust / identity), there is nothing about tech stack or open source. These are going to be paramount in any civics platform, b/c transparency and the trust-pocolipse. |
|
|
It’s currently built with Next.js and Firebase. Responses are stored separately from identity data, there are no public profiles, and only aggregate results are exposed in the UI. Verification is used to increase resistance to bots, but answers are not tied to public identity.
I agree that any civic platform lives or dies on transparency right now. I’m actively considering showing the question schemas and aggregation logic so the mechanics are inspectable rather than opaque.
If you have strong opinions on what absolutely must be open versus what can reasonably remain closed, I’d genuinely value that perspective. This is still early and the landing page is pretty barebones, but the core web app and data model are where most of the effort has gone so far.