Best Practices for Public Hubs

Tue, 05 Sep 2023 04:25:21 +0200

adminsforum@hubzilla.org

Scott M. Stolz schrieb den folgenden Beitrag Tue, 05 Sep 2023 04:25:18 +0200

Best Practices for Public Hubs

I am getting close to opening a public hub, and was wondering if there are any resources or advice for doing so.

The first public hub we open will be a content website, so most of the people will join to access the content and the local forums. We might even leave ActivityPub off during the launch to reduce the risk of abuse. But we still need a plan in place in advance.

Any resources or information would be appreciated.

show all 6 comments

Tue, 05 Sep 2023 22:07:41 +0200

Grouchy

grouchy@hub.grouchysysadmin.com

Write policies and stick to them. Make sure your users know the policies.

If you're in the USA, sign up as a DMCA agent. Also make sure you have a documented process for handling and reporting situations to NCMEC.

Have public, easily found contact information and respond to abuse reports.

Wed, 06 Sep 2023 08:52:47 +0200

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Grouchy

Have public, easily found contact information and respond to abuse reports.

This, by the way, should include your admin channel so that people can contact you through the Fediverse. E-mail is likely to be too tedious for mobile users who are the vast majority of Fediverse users nowadays.

Also, the admin channel must anyone who is authenticated to send it DMs.

Wed, 06 Sep 2023 12:06:54 +0200

Scott M. Stolz

scott@loves.tech

Okay, thank you, that is useful. I am also considering forming a separate limited liability company (LLC) for the public hubs as well.

Wed, 06 Sep 2023 18:57:27 +0200

Grouchy

grouchy@hub.grouchysysadmin.com

@Jupiter Rowland

This, by the way, should include your admin channel so that people can contact you through the Fediverse. E-mail is likely to be too tedious for mobile users who are the vast majority of Fediverse users nowadays.

Having a Fediverse contact point is a good idea. Especially for moderation or community management. That said, you definitely need an email. Abuse reports from third parties are almost always going to come that way.

@Scott M. Stolz

I am also considering forming a separate limited liability company (LLC) for the public hubs as well.

If you're taking money, this is a must. If it's free, a liability shield is still a good idea. Don't forget to get insurance too.

Wed, 06 Sep 2023 18:57:27 +0200

Grouchy

grouchy@hub.grouchysysadmin.com

@Jupiter Rowland

This, by the way, should include your admin channel so that people can contact you through the Fediverse. E-mail is likely to be too tedious for mobile users who are the vast majority of Fediverse users nowadays.

I am also considering forming a separate limited liability company (LLC) for the public hubs as well.

If you're taking money, this is a must. If it's free, a liability shield is still a good idea. Don't forget to get insurance too.

Fri, 08 Sep 2023 08:41:33 +0200

Scott M. Stolz

scott@loves.tech

@Grouchy

Having a Fediverse contact point is a good idea. Especially for moderation or community management. That said, you definitely need an email. Abuse reports from third parties are almost always going to come that way.

I have a ticket system set up and people can send email to that. Come to think of it, I probably should set up abuse@example.com for every domain that is a public hub or forums.

If you're taking money, this is a must. If it's free, a liability shield is still a good idea. Don't forget to get insurance too.

Good point about the insurance. At the very least, an umbrella policy would be the bare minimum you want. And they aren't too expensive.