If there are still problems you should open a new issue. We cant leave issues open forever because they go stale and dont account for new features. By the way we are planning to implement multi-communities.

Thanks a lot for the donation! Weve added you to the “Gold Pressed Latinum” sponsors on join-lemmy.org.

Sounds like you are looking at the api tests then. There are also unit tests which you can run with ./scripts/test.sh. The database is a fundamental part of Lemmy, so its obviously required for many of the unit tests. It may be possible to mock the db, but that would be a lot of effort for very little benefit, and might even introduce additional bugs.

There is already an open PR for Oauth, though Im not sure whats the difference to LDAP. Regarding tests you must have looked in the wrong place, we have a couple hundred already. Docs are here.

Lemmy 0.19 supports authorized fetch when retrieving remote objects. Enforcing it for fetches from Lemmy would also not be hard. It doesn’t make much sense though as long as we don’t have private communities.

All of the fields should be defined in context. Which one do you think is missing?

The spec allows using plan JSON for Activitypub.

https://www.w3.org/TR/activitypub/

Downvotes federate as Dislike activity which are part of the standard. There are some nonstandard parts eg for locking posts distinguishing comments. But most platforms including Mastodon or Peertube have such custom fields.

There is already Sepiasearch specifically for Peertube.

There is no specific release date. It depends how much time we need to fix remaining bugs which are being reported.

Thats interesting because for me it feels just like before with Firefox. Also the yellow background for new comments is way too much.

Well there are some different ideas for implementing hashtags. One idea was that Lemmy could follow hashtags from Mastodon etc to display them in the corresponding community. The only way to receive these hashtag posts is by following the users who create them, but Lemmy doesnt support user following.

Another option would be that Lemmy adds hashtags to posts so that they are picked up by Mastodon etc, without Lemmy itself using hashtags. This is definitely doable, for example it would be very easy to automatically add hashtags based on the community name, so everything in /c/memes would have #memes hashtag. It would also be possible to configure the hashtags in community settings similar to this tagginator tool, but that would require more extensive changes.

A third option would be to add hashtags based on post tags, thats what db0 was discussing before and which I referenced with that comment. However we are still discussing how post tags should work as you can see from the issue and from the RFC.

So option two or three seem reasonable, but like you say none of the maintainers seem to give this much priority. So the only way this will get implemented is if someone else writes the code. Thats just the reality, complaining wont change anything.

There are countless feature requests for Lemmy, but we are only two fulltime devs. Our time is limited so we have to set some priorities, and no matter what we do, some people will always disagree with those priorities. And besides implementing new features we also have many other tasks like reviewing pull requests, or right now bug fixing to get already implemented changes out into production. The only way to implement more features faster is by having more developers. Either as volunteers, or by hiring people with donation money.

I think your proposal is reasonable. However it depends how exactly post tags will get implemented, which is still rather vague. I dont think it makes sense to implement federated hashtags before we have post tags in Lemmy figured out.

In any case your tool looks very useful as a stopgap, and can help to test how hashtag federation can work in practice.

You can ask in the Matrix dev chat.

The only thing to keep in mind with 0.19 versions is that they are meant to be used with 0.19 backend. This post has some info about supporting 0.18 and 0.19 from the same client, but Im not sure if lemmy-js-client supports that as lemmy-ui only needs to be compatible with a single backend version.

Alright I will post these updates to /c/announcements in the future.

lemmy-js-client already has versions for the latest Lemmy code. So you just need to upgrade to the latest version and adjust your code where necessary.

About your second point, there is !announcements@lemmy.ml where only Dessalines and I can post. We could post the updates there and you could follow the community via RSS feed to get notified.

Yes it includes community follows, saved posts, blocklists and profile data. Here you can see everything thats included:

https://github.com/LemmyNet/lemmy/blob/main/crates/apub/src/api/user_settings_backup.rs#L41-L60

Edit: I just noticed that instance blocks are missing from the export. Added here

Wikipedia completely slanders people it doesnt like. For example Daniele Ganser who helped to reveal Operation Gladio.

cc @dessalines@lemmy.ml