From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Heads up: incompatible protocol changes, Android experiment
Date: Fri, 02 Sep 2022 16:51:42 +0200 [thread overview]
Message-ID: <87k06lvngh.wl-jch@irif.fr> (raw)
Hi,
I've made a few protocol changes; the goal is to avoid hardwiring the
server structure in the client.
1. The handshake message now contains a version string; if the client and
the server mismatch, you'll get a useful error message. For now, it's
just a warning, but it'll become a hard error in a future version.
(This is handled for you if you use protocol.js.)
2. The group name is now derived from the status file; this means that the
client no longer needs to parse the URL in order to determine the group
name.
(This is not handled by protocol.js, you need to parse .status.js yourself.)
3. The websocket endpoint is no longer hardwired in the client, it's
published in the status file.
(This is handled for you if you use protocol.js.)
4. The group location is now stored in the public-groups.json file,
the client no longer needs to construct a suitable URL itself.
The reason for that: I've been frustrated with the inability to do
screenshareing on mobile, so I've been toying with a native Android
client. If you're brave, you can find it at:
https://galene.org/galene.apk
Sorry for the size of the file, that's because it contains four versions
of the native WebRTC library (ARM, ARM64, x86, AMD64).
-- Juliusz
reply other threads:[~2022-09-02 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k06lvngh.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox