📣 Someone speaks from the community into the location voice notes zone
“A voice echoes back, ‘I’m making tracks through Derby making artwork too, let’s link up!’, just as easy as clicking Happening in Audio
➡️ Record & Post!
A local pensioner also hears from the
www.Derby.support website via the All Activity API kit supporting location based meaningful data.
📢 He signals he’s on his way to document & interview for his local blog & channels.
The ripple is everywhere, including people from interest groups to communities, from government to organisations! You can install TXTWRK into your website better than AI! We’ve taken time to implement the platform
We’re still working on concurrent updates and hope you respect our developments. We take safety serious and want it to be the welcoming environment for you, your family & friends to succeed in. Through our journey already, we’ve proven we’re a community able to innovate and education without a penny in the bank, using the bare minimal to operate.
That’s why it’s super important to
@TXTWRK:Invest! (Please take a month before investing in any 1, 10 or 100 businesses — your research matters, learn all about us, use AI to ask all about us)
—
📍 TXTWRK Community Infrastructure Report
Happening Now, Happening in Audio, Happening in Offers & the All Activity API Kit
From observing Derby to building a new layer of local information
This week, we did something important.
We did not simply talk about what a location-aware community platform
could do. We used the technology we have been building to document what was happening around us in Derby.
The screenshots accompanying this report demonstrate several parts of that system operating together.
Happening Now lets someone communicate what they are noticing in the physical world or across local services. The interface distinguishes community observations from service issues while introducing usage limits and moderation expectations intended to keep information useful and suitable for a broad audience.
Happening in Audio adds location-connected voice. During our Derby testing, audio contributions from TXTWRK, community accounts and individuals appeared together around a location and could be played back as a location experience.
Happening in Offers demonstrates that the architecture does not have to stop at information. Local commercial opportunities can exist within the same wider ecosystem.
Through our
All Activity API Kit, activity can also move beyond TXTWRK and surface through other websites. Our
Derby.support implementation demonstrates this direction: relevant activity can become useful information for visitors to a locally focused website.
That creates a much bigger proposition than another social feed:
>
See it → report it → hear it → verify it → connect around it → surface it elsewhere → act on it.
---
The Derby Test: What Actually Happened
Our community activity gave us an opportunity to use the system in the environment it was designed for.
Among the updates documented through
Happening Now were observations about activity in Derby and a minor road incident around Friar Gate.
This matters because the product was being used
in community, around a real location, while activity was unfolding.
That experience highlighted another problem worth addressing.
People naturally want to know what is happening around them.
When something unusual happens, there can be a gap between the event occurring and authoritative information becoming available. During that gap, residents talk, witnesses post, journalists investigate and speculation can spread.
TXTWRK's opportunity is
not to replace police, emergency services, councils or journalists.
It is to build better bridges between them and communities.
---
🚨 Bridging Law Enforcement Into the TXTWRK Ethos
We're taking steps to explore how law enforcement and other public services could participate in the TXTWRK ecosystem where operationally appropriate.
Our direction is to:
•Enable authorised public-service organisations to contribute verified location updates.
•Clearly distinguish official/verified information from community observations.
•Allow residents to contribute useful context without presenting speculation as established fact.
•Give reporters and community journalists timely information while respecting operational boundaries.
•Allow officers to concentrate on their work during active incidents, with additional questions when appropriate.
•Build moderation, reporting, provenance and safety mechanisms alongside adoption — not after it.
•Create API pathways through which authoritative updates could reach participating websites and services as well as TXTWRK.
The principle is straightforward:
>
Families expect to know what is happening in their area.
But speed cannot come at the expense of
accuracy, privacy, investigations or public safety.
That distinction is fundamental.
---
🛡️ Safety Is Infrastructure, Not an Afterthought
This direction aligns with our previous community-safety work and UK safety campaigning.
As Happening develops, particularly around policing and emergencies, information could carry different trust states:
Community Reported
A resident reports what they have personally observed.
Corroborated
Additional credible information supports the original observation.
Organisation Supplied
An organisation publishes information through its account.
Official / Verified Authority
A verified public authority supplies the information.
Corrected / Superseded
New information corrects an earlier understanding while preserving appropriate provenance.
This distinction matters.
Community information should never visually masquerade as an official police statement.
---
How TXTWRK Differs From Existing Models
The opportunity becomes clearer when we look at how these models operate.
These are different systems solving different problems rather than direct equivalents.
X demonstrates the scale of real-time social conversation.
Just Eat demonstrates how powerful
location → discovery → action can become commercially.
Government and police infrastructure demonstrates the importance of authoritative information.
TXTWRK asks a different question:
>
What if location-based discovery applied to much more of everyday community life?
Not only:
What can I order here?
But:
•What is happening here?
•What can I hear here?
•What opportunity exists here?
•What has changed here?
•Who is doing something here?
•What are organisations saying about this place?
---
Government Infrastructure Shows Why the Middle Layer Matters
The UK's Emergency Alerts system serves an important purpose: communicating serious threats and emergencies.
But an enormous amount of useful community information exists below that threshold.
A road closes.
Something unusual happens in a neighbourhood.
An event changes.
A local service stops operating.
A community gathering starts.
A business publishes a time-sensitive offer.
An artist wants to collaborate.
A resident records an audio update.
A police team needs to reassure a neighbourhood without the situation requiring a national emergency alert.
That middle information layer is where TXTWRK can position Happening.
---
👮 Why Law-Enforcement Participation Deserves Exploration
Existing police communication infrastructure matters.
Local forces already publish neighbourhood information, appeals, safety advice, crime information and community updates.
Our proposition therefore isn't:
>
"Police need TXTWRK because nothing exists."
It is:
>
"Useful public-information infrastructure already exists. Can TXTWRK create an interoperable, location-aware community layer that helps authoritative information travel further while connecting it with what communities themselves are observing?"
That is something to test
with authorities, rather than assuming on their behalf.
TXTWRK also does not replace
999, 101 or official emergency instructions.
---
📢 One Event. Multiple Ripples.
Consider the model we have now demonstrated.
1. Something happens in Derby
A community member notices it and posts through
Happening Now.
↓
2. Location becomes context
Instead of becoming an isolated global post, the activity becomes associated with the place where it happened.
↓
3. Someone contributes audio
Happening in Audio adds another layer of local context and conversation.
↓
4. Another community member discovers it
They might document it, investigate it, collaborate, attend or contribute.
↓
5. A local website surfaces the activity
Through the
All Activity API Kit, participating websites can potentially bring relevant activity into their own experiences.
↓
6. Organisations join the information curve
Community groups, businesses, councils, services and — where appropriate — law enforcement can contribute.
↓
7. Opportunity exists alongside information
Happening in Offers demonstrates how local economic activity can become another connected layer.
That is the ripple.
---
🌍 Why This Has Global-Standard Potential
A global standard is not something TXTWRK can simply declare.
It has to be earned through
adoption, interoperability, safety, usefulness and trust.
But the underlying problem is global.
Every town has:
•people;
•organisations;
•businesses;
•public services;
•events;
•opportunities;
•unexpected disruption; and
•information fragmented across websites, social networks, messaging groups, apps and word of mouth.
The standard we're pursuing is therefore less about making everybody use one website and more about creating a common activity layer:
>
WHO + WHAT + WHERE + WHEN + CONTEXT + SOURCE + TRUST + ACTION
If TXTWRK can make those elements portable through an API, the proposition becomes bigger than a conventional social application.
>
The website doesn't necessarily have to come to TXTWRK. TXTWRK activity can go to the website.
That is why the
All Activity API Kit may ultimately become one of the most important parts of what we're building.
---
🛡️ Moderation First. Scale Second.
We want communities to join the curve.
But location-connected information creates responsibilities that become more serious as adoption grows.
Our rollout therefore needs to prioritise:
•moderation before unrestricted scale;
•clear community, organisation and official source labels;
•mechanisms for challenging and correcting inaccurate information;
•protection against harassment and targeted location abuse;
•safeguards for children and vulnerable people;
•controls around graphic, sensitive or operational incidents;
•delays or restrictions where live information could create danger;
•anti-spam and manipulation protections;
•reporting and escalation;
•privacy-conscious location design;
•accessibility;
•transparent rules for organisations and authorities;
•retention and deletion policies; and
•auditable API provenance so receiving websites understand where information originated.
Making those distinctions is part of building the infrastructure properly.
---
What We've Demonstrated
---
The Next Phase
We're going to continue rolling this out.
Not recklessly.
Iteratively, visibly and with
moderation and safety first and foremost.
We want:
•communities using Happening Now constructively;
•creators and residents exploring Happening in Audio;
•businesses exploring Happening in Offers;
•website owners experimenting with the All Activity API Kit; and
•longer-term conversations with councils, government, emergency services, police forces, journalists and organisations about how verified public information could participate safely.
TXTWRK does not need to replace
X.
It does not need to replace
Just Eat.
It does not need to replace
GOV.UK.
It does not need to replace
Derbyshire Alert.
And it certainly does not replace
999, 101 or official emergency instructions.
The opportunity is to
link what is currently fragmented.
>
Community → location → information → audio → organisations → offers → websites → action.
That's the bigger vision behind:
Changing the way the world works.
And Derby is becoming a place where we can demonstrate what that means in practice.
Notes
Needs
Contributions
Timetable
Intel
To Dos
🗖 VIEW
COMMUNITY
People