lgvwiki/en/orgs/mannchri/etc/whence/v/villagetel.md

50 lines
3.5 KiB
Markdown
Raw Normal View History

---
title: App Store
description: Les Grands Voisins proposes an App Store with Applications and Unique User Identifiers
2022-04-30 11:18:28 +02:00
published: false
date: 2022-07-15T12:00:18.777Z
tags:
editor: markdown
dateCreated: 2022-04-30T08:54:07.893Z
---
# App Store
This is the main telecommunications hub for Les Grands Voisins / A Good Village.
Here is the purpose. We want Les Grands Voisins to be a viable alternative for Neighbors on-line and in the real world with regard to shared ressoruces of any nature.
## village.tel
The domain village.tel may provide an app store in two ways. First, it offers a central app-store hub for Villagers. Second, it offers a base domain for user identification.
Users are identified as follows: "username@village.tel". Username is reputed as unique. username@village.tel is also a valid email address, although not the primary address of the user utilmately. The idea is to provide a unique identitiy to each Villager.
I have a better idea of a multilingual domain name other than village.tel, but village.tel will do for now.
## Email Configuration and username@village.tel coexistance
I may be puching things a little too far, but email configurations may or may not have some incidence with user identification with the identity village.tel. My thought is that each Villager must have a village.tel identity and may have other identities and accounts as well. There should be a link wetween the village.tel identity and the other accounts.
In practical terms, our current email setup allows for the following.
There are three levels of administration in our %software/mailcowemail :
1. Individual user self-administration
2. Autonomous email-server-level administration for one domain and a number of domain aliases
3. Administration of all autonomous email servers (that we can call super-admin)
The domain name village.tel has its own autonomous email server.
Here are notable characteristics of each autonomous email-domain server:
1. Each autonomous email-domain server has users as defined by a unique string of characters to the left of the @ in the email address.
2. All domain aliases of an email-domain server will deliver email to the same mailbox as defined by the user-identifier to the left of the at-sign (@) on the main-domain of the email-domain server.
3. Individual email aliases may cross autonomous email-domain servers.
2022-04-30 11:18:52 +02:00
4. Configuration of individual email addresses is easy simply by supplying username@example.com where "example.com" is the primary-domain on the autonomous email-domain server.
2022-04-30 11:22:37 +02:00
## Ease of Regular Email Configurations (lesgrandsvoisins.com, agoodvillage.com, etc)
2022-04-30 11:18:52 +02:00
Ease of use of the email servers is a primary consideration. If someone's main email is for example robert.graves@communitiness.com, that person is bes served with a username of robert.graves and an autonomous email server of communitiness.com. This would allow the simplest email setup for the client application use of robert.graves@communitiness.com. Effectively the end user would simply input the email address and the password. Autoconfigure would handle the rest.
I am currently wondering how to handle the email domains lesgrandsvoisins.com and agoodvillage.org. I prefer usernames to be a bit cryptic and uniform: using the first four letters of the first name followed by the first four letters of the last name. I am horrible with names and this is a way of separating individual identity with a village immatriculation. This pratice doesn't help with the email configuration where the email is the user identifier in and of itself.