Just starting to see the benefits of our #thoughtworks instance

- Local timeline: find out what colleagues are up to
- Global timeline: Find out who colleagues are interacting with
- Domain as account verification (e.g. @mfowler )
- It's an onramp for corporate citizens otherwise tightly bound to enterprise SaaS
- Employees hosting software for each other is beautiful (hopefully sustainable, too)

Thank you @mheiber & @judeswae for keeping it going for years already now !

@kfleerko @mfowler @mheiber I think this also creates a sane relationship between employees, employer and social networks.

Currently, there's a blurry line when companies ask their employees to reshare official comms through their employee's personal profiles on IG, FB, etc.

Hosting your own corner of a federated social network creates a situation that benefits both the company and employees.

Especially, as with Mastodon, an employee can move their followers list along with them.

@judeswae @kfleerko @mfowler @mheiber agreed - I'm planning on maintaining both a thoughtworks account, for work specific community and content, and a personal account for everything else. I can always boost one on the other as well. Seems quite a nice option to have!
@ksietsma @judeswae @kfleerko @mfowler it’s what I’ve been doing since 5 years. It works quite well.
@kfleerko what happens when someone leaves TW? do they loose their account and forced (like email) or they can migrate their accounts elsewhere
@kfleerko the bottom question is do the people on that instance own their content ?
@roundcrisis Yes ! You can export all toots and other content, redirect to another profile or move followers over all together with any installation of Mastodon https://docs.joinmastodon.org/user/moving/
Moving or leaving accounts - Mastodon documentation

Take your information and do what you want with it.

@kfleerko @mfowler @mheiber @judeswae

Had a question about this yesterday - would love to see how we can defragment people silos

https://tane.codes/@tanepiper/109262680497570764

Tane Piper (@[email protected])

Is anyone running a private #Fediverse in #Enterprise? I realise it might be a controversial question on here, but I'm looking at how you reduce #silos at scale, fast without exposing beyond the firewall? Behind #sso is one option, but it's also ensuring nothing is pushed out - I guess you also have to lock down who they can connect with? I know it sounds antithetical to the #Fediverse but it might be a way to enable tool adoption in different environments? #thoughts ?

Tane's Fedeverse

@tanepiper @kfleerko @mfowler @mheiber As you found out, we run an "enterprise" Mastodon instance at #Thoughtworks. But if you want to call it part of the #fediverse, it can't be private, in my opinion.

If you are looking at posts that don't federate, there is a #Mastodon fork called #Hometown https://github.com/hometown-fork/hometown which allows you to do that.

I would discourage its use in an enterprise context. The risk of leaking info that should be internal only is too high, imo.

My 2 cents.

GitHub - hometown-fork/hometown: A supported fork of Mastodon that provides local posting and a wider range of content types.

A supported fork of Mastodon that provides local posting and a wider range of content types. - hometown-fork/hometown

GitHub

@judeswae @kfleerko @mfowler @mheiber

Thanks - yes it would have to be for low risk areas. Also wondering if we can build on top of APIs to support collaboration tools in other contexts that us it's threading and federation.

@tanepiper @kfleerko @mfowler @mheiber It's open source software, so I guess you can build on top of the API. But I gusss it depends on what you mean by collorative tools, etc.

@judeswae @kfleerko @mfowler @mheiber

#semanticWeb and #FOAF, the ability to connect to a data mesh a layer of people, org structure and roles, etc.

Imagine I push out a new design or idea and what to start gathering feedback on it asap

[[foaf]] - anagora.org

The Agora is a crowdsourced distributed knowledge graph: anagora.org.