Our Events
Schedule a happening, invite people, and see who is going.
Our Events is a calendar of things happening, on your own server. Schedule an event with a start time, an optional end time and a place; invite the people on your install; and let them respond going, interested or not going. It is the same shape as a social network's events, kept in your own database — so the guest list is yours and no platform is between you and the people you invited.
An event is deliberately not a post. It has a start and an end, a place and a host, and it is a container for two things a post has no room for: who was invited, and who is coming. That is why it is its own kind of row rather than something written to a feed — a post has none of those, and folding one in would leave the time with nowhere honest to live. Inviting someone is one row per person, so inviting twice cannot send two invitations; responding is one row per person, so changing your mind moves the headcount rather than adding to it. What this app deliberately does not have is the ticketing, the paid promotion and the public directory — those are features of an events platform open to strangers, and your install is one team.
Step by step
How to schedule your first event
Every step is the real one in your own install. An event is a row in your own database, and so is every invitation and every response.
- STEP 01
Open Events
From your workspace, open Events. It shows what is coming up on your install and the form to schedule a new event.
- STEP 02
Schedule an event
Give the event a title, a start time and, if you like, an end time and a place. It is scheduled and appears at the top of the upcoming list.
- STEP 03
Invite people
On the event's own page, invite the people on your install by handle. Each one appears on the guest list, and inviting them again changes nothing.
- STEP 04
Take the RSVPs
Each guest responds going, interested or not going. Only going counts toward the headcount, and a guest can change their answer at any time before the event.
- STEP 05
Cancel if plans change
Cancel the event and it leaves the upcoming list. Every invitation and response stays readable, so the record of who was coming is not lost.
What it does
A scheduled happening, its guests, and their answers
An event with a real time and place
Give an event a title, a start time, an optional end time and a place. An end at or before the start is refused, so a stored event always describes a window that could actually happen.
Invite the people you have
Invite anyone on your install by their handle. An invitation is one row per person, so inviting someone twice cannot send a second one — the list stays exactly the people you asked.
Three honest answers
A guest can say going, interested or not going. The middle one is the common case, so it is its own answer rather than a yes or no that would have to lie about a maybe.
A headcount that counts the right thing
Only people who said going count toward the headcount. Changing your answer from interested to going moves the number rather than adding to it, so the count is always who is actually coming.
Cancel without losing the record
Call an event off and it leaves the upcoming list, but every invitation and every response stays readable — cancelling is reversible and never destroys the guest list.
Everything on your own server
The events, the invitations and the responses are rows in your own database, on your own disk. There is no ticketing platform, no public directory and no third party holding your guest list.
Questions
Questions people ask
Straight answers, and where something is not built yet it says so.
What is Our Events?
How is an event different from a post?
What does 'interested' mean?
Can I invite the same person twice?
What happens if I cancel an event?
Where is all of this stored?
Our Events is ready on your install
It is part of Social Jinni and it runs on your own server — nothing to register, nothing to approve.