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 (12 children)

I just disabled the https redirect, does that fix anything?

[–] [email protected] 1 points 1 year ago (10 children)

In a little while I should be in a position to spelunk some logs from the other side and see if there's anything explaining what it's not seeing there.

[–] [email protected] 1 points 1 year ago (2 children)

Alright, do you want me to restore the https redirect before then or should I wait?

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I don't think http/https redirects are likely to be involved, so you should probably put that back (and the cdn too if you haven't for the sake of your bank balance)

[–] [email protected] 1 points 1 year ago

I will leave the CDN out for tonight, I need to go catch some sleep. I will check tomorrow to see if you found anything. 🤞

load more comments (7 replies)
load more comments (8 replies)