Our effort in this project is not to build an alternative that mimics mainstream solutions, we respond to different needs. The assumption here is that technology is neither good nor bad, nor is it neutral. It does not depend (only) on how it is used.
Building software means taking a stand, making decisions, choices. These choices start from a precise look at reality, from specific needs and ends implementing specific features, choose default values, simplify some flow and patterns while making difficult others.
The use case we have in mind is that of small nodes tied either to a specific territory or at the limit a small thematic community. This choice is not very fashionable: for a long time in IT one of the priority values is scalability, this is because you are forced to imagine platforms that are suitable for hosting millions of people, millions of customers.
Structuring a project in this way simply means creating a lot of power and centralizing it in a specific place.
Long story short, even if fb/insta/tiktok was in our hands it wouldn't work, it's not only the wrong owner, it's just the tool that wasn't designed with decent values.
When we started developing gancio, we were asked for a national platform, we preferred to imagine small nodes for local communities.
All people looking at the home page see the same events, there are no personal timelines.
Nowhere on gancio appears the identity of who published the event, not even under a nickname, not even to administrators.
The reason for this is not only to avoid gamification but also to consider the use case we're all going into of states increasingly intolerant of displays of dissent.
That's also the reason why adding events by anonymous people is a feature enabled by default.
We don’t care about making hits so we export events in many ways: via RSS feeds, via global or individual ics, allowing you to embed list of events or single event via iframe or webcomponent on other websites, via ActivityPub, microdata and microformat. Unlike GAFAM that does everything to keep users and data about them, we believe that information, like people, must be free. People can stay updated without necessarily going through the site because we don't need your attention or to sell you anything.
Made with ❤️ by underscore hacklab
- Download source
git clone https://framagit.org/les/gancio- Install dependencies
yarn- Use a default sqlite configuration
cp config.example.json config.json- Run db migrations
./node_modules/.bin/sequelize db:migrate- Create a first admin user (see the CLI documentation for
users)
./server/cli.js users create admin@example.org thisisthepassword --role admin- Hacking
yarn devinfo "Info" You can skip step n.5 and register the user from the UI, the first registered user will be an active administrator.
- Build the container
docker build -f Dockerfile.dev -t gancio .- Install dependencies
docker run -v $PWD:/home/node -it gancio yarn install- Hacking
docker run -v $PWD:/home/node -it gancioPlease use the issues to discuss any modification.