In this case I was looking for the instance feddit.nu since I was trying to sync up subscriptions on the accounts I have. Try [email protected]. Previously I tried [email protected] and it still doesn’t show up no matter what I search for in the top-right magnifying glass next to the username but it has finally appeared in the magazine list now.
Thanks for testing for me. Very very strange. Must be specific to kbin.social? I’ll try to make an account on your instance tomorrow and check if it works from there.
Sure, you can do that. I think I have the answer though. Both sh.itjust.works and feddit.nu have the issue where they return html when they should return json if the Accept header isn’t a very specific string. There’s a patch for the nginx config to solve it available but it seems they’ve not applied it yet.
You can test any instance for this by doing the following.
Find a local user on the instance and get their page (https://instance.tld/u/username).
Find a linux (or any OS that has it) with curl installed and type the following:
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, and I’ve patched my kbin to use this Accept header until all are fixed.
Oh that makes sense, thank you for going above and beyond!
Is it worth contacting Ernest about implementing your fix for the main Kbin code for better compatibility or are most Lemmy instances likely to fix the issue so soon it’s not worth bothering him?
I have pull requests for other changes to do with federation. I have a branch with this change in, but I’ve so far not made it a PR because I didn’t consider we should need to change this, and also because there was a patch on Lemmy’s side already available. Lemmy.ml, lemmy.world, beehaw.org are all working correctly now for example.
But if this is going to go on for long, I may well turn it into a PR too and see what people think.
In this case I was looking for the instance feddit.nu since I was trying to sync up subscriptions on the accounts I have. Try [email protected]. Previously I tried [email protected] and it still doesn’t show up no matter what I search for in the top-right magnifying glass next to the username but it has finally appeared in the magazine list now.
Worked fine. First line of the returned info was “Senaste nytt om Lemmy-instansen Feddit.nu!”
https://kbin.life/m/[email protected] nothing there yet. In theory if you liked something over there it would arrive there though.
Very very strange. What did you put in the search bar? Exactly “[email protected]”? And can you see the user [email protected]?
Yes, exactly that. And posts have already started appearing in that magazine.
Also yes, I see that user. I think it was already cached because I see some comments from them show up too.
Thanks for testing for me. Very very strange. Must be specific to kbin.social? I’ll try to make an account on your instance tomorrow and check if it works from there.
Sure, you can do that. I think I have the answer though. Both sh.itjust.works and feddit.nu have the issue where they return html when they should return json if the Accept header isn’t a very specific string. There’s a patch for the nginx config to solve it available but it seems they’ve not applied it yet.
You can test any instance for this by doing the following.
Find a local user on the instance and get their page (https://instance.tld/u/username).
Find a linux (or any OS that has it) with curl installed and type the following:
curl -X GET -H 'Accept: application/activity+json,application/json' https://userlinkIf the result is html they have not patched, if it is json, they have patched.
curl -X GET -H 'Accept: application/activity+json' https://userlinkWill return json all the time on all instances, and I’ve patched my kbin to use this Accept header until all are fixed.
Oh that makes sense, thank you for going above and beyond!
Is it worth contacting Ernest about implementing your fix for the main Kbin code for better compatibility or are most Lemmy instances likely to fix the issue so soon it’s not worth bothering him?
I have pull requests for other changes to do with federation. I have a branch with this change in, but I’ve so far not made it a PR because I didn’t consider we should need to change this, and also because there was a patch on Lemmy’s side already available. Lemmy.ml, lemmy.world, beehaw.org are all working correctly now for example.
But if this is going to go on for long, I may well turn it into a PR too and see what people think.