Bug report: @Waveform.social accounts not visible from Mastodon
Bug report: @Waveform.social accounts not visible from Mastodon
Hi. I am excited about waveform.social.
I already use have an account at mastodon.social, which is another ActivityPub application. In theory, Lemmy and Mastodon should be able to "see" each other. It should be possible to look up a Lemmy user or community from Mastodon, see the posts, and reply to them. This will be ugly in the interfaces but it is expected to work.
If I go to mastodon.social, and I type @[email protected] into the search box, it does not recognize @[email protected] as a Fediverse address.
This is not a problem I have with other Lemmy servers. Other Lemmy servers I can at minimum look up the users and see their profiles (sometimes I cannot see the posts without following first). This makes me believe it is not a problem with the Lemmy software. Also, the problem is not limited to mastodon.social. Users on other Mastodon servers see the same problem. So this makes me believe it is not a problem with mastodon.social's moderation setup.
In a discussion on mastodon.social, we came to the conclusion this problem may be (1) on waveform.social's end, and (2) due to your frontend caching/CDN/WAF setup. Of course edge caching is a good idea. But it appears you need to configure it a certain way to be compatible with Fediverse servers. As is, waveform.social might not even be fully compatible with other Lemmy servers.
Explanation thread: https://social.treehouse.systems/@megmac/110527459896730724
Thread related to waveform.social particularly: https://mastodon.social/@[email protected]/110527420111615988 (link goes to end)
The one sentence explanation is "The webfinger URL for a user needs to know how to accept the Accept: application/activity+json header."
I do not fully understand all of these issues (my Mastodon development has been in mobile clients only) and I don't know what your server-side setup looks like. If I am describing this wrong I apologize. All I know for sure is it does not work. If you can identify that the "no visibility" problem is happening at the side of Mastodon.social or the Mastodon software, I can go raise the issue at that end. I am good at pestering the Mastodon devs :)
Thanks!
Interesting, I have a CDN set up for sure. Let me share what I can see:
If you actually run
curl -v -H "Accept: application/activity+json" https://waveform.social/u/mccyou will get a proper json with type=PersonHowever if you try to access waveform.social over http (not https) I will force you to redirect to http. Is that what Meg means with a "html page"? (The response is a redirect with no content).
In short:
The bad request:
curl -H "Accept: application/activity+json" waveform.social/u/mccThe good request:
curl -H "Accept: application/activity+json" https://waveform.social/u/mccHey. I'm megmac over on treehouse.
I edited the post a bit since I did say http when I meant html in it, and the mastodon link-cleaning made hash of my curl command. It does appear to work correctly now using curl so I was probably doing something weird (I was trying a lot of different combos of different things to compare at the time).
Still, can't seem to see anything from waveform.social from treehouse. So maybe it's something else. Note, I'm not directly affiliated with treehouse in any way so I have no direct insight or anything. I do know there are other servers that have cdn stuff getting in the way (kbin.social was the main other one that I was looking at and is why I talked about cloudflare in that post).
@mcc another test