Source, relays, and public infrastructure for Interpoll.

Source repository

The public source is available on GitHub at github.com/Interpoll1/decentralised. It contains the app code, public rendering work, relay-facing logic, and the implementation details that connect the browser app with the searchable SSR layer.

For readers, the important point is simple: Interpoll does not rely only on marketing claims. Public post and poll pages, sitemap generation, slugged URLs, proof-of-work-oriented publishing, and encrypted coordination flows are visible as engineering decisions inside the project.

What to inspect

If you are reviewing Interpoll for a community, search engine quality, AdSense readiness, or general trust, start with the public SSR pages, API routes, relay configuration, sitemap route, and the browser app paths for publishing and chat. Those areas show how public content becomes readable on the web while private material stays in the interactive app.

The security model is layered rather than magical: signatures, timestamps, nonces, relay validation, proof-of-work challenges, spam scoring, and moderation logic all help make automated abuse more expensive. Encrypted chats and private spaces use encrypted payloads instead of treating relays as trusted readers.

Public pages and the app

The public website at interpoll.endless.social is the readable layer for posts, polls, communities, topics, source context, about, contact, privacy, and terms. The full app at endless.social is where users publish, vote, join communities, manage identity, and use encrypted coordination.