Its unrelated, problem was from removing Host header in nginx.

deleted by creator

Right, 1.0 still needs some more months of development before it’s ready for production.

We are running a beta version on lemmy.ml right now. But it only has minor changes, I guess it should properly be called a release candidate too.

Why do you think that? We are actually running a beta version right now.

Edit: or do you mean testing 1.0 on lemmy.ml? There are still various changes needed before it’s ready for that.

Youre right, made a PR to fix that.

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

Okay Ive added it.

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.

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

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 @[email protected]

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.