Human Web CollectiveCursed hack to fix Mastodon-Threadiverse communication
submitted by
julianIf I post something to a remote community, Mastodon people reply directly to me, and it doesn’t make it to the remote community. 👎
If I snuck in a mention to the community (but not in text), Mastodon would prefill the community mention and it would propagate correctly. đź‘Ť
Tell me this is a bad idea…….
NodeBB now sneaks in a mention to the category/community, and this gets pre-filled in the Mastodon composer.
I tested it against piefed’s crust instance, and the response from Mastodon to my post on NodeBB successfully made its way to crust for distribution :tada:
@rimu@piefed.social
@julian thanks, i hate it
i mean, i get it... but i hate it xD
i would rather mastodon fixed this in mastodon, but i wouldn't blame you if you did. mainly, mastodon should use to/cc/audience when composing a post, not tag.
we have github.com/mastodon/mastodon/i which is the inverse (receiving, not posting). i just filed github.com/mastodon/mastodon/i for the other direction (posting, not receiving)
@trwnh@mastodon.social oooh that’s interesting. I actually commented on the former.
But I am realizing now that NodeBB actually explicitly addresses quite a few people because we try to keep everybody in the loop.
Responding to a topic with hundreds of posts could mean a Note object with hundreds of individual users addressed in cc.
Perhaps it’s wiser to not assume “addressed? generate notification.”, and instead have configurable notifications based on thread/context participation.
Have you tried putting things into the
toorcc?Mm I believe the community is already addressed. Mastodon doesn’t prepopulate the mention in a reply unless it is explicitly in the AP object.