Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Randomize the list of instances #45

Merged
merged 1 commit into from Oct 27, 2017
Merged

Randomize the list of instances #45

merged 1 commit into from Oct 27, 2017

Conversation

ghost
Copy link

@ghost ghost commented Sep 18, 2017

The list of instances is now some non-semantic order (physical position in the database?). It has better to be randomized.

@ghost
Copy link
Author

ghost commented Oct 9, 2017

It is not fair nor user friendly that the table of instances is now fixed ordered. Why always we have to see mastodon.xyz, awoo.space, social.tchncs.de and other sticky instances.

@Miaourt
Copy link

Miaourt commented Oct 9, 2017

might be cool to, like before, add the security/stability/longevity of each instance into account too. Seem to be gone rightnow :v
But it's more something @TheKinrar have to do in the backend of instances.social...

Not that it's isn't fair, but user wise, being catapulted into an instance ran by someone that don't give a shit if it close in a month, etc, might be harsh...

@TheKinrar
Copy link
Contributor

I'll work on that soon @Technowix, looks like a good idea :)

@Miaourt
Copy link

Miaourt commented Oct 9, 2017

After some tough might be better to have a list of "passable" instances, that get enought uptime / security / etc, and then randomize them ? :)

@TheKinrar
Copy link
Contributor

That's what I'm doing on the wizard in fact. Okay. :)

@ghost
Copy link
Author

ghost commented Oct 20, 2017

The sticky (top positioned) instances are not always stable nor user-friendly, because:

(5th) socially.constructed.space is now down.

(8th) social.diskseven.com is private.

(9th) social.gestaltzerfall.net is now down.

(10th) social.imirhil.fr is private.

I suppose that randomize is better (not the best) than the fixed order.

@Miaourt
Copy link

Miaourt commented Oct 20, 2017

Of course fixed is shit, but "filtered" might be better here

@Gargron Gargron merged commit 7082836 into mastodon:master Oct 27, 2017
@ghost
Copy link
Author

ghost commented Oct 28, 2017

😍

@ghost ghost deleted the patch-1 branch October 28, 2017 13:30
Gargron added a commit that referenced this pull request Nov 3, 2017
…ooltips

There is no UI indication that the instance list shows incomplete data,
so presenting a random sample can paint Mastodon in a bad light if all
of the results are really small instances. I revert it to show 500
non-random instances instead, excluding closed ones, since that result
is guaranteed to be more useful, until the UI of the list changes
@ghost ghost mentioned this pull request Nov 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants