Likes were previously marked as public in federation messages. This obviously didnt make sense, so now they are marked as private.

FYI this will be fixed in Lemmy 0.17

I always thought that .ml was used simply because its free. But what do I know…

Looks like you are running the dev branch of lemmybb which requires Lemmy 0.17 (not released yet). For now you need to run lemmybb release 0.1.2.

Thank you i opened an issue.

https://github.com/LemmyNet/lemmy-ui/issues/897

It helps a lot to realize that we are not obligated to respond to anyones issue. Wee are providing a software for free, and if sonething cant get it working, thats their problem. They can just not use it, or pay someone for help. Just because I wrote some software doesnt mean I owe anyone an explanation how it works.

In this regard I think it will be helpful if we aggressively close any support requests on Github, and tell people to ask on Lemmy/Matrix, where other people can help them.

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

Could you show an example screenshot how that looks like? I cant really imagine it working in Lemmy.

Posts without title would completely break post listings in Lemmy.

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.

Direct link to the blog post: https://nolanlawson.com/2023/01/09/retiring-pinafore/

Not so good, because this would require a lot of customization options to fetch communities according to different criteria. I think this makes much more sense as an external tool, then it can have a config file or be forked for different behaviour.

Thanks, i updated the link.

Crossposts are only implemented in the frontend (using search afaik). The backend doesnt know anything about this concept and so cant federate it.

It would be pretty easy to write a bot which does this automatically. Problem is that you could easily end up with a lot of spam or other unwanted content.

The cross-posts for a given post are not federated. This means you will only see cross-posts in cases where you or someone else on your instance already follows the communities where it was posted. So they dont help for discovering content on a new instance.

You need to wait for Lemmy 0.17.0 for this to work.

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.

Doesnt look like this can be selfhosted.

Running checks on multiple services creates multiple points of failure, so if any one goes down, it takes time to investigate and fix that. So I dont see any benefit to this.

On this page you donation options. However renting a fast vps is generally very expensive, so selfhosting is much more cost effective. That needs some time and to setup and manage though. As we already host a number of different servers, it would be helpful if someone else could manage this one.

That looks good then, I will send you a pm.

Possible yes, but then we would be relying on a specific company (Microsoft) with no easy way to switch to another provider. And we would have to pay money to them if the free tier isnt enough. With drone.io we initially used their free cloud offering, and then seamlessly switched to a selfhosted instance. Now if we need more resources, any server can be used.

You can test it by installing Rust and running cargo install lemmy_server.

Maybe what youre looking for although it looks quite different: https://github.com/LemmyNet/lemmyBB

Pleroma doesnt support new HTTP signatures which Lemmy currently sends. This problem should be fixed in 0.17.0 when Lemmy uses an older HTTP signature version for backwards compatibility.

There are plenty of trolls on Lemmy as well, so this wouldnt solve anything.

Its exposed to the admins of instances where the involved users are registered. For example if @sally@mastodon.social sends a dm to @nelly@example.com, only the admins of mastodon.social and example.com can access it.

Afaik DMs on Twitter are also not encrypted, so moderators or other employees can view them. So the number of people who can view your DMs on Twitter is probably much higher (hundreds of employees) compared to Mastodon (a couple of server admins).

We have a selfhosted Gitea instance which is currently hosting mirrors of Lemmy repos. For now thats not ideal because everyone would have to create an account to open issues and contribute, and it could easily fill up with spam. Once Gitea federates it would definitely be a great option.

Bisher kann man Lemmy-Nutzern nicht folgen, weil die Funktionalität nicht implementiert ist. Deshalb wird es dauerhaft als “pending” angezeigt.

Mit Lemmy 0.17.0 das wir bald veröffentlichen wird es möglich sein, auch Usern zu folgen. Dann muss man allerdings erst entfolgen und dann neu folgen.

Das liegt wahrscheinlich am Rate limit, siehe https://github.com/LemmyNet/lemmy/issues/2612

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.

This is ridiculous, how would you even determine that a given image was created or edited with AI? And what about images that were generated with Photoshop, do they also require a watermark?

It seems very common with Twitter-like social media platforms (which includes Mastodon). In my experience it happens much less in forums or link aggregators.

Mastodon as a platform is really good at generating pointless drama from the most minor incidents.

Unfortunately thats a very common problem, lots of people consider Mastodon and Fediverse to be synonyms. Its probably because Mastodon is so much bigger than all the other Fediverse platforms, and its the first one that people hear about. I think over time they will also start getting to know the other projects.

Content on stack exchange is licensed under creative commons, so in a sense they are encouraging others to reuse it.

https://stackoverflow.com/help/licensing

They are currently implementing sitewide sticky posts in Lemmy, which is almost finished.

Federation with Pleroma is currently broken, because Lemmy sends HTTP Signatures in a newer, incompatible format. This will be fixed in 0.17