Following up on this thread: https://lemm.ee/post/58774156?scrollToComments=true , which was used to announce people that we were moving (similar to https://lemmy.world/post/24312613)

General feedback was negative.

Lessons learned: find a way to notify only subscribers

An admin told me that if this kind of action os coordinated with the community instance admins, they could consider sending a mass direct message, which could then also target only subscribers.

This would require direct database access.

For context, the previous experience was https://lemmy.world/post/24312613

Feedback there was

thanks, I’m sure I only shitposted one time here about football’s cultural atmosphere or game theory/sportsmanship in general.

Thank you for the heads up folks

As a lemm.ee user myself, I approve of this.

I saw the automod tag everybody, and that’s a really nice solution you’ve come up with

I’m also not subscribing to the new one b/c I’m starting to get annoyed with the notion that communities need to be consolidated. That’s not a discussion for this post, though.

  • Blaze (he/him) @lemmy.dbzer0.comOPEnglish
    3·
    2 days ago

    I don’t think the idea is wrong, but I think that the messages should have been direct messages to users that clearly explained why that individual user was receiving the message, plus whatever else you needed/wanted to say. I would have had more rigid criterion for inclusion, too. Subscribers, certainly, and perhaps people who have interacted with the community a minimum number of times within a limited time period. For me, 3 times in 3 months seems generous enough to cast that wide net while also not being overly-broad. So if I were executing this, I would have had the bot direct message people, and say “Hello, I’m a bot acting on the behalf of X community. You are receiving this message because you are a subscriber or have recently interacted with the community. We wanted to let you know that the community is moving! It can be found at Y.”

    From @[email protected]