Yes with Activitypub federation you generally have to trust server admins with the data they handle (similar with private messages). Though I suppose it would be possible for communities to anonymize votes when announcing them to followers, then only the admin of the community’s instance could see who voted.

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

Thats a possibility, but it would get very verbose in case of a discussion with long comments. And then there would be cases like a user manually quoting something (so the same text might be quoted twice in a row), or having to exclude the automatic quote when the responded comment comes right before the current one.

I think this solution is preferable.

Yes thats exactly what i meant, though probably without the hover functionality.

Displaying comments in nested form would look very bad, i dont want to do that.

Another problem is that phpBB forums are always organized into hierarchical categories (example). To make it work properly, such categorization will have to be added to Lemmy (optional, could be disabled for instances that use lemmy-ui).

By the way, contributions to this project are very much welcome. It doesnt even require knowledge of Rust programming, many things can be improved simply by editing the HTML templates.

Auto-generating quotes is one possibility, though I dont like that it implies rewriting the comment text. It could also be ugly in case there is already a quote. Or there could be a text field which links to the comment being responded to.

Another option would be a config option which disables nested comments entirely (both over federation and api). That means lemmyBB users wouldnt get to see all comments.

It would be a pretty complex change, probably better to start with something smaller first. Anyway its always good to have more contributors :)

Yes that migrating the urls would be possible. Just needs someone to implement it, as always ;)

Cryptocurrency trading is like a speedrun of stock market trading.

Actually I tend to agree with @PP44@lemmy.ml. Maybe the problem you are describing could be better solved by having admins review new communities.

You can open an issue for this if you want.

It can be useful as a word seperator. If its a copy, instance admins can remove it if necessary. Also, it seems inconsistent to allow _ in community names, but not in usernames (if thats what you’re suggesting).

I suppose there could be options to crosspost as copy (current behaviour) or as link to the existing post (as requested here).

It should work fine. Feel free to open an issue to discuss the details.

Seems like a very useful project. You can add a link to it in the Lemmy docs if you want.

Btw instead of copy-pasting the structs from Lemmy into your project, you could pull them directly from crates.io. Disadvantage is that it will force you to pull in lot of dependencies that have to be compiled, but that could probably be avoided in the future by adding feature flags to Lemmy crates.

It would be possible to federate a list of all communities on a remote instance, so you could browse that. But probably only the community name and profile, fetching posts/comments could use a lot of resources.

This would quickly get complex, as it would require configuration options for instances to fetch from, fetch interval, number of communities to fetch each time, etc. At least for now i think its better to have an external tool. But it could be linked in the docs so other admins can easily find it.

I still have to check if the retrieved communities don’t get somehow deleted if they are never used (if nobody subscribes)

Communities will be stored forever, unless you manually go into the database and delete them. Even the delete buttons on the frontend only hide them.