@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.

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

The 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).

https://github.com/LemmyNet/lemmy/pull/6057

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.

These logs are from the api, not from federation. So a client is trying to access posts and comments which dont exist. Is the Lemmy frontpage looking normal? Regarding federation, other instances would have marked your instance as dead by now. This should be reset automatically after a few days, or you can manually trigger it (eg unfollow and refollow remote communities).

I would also suggest you join the admin chat on Matrix to get more help: https://matrix.to/#/#lemmy-support-general:discuss.online

Por supuesto puedes hablar en Español por aquí.

It looks like Castopod is the main podcasting platform on the Fediverse. I had a quick look how it federates. Unlike Peertube it doesnt use groups, so it wont be possible to follow the podcasts from Lemmy. What you could do is make a Lemmy post with a direct link to the Castopod audio file so users can play it from Lemmy (that is after 1.0 is released with the audio player feature).

Sounds like an adoption of this bible text: “Put your sword back in its place,” Jesus said to him. “For all who draw the sword will die by the sword.” Basically a version of karma.

https://biblehub.com/matthew/26-52.htm

It seems like there was a badly behaved script or possibly an attack.

https://github.com/LemmyNet/lemmy/issues/6010

I had a video chat with them once, but afterwards they ignored me. So they are clearly not interested in giving us a grant.

Adding a new sort type is not a big deal, so dont worry about it. And a new admin setting for this would also require UI changes, so the new sort type is easier overall.

The current sort options calculate the rank for each post only from the data on that post (number of votes, creation time). Your suggested algorithm looks much more complicated than that, as it requires two iterations and needs to access data from multiple posts at once. Im not sure if this can really be implemented in a way thats performant enough for production use. Anyway feel free to open a pull request, then hopefully other contributors can help you to get it working.

Sounds interesting, though from your links it’s not clear to me how exactly it works. Depending on that it could make more sense to implement as a separate sort option, then each user could try and compare it to the existing sorts.

The proxied images will be refetched from the origin if they cant be found locally. There should also be a configurable maximum size for the image cache but I dont see it mentioned in the pictrs readme. So like Dessalines said you need to ask the developer directly.