22
Yeah that would work. I also recommend you to check Lemmy Federate.
Allow list is explicit. If you allow at least one instance, all others will be blocked. You only allowed the following instances:
- lemmy.world
- sh.itjust.works
- beehaw.org
- programming.dev
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.
84
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:
131
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.
It's been over for so long that it's almost forgotten, huh? Here's the announcement: https://beehaw.org/post/567170
As I remember, it was about open registration policy and poor moderation.
Do they need blockchain for it though?
Another reason to not use ccTLDs.
This got me. A little dangerous sentence to start post with 😄 I'm not a user from dbzer0, but I appreciate your work on Fediseer 🙏
All of those are replicated to all servers.
Now thats what inconvenient is.
tldr the tldr
Code base is shit. We’re not doing what we’re promising or any close of it. We’re probably going to bankrupt in a year or two.
view more: next ›
iso
joined 2 years ago
I’ve been waiting for this thanks 🙏