Wow this “policy” has 3700 lines in total. It must take a lot of time to create and maintain it. How does someone even find the time for that?

I tried to access some blocked users and communities via tesseract.dubvee.org and it simply shows a generic “Not Found” error. So this is impossible to figure out for the average user. Even for developers it would be hard to figure out if the JSON file was hidden a bit better.

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

At the moment I’m reading the “Book of the new Sun” series. Its quite confusing in the beginning, but with time it gets better and better. I like that it covers a lot of philosophical questions, while still being a fun fantasy story.

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.

I believe this is the right answer. Additionally, one character in CJK languages represents a single syllable, so you get less line breaks per word. For example the world “union” can be transliterated to Korean as 유니온. Writing that vertically takes 5 lines in English (one line per letter), but only 3 lines in Korean:

유 니 온

Open all the windows during night time when its cool, close windows and shutters during daytime. If you dont have shutters, put foil on the outside of the window, not inside. Also use a fan for air flow.

You can follow Lemmy users from Mastodon etc. But the outbox isnt even used by Mastodon, so we havent bothered to implement it properly yet.

if i open my own user profile from mastodon, it only shows me about half the posts that i actually make.

That is normal, its usually because no one on that instance follows your user profile specifically. Part of your posts are federated because someone is following a subset of the communities where you are posting.

Private communities in Lemmy only federate with approved users and their instances. So if you dont trust lemmy.xyz, simply dont approve any followers from that instance, then it will never receive any private content.

Good, I can fetch the community now from lemmy.ml and made a test comment.

That sentence is from the old covenant, which also requires animal sacrifice among other things. The entire old covenant is not binding for Christians anymore, since Jesus replaced it with the new covenant.

Your instance is not configured properly. curl -H 'Accept: application/activity+json' https://лемми.опенсорс.рус/c/rust_rus should return JSON data but it returns HTML. See the troubleshooting page and make sure you followed the setup instructions properly.

You can also get help via Matrix.

Normally Lemmy returns an error if activities cant be handled (eg instance is down). Then the sending instance keeps retrying until it is successful. But in this case its a bit different, and the sending looked successful.

Anyway I made a change to the federation library to add Host header automatically if missing, then this problem wont happen anymore in the future.

Old posts and comments will come in when we receive votes or replies for them. But missing votes won’t be federated.

I found it now, posts are coming in normally again.

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

Found the problem, I had commented out the Host header in nginx thinking it would not be necessary. Turns out I was wrong. Adding the header back in fixed the problem.

Big thanks for notifying about this!