element-ios
ircv3-ideas | element-ios | |
---|---|---|
2 | 11 | |
46 | 1,707 | |
- | 0.5% | |
10.0 | 9.4 | |
about 5 years ago | about 3 hours ago | |
Swift | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ircv3-ideas
-
Matrix 2.0: How we’re making Matrix go voom
> "At least as standard" how?
There are 8 people who vote on changes to the Matrix spec (the Spec Core Team), 7 of which are Element employees (including Matthew, Element's CEO). Element also controls the development of clients and servers used by the large majority of users in the public federation.
> A substantial portion of the IRC comunity is actively hostile to the IRCv3 extensions, and in some cases prefer incompatible implementations of the same functionality; Matrix has nothing like that going on.
But any IRC client will work fine on any IRC server, and they can connect to various servers with different implementations.
On Matrix, clients (generally) can only connect to one homeserver at a time; which forces them to converge on following exactly the same spec. And if your server differs ever so slightly from the other ones in how it implements some parts of the spec (room consensus), then it can be split-brained from the rest of the federation. Instead, changes to the room consensus are done by pushing new room versions, and each server implementation needs to explicitly support it or they can't join it. This means Synapse devs (which are a majority of Element employees) get to decide what room versions can get traction.
It is not uncommon for people in the Matrix community to complain about this and Element keeping specs in limbo, and PRs to the flagship clients being stuck in "design review tar".
> And there seem to be more visibly independent implementations of Matrix than IRCv3.
Clients, maybe, at least in the number of implementation. It's hard to find stats of this, but I feel that >95% of people in the public federation use Element even in tech-y rooms; IRC has a healthier mix of major clients (weechat, irssi, IRCCloud, Hexchat, KiwiIRC, The Lounge each have >5% of desktop/web users). But I admit that's just my very subjective point of view.
In terms of servers, Matrix has three open source ones as far as I know: Synapse (controlled by Element), Dendrite (controlled by Element, and almost on par with Synapse according to https://arewep2pyet.com/ ), and Conduit. Based on https://gitlab.com/famedly/conduit/-/milestones/3 , Conduit seems to be far from implementing the spec yet (eg. it doesn't seem to support leaving rooms or respecting history visibility).
> things like: server-side history extensions tended to mess up my client's history implementation (I'd end up with multiple copies of the same messages in my local logs, often with the wrong timestamps)
You can use https://ircv3.net/specs/extensions/message-ids to deduplicate them.
> And if you're in a conversation where people are using embedded gifs, then fundamentally you'll always be a second-class citizen if you're trying to participate in that with a client that can't display embedded gifs.
A conversation where people where people are using embedded gifs will exclude me regardless of client, because they are too distracting. At least on IRC I can expect people not to do it too much, and use words or emojis instead of reaction gifs.
> SSO access control; you just can't do that in a nice way if the client doesn't support it
That's a fair point; IRC is made by hobbyists more than companies, so that's not surprising. There is some discussion around it though: https://github.com/ircv3/ircv3-ideas/issues/74 and Sourcehut is sponsoring implementation (https://emersion.fr/blog/2022/irc-and-oauth2/).
- Ergo – modern IRC server written in Go
element-ios
-
Matrix 2.0: The Future of Matrix
There are quite a few issues that they've stopped fixing in the Element app in favor of doing it in Element X, the one I've been following is where the iOS app causes a breakage in E2EE when you use the share extension, so they just disabled the share extension entirely and said they'd fix in X - https://github.com/vector-im/element-ios/issues/7618
But X requires Sliding Sync on the server, which is still a separate service to run alongside the homeserver and doesn't have a stable API, much less a spec (?). I am increasingly disappointed with how centralized Matrix is becoming, since AFAIK there isn't really an alternate client close to the same level of quality as Element.
I probably would've made all of the same decisions myself though, so I don't blame them I'm just a bit disappointed in how it's shaking out.
-
Matrix 2.0: How we’re making Matrix go voom
Element X is an entirely new client written in Rust + Swift UI/Jetpack Compose (https://github.com/vector-im/element-x-ios and https://github.com/vector-im/element-x-android) which will eventually replace the legacy Element apps (https://github.com/vector-im/element-ios and https://github.com/vector-im/element-android).
The features already exist serverside; we're just working on getting them out of beta.
-
Matrix client Element's Spaces is out of beta
You're being downvoted, but I originally had the same question.
It's actually a native app. It's mostly Objective C, but increasingly written in Swift. https://github.com/vector-im/element-ios
There is clearly room for improvement, but apparently they just hired a handful of new iOS developers to work on it. Good things should be coming soon.
-
Newbie here. I have multiple accounts on Elements, each one with a different username and on a different server. Is there any way to easily switch accounts without having to sign out ?
afaik, there is no "official" way to do it: https://github.com/vector-im/element-ios/issues/590
-
Any intention on creating mobile apps?
Sure. Element for Android, iOS, and web
-
WhatsApp to move ahead with privacy update despite backlash
Every issue I had with Signal, and listed here, is solved.
One issue I have with the Element iOS client is that it doesn't respect system font sizing. So, for older relatives, that app can't be used. I put my mom on something called "Fluffy Chat" though, which does respect font sizes. If Element fixes that, I'll move her back again. It's kinda nice having multiple clients to choose from, though Element is by far the most polished.
https://github.com/vector-im/element-ios/issues/3245
-
Is there an IpadOS App for Beeper?
That lets me assume that they either have a restyled fork of Element, or are directly telling us to use Element.
-
Signal is having technical difficulties
Here’s the iOS pull request for example: https://github.com/vector-im/element-ios/pull/3890
-
WhatsApp Status to convince your family & friends to switch to Signal – an educational approach (EN & DE)
There's a GitHub issue mentioning the same domain, but it doesn't suggest it's used for verification
-
Slack Ongoing Connection Issues
4. While core functionality is both broken and undocumented, the maintainers announce rabbit hole features that no one asked for and seem very much like distractions, like their recently-announced microblogging view/client[4]
In short the Element maintainers have shown little interest in making the platform accessible to the people who need its differentiating features the most, and have prioritized the "mad science"/technical aspect of their platform at the expense of the human element (end-users and operators).
It'd be cool if Element used their resources to hire some UX folks and community advocates whose sole focus is addressing the horrid accessibility of their platform. I think most users would rather see that than further "mad science".
[1] https://github.com/vector-im/element-ios/issues/3762
What are some alternatives?
The Lounge - 💬 Modern, responsive, cross-platform, self-hosted web IRC client
Ferdi - Ferdi is a free and opensource all-in-one desktop app that helps you organize how you use your favourite apps
element-x-android - Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose
hydrogen-web - Lightweight matrix client with legacy and mobile browser support
convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser
whatsapp-viewer - Small tool to display chats from the Android msgstore.db database (crypt12)
znc-push - Push notification service module for ZNC
element-android - A glossy Matrix collaboration client for Android.
element-meta - Shared/meta documentation and project artefacts for Element clients
mnm - mnm implements TMTP protocol. Let Internet sites message members directly, instead of unreliable, insecure email. Contributors welcome! (Server)
ircv3-specifications - IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
Mumble - Mumble is an open-source, low-latency, high quality voice chat software.