Nope. lemy.lol. With only one l, peepo logo.
Frankly, I would prefer using Nautilus, VLC in a stable cosmic-comp. I believe the S76 team has strayed bit of the target by working on features that are not urgent (like Cosmic Edit, Cosmic MP). Still, it seems to be progressing pretty well.
I tried daily drive but could not continue due to some critical but minor issues. I will try it again when it is labeled as beta because I really like its speed and appearance.
Niche Communities won't be able to reach their true potential until lemmy adds a sort that takes engagement into account.
I agree that fediverse needs a personalized "explore" page in general. For example, this is the only plus feature of Bluesky over Mastodon (in terms of technology). It is obvious how big difference it makes.
I generally avoid the evil algorithms found on other social networks, but I hope we see that in Lemmy.
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 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 ›
TBH Toastify is not that awesome.