Okay Ive added it.

Okay I’m adding that to the donation page on join-lemmy.org.

https://github.com/LemmyNet/joinlemmy-translations/pull/50

Found the problem, on 0.19 you have a very long displayname and 1.0 cant fetch your profile for that reason. So all federation with your account is broken. Made a PR to fix it.

Its intentional because not every post and comment needs to show that a user is admin or mod. Makes it difficult to participate in normal discussions as everything looks like “official” communication. Also the distinguish feature was barely being used.

Better integration with Mastodon or Pixelfed mainly needs to be done from their side, but it seems those projects are not interested. Are there any specific improvements you would like to see?

Thanks for donating!

These are working fine for me. Maybe theme reload is not working in your browser, try reloading the page.

If you don’t have a smartphone are you truly human? ^/s

Lemmy puts up full-page advertisements for donations but a lot of that funding goes to running Lemmy.ml and seemingly only very little to actual code development.

Please stop spreading misinformation. The server for lemmy.ml only costs ~70€ per month which is only 2% of the total donation amount (3336€). With Lemmy we care a lot about writing high-quality and bug-free code as well as offering a good user experience. All of that takes time to do well.

Edit: For your information, only donations via Opencollective pay for lemmy.ml hosting. All other donation methods are exclusively paying for developer salaries.

Checking now I also have one community pending, and another subscribed. Made a fix for private community permissions.

Which comment specifically? Dont see anything recent on voyager. For me follow from enterprise to voyager worked fine.

Yes pretty much. Its just that “featured” is for posts, and “distinguished” for comments.

Is that also RBlind theme? I made a fix for that now.

That will be done automatically once we update js client to use the latest backend structs, and then update lemmy-ui to use the latest js client.

cc @dessalines@lemmy.ml

Distinguish as moderator is only for comments, while feature is only for posts. Both of these are similar but different. I suppose we could rename “distinguish” to “feature” as well?

For mod actions there is a simple api response field can_mod, and its always false if the other user is a higher ranking mod or admin. We dont distinguish between can_remove, can_feature etc because that would get too complicated.

Opened an issue for RBlind themes, but darkly themes look just fine here. Any screenshots or more details?

https://github.com/LemmyNet/lemmy/blob/main/crates/db_schema/src/impls/local_user.rs#L68

Like I said, this is basically expected behaviour. Otherwise you would get an error every time you submit changes to user profile without changing any LocalUser value. For example only changing bio would throw an error because its stored in Person table, so LocalUser would have an empty update query. I suppose we could change it to explicitly check if every field is empty.

And making the whole settings import fail because of a single value thats too long also doesnt sound good.

Feel free to open an issue to discuss possible solutions, but its not a clear bug which can be easily fixed.

I changed the rate limit for imports to 10 per hour now.

Thats because a too long username will make the update query fail, but we are updating errors from that specific query. Otherwise there would be errors all the time from empty update queries. Not a big problem imo, making profile import from 0.19 work perfectly would be too much effort.

Here is the change to reduce max displayname length. As you can see existing names are truncated.

I went through all your replies in this thread (at least the ones in my notifications) and open issues or made fixes for them. Thanks for your effort! I hope you will do more testing once we publish the next beta version.

Makes sense, fixed that.

Wow I didnt think that there are still problems like this on the web. Will be difficult to fix as we dont use iOS devices. Do you know if there is any workaround?