Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
microchat
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ale
microchat
Commits
07eafe05
Commit
07eafe05
authored
4 years ago
by
ale
Browse files
Options
Downloads
Patches
Plain Diff
Add a README
parent
ae4edf36
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+31
-0
31 additions, 0 deletions
README.md
with
31 additions
and
0 deletions
README.md
0 → 100644
+
31
−
0
View file @
07eafe05
microchat
===
An experimental minimalistic ephemeral web-based chat.
It is meant as a very quick way to exchange real-time messages with
somewhat-trusted parties, with a few peculiar characteristics:
*
no custom application required, it works on desktop and mobile with
just a web browser;
*
no user registration process, no connections to external identities
(emails) or any other form of long-term user identity;
*
based on a
*rendez-vous*
workflow, participants agree on a "secret"
beforehand, which in this case is the room name;
*
no logs, messages are not persisted in any form except in the
browser window of the participants: when it is closed, they're gone
-- no room history is kept for new participants.
There is no access control on rooms: if you know a room name, you can
join it. This is partially mitigated by making room membership
prominently visible.
The chat implements end-to-end encryption, primarily as a way to make
it safe against corporate proxies and such, and to avoid liabilities
for instance operators: participants still need to trust the instance
operator, as it may be serving a back-doored version of the
application.
From a forensic perspective, all it requires from the participant is
the usage of a browser "incognito" window, to avoid leaving the
instance name in the browser history.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment