mcc

joined 1 year ago
sorted by: new top controversial old
The Release Date and Key Features of Windows 12 Unveiled in c/[email protected]
[–] [email protected] 8 points 1 year ago

They meant it was going to be the final one worth installing

Mastodon thinks Lemmy’s privacy stinks. What say you? in c/[email protected]
[–] [email protected] 3 points 1 year ago (3 children)

I don't even understand why the OP calls this "Mastodon's" opinion. The link doesn't go to Mastodon. I think the parent post is being a bit of a troll honestly :( The criticisms at the link don't make sense, the person posting the link doesn't seem to think the criticisms are good, and they attribute the criticism to Mastodon while posting "Raddle". It's like they're only doing this to get everybody riled up

1
Bug report: @Waveform.social accounts not visible from Mastodon (waveform.social)
 

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!