|
|
|
|
|
by gucduck
131 days ago
|
|
That’s fair feedback. I’ve updated the post to include a section with more implementation details. 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. |
|
This is increasingly looking like the tell tale for Ai bots masquerading as humans. I've heard essentially this phrase as the first in several recent interactions which ended up being bots.
Can you prove your humanity? Bots and agents are not allowed on HN