matrix-doc VS eth-phishing-detect

Group voice and video calls are not E2EE, and use Jitsi, but this is expected to change with Native Group VoIP Signalling.

DMs in Matrix are always E2EE, and MSC3401: Native Group VoIP Signalling means there should be E2EE in group calls.

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.

The project is called MATRIX ABYSS, but their website is https://abyssmatrix.world. When I looked up https://matrixabyss.world/ there is an error saying that this website has been flagged for phishing, by metamask eth-phishing-detect. Super sus.

This was an issue with Metamask's fuzzy filtering, see here. The issue has been resolved, and it's been plenty of time for the change to propagate around. Not sure if you need to update your Metamask or clear your cache or something. Unfortunate that it's still causing trouble.

MetaMask already has a blacklist for phishing websites: https://github.com/MetaMask/eth-phishing-detect

Yea, no idea why: https://github.com/MetaMask/eth-phishing-detect/issues/7876

they added sudoswap to their fuzzy list https://github.com/MetaMask/eth-phishing-detect/pull/7633 and that caused issues with other domains with "swap" in the name

According to the code on https://github.com/MetaMask/eth-phishing-detect/blob/45ea5cf..., looks like that everything within Levenstein distance of 3 from whitelisted hosts (like "metamask.*") is blocked.

Metarank and Metamask have the distance of 3. I've made a ticket some time ago in their github repo (https://github.com/MetaMask/eth-phishing-detect/issues/6855), but it seems that it was lost in thousands of similar tickets.

Do you have an old version of Metamask? That site was accidentally picked up by a blacklist regex but was whitelisted again back in october - https://github.com/MetaMask/eth-phishing-detect/pull/5563