mcc

joined 2 years ago
sorted by: new top controversial old
where else in the fediverse do you hang/lurk/reside? in c/waveform@waveform.social
[–] mcc@waveform.social 1 points 2 years ago

I post on Mastodon at https://mastodon.social/@mcc … relevant to here I do a kind of daily music blog there, in the form of a single enormous thread where I post a new track from YouTube every day. Most of it is electronic/synth jam stuff…

The other Lemmy instance I follow besides this one is Beehaw, but so far it seems to be letting me post with my Waveform account there, so I haven't signed up for a Beehaw account proper.

The Release Date and Key Features of Windows 12 Unveiled in c/technology@beehaw.org
[–] mcc@waveform.social 10 points 2 years ago

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

Should we move to KBIN? in c/waveform@waveform.social
[–] mcc@waveform.social 1 points 2 years ago* (last edited 2 years ago)

Not completely true, I think :( I think you're right posts work that way, but not as far as I know users, and anyhow the point of a user is the ability to post. Your domain still holds all the waveform.social accounts, so if you shut down the domains, all the users become unusable. I would very much like to see this problem fixed…!

Looking for: creative coders, algorithm designers, generative musicians in c/waveform@waveform.social
[–] mcc@waveform.social 1 points 2 years ago* (last edited 2 years ago)

In short: Yes :)

I spent years composing music generated by simple C programs and then some years more making algorithmic A/V toys disguised as video games, and I am currently making a commercial video game where all the music is generated in realtime by PureData.

I got interested in eurorack primarily because I thought I could control everything DAWless by algorithmic voltage control from an Arduino or something. That project's actually been a total failure LOL

I think the places I'd recommend for this sort of thing RN are the forum https://llllllll.co/ and the various members of the highly inspirational Mastodon server https://merveilles.town/ , though the best discussions there require you to join so you can be a member of the local feed.

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 @mcc@waveform.social into the search box, it does not recognize @mcc@waveform.social 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/@megmac@treehouse.systems/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!