@ok https://open.spotify.com/track/0WJtFOBSkPQrwTemKyCgeG

My previous PR for #Misskey was accepted a few weeks ago. It was a similar compatibility fix. I really appreciate when recent issues get prioritized, especially if they cover on-the-wire compatibility with other projects. Thanks @syuilo for your hard work, and good example of leadership.

https://github.com/misskey-dev/misskey/pull/17275

@evan @ok no. It takes a major resources over a long period of time to inflict the damage we have all suffered, and most have a fake reality beaten in to their skull, so they are oblivious.

@ok
What’s another way to express ‘Absolute Zero’?

@evan

@evan@cosocial.ca OK

@indyradio I don't that's @ok 's fault, though.

I had a problem with #Misskey and its handling of the `actor` property of activities. It wasn't handling a format for that property that is defined in the Activity Streams 2.0 spec. I changed my code to be compatible (be conservative in what you send, as the #PostelPrinciple suggests) and made a PR on the Misskey codebase to make sure it could handle that format in the future from other software (be liberal in what you accept). Let's hope it gets merged!

https://github.com/misskey-dev/misskey/pull/17340

@evan @ok no. the nazis seem to have won

So, I made some changes to #tagspub today, concentrating on interoperability with #misskey. I had a lot of fun setting up a Docker environment with a Misskey and a tags.pub and watching them chat across their imaginary network.

If you're a Misskey user, could you try following a tags.pub account like @misskey ? If you've tried before, and it's been stuck, make sure to cancel the follow and try again. Let me know how it goes!

@ok you OK?