Lemmy maintainer. Interested in politics, video games, and many other things.
The Activitypub standard doesnt mandate any specific properties, not the title and not even the content which Mastodon sends. Thats one problem with Activitypub, you can send almost anything you want and its technically valid (even if no other platform can handle it). However the presence or lack of a title isnt really related to groups.
In addition to what @Austin_Skeldon@lemmy.ml says, another problem is that each software prefers to implement things in their own way, and not in the way that would be most compatible with other software. This is partly the fault of Activitypub, because its such a generic protocol that the same information can usually be represented in many different ways.
Another big problem is funding and thus developer time. Only few devs are paid to work on Fediverse software, and its not enough to keep up with all the work. So compromises have to be made, and often a nice user interface or other features are seen as more important than perfect federation.
All that said, I imagine the area that China is concerned with would be AI generated content passed off as news. You can easily generate deepfake video of a politician for example, and having rules to prevent such a video being passed around as real seems prudent.
The solution to that is verifying sources and cross-referencing to make sure that its actually real. It has been possible for a very long time to edit images and videos in a way that appears real, AI just makes the process faster.
Content on stack exchange is licensed under creative commons, so in a sense they are encouraging others to reuse it.
You can make a post to ask for a dev in !lemmy@lemmy.ml, maybe also on Matrix and in the rtl Github issue.
That sounds great. I hope you can find a developer who has some experience with open source, because many of these changes should be merged into Lemmy directly. Especially RTL support (or rather bidi) has been requested by many people. In fact there is already an RTL fork of lemmy-ui which could help you get started.
The other changes you mention could also be merged directly into lemmy-ui (except the homepage redesign i guess). Then others can also benefit from them, and it would be much easier for you to upgrade to new Lemmy versions. I suggest you open issues to discuss these changes (or look for existing issues). You can also join the Lemmy Dev Matrix chat.
Yes I banned that user, because he consistently broke the site rules, and even kept breaking them after receiving a one week ban. Its really simple, if you dont follow the rules there will be consequences, if not other users will also be encouraged to imitate such bad behaviour.
The way rules work is pretty simple. Whenever you post in a community ending in @lemmy.ml
, you are a guest on that instance and need to follow the rules in the sidebar, or face the consequences.
Other admins also didnt see any rule violations in the comments you shared above. We simply dont have a rule against promoting Lemmy instances, in fact we encourage it because thats the best way for Lemmy to grow. If you have a problem with other instances, I suggest you talk to the admins directly, or alternatively block the instances so content from there wont be visible at all to Lemmygrad users.
Reports work in a very basic way for now. Basically they are sent to all mods of the community, and to instance admins. If any one of them decides to resolve the report, others will generally not see it anymore. Also, the action of resolving a report isnt federated at all. So basically, a report needs to resolved once on each instance. Here is an issue about improving reports, feel free to add suggestions.
I would say that the comments you mention are simply subjective views of these two individuals. You might not agree with those views, but calling it lying seems exaggerated. I also dont understand how you can hold the entire instances responsible for actions of individual users. In any case, I will discuss this with our admin team.
So you have the same approach of generating a title from the post body. Only you do it on the frontend and not the backend. In Lemmy that might be a bit complicated because the body is already optional, and we would have to somehow encode that either title or body must be set (or both).