Welcome to Lemmy!1

This looks very good, welcome :)

Gute Idee, hab den user-agent eben hinzugefügt.

Cool! Ich hab übrigens die letzten Tage ein paar Verbesserungen am crawler gemacht, kannst du dir mal anschauen, und mir sagen was du davon hältst. Oder auch falls du irgendwelche bugs oder feature requests hast.

Lemmy only mirrors text, which takes almost no space at all. What does take a lot of space is media, so mirroring that can fill up your disk really fast. Inthat case, it is necessary to delete old, cached media which can easily be automated.

Good to know. But Lemmy is open source, so they have the same right to use it as everyone else.

I think this makes a lot of sense for the local and federated feeds. In fact i opened a very similar issue recently, but only regarding posts from communities. It should be pretty easy to implement the same logic for users as well.

Sure, following hashtags can be done locally on an instance, but its not possible over the activitypub protocol. So it only makes sense if you follow users, and then show their posts with a hashtag as a kind of local search.

There is no previous work on Peertube compatibility, it just happens to use Groups for its channels, which Lemmy also uses for communities. Lemmy cant handle videos, but i might look into that.

Subscribing to hashtags doesnt really make sense. Activitypub groups (which Lemmy uses for communities) work by following an actor, and it then sends all new items to the follower. On the contrary, hashtags are displayed simply by taking all locally known posts which contain that hashtag. There is no way to follow anyone to get all new items for that hashtag, and no way to have moderators or a description for the hashtag, like we have for communities. Its just a very simple and primitive implementation that doesnt work with the data structures that Lemmy uses.

You’re welcome :)

You are right, this is a problem in Lemmy. Just fixed it.

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

This is a problem with Mastodon, as i described here. It also existed in the initial Lemmy release, but back then you generally replied to comments from lemmy.ml users in lemmy.ml communities, so everything looked fine.

Did you install manually? Then you need to ensure that the ports for lemmy and lemmy-ui are set correctly in nginx config. You also need to apply changes with nginx -s reload

Done.

FYI mentions arent implemented for posts, only comments. So they wont get notified from this.

You have to do it through the database.

Go to the original instance where the community is hosted, it has the total subscriber count. Or use command line: curl -H 'Accept: application/activity+json' https://lemmy.ml/c/lemmy_support/followers | jq .totalItems

As a workaround you can share the link via another instance. You just need to take the fedilink of the item post/comment you want to share, pick an instance from join-lemmy.org/instances, and paste it in the search there.

Wow i had no idea. Looks like it could easily take a day to install with all those steps.