Audience is added back with this PR: https://github.com/LemmyNet/lemmy/pull/6157
This is not possible with the way Lemmy is implemented, because each post belongs to exactly one community. This is not something we can realistically change. We are considering to show comments from different posts with the same url together, but that is controversial.
In any case NodeBB, Lemmy and Piefed are different platforms with different implementations and different users. So it makes sense that some features are implemented differently, or only available in a subset of platforms.
This will come with Lemmy 1.0
Going to respond from here, the other account was mainly because that post didnt federate to Lemmy.
You are right I removed
audiencebecause it wasnt really being used at the time. But it looks like that changed, and its part of the standard that I wrote after all. So I will have to add it back then.
@dessalines@lemmy.ml made various UI changes that seem controversial to me. Such as changing the theme colors or moving most post/comment actions from the action menu to the context menu. If you have strong opinions on the design it’s best to follow the repository on Github and comment in the issues or pull requests where these changes are made. Otherwise these may also get adjusted later during beta testing.
I live in Spain. The user donations alone would not be sufficient, but together with the money from NLnet it’s enough to pay the bills.
Of course I could earn much more money by working for a company. But I don’t like to be ordered around by a silly manager, be stuck in an office for 8 hours every day and get stressed working on a project I don’t care about. With Lemmy no one can tell me what I have to do, and it’s work that’s actually meaningful.
1·19 days agoHmm on lemmy.ml we dont have such a problem with RAM usage by Postgres. In our case total RAM usage is quite stable with 10 - 16 GB over the past month. Its also strange that restarting Lemmy would solve the problem, I would expect that you have to restart Postgres.
The list of popular communities is only loaded when a new instance is setup for the first time. For existing instances like slrpnk.net it wont be used at all.
has huge memory issues (ironically given that it is written in Rust) that the devs ignore since years,
What exactly do you mean by this? Did you report it on Github?
the next version will hardcode lemmy.ml as a source to pre-fetch popular communities
To be clear it uses the lemmy.ml api to get a list of most active communities. Most of these communities are not hosted on lemmy.ml, and the data looks almost identical to that from lemmyverse.net (more details).
The change only affects posts which were deleted by the creator and have at least one comment. If the post was removed by a mod or admin the behaviour remains unchanged, and only the creator as well as mods/admins can view it.
For comments there is no change. For posts, if you delete a post which has no comments it wont be visible to anyone else. If it has comments and you delete the post, then it will only be accessible by direct link but not via post listings on the community page or frontpage.
This is a known issue and will be fixed in Lemmy 1.0: https://github.com/LemmyNet/lemmy/issues/5210
7·24 days agoThe best channel is through the issue tracker, for example github.com/LemmyNet/lemmy-ui. In practice Im not sure how the UI could be changed to make this clearer. Do you have an idea, or an example how another website handles this?
This will be partially addressed in Lemmy 1.0 by making deleted posts and their comments viewable, but only by direct link (not via post listings).
In theory apps can do anything that the website can, but this app probably hasnt implemented the feature yet.
We always dream, but usually we cant remember the dreams. It helps to keep a dream journal, ie every morning directly after waking up, write down as much as you remember from last nights dreams (or instead talk about it with someone). Over time you will remember more and more details.
You are using Piefed but this community is only for help with Lemmy.
This is a problem with your instance (lemmy.org) so you will have to contact the admin.
The community id is currently not being logged but Im adding it: https://github.com/LemmyNet/lemmy/pull/6083
Its also possible that this error happens because the check is currently too strict:
Lemmy 1.0 is backwards compatible with the current API v3. You can try it here. This uses the API from our test instance at voyager.lemmy.ml which runs the latest alpha version.