@DavidBHimself @mastodonmigration @moiraSolarbird :flag_cascadia: @quillmatiqAnuj Ahooja @anewsocial The difference now is the difference between opt-in and opt-out. When there's an automatic opt-in, you're (pretty much by definition) pulling in users (especially NEW users) who may not fully understand the ramifications of the situation and what they're posting. I would submit that there are other issues too that come into play as the system moves from fully opt-in -- including potential conflicts between Mastodon and BS terms of service and content policies.

There is a parallel here to what happened when Google disastrously tried to integrate YT comments with G+ threads. I was working inside G during part of that period and it was quite the train wreck because the expectations of users in the two services were very much different.

@laurenLauren Weinstein
> There is a parallel here to what happened when Google disastrously tried to integrate YT comments with G+ threads

Difference here being that what's bridged is the fediverse () and the ATmosphere (), which are protocol-defined networks, not monolithic platforms. There is already a need to address different kinds of UX within each network. So bridging them doesn't introduce new UX problems to either.

@DavidBHimself @mastodonmigration @moiraSolarbird :flag_cascadia: @quillmatiqAnuj Ahooja @anewsocial

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.nzoss.nz/users/strypey/statuses/114775437070610143 on your instance and quote it. (Note that quoting is not supported in Mastodon.)