All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Commonside | My little Email Service
itzsenu
Member
Hey everyone,
Commonside is an non-profit, privacy-focused email service.
I'm starting with the LowEndTalk community.
Requirements to join
- Your LET account should be at least 6 months old.
- Your account should be active with genuine, non-spammy posts ( least 10 ).
- Newer members may still be accepted depending on their contributions to the community and their reason for requesting an account.
How to get an account
- Visit https://commonside.org/
- I'll randomly post invitation codes in the comments of this thread, so keep an eye out.
- Use an invitation code to submit your registration request.
- In the request reason, include a randomly generated 32-character string.
- Post the same 32-character string in the comments here so I can match your request with your LET account.
- Once your request is approved and your account is created, simply reply "Thanks" here so I know you've received access.
Things you should know
- Commonside is currently operated and maintained by me.
- The service is still in its early stages, so some features and improvements are still being developed.
- There is no SLA or guaranteed service lifetime, but I'll do my best to keep everything running.
- Losing both your password and recovery key means your account cannot be recovered by an administrator.
- Standard email is not end-to-end encrypted by default. I recommend using OpenPGP for sensitive communications.
- Abuse and spam are not tolerated. Please use Commonside for personal use only. Commercial use, bulk mailing, and spam are not allowed.
Community support
Commonside is entirely non profit and open to voluntary contributions from providers and LET members.
- Providers and members can contribute servers, storage, domains, networking resources, technical assistance, or anything else useful.
All contributed infrastructure will be operated and managed exclusively by me.
Contributors won't receive administrative access to the service or user accounts.Sponsored domains may be added as additional domains for email aliases. The primary Commonside domain will remain unchanged.
- Contributions can be temporary or long term, depending on what the contributor is willing to offer. Long term support is especially appreciated.
- Supporting providers and community members can be credited on the project website with their names or logos if they wish.
The reason I'm taking this approach is that cryptocurrency is restricted here. I'll try to find a way to accept crypto donations in the future, but for now, Commonside won't be accepting any financial donations.
The idea is to keep Commonside independent while allowing the community to help with the infrastructure and development.
Thanks to the LET community for making projects like this possible.
If you have any questions, suggestions, or feedback, feel free to comment.
Website: https://commonside.org/
Approved by @jbiloh
Comments
I'll be dropping invitation codes randomly in the comments, so keep an eye on the thread. I'll add more whenever possible, depending on available capacity.
If you're requesting an account, please include a random 32-character string in your request reason and post that same string here. This helps me match your request with your LET account. Once you've successfully registered and received your account, simply "Thanks" so I know everything worked.
Thanks everyone!
Sweet
nice wondered if you were ever gonna announce it
hmm
humm... Seems cool
Hehe, the admin gave approval a long time ago, but I was still working on the encryption. The previous method used server held keys with three custom encryption layers ( It was somewhat similar to the new one, but not exactly. I wanted to make it more secure than the current version, but it introduced more delays when sending and receiving emails. I also found that it could potentially be exploited, so I ended up changing the whole approach. ) . The new one gives each mailbox its own secp256r1 key, uses PBKDF2 for password based key derivation, and has a separate recovery code. The idea is to reduce how much access I have to users' stored emails and avoid keeping the keys directly on the server.
Of course, Incoming emails can still arrive in plaintext,
.
An email service with a 1Kb message limit could be interesting
@angstrom Could you move the thread to Offtopic? I think I accidentally posted it in the wrong category. I originally wanted it in Offtopic so it wouldn't be visible to people outside LET.
is there anything blocking the load of the page since load time is almost a second for a pretty simple homepage without js (GOOD!!!!)
Noice, itz senu
do you handle email outbound yourself?