Out of curiosity- what instances are y’all on - and why?

[catelli@social.vivaldi.net]

@Paulatics I went with Vivaldi. No pros or cons other than it is supported by the company that makes the Vivaldi browser. " fully funded by Vivaldi Technologies, an employee-owned company."

So... the Pro is, no drama. So far.

[kzurell@cosocial.ca]

@Paulatics @coop cosocial.ca 'cause it's a #coop and #canadian; moved from infosec.exchange which was job-relevant and managed by a security pro, but USian nevertheless.

[villapirorum@indieweb.social]

@Paulatics Hello,

indieweb.social
1. To stop participating in centralization around mastondon.social main instance
2. Because I trusted people from this instance
3. Because I adhere to indieweb principles

But that's not the only instance I'm in.
- Got a secondary one from omg.lol (because i'm part of its community)
- Got one on sharkey , because that was the only way to contact some people.
- (Ofc I don't count accounts on pixelfed etc.)

[kimberlyn@cosocial.ca]

@Paulatics

I’m on Cosocial.ca. It’s a co-op instance, hosted in Canada, where all members contribute to, and have ownership of, the instance. I’ve been here for a couple of years now, and I really appreciate the co-op model because it provides more financial stability, responsive moderation, and encourages all of us to contribute to the decisions that are made here. So lots of pros. Character limitation falls into the con category…but that forces me to be more concise.

[meadmin@qlub.social]

@Paulatics #Qlub ! Pour offrir une instance francophone aux québécois et héberger leurs données ici au Québec.

[westcoastmaven@mastodon.social]

@Paulatics I’m on Social. I wanted an instance that has a robust team of IT individuals behind it without being a corporate venture. (Social is a registered charity.) I also wanted it located in the EU which tends to have progressive consumer standards & protections.

[stefan@stefanbohacek.online]

@Paulatics I run my own Mastodon server.

The pros are that I have more control over my social media experience, I get to experiment a bit (I've brought down my server once or twice), and I'm unaffected by moderators of two servers not getting along and severing ties between the followers on their respective servers.

The cons are, well, I have to pay for the hosting. And after I'm gone, I'll take my server down with me, with all my posts.

Wait. Maybe the last one is a pro.

[biglinter@mastodon.social]

@Paulatics im on the first one ive found when i searched for mastodon.

dont have any favorites, it just works.

[renata@cosocial.ca]

@Paulatics @stephanie Cosocial.ca @coop
It’s a cooperative
It’s incredibly well organized - you pay the coop fee to join to keep things running, receive regular updates (and can participate) on decisions about how the instance is run. It feels right.
Also one of the key people is Activity Pub’s @evan
All canadian infrastructure

[df@s.dfaria.eu]

@Paulatics I’m using an instance I created myself, developed in pure PHP on a shared host.

Pros:
- It allows you to gain a deep understanding of how the #Fediverse works and just how fascinating this concept is.
- Complete sovereignty and control over your identity and data.
- No issues with moderators.

Cons:
- Because it is a personal and very small instance, synchronization with the entire Fediverse is imperfect and partial, meaning there is “thread fragmentation”.

[liaizon@social.wake.st]

@df @Paulatics you could implement conversation containers or some of the methods to make sure when you load a thread all the responses to that thread come in
https://codeberg.org/fediverse/fep/src/branch/main/fep/76ea/fep-76ea.md
https://socialhub.activitypub.rocks/t/fep-convergence-400e-7888-171b-conversation-containers-76ea/4669

[df@s.dfaria.eu]

@liaizon Thanks! That's helpful.