Small things like ‘Auto expand media’ being set to true, can have a huge impact on user retention rate.
The vast majority of people never open or change default settings in the social media they use.
When they try out Lemmy etc., and the defaults aren’t great a lot of them will have a bad User Experience and leave.
I’m a IT professional, and joined Lemmy a few months ago, the UX sucked, most of that could have been fixed by having good defaults in place.
I powered through, but I won’t recommend Lemmy to many of my friends or family because I know they will give up due to too much friction in finding the right settings and how things work.
For the Fediverse to succeed focus needs to be put on giving people a very smooth UX from first opening a app or page, to finding enjoyment seeing and engaging with content.
It seems like running a pictrs server is optional when running Lemmy. I'm trying to figure out if a given instance supports pictrs.
I see in the documentation for pictrs, there is a GET /healthz endpoint. However when I try to access https://lemmy.ml/pictrs/healthz for example it gives me a 404. Even tho I know that Lemmy.ml has a pictrs server.
What is the best way to determine if a Lemmy server has pictrs?
Lemmy RSS PyBot is a powerful Python bot that reads RSS feeds and posts new articles to your favorite Lemmy communities. - sv1sjp/lemmy-rss-pybot
Link Actions
Hello everyone! 🎉
I’ve created an RSS Feed Bot that automates sharing news in Lemmy and Fediverse channels, helping to keep Fediverse users better informed. The bot is written in Python3 and can easily run via Docker Compose.
I'm using lemmy-js-client for app development. I want to render comments in the nested form (like normal people do).
The problem is, the lemmy backend spits out comment lists in a fashion that is unfriendly for nested rendering. Why? It outputs comments whose paths are like follows (for example):
0.1.2.3.4
0.1.2.1
0.1.2.3.4.5
0.1.3.1.5
0.1
Let's say the limit that I've set here is 10. Many a times, the parent comments of the comments in the page are out of the page.
For example, let's say I asked lemmy for comments for a given post. It gives me an output like above. There are many children comments here on page 1 (like 0.1.2.1, 0.1.2.3.4 and so on). Their parent (0.1.2) is NOT on this page. It is on the page that follows.
Hence, I would need to do client side bs to get the correct parent comments.
What is your approach for doing the above?
This is what I have settled for now unfortunately. I fetch all the comments under a post and then convert them in my nested form. This
I’ve updated @[email protected] to remember the whole tree of comments when replying to you, so it can do follow-up responses. You still have to mention it on every message, though. Example in the comments.
I just implemented a user overview of mixed posts and comments, but I'm unsure how to do so while respecting sort (hot, new, old, etc.). Currently I merge the user's comments and posts into a list, then sort them all by timestamp.
Because sorting is handled on the server, and merging posts/comments happens after, I can't see how I can't respect sort and still merge the two sets. Does anyone have any pointers?
I expect a similar issue would arise for the unified inbox view also (replies, mentions, and private messages), although in that case there's less need to sort by anything other than recency.
EDIT: here's the relevant ts code in the official lemmy ui. it sorts by date if sort is new, which i already do, then otherwise it just sorts by "score".
I recall someone mentioning a way to do it through an ActivityPub “resolve object” endpoint (or something like that) but I couldn’t find anything on it again. #1101 will solve this, but how are you guys handling this in the meantime?
So I'm developing a mobile client using React Native, where I'm utilizing Lemmy's messaging functionality as well. This makes it extremely crucial to have notification support (including push notifications).
How are you guys dealing with this problem?
This is what I think an elegant solution could look like. We would need to achieve two things:
Bring back websockets only for notifications by directly changing lemmy server side code.
Find where the email notification code is at, and simply implement expo notifications there.
currently my client displays child comments/replies to a given comment based on a get-comments request and the sort arg. if a child comment is returned by such a request, it will be included as part of the tree, but otherwise not. it means the child is subject to sorting itself.
but what is needed is that if a parent comment is displayed/returned by request/sort arg, all its children should be also. that seems to me to be how the webUI works also.
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Note that the bots default upvote is not considered for the stats. Positive comments are those where there's more upvotes than downvotes, neutral ones are those where downvotes and upvotes are the same and negative are when the comment has more downvotes than upvotes.