Synapse VS matrix-doc

Beeper is just a Matrix server with a bunch of bridges from developer tulir with proprietary web and mobile clients. If you have technical prowess or just want to learn IT/sysadmin stuff, I highly recommend learning how to spin up your own synapse server. synapse is the name given to the server software itself that runs the Matrix protocol.

Fully open source server software

Or setup your own matrix instance (e.g. with a Synapse container) and run your own server. https://github.com/matrix-org/synapse

Where is it in the synapse Github repo?

I'm also following this official guide for reverse proxy: https://github.com/matrix-org/synapse/blob/develop/docs/reverse_proxy.md

Hey all, I have installed Synapse on my Unraid server using the official docker-compose and I can see the static page by going to myserver.local:8008, but I would like some help getting my Nginx Proxy Manager to proxy matrix at port 8448 **With my root domain, not a subdomain like matrix.example.com** and then have a .well-known that points both users and federation servers to port 8448. I don't know where the .well-known file would be proxied and for some reason trying to issue a cert for my example.com root gives an "internal error". Thanks in advance for any help.

Beeper is a Matrix server with a bunch of bridges from developer tulir. If you have technical prowess or just want to learn IT/sysadmin stuff, I highly recommend learning how to spin up your own synapse server. synapse is the name given to the server software itself that runs the Matrix protocol.

database: image: postgres restart: unless-stopped environment: POSTGRES_USER: ${POSTGRES_USER} POSTGRES_PASSWORD: ${POSTGRES_PASSWORD} POSTGRES_DB: ${POSTGRES_DATABASE} # ensure the database gets created correctly: https://github.com/matrix-org/synapse/blob/master/docs/postgres.md#set-up-database POSTGRES_INITDB_ARGS: --encoding=UTF-8 --lc-collate=C --lc-ctype=C volumes: - ./.files-postgres:/var/lib/postgresql/data

From my perspective, the really exciting thing about this that it works equally well in mobile web browsers as well as desktop web - clicking on a link on Mobile Safari should Do The Right Thing without having to install anything.

Moreover, because it's built on Matrix, MSC3401 (https://github.com/matrix-org/matrix-doc/blob/matthew/group-...) means that we'll finally have decentralised cascading video/voice conferences once the SFU (selective forwarding unit) component is added into the mix. So, for instance, users on the same homeserver will get their video feeds relayed locally with minimal latency... and then users on another remote homeserver will also get mixed locally with minimal latency, trunking the two together. If the link dies or one homeserver dies, the conference will keep going - i.e. precisely the same semantics as normal Matrix.

What metadata does Matrix protect? Encrypted state events still aren't a thing for example https://github.com/matrix-org/matrix-doc/pull/3414 This means that server admins know what groups a given account is a member of, private or not, and they also have a general idea of what the topic of said groups are, even if they're encrypted. This would be a problem for groups about sensitive personal medical issues, like a private HIV survivors or Alcoholics Anonymous group.

The protocol itself is flexible and can be changed through spec change proposals on their Github. They're currently working on implementing threads, and they recently implemented spaces, which functionally combine the concept of Discord servers and server folders. They can also be nested.

At the moment this only works with Jitsi. It will be implementet soon with MSC3401

Something we're trying to do about this on the Matrix side is MSC2716 (https://github.com/matrix-org/matrix-doc/blob/matthew/msc271...) - the ability to import archives of existing content into Matrix, and thus 'lock it open' and decentralise it for posterity: as long as one of the servers participating in that room stays alive (and the room is set up with infinite data retention, obviously) then the conversation will live on forever. (That MSC is also well worth a look for those interested in how Matrix works under the hood; MSC2716 was a surprisingly tricky problem to solve but it's basically finished now!).

Our first step will be to import all of Gitter's archives into Matrix - but we're then planning to add MSC2716 to all the existing Matrix bridges so that folks can use it to liberate chat history from Discord and Slack if desired, and avoid it getting paywalled/siloed/lost/held-hostage forever. We're also expecting to do USENET, mailing lists, forums, public IRC channels which have explicitly opted into logging... and generally archive as much possible in an open decentralised fashion, and ensure that gatekeepers can't lock up and blackhole info going forwards. After all, information longs to be free :)

by 'broken links' i guess you mean https://github.com/matrix-org/matrix-doc/issues/3628? it's a bug on the new spec website; we're working on it.

This is an accident of history and will eventually be corrected: https://github.com/matrix-org/matrix-doc/issues/2678.

It is certainly not intended that new features are unencrypted, but unfortunately sometimes it happens in order for features to get added sooner.

On the Matrix side we've been keeping a close eye on JMAP, which operates in a fairly similar space to our new 'sliding sync' protocol (https://github.com/matrix-org/matrix-doc/blob/kegan/sync-v3/...). We would love to adopt JSCalendar & JSContact in Matrix if they are good to go :)

The are working on it https://github.com/matrix-org/matrix-doc/pull/2716