* * *
Tired of living in a system where others waste your time?
* * *
Have the feeling that your life is in control by other forces?
* * *
Realize that there are other things in life than money?
* * *
Tired of dealing with fake news?
* * *
Afraid of saying something wrong?
* * *
Trust people you don't even know?
* * *
Wasting hours following meaningless discussions?
* * *
Liking someone's opinion you actually don't like?
* * *
Don't wanna feed "big tech" with your data?



Then why not building up your own little "network" and grow in a natural manner with people you care, focus on things in your real life and environment, unplug and get off the grid!

Only dead fishes go with the flow,
if you wanna find the source
you have to swim upstream.

Last Update: 2024-06-12

Table of content:

Footer
Project Tribe
Tribe features
Messaging
Filesharing
Audio / Video Broadcasts
Audio / Video Calls
Intaractive Snippets
Location Service
In Pipe: Marketplace, Web3 Bridge
Tribe Apps
Chief Chief
Chief Wanderer
Chief Elder
Chief Servant
Chief Shaman
Chief Tribe Server
Chief Ias
Chief Colony
Application Features
Features by App
Apps by Operating System
FAQ
General Questions
Tribe Questions
Tribe Explained
Technical Information
Message Encryption
Footer

Project Tribe


Tribe is a project to digitally connect individuals with similar ideas, same traditions or regional relationship. Unlike traditional “social” networks or chat programs, which are usually hybrid (P2P - Client-Server) solutions, Tribe avoids the use of servers to transmit or store data.

Tribe is based on pure peer-to-peer technology, which is abbreviated here as P3.

Tribe makes it possible to create your own, private (closed), local and/or global networks. It largely avoids external dependencies to external resources and helps to keep relevant data consistantly accessible.

The aim of Project Tribe is to be helpful in the formation of regional but also global communities through the tools implemented.

Tribe consists of 8 apps which can be catagorized as following:
  • Tribe Apps
    Tribe apps are directly used to interact in and with Tribes.
    Apps: Chief, Wanderer, Elder
    Note: At that phase of development and for reason of testing, Wanderer and Elder are full-blown apps and have the same feature set as Tribe Chief.
  • Assistive Apps
    Other than Wanderer and Elders, assistive Apps come with some additional features assisting a Tribes Chief. They fully interact in a Tribe with their automation tasks, one to lower the load of the Chief app, secondly providing services while the Chief is offline.
    Apps: Shaman, Servant
    Note: At that phase of development and for reason of testing, Shaman and Servant are kept as full-blown apps with all the features of the Tribe Chief Application.
  • Supporting Apps
    Supporting apps are outsourced features as dedicated apps; allowing you as a Tribe Chief still focusing on your Tribe activities while working on some features / changes of your Tribe. In contrast / other than assistive apps, supporting apps to not interact in Tribe activities themselves.
    Apps: Ias, Colony
  • Tribe Server
    Apps: Server

Essentially, Tribe is made up of following features:

Tribe Features

Messaging

Message delivery types:

There are basically two different types for sending messages

Message content types:

In Tribe there are basically 2 methods for sending messages. The Tribe chief determines which of the two is active and in which of its meshes.

Message attachments:

Enhanced messages facilitate authorized or all clients to embed, attach or link data. A tribe owner specifies limits and defines the kind of data or information which can be attached.
Something about read confirmations:
Note: Only affects direct Messages.

A (directed) message will be marked as unread as long as the client didn't set the focus on it. A read confirmation will be sent to the origin at the moment the recipient highlights that message. In my point of view that process does not go along with the ideas about privacy. There are following options:
  • Keep it implemented and user can not change t. A read confirmation for direct messages will always be sent.
  • Keep it implemented but make it as an optional feature for the Tribe owner; he could activate "send read confirmations" for all or some of his meshes.
  • Keep it implemented but make it as an optional feature for the Tribe visitor; he could activate "send read confirmations" for all or some of his meshes.
  • Take it completely out.
Ways of implementation:
  • indicate this setting clearly within the actionbar, so that a user knows the current setting.
  • Inform a user about this setting when/before a private message got sent.
I'm considering it as an open item and let the experience make the decission.

Audio / Video Broadcasts

You can stream flv, mp4 videos, your devices camera and/or microphone to other members within a NetGroup.
In contrast to the calling feature, Braodcasts will be streamed over the mesh to all connected members. It is up to the Chief to activate and configure this feature. Each of the meshes has its own configuration.

Configuration options:
Scenarios:
News Channel, Radio Station (One to many), Podium discussion (inviting people onto the stage), ...

Tip:
Utilize the virtual cameras of your streaming Software for a more professional environment.

Audio / Video Calls

Other than broadcasts, a call will not utilize the mesh to connect two nodes with each other but establish a direct connection between these two peers.

Note:
A call can only be made if the two clients join at least one of the same Tribes.
For now I would like to keep it in that way; Nevertheless, the experience will tell if additional techniques are required.

Filesharing

With filesharing enabled, members or authorized clients are able to share files of any size by utilizing objecte replication. Object replication uses the full transitive connectivity of the group’s self-organized structure. It replicates objects through the group from nodes that have the objects to nodes that need the objects.
Tribe uses different ways of sharing files. Global filesharing allows users to prepare files for sharing and reuse them within different meshes. Whereby meshed shared files are only available for that specific mesh. You may consider global filesharing if you often share the same file or intend to share a big file to more than one mesh.
This feature can be set and configured by the Chief for each mesh separately.

Configuration options:

Interactive Snippets

An intarctive snippet is a kind of shared document. Different to messaging where clients usually react in a sequential fashion, the interactive sheet is a more or less static message where members commonly fill out form fields or set input controls values and push their data to either the Tribe owner or all members within a NetGroup. The creator of a snippet has the ability to split up the document into parts visible to the Chief or visitors only or both of them. The sent data will be stored into a data collector, a so called dataprovider. With charts the data can be visualize.
Allthough, interactive snippets can be used for simple non-interactive messages as well.

Available controls:
Info:
Ias is a dedicated app for creating interactive snippets.

Scenarios:

Locations

Locations is a features allowing you (as a Chief) to create locations as (points), borders or paths (lines) or areas (polygons) on virtual or real life maps. Whatever you decide, locations are always bound to real Longitude/Latitute encoded locations. It is especially usefull if you use the location feature in real world scenarios; visitors are then able to use their GPS (Global Positioning System) to be directly linked and shown on the map.
In case of virtual locations your visitors have to navigate manually.

Scenarios:

Marketplace (Future)

A marketplace where you and your visitors are able to share any kind of things.

Intended features:

Web3 Bridge (Future)

A integrated bridge from Tribe market to the Web3.

Intended features:

Application Features

Tribe is a set of several apps. Each of them has its own features set. Nevertheless they share some common ones especially a unified user interface.
The unified user interface shall give you a kind of familiar feeling to intuitively find the things you are looking for. The user interface is mainly split up into following areas:

User Interface

For more details please check out the Tribe Documentation

Common Features

Common features are features which have been implemented in all tribe apps. They are mainly for customization your in app experience and incooperate between the Tribe Apps itself.
On top of these 'common' features, each app has its own purpose and brings therefore some specific feature.
For details about the apps specific features, please read the features set section for the corresponging app or for a brief overview check the table Features by App

Common Tribe Features

Tribe Apps

Chief Chief

Message attachments will be either embedded or linked as a fileshare.
Um vertrautheit gewaehrleisten zu koennen bietet Tribe techniken ungewuenschte Clients zu identifizieren und aus der Gruppe auszuschliessen.
Chief is if you will the main app of Project Tribe. With Chief you create and manage your own Tribes and its lodges.
The Tribe mesh is the entry to your Tribe. Visitor has to pass through or join your Tribe Mesh first before being able to enter any of your lodges. You can see your Tribe mesh as a "Welcome/Lobby/Front Desk". After a client joins a mesh he either receives the lodges information automatically (according to your strategy and setup) instructions or information about your Lodges. from there they will receive additional information entering your Tribe through that Mesh and receive further information. As a chief of a Tribe set the properties and assign roles or duties to assistime members. If your tribe is growing you might wanna have some assistance like having moderators Share your Tribe's url via QR code or simple a rawtext url and publish it on your homepage or on our server
For details on the feature set refer to table Tribe Apps Feature Comparison.

Chief specific features

- Recommended: Desktop OS Availability: Linux (not yet), Android (x86) Features Overview: (see table) Develpement Status: Is Feature: No

Wanderer Wanderer

Wanderer is the thinest of all Tribe Apps and therefore ideal for mobile devices. With Wanderer you have all the features you need to visit your favourite Tribes.

Elder Elder

Elders is a Version of Tribe with an, to the minimum required features, reduced UI and implemented feature set. It is optimized for Users tending to deal with only a single Tribe at a time and work in a default setup environment.

For details on the feature set refer to table Tribe Apps Feature Comparison.

Servant Servant

Tribe Servant is the dedicated App for the "Servant" feature. The Servant is the entitiy within a Mesh which serves its clients (if assigned by either the Tribe Nani or by your own) as a data holder (a post office if you will). As Tribe is a P3 Solution, there are no Servers for a intermediate storage. There are times you want to send messages to clients which are currently not online but its important to you to get the message out. Tribe offers different ways to deal with such situations.

  1. The message will be queued on your divice and automatically delivered as soon as the recipient gets online. That's the default setting in cases you are connected to Tribe in which the Nani does not provide a trusted Servant or you generally deny the use of 3rd Party Servants.
  2. Utilize a Servant. A Servant should be constantly only to be accepted as a reliable Node. The advantage against queueing a message is that you don't have to be online at the same time as your recipient to get your message delivered.
a specific client but can't wait until he gets online A The advantage of having an servant connected

For details on the feature set refer to table Tribe Apps Feature Comparison.

Shaman Shaman

A shaman is meant to be a wise entity within a Tribe... the idea behind having a "Shaman" (didicated Software as well as implemented as feature in "Naantaani/Nani/Chief" is that questions could be asked with an automatic response. A Nani is backed by a Database which contains / stores / collect Articles / Sentences ... in form of a "Snippet" (see What is a Snippet) which will be feedbacked to a rquestor by entering a trigger word or combination (specified by the Nani) Scenarios: You could build up your own - Sharable knowledgebase (e.g. Wiki) - Help replies - Introductional purposes - ... At the point of developement and for testing reasons, all Tribe Apps contain the "Shaman" feature which can be easily enable/disabled in a Mesh (where messaging is enabled).

Configuration

Tribe Server Tribe Server

Tribe Server is the bridge/gateway to the internet. Tribe has two different ways to build up communal networks.
You can either by running a Tribe within a private (local) network environment and connect clients to a mesh by local discovery; the other way is to connect them via a so called "Rendezvous Service".
The sole job of Tribe Server is to connect members to a mesh. The rendezvous protocol is a network protocol that enables P2P network peers to find each other. No data is floating over or through the server.
Behind Mediator lays the excellent work from xxx, the devs of MonaServer. Mediator is utilizing the rendezvous service of MonaServer. MonaServer itself is a full blown server with following capabilities:
which consumes minimal server bandwidth and system resources.
MonaServer is a lightweight web and media server customizable by LUA script applications. MonaServer supports currently following protocols: HTTP(TLS) with a rendez-vous extension (cmd RDV) to meet peers together (e.g. SDP exchange for WebRTC) WebSocket(TLS) STUN RTMP(E) RTMFP SRT RTP, RTSP (in progress...) MonaServer supports advanced features for the following media containers: MP4 FLV, F4V TS HLS ADTS, AAC, MP3 SubRip, VTT Mona

Ias Ias

Ias is the dedicated app for creating interactive snippets. Creating Interactive Snippets is an exclusive feature of Nani. It could be helpful to create snippets while still being able taking care of your other tribe activities. For more details on interactive Snippets please read the Interactive Snippet Feature

Colony Colony

Colony is the dedicated app for the locations feature. It allows you to create simple floor plans, points of interest or other meaningfull locations (fiktive or real locations) all together called location objects; while still interacting with your main Tribe app. After you are done you simple share your work in the backstage with your prefered Tribe app. In addition to the Locations feature, Colony allows you to ... not sure if we should restrict the Location feature. For more details about the Location Feature and its inside please refer to
Locations

Tribe Features By App

Feature / App
Chief Chief
Wanderer Wanderer
Elder Elders
Servant Servant
Shaman Shaman
Tribe Server Tribe Server
Ias Ias
Colony Colony
Create, Manage, Tribes and Lodges
Messaging
Broadcast
Sharing
Calls
Map
XDoc
Events
Backstage Sharing
Multiple Badges
Snippets
Themes

Tribe Apps by Operating System


Desktop = Linux, MacOS, Windows;
Mobile = Android, iOS;
All = Desktop, Mobile;
Note to Linux: Ubuntu only, at the moment.

App OS Remarks
Chief All Recommended: Desktop
Wanderer All Reduced feature set
Elder All Reduced feature set, Reduces UI
Servant All Damn it stinky YenZi
Shaman All Recommended: Desktop
Tribe Server Desktop
Ias All Recommended: Desktop
Colony All Recommended: Desktop

Tribe Explained


Technical information

Encrypting a direct routed message

A private message will be encrypted by: Message content will be encrypted by a symetrical block algorithm called Blowfish

FAQ

General Questions

Communicating is the base of forming a working group. The Tribe Applications provide such a functionall. Furthermore, Tribe provides besides messaging some additional features which might could help dealing with your ideas. Tribe is kept as abstract as possible and not build for a sole idea. Its up to your creativity what you are going to do with it.

I would say nothing ... but you could make it special.

My intention is it to keep it free and provide it as an open source project. Nevertheless, please check the donate page for more details and options.

No, Tribe is completely independent and does not connect to our Website. Furthermore we do not run any service other than a publicly accessible Tribe server.

Pre-Experimental means it is not yet ready as a complete solution. Some features are not fully implemented or integrated to go along with each other. Please read Status Page and Roadmap Page for more details.

It is also not suggested to install it but review the screenshots for each of the apps. See Documenation Page.

No, not at all. All these social Platforms and Chat Applications have their place, unique and powerful features.

First of all, we will never compete. As it is my intention I would like to provide the whole solution as open source and would be glad if others could either build their own solution or we grow together and make Tribe bigger.

Competing in terms of performance: No, even I've not tested Tribe in an active environment, Server or Hybrid solutions are probably unbeatable in regards of network performance.

Well, I think the mask pretty much reflects what Tribe is or it represents.
When you join a Tribe you are usually a stranger to the community at first, you hide behind a mask and do not fully expose yourself.
People knowing you, know what's behind that mask, others have to learn about you. Additionally, it might give someone the feeling of long time ago communities their tradions and the Elders knowledge ... going back in time and find your roots.

Tribe Questions

Local Discovery

For a technical understanding I would suggest you to visit a library and find a book about "Peer to Peer" which matches your learning or reading style.
Here I will just try to explain it in a way how the terms used within Tribe.

Peer A member of a group, also called a "Node” or "Client". A peer is a client that joins a group over the RTMFP protocol. A mesh network is a topology used to organize nodes into a network that can transmit data between nodes that are not in direct physical contact with each other. P2P on the other hand refers how endpoints talk to each other on the application layer, i.e. they connect to each other "directly" (abstracted over the underlying network layers of course) to exchange information. It contrasts with the client-server model, where a server would act as relay or storage for the data that clients read or write.

Group
A group is a collection of one or more RTMFP nodes who agree on certain parameters and capabilities. There is a path between every peer in a group that forms a peer-to-peer mesh. There may not be a direct connection between two peers, but there is a always a path through other peers. A group is also called a “peer group” an “RTMFP group” and a “NetGroup”. Tribe Server handles introducing a client to a group. The Tribe Apps handle peer communication within a group, organizing and optimizing a group for latency, and maintaining the full-connectedness of a group. The group maintains the connections between peers automatically. Once peers are fully meshed into a group, then they can pass data within the group. Data does not need to be sent to the server to be distributed to each client. Peers can share data such as audio, video, and any other data objects.

Mesh A NetGroup forms a Mesh and NetGroup. A Mesh is a group of clients formed into a PPP-Mesh

They are identical and used interchangable. A Client is a member of a Mesh

They are identical and used interchangably. A Client is a member of a Mesh

Each of the Tribe Apps allows you to create so called 'Profiles'. You can use different profiles for different Zwecke. e.g. create a profile for a specific Group of People e.g. Family tribes or create a more serious profile for company/business usage) Each Profile will remember the set of Tribes you are connecting. NOTE: Remember, each Badge is unique even you are connecting to a Tribe with different Devices, a Badge will still be unique. A Badge is a kind of an ID or Name Card how you can be identified within a Mesh. Each Badge has a unique id in form of a 36 long UUID ('00000000-0000-0000-0000-000000000000' for more details see UUID) A Badge contains following but not only information: - Unique ID, - Creation Date, - Modify Date (Whenever you make changes to your badge, that date will reflect the time of modification), - A color which appears in any of the meshes and could help for easier differentiation either by you or the other clients (Optional and decided by the Tribe Owner if displayed). That color is often uses as an first identificational property. - Display Name: That's the name as you appear in any of the meshes It is mandatory to provide a display name. - A public and a password protected private key for signing or / and enccrypting messages For easy sharing of your information you can add additional information to your Badge to make it available to share some details about you: - Personal Information (NOTE: these information will only be shared if you explicitely send it to someone): - Title - Gender - Firstname - Familyname - Birthday - Religion - ... - Other Information (NOTE: these information will only be shared if you explicitely send it to someone): - Url's e.g. your Webpage, Social Network Accounts ... you can typisieren your provided URL - ...

They are identical and used interchangably. A Client is a member of a Mesh

They are identical and used interchangably. A Client is a member of a Mesh