dessalines

Its kind of a bug; although the API for search can take in all those sort types, it actually can only use a few of them, so TopWeek gets turned into TopAll. This is because when searching for All types, many of them have no concept of TopWeek, like a search for users.

In lemmy 1.0 I'd like to fix this by showing a specific set of filters and sorts for the given searchable item type: https://github.com/LemmyNet/lemmy-ui/issues/3995

Only new. It's your inboxes rss feed.

We don't allow vibe-coding for lemmy, see here.

I don't know what this means, you'll have to use the search to find content.

One way you can do this is via RSS feeds. Go to the /inbox page on all your accounts, and add it to an RSS reader. You'll then get notifications for new items (at least as often as your RSS sync frequency).

This is finished but unreleased as part of lemmy 1.0 . You can test it on https://voyager.lemmy.ml/

lemmy.ml seems to have a fairly low send queue to kbin.earth, but lemmygrad was behind and picked up within the last day

See if its resolved now.

Zero to racism in less than a few hours

I'm not an expert, but I think the fact that you need to set a TARGET in anubis, IE, where does anubis send you after passing it, means that you do need separate anubis's for each site.

Lemmy has a separated UI and backend hosted on different ports, so its trivial for us to just only use anubis for the front end. We couldn't put it in front of everything due to apps also.

Yep, essentially the botPolicy.yaml there could be a collectively developed anubis config, based on what works best.

Thx! We've been doing a lot of work on it lately.

Plz open any issues or suggestions for improvements to https://github.com/LemmyNet/lemmy-ui/issues

That's a really long AI post that I'm not reading.

Most of these concerns are being alleviated by all the work @nutomic@lemmy.ml is putting into join-lemmy.org , which is our centralized onboarding site.

If you have suggestions there, you can open up issues on https://github.com/LemmyNet/joinlemmy-site

@nutomic@lemmy.ml brought up https://github.com/LemmyNet/lemmy/issues/5871 , which would at least be a way for communities to explicitly link to each other, and we could possibly create a superset of Subscribed.

In 1.0 there is the Suggested filter, where admins have a preset / chosen list of curated communities they like, and a way to view all the posts from them.

I'd rather not do complicated algorithms to try to figure out interest / community adjacency based on user activity, as this could get really complicated and also probably show things people don't want to see.

I totally agree that content discovery could be better, but I'd like it to be explicitly chosen by the user, rather than generated. So I think the best way is still just to go to the communities page, and click subscribe on anything that might potentially interest you.

This is what scares me more than anything, and why I want to reject requests to drive ppl to the larger instances.

The more decentralized, the healthier we are.

You can already just use the URL / link field to link to that album, and also choose a custom image if you like.

You can also just use the post markdown body to post a lot of pictures also.

No they don't use sql views, they're built using an in query (which we still have to see how performant that'll be, and is pretty much the same problem as subscribed communities, needing to sort and filter based off joined data)

You can see them in action here: https://github.com/LemmyNet/lemmy-ui/pull/3521

Multi-communities are already completed in the back-end, and front end will be done shortly.

Community post tags will be in 1.0 . The back end is done, and the front end is in my list of next 10 or so things to do.