If you want #SafeHarbour protections as an intermediary, not a publisher responsible for content, it's only fair that you behave as - and get regulated as - as #CommonCarrier. If you make any editorial decisions whatsoever about who and what can be transmitted through your system, you are behaving as a publisher and it's only fair that you get regulated as a publisher. That means you're legally responsible for all content transmitted through your system. Carrier or publisher, which is it?
Conversation
Notices
-
Strypey (strypey@mastodon.nzoss.nz)'s status on Sunday, 16-Dec-2018 23:27:24 EST Strypey
-
Strypey (strypey@mastodon.nzoss.nz)'s status on Sunday, 16-Dec-2018 23:29:57 EST Strypey
To give an example, the fediverse is a common carrier. The people who define federation protocols are not responsible for anything transmitted using them. Whereas any fediverse instance that does any kind of blocking of other instances, or moderation of users, is a publisher. So they are responsible for everything hosted on and transmitted through their instance. In summary, if you want the power, take the responsibility.
-