Loomio

Social Coop is a company that claims to have acquired three Mastodon servers???

Richard Hull PublicSeen by 238

Item removed

Thomas Beckett

Maybe we should file a trademark application. Are we formally incorporated or still just an opencollective instance?

Sven Shipton

We are not. We have a fiscal sponsor but are otherwise an unincorporated association. I believe we should register as a cooperative society with the FCA. Happy to help with the efforts on this, though possibly the details should be handled by the legal working group or something?

Sven Shipton

Regarding a trademark application: where do we file it? Unlike copyright, trademarks aren't universal, and it would get pretty expensive to protect the name everywhere.

I do agree with this in principle though.

jonny

dang foiled by the fact that there's no way I'm putting my credit card into this webzone to look up more info

Josef Davies-Coates

I use throw away virtual one time card details for such things. I use Revolut app https://www.revolut.com/ , but there are other options out there too. Indeed, I think even Open Collective offer virtual cards for some collectives (I think at present just the collectives they host), powered by privacy.com last I read about it (but I think planning to connect with other providers too).

Jamie Gaehring

I think getting a trademark is a good idea, and I'd even suggest a trusted member could do it so sooner rather then later under their own name, then transfer it to a proper legal entity once we've cobbled one together.

To @Sven Shipton's point, I think it's probably wise to at least cover a couple jurisdictions where we have a sizable number of users, or hope to have users. The main risk, imo, is they stand-up a Mastodon server that is similar enough to social.coop that it confuses users who think they're joining our instance, whether that's intentional or not. If those users are in a location we have TM, it seems like it would lower that particular risk, but (obligatory) I am not a lawyer.

Sadly, I've known others in the FOSS community who've been forced to deal w/ TM issues. This is one resource I've found helpful in the past:

https://www.nolo.com/legal-encyclopedia/likelihood-confusion-how-do-you-determine-trademark-infringing.html

Item removed

Nathan Schneider

I know the folks behind Social Coop and they have agreed to stop using the name. (Also in this thread is a record that I have discussed Social.coop with them in the past.)

jonny

well, awesome. thanks for handling that. and that is uh a... revealing? approach to moderation?

jonny

Also what the heck kind of coincidence is that, just like Google those words and it would be clear there is already a thing named that.

Matt Noyes

@Nathan Schneider How solid is that commitment to change the name? Will they actually change it, or just not use it in their promotion?

Josh Davis

Yes, we need more than a text message confirmation.

Justin du Coeur

Suggestion that has come up in conversation: we should probably say somewhere publicly that we are not affiliated with "Social Coop Limited". A fair number of folks are freaked out by corporate buyouts on Mastodon, so there's conversation flying about the whole thing.

I don't know who would craft an official statement, or where we would put it -- just passing on the suggestion, which makes sense to me. Even if the company does change their name, the news reports aren't likely to be updated to reflect that.

jonny

could it be as simple as "we are not affiliated with Social Coop Ltd, the company that owns pawoo and jp?"

Justin du Coeur

Could be -- just not quite sure what the right way to go about it is.

Erik Moeller

Agreed. I would suggest a short post from the @SocialCoop@social.coop account, maybe something along these lines:

You may have read about an entity called "Social Coop Limited" acquiring a Japanese Mastodon instance. This entity has no relation whatsoever to social.coop. Due to the risk of confusion, we have reached out to them requesting a change of name.

social.coop is a co-operatively run Mastodon instance that was founded in 2017. Read more about us here: https://wiki.social.coop/home.html

Océane

Why overdoing Jonny's version? People don't come on Mastodon to be pointed to wiki pages. It makes sense for us because we socialize mainly on Loomio, AFAIU it Mastodon is both a co-owned personal microblog and coop advertising platform, and an excuse to put experience on our resumes and hang out here. But people want information to drop in their TLs, to be consumed effortlessly.

Erik Moeller

I'm fine with a short toot, but some context might be helpful, and I'm always in favor of pointing people to more information about who we are.

Who can actually post from the @SocialCoop@social.coop account though? @Nathan Schneider are you able to?

Sam Whited

I'm on call right now and can do that if you'd like; anyone else have comments on what we should say before I send it out? The above sounds fine to me.

Erik Moeller

That would be great, thanks @Sam Whited and happy holidays :)

Nick Sellen

