@liaizon @pixelfed I understand where you're coming from, but the current UX is complicated and not to mention the issues people have with outdated or broken instances.

My goal is to make Pixelfed easier to join (and allow account migrations), and having a default instance seems like the best path forward.

That being said, if you're open to discussing alternatives to this, we should chat. I appreciate your support and would love for you to help steward a path forward!

Pixelfed isn't just me 😉

5
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
˗ˏˋ wakest ˎˊ˗

@dansup @pixelfed what about somesort of server covenant that general servers who want to be included in some sort of prominent placement could join and promise to be on the latest version and be checked to be fully functional and running at a desired speed. then the "default server" button could be randomized between trusted servers, reminiscent of the "im feeling lucky" button google used to have.

1
1y
Hirad

@dansup @liaizon @pixelfed
Many apps ask user about their interests at initial setup. Why not have that?
First page ask user to choose language, next their favorite topic. and then show a big sign up button for an instance that fits those answers. Its easy to understand and also not limited to just one instance.

0
1y
Mike Fraser

@dansup @liaizon @pixelfed Right now we have thecanadian.social (Mastodon) thecanadian.online (WordPress) and thecanadian.photos (intended Pixelfed). The strategy is to create a federated ecosystem under one banner. I don't mind you dumping users into a flagship instance as long as you don't mind us promoting our instance there and giving users an easy option to move.

0
1y
Christoffer B. Tallerås 🇧🇻

@dansup I'm glad that you are going this direction. Umbrella plattforms has their place, but it is wise to look towards what works for most people, and email being the most successfull ecosystem of this kind its very smart to learn from what made these email providers so useful to most people.

0
1y
Ambassador

@dansup @liaizon @pixelfed I think rather than a single default instance, have a pool of instances that are known to be open and accepting new users (could be opt-in I suppose), and round robin the instance suggested to new users from this pool?

It's a compromise approach, that should address the perceived difficulty of on-boarding, but also not end up with a single default instance like mastodon.social.

0
1y
Replies