CoSocial Board Decision on Threads

Two weeks ago, the CoSocial board asked the membership to comment on the question of whether our Mastodon instance should pre-emptively defederate from the soon-to-be-released ActivityPub-enabled Meta community, Threads. The results are available under the hashtag #CoSocialMeta.

Only a few of the responses are in favour of pre-emptively defederating. The primary response is “wait and see”.

Based on this input, the board voted unanimously in favour of the following proposal: will not pre-emptively defederate from the Threads app fediverse instance by Meta. However, we authorise the Trust and Safety team to take all necessary steps to protect user safety on CoSocial.”

Our reasoning is this: CoSocial is a service that its members pay for. If the board and staff restrict that service in any way, it should be to improve the quality of the service for everyone.

We do block over 200 instances that have been set up intentionally for harassment and abuse, or that are so poorly managed that they are a haven for harassers and abusers. We think blocking those domains makes the experience of the fediverse better for all CoSocial members.

Until the Meta service is released, we won’t know what the impact will be on CoSocial members. Absent a very strong signal from our membership to do so, we should not preemptively block that server.

Individual CoSocial members will be able to block the domain. This should screen any incoming content from the Meta site for them, and keep anyone on the Meta site from following them.

First Operations Update

The board and core team leads meet most Tuesday evenings to move the co-op forward. Agenda items and team notes are gathered ahead of time and discussed live. We’re going to start publishing some basic updates around what we’re talking about and working on.

Special Topics

Blocking Meta’s new ActivityPub service

With talk of Meta joining, there are voices proposing to de-federate (a technical process with Mastodon to block connections for an entire server)

At this stage of the co-op, our approach is to solicit feedback from membership on whether we should de-federate, and then the board will vote next Tuesday. A server announcement has been posted, and we are encouraging members to provide feedback to the board by using the #CoSocialMeta tag.

Team Updates


Test Lemmy (Reddit clone) instance up at Early adopter members welcome to experiment, but ⚠️⚠️ currently undocumented and filled with bugs ⚠️⚠️. Follow #NewsCoSocial for updates, as well as the group.

Board previously approved a part-time sysadmin role, our first paid position. This will be a junior role, with only a few hours per month. First draft of a job description, to be posted next week.


First office hours / open working session hosted by Alka and Dawn. Tuesdays @ 4pm PST / 6pm CST / 7pm EST, watch for more posts and details.

Hosting some regular chat sessions on different topics. On deck: Tim Bray, next Wednesday June 28th, with the latest in hot fediverse topics, aka #HotFedi


Will be refreshing the info site here in the coming weeks. More content — and writers! — needed. Discussion on sharing basic info about the fediverse, both for new / prospective members, as well as for Canadian media who might be interested due to growing activity in the space such as Meta, Reddit, etc.

Want to help with comms, news, and documentation? Email


We have a bank account at VanCity! We’re still taking payments through OpenCollective, which has worked very well for us. Perhaps more important, we have cash on hand – member subscription fees, that’s all we collect – for many months of operations.

To-do: Review of OpenCollective setups, review of projected finances, updates from TechOps on hosting fees, and first paid role.

Trust & Safety

To schedule: a live review / tour of our test Lemmy instance. Moderation tools are very basic, manual block list.