@derralf https://github.com/lambadalambda/rustodon by @lain and https://codefloe.com/plamenu/plamenu by @lnkr

> This wasn't too hard, but to make social publishing truly accessible, I feel like the direction to go is handling the social aspects via the consuming application (Mastodon and friends) rather than forcing each publisher to reinvent the wheel. @wrlach@wrla.ch you might be interested in the work @django@social.coop is doing with the ActivityPub API Task Force. @api That's the exact kind of thing they'd want to make happen.

@strypey I think @sutty is a fork of Jekyll with an AP plugin, not sure it that counts

@schwim there's a divide here between people who want a big fedi vs small fedi. who want everyone here and who want lots of limitations on what they can stumble on or who can reply to them.imo that's about what we want this place to be. we cannot make it serve both interests well. trying to do this leads to posting options that confuse people and anger over bots that try to make hashtags more visible, for example.like with bridging AT/AP, these decisions are costing a lot of money/effort.

@evan@cosocial.ca what about non-mentioned replies? I guess it wouldn't be received then

@evan Thanks for continuing to work on this. I get a lot of notifications from tags.pub.

@greyarea Thanks a lot for reviewing it.Now that I understand the basics, it's time to explore more complex schemes with perfect forward secrecy. I'll probably start with MLS and its "decentralized" variants.

@wjmaggos CBOR is more difficult than JSON-LD.(AT-Protocol uses CBOR where ActivityPub uses JSON-LD.)