[META] The merger from lemmy.world has locked out k.bin members.

sgnl@lemmy.world to Android@lemdro.id – 76 points –

Is this being worked on/looked at? I ask since the post mentioned discussion was happening with the .id admins but I haven't seen any answers about whether that's a priority (it seems Lemdro.id is the one that needs to federate with k.bin).

Just kinda bummed since I use kbin the vast majority of this time.

72

You are viewing a single comment
View all commentsShow the parent comment

Once you've finished updating it, can you share the changes you made to your Nginx config? If the default references have issues with them, I'd like to make sure mine doesn't have the same problems.

sure! take a look at this issue: https://github.com/LemmyNet/lemmy-ansible/issues/106

It is likely yours is fixed if you deployed recently

You can test an instance like this.

Find a local user on the instance and get their page (https://instance.tld/u/username).

In linux:

curl -X GET -H 'Accept: application/activity+json,application/json' https://userlink

If the result is html they have not patched, if it is json, they have patched.

curl -X GET -H 'Accept: application/activity+json' https://userlink

Will return json all the time on all instances.

I patched my kbin instance to send just the latter until it's resolved everywhere.