Strange, I opened an issue: https://github.com/LemmyNet/lemmy/issues/6609

Okay in the browser dev tools open “Storage” tab and go to “Local Storage”. There should be an item oauth_state with a value like {"state":"xxx","oauth_provider_id":1,"redirect_uri":"https://voyager.lemmy.ml/oauth/callback","prev":"/","expires_at":1783389838355}. Sounds like one of those items is missing.

Request error while calling POST /oauth/authenticate with {“code”:“3ed55281d78996fe5c2f”,“oauth_provider_id”:1,“redirect_uri”:“https://voyager.lemmy.ml/oauth/callback”}

This must be the problem but I dont know what it means. Check the network tab in browser dev tools for that request, and see whats the response or why it failed.

Tried the Github signup just now and it worked fine. You approved the Lemmy login once it redirected to Github right? Maybe try going into your Github settings and removing Voyager entry, then try again. Also check the browser console for any errors. And try a different browser, or disabling privacy plugins.

We wiped the data on voyager at some point so your existing account is probably gone. You can just make a new account with the same name.

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

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 @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.