Wiki
Meeting 2026 06 01
Participants. Michell Zappa, Roy Bekhuis
Transcript. Granola share (a) · Granola share (b) · chat with transcript (auth required)
Uitwijken platform vision
- Community-focused social network for neighborhood engagement.
- Events discovery: hyperlocal + topic-based interests (T-shaped approach).
- Resident services: skill-sharing, mutual aid, local governance participation.
- Public-only interactions to prevent misuse and maintain transparency.
- Roy's motivation: enable community investment vs. tourist consumption.
- Amsterdam city center losing Dutch residents to speculation.
- Utrecht provides a better community-engagement model.
- Technical foundation already mapped.
- Event sources identified: overhide, pantanal, Amsterdam data pump.
- Open-data structures available for integration.
- Domain registered (.com for €11).
Development approach & resources
- Friday meeting with Roy's colleague (design specialist).
- Focus: engagement strategies and personal anchors for platform adoption.
- Open question: why external help needed vs. internal talent / resources?
- MVP prototype strategy:
- Quick prototyping with Envisioning resources.
- Internal testing (team as social-network users).
- Practical testing within municipality.
- Current status: pet project for Roy, seeking project manager and funding.
- Potential sources: Amsterdam municipality or external grants.
- Technical experimentation planned.
- Interactive pages beyond wireframes.
- Dutch mapping service integration (previous API issues noted).
- Event-source mapping and API negotiations.
Platform architecture considerations
- Core interaction types (limited building blocks approach):
- Events (informal meetups to major community gatherings).
- Messages / conversations threaded to events.
- Surveys / polling for local governance.
- Geographic scaling: postcode → street → neighborhood levels.
- Authentication vs. anonymity balance needed.
- Moderation built-in to prevent misuse.
- 20+ years online-community-management experience (Michell).
- Web 2.0 patterns applicable: machine tags, thread-oriented structure.
See History for the broader timeline, and Meeting-2026-05-22 for the prior session.