Pictrs is only made for images (and videos), as the name implies. Supporting other types of files in pictrs wouldnt make much sense. This means that other file types would have to be stored by a different backend tool, or directly in Lemmy. As we are only two fulltime developers on Lemmy, we dont have the time or resources to work on this, and need to focus on the most popular features.
There is no way for admins or mods to modify user comments or impersonate users, except directly through the db which is unavoidable.
We had a very long discussion recently how vote privacy should be handled, and the current behaviour seems to be the best compromise.
Multi-communities is one of those popular features we are going to implement soon.
Hello,
Thanks for taking the time to respond
I believe that pict-rs does support
video files with sound
I believe it is only the default pict-rs of lemmy hosts that disables and auto-strips audio
video files and images under 1MB work just fine
I understand that big tech has forgotten about audio files, but a good way to think about them is that they are just video files without a video track.
As for preventing comment tempering, a public key in the user profile and storing a signature as metadata of the comment would make comment tampering more effort than they are worth to future /u/spezes
As for vote privacy, I understand the convenience aspect of users not being made aware that their votes are public. I object in principle to the UI hiding this fact for convenience. I was unable to further express this disagreement as the thread was locked when the final decision was taken.
As for multi-reddit style community aggregation, I have investigated, and unless the default behaviour will be to make all /c/books across all federated server aggregated in a single default view, then I believe they will not be effective as countering Lemmy’s current biggest problem, the super-centralisation of all communities in a single big server in a single big community. For all intents and purposes, posting anywhere BUT the biggest community, is an exercise in futility. And this gives the owner class of that specific server immense reddit-like leverage over that specific topic not just on that one server but over the entire lemmyverse for that specific community topic. It will take extreme misbehaviour by the moderators to get the users to migrate out of the “big community”. As we’ve seen with reddit’s ability to misbehave with effectively no backlash, we can expect the same dynamic to occur here in the future as lemmy grows.
I cannot overstate how important it is for the power of federation to counter the power of moderators, that the default view of /c/books MUST include all /c/books or all federated server as the DEFAULT view. Anything else hands over all power of cultural control of that topic over to the big /c/books community on the big server.
Pictrs is only made for images (and videos), as the name implies. Supporting other types of files in pictrs wouldnt make much sense. This means that other file types would have to be stored by a different backend tool, or directly in Lemmy. As we are only two fulltime developers on Lemmy, we dont have the time or resources to work on this, and need to focus on the most popular features.
There is no way for admins or mods to modify user comments or impersonate users, except directly through the db which is unavoidable.
We had a very long discussion recently how vote privacy should be handled, and the current behaviour seems to be the best compromise.
Multi-communities is one of those popular features we are going to implement soon.
Hello, Thanks for taking the time to respond I believe that pict-rs does support video files with sound
I believe it is only the default pict-rs of lemmy hosts that disables and auto-strips audio video files and images under 1MB work just fine
I understand that big tech has forgotten about audio files, but a good way to think about them is that they are just video files without a video track.
As for preventing comment tempering, a public key in the user profile and storing a signature as metadata of the comment would make comment tampering more effort than they are worth to future /u/spezes
As for vote privacy, I understand the convenience aspect of users not being made aware that their votes are public. I object in principle to the UI hiding this fact for convenience. I was unable to further express this disagreement as the thread was locked when the final decision was taken.
As for multi-reddit style community aggregation, I have investigated, and unless the default behaviour will be to make all /c/books across all federated server aggregated in a single default view, then I believe they will not be effective as countering Lemmy’s current biggest problem, the super-centralisation of all communities in a single big server in a single big community. For all intents and purposes, posting anywhere BUT the biggest community, is an exercise in futility. And this gives the owner class of that specific server immense reddit-like leverage over that specific topic not just on that one server but over the entire lemmyverse for that specific community topic. It will take extreme misbehaviour by the moderators to get the users to migrate out of the “big community”. As we’ve seen with reddit’s ability to misbehave with effectively no backlash, we can expect the same dynamic to occur here in the future as lemmy grows.
I cannot overstate how important it is for the power of federation to counter the power of moderators, that the default view of /c/books MUST include all /c/books or all federated server as the DEFAULT view. Anything else hands over all power of cultural control of that topic over to the big /c/books community on the big server.