

Right, fixed now.
Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.


Right, fixed now.
Opened an issue: https://github.com/LemmyNet/lemmy-ui/issues/4344
Thank you this is very helpful, I finally figured out why OAuth login was broken only for some users. See #4343 for details. If you try OAuth login on voyager again it should work now.

Consider using the fork by db0 which removes this stuff: https://github.com/db0/tesseract


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.


Do you think all European people are a hive mind like the Borg? There are many people here who followed the events in Ukraine from 2014. Especially the numerous ethnic Russians in Eastern Europe and Germany. However the mainstream media never reports about them. In many cases they were even criminalized for supporting Donbass and Russia.
If you only follow the news media, you will see what the European ruling class wants you to see and nothing more.


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.


If European people supported these things, there would be no need for censorship.


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.


FYI only donations via OpenCollective are used for lemmy.ml hosting (see the expenses). Other donation methods are purely to pay for development work.
Not that I know of, but I also haven’t tested Piefed nor followed the development closely.
Recently there was a case where federation of Piefed Feeds was incompatible with Multi-communities in the Lemmy dev version. It would have taken me a lot of boilerplate code to make these compatible, for little or no benefit. Rimu agreed to change it on the Piefed side instead, much easier.
A few days ago I read read about some blocking or hiding feature in Piefed that is incompatible with Lemmy. That might be inevitable if Lemmy simply doesn’t support that feature. In the end there will always be some degree of incompatibility on the Fediverse, because every software has very different priorities.
ActivityPub compatibility has never been a problem with Piefed, and in fact we are collaborating very well in private. Of course Lemmy doesnt yet support all the features that Piefed has, but thats not their fault.
Thats from the rate limit, it seems you already did a settings import recently. That can take a lot of resources so its limited to once every 24 hours by default. If the import didnt work last time try again a day later.
Did you edit docker-compose.yml with the new version number?