I've been working on Habitat for the past two years. It all stemmed from this idea that I posted in April 2024.
Habitat is a free open-source, self hosted social platform for local communities. It is aimed at fostering local community discussions and discovery of areas of interest. This is why it is built primarily around location. A Habitat instance centers on a specific area, and the local community can make generic posts about that area, or they can make posts about specific locations in that area. More about what I've been building and the future plans here.
Features
- Habitat specification of location and size - enabling posts related to the local area
- Home feed - Displays the most recent posts
- Nearby feed - Displays posts sorted by proximity to the user
- Create posts - Upload photos, set locations, comments
- Categories - Location rules
- Amazon S3 image storage option
- Personalisation - Overrides Habitat defaults per user: kms/miles, hidden categories
- Moderation tools - User, post, comment moderation, block email addresses
- Announcements - Scheduled announcements
- Public moderation log - Keep moderator actions visible for 30 days
If you're interest in this at all, please give it a spin and let me know how you get on. I'll keep an eye here on Lemmy, but you can also post to the Habitat discussion board on GitHub.
If you don't mind my asking, what drove the decision to not base it on ActivityPub? On the surface that seems to be an easier starting point that building evetything out from scratch
Activity Pub doesn't take advantage of the unique solution we have by knowing the user's location and the location of instances. In a way, it seems overkill for what we want. Additionally, I don't necessarily want other software communicating with Habitat. You never know, I might change my mind as I delve into it. I changed my mind on a great number of things as I came to develop them for phase 1. I accept that there are things about existing protocols that I don't fully understand.