this post was submitted on 11 Jun 2023
7 points (100.0% liked)

Waveform

31 readers
1 users here now

A place to talk about how we organise ourselves.

founded 1 year ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I just removed my CDN to be sure, so wait for DNS to propagate and test again if you can. The correct ip should be 31.201.5.235. Let's hope this isn't going to make my bandwidth cry ๐Ÿ˜…

[โ€“] [email protected] 1 points 1 year ago (1 children)

It's about 4 hours later which unless you set a weird TTL should be enough time for DNSโ€ฆ I just tried @[email protected] and @[email protected] from the mastodon.social search. Neither went through. So whatever the problem is maybe it wasn't the CDN. Honestly I would suggest turning your CDN back on that could get bad real quick if you don't!! LOL

I am sorry to have set off a wild goose chase, I guess at this point what I'd recommend is escalating to either the Lemmy or Mastodon devs to ask if they know why it's not working.

[โ€“] [email protected] 1 points 1 year ago

Alright, thanks for testing and troubleshooting with me. I will enable the CDN again.