Oh yeah, that's quite bad...! I fired off an email to press@crunchbase.com to tell them... (only email address I could find on their site in <1 minute...).

Josh Davis

I also just called Crunchbase out on Twitter with a link to our statement. Hopefully that does the trick.

Josh Davis

Second the suggestion for putting an emergency banner on the wiki.

Josh Davis

Update on this. I also contacted crunchbase and was told that all company listing are user-created and editable. So I made an account and edited our entry. So at least that is taken care of.

Josh Davis

I think we should make another toot from the admin account reporting that Suji Yan has agreed to change their name (because I wouldn't be surprised if he doesn't). I have a very, very difficult time believing that this was just a coincidence, given that Nathan had already discussed our group with them. My guess is that the name "confusion" was done intentionally, specifically to hook progressive types. It's not exactly a new tactic. Given that this is a crypto "entrepreneur" we're dealing with, we should expect that nothing is being done in good faith, imnsho.

Graham

This thread is publicly accessible.

Josh Davis

Um...not just for our members?

Matt Noyes

anyone who has the link, seems like @Richard Hull must have selected that option when starting the thread (I think they default to members only)

Richard Hull

No. I didn't deliberately make it public at all. I have no idea how that happened, and I have not shared the link anywhere or with anyone.

Matt Noyes

My mistake! I just checked and our default privacy setting for all threads is public.

Richard Hull

Phew! But that needs to be changed surely? I had believed it was private to members.

Matt Noyes

So, some of the subgroups are private to members, but any thread or poll by itself can be made open to "guests." We can change the main setting to "closed." I, too, had assumed that was the default setting...

Temperature check: should all Loomio threads be closed (non-public) by default?

proposal by Matt Noyes Closed Wed 28 Dec 2022 6:01PM

Outcome
by Matt Noyes

Sorry for the unclear wording; it seems clear that there is not a strong sentiment in favor of changing our Loomio settings, which is what I was curious about. Thanks for giving your opinions.

Just realized that the default setting for all threads is Public, which means anyone can see them. Should we change that to Closed, which makes threads accessible to people who have the direct link?

Results

Matt Noyes
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Many good points made, public by default seems fine if we make it clear to users.

Jonobie Ford
<span class="translation_missing" title="translation missing: en.poll_proposal_options.not sure what i think / aún no estoy seguro">Not Sure What I Think / Aún No Estoy Seguro</span>

I’m not sure I’m clear on what this means? Is it that our “local” feed is public by default? Or that replies to threads are public by default, or something else?

Bjorn Toft Madsen
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

One of the strong attractors of our Mastodon server is the open, social nature of our governance. I say we lean into this and keep things public. It will allow would-be members a better sense of what they would be joining as well.

Clayton Dewey
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

I use my account as a generally public one, so I like the default as is- public for all.

Scott McGerik
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Making the threads private doesn't seem to provide any benefit and would hinder non-instance members with discovering whether or not this instance is a good fit for them. I read several discussions on Loomio before applying for membership to social. coop.

Aaron GK
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Changing my vote. Saw at least one person say that seeing the democratic process in our loomio threads helped convince them to join. So, voting yes at this point.

Brian Vaughan
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

In general, I think it's best that policy discussions be public as much as possible. I can imagine circumstances when we might need a private discussion, but those should be rare, and we should create private threads only when those come up.

Jamie G
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Being able to read the public threads was a big factor in wanting to join, for me. The public discussions are an asset. Maybe it should be more clear to users that threads default to public if there are issues there.

Jeff Piestrak
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Like a lot of other folks, being able to browse and read threads here on Loomio and see the democratic processes at work played a part in my choosing to become a social.coop member. I think we should keep the default as public, while selectively making some threads closed as appropriate.

Jeff Forcier
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

I don't see any significant benefit to having Loomio threads be private, which to me says the various benefits of openness/transparency (as others have said, being able to observe historical community discussions/decisions before signing up was very nice as a prospective member) win out by default.

Sam Whited
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

Seems fine to let threads be visible; if there is something sensitive to discuss we can always make it private. The more important thing is that we make it clear (I had no idea threads were public).

Aaron Wolf
<span class="translation_missing" title="translation missing: en.poll_proposal_options.i have concerns / preocupado">I Have Concerns / Preocupado</span>

I think private should be opt-in, chosen when there's some reason for it