conduit
fdroiddata
conduit | fdroiddata | |
---|---|---|
18 | 132 | |
- | - | |
- | - | |
- | - | |
- | - | |
- | - |
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.
conduit
-
Advice for a small Matrix server
I'd like to suggest Conduit. I found it very easy to install and maintain. https://gitlab.com/famedly/conduit
-
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/).
- Matrix conduit server takes forever to join channels
-
Looking to deploy a Conduit Matrix server. Is it possible to make a server which does NOT require a domain?
To start, this will be strictly Non-Federated. Just a few friends will be using this. Here: https://gitlab.com/famedly/conduit/-/blob/next/DEPLOY.md is the documentation I am following. It tells me I must "use my server name", but what is this exactly? What do I put in there? Do I have to go out and buy a domain?
-
Instant Messaging: XMPP or Websocket
Either Tinode (https://github.com/tinode/chat) or Matrix Protocol (https://gitlab.com/famedly/conduit)
-
Planning to make a video on cool Rust apps focused on the end user. Make recommendations!
Matrix Protocol: Fractal (Client), Conduit (Server)
-
Discord-esk encrypted platform?
If self-hosting is an option then I'd say Matrix, you can try Conduit (server) and Elements(client). To simplify deployment you can refer to this repo.
-
anyone using rust in production? what do you do?
You can babble on and on about how its not how you do it, no one needs it, etc... But its a demonstrable need in this space and its caused me great pain trying to write applications that would be used by such people. It's even bit Conduit to the point they have 5+ DB backends coded in now that the user can choose between based on their local system setups.
-
Given my server's specs, can I handle Matrix/Synapse?
Give Conduit a try. It uses way less memory than Synapse. It is still in early stages but works great. I have been running one on a Pi4 for like a year, going great so far.
-
Is there an example app that uses Sled database in Rust?
There's a Rust implementation of a Matrix server that uses sled: https://gitlab.com/famedly/conduit/
fdroiddata
- F-Droid: WireGuard inclusion policy violation (auto-update w/o explicit consent)
- Proposal to relax in-app updater policy for Reproducable Build apps
-
Publishing to F-Droid
Fork this repository.
-
Help with ReactNative Reproducible builds in FDroid
For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183
- Amethyst an Android Nostr client removed from F-Droid
-
Gitlab pipeline - checkupdate stage failed
You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.
-
Google account deleted after 2 hours of Aurora
To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).
- Amethyst (nostr client) is not FOSS
-
difference between the various Osmand versions - and f-droid
OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400
-
How to discover new FOSS apps?
You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.
What are some alternatives?
Synapse - Synapse: Matrix homeserver written in Python/Twisted.
OsmAnd - OsmAnd
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
nextdns - NextDNS CLI client (DoH Proxy)
gomuks - A terminal based Matrix client written in Go.
adblock-rust - Brave's Rust-based adblock engine
matrix-rust-sdk - Matrix Client-Server SDK for Rust
Nebulo - Mirror of https://git.frostnerd.com/PublicAndroidApps/smokescreen. Feel free to contribute here as well.
fluffychat
OpenBoard - 100% foss keyboard based on AOSP, with no dependency on Google binaries, that respects your privacy.
matrix.to - A simple stateless privacy-protecting URL redirecting service for Matrix
Smart-AutoClicker - An open-source auto clicker on images for Android