Same. As an instance admin, I like to read other admins' experiences with new version updates and being aware of possible attacks/issues in the fediverse.
I got the email too but can’t install from TestFlight.
If apps are native, I think it makes sense. No one watches short videos from PC.
I will. I was asking from CPU power and price perspective though.
When I decided to try XMPP, I had to do a lot of research to decide which applications I should use for the server and client. I did not experience this in Matrix. And yes, I know Matrix is not stable. I am not against that. It's just easier to get on board.
If we told two people to use these two software independently, they would start using Matrix much more faster than XMPP. I think this is enough to call it uncomplicated.
Also, would you recommend Snikket server (or Prosody) for 1:1, group calls and screen sharing?
I don't want to defend Matrix. I agree that it is not stable and lightweight. However, I believe it is simpler than XMPP. Wanna set up a server? Synapse. Need a client? Element. The default softwares are easy for new users to discover.
Also, the fact that Matrix has a single protocol means that in theory all servers and clients can work with each other (Although I know we are far from that at the moment). It is much better than XMPP's XEPs in terms of simplicity.
It's not that I don't like XMPP. I want a stable, encrypted, federated messaging platform. However, in terms of money and motivation, Matrix seems to be closer to that right now.
way less complex
I don't agree with this.
Huge!
Ensuring that Unable To Decrypt (UTD) bugs never happen. Huge amounts of work has gone into this over the course of the year, especially via complement-crypto as a comprehensive end-to-end-test suite for both matrix-rust-sdk and matrix-js-sdk based Matrix clients. We are finally at the point where UTDs are so rare that most people simply never see them.
Of course not. There is no limit. I just gave it as an example.
I've been rewriting Lemmy Federate for the last 3 days and finally finished it. While there are no changes on the frontend, many things have changed behind the scenes.
Mbin support
After several requests, I have added Mbin support to Lemmy Federate. It is currently in experimental state. I may improve it in the coming days.
Currently, Lemmy-Mbin connection is off by default. You can enable it by activating the "cross software" option in the instance settings.
how it works?
Since Mbin has OAuth support, the tool creates the client with OAuth instead of creating a bot user directly. Theoretically, you should be able to activate the tool simply by creating a OAuth client from instance settings.
But unfortunately, I couldn't try it enough because I'm not an admin on an Mbin instance.
Federation mode option
I added this option for small/single user instances. If you select federation mode as seed only in the instance settings, your instance will not follow other instance communities, but other instances will follow your communities.
Although I am not a fan of this option, I think it will work for instances like under 100 users.
Here’s example settings page:
I still think it will not explode bandwidth and storage, but I can't argue because I don't have any valid evidence :)
The reason I say this is that communities take up a few bytes in the database and if there is no activity (post/comment), they don't use any bandwidth either.
However, I can't say anything about the organic /all tab argument. It's a matter of preference. Kind of funny one.
I need to register on bsky.app to log in. Where is the federation in this?
I prefer simplicity and using the first example but I'd be happy to hear other options. Here's a few examples:
HTTP/1.1 403 POST /endpoint
{ "message": "Unauthorized access" }
HTTP/1.1 403 POST /endpoint
Unauthorized access (no json)
HTTP/1.1 403 POST /endpoint
{ "error": "Unauthorized access" }
HTTP/1.1 403 POST /endpoint
{
"code": "UNAUTHORIZED",
"message": "Unauthorized access",
}
HTTP/1.1 200 (🤡) POST /endpoint
{
"error": true,
"message": "Unauthorized access",
}
HTTP/1.1 403 POST /endpoint
{
"status": 403,
"code": "UNAUTHORIZED",
"message": "Unauthorized access",
}
Or your own example.
view more: next ›
F 🫡