This repository has been archived by the owner. It is now read-only.

Randomize the list of instances #45

Merged
merged 1 commit into from Oct 27, 2017

Conversation

Projects
None yet
4 participants
@hakaba-hitoyo
Contributor

hakaba-hitoyo 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.

@hakaba-hitoyo

This comment has been minimized.

Show comment
Hide comment
@hakaba-hitoyo

hakaba-hitoyo Oct 9, 2017

Contributor

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.

Contributor

hakaba-hitoyo 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.

@Technowix

This comment has been minimized.

Show comment
Hide comment
@Technowix

Technowix Oct 9, 2017

Contributor

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...

Contributor

Technowix 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

This comment has been minimized.

Show comment
Hide comment
@TheKinrar

TheKinrar Oct 9, 2017

Contributor

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

Contributor

TheKinrar commented Oct 9, 2017

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

@Technowix

This comment has been minimized.

Show comment
Hide comment
@Technowix

Technowix Oct 9, 2017

Contributor

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

Contributor

Technowix 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

This comment has been minimized.

Show comment
Hide comment
@TheKinrar

TheKinrar Oct 9, 2017

Contributor

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

Contributor

TheKinrar commented Oct 9, 2017

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

@hakaba-hitoyo

This comment has been minimized.

Show comment
Hide comment
@hakaba-hitoyo

hakaba-hitoyo Oct 20, 2017

Contributor

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.

Contributor

hakaba-hitoyo 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.

@Technowix

This comment has been minimized.

Show comment
Hide comment
@Technowix

Technowix Oct 20, 2017

Contributor

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

Contributor

Technowix commented Oct 20, 2017

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

@Gargron Gargron merged commit 7082836 into tootsuite:master Oct 27, 2017

@hakaba-hitoyo

This comment has been minimized.

Show comment
Hide comment
@hakaba-hitoyo

hakaba-hitoyo Oct 28, 2017

Contributor

😍

Contributor

hakaba-hitoyo commented Oct 28, 2017

😍

@hakaba-hitoyo hakaba-hitoyo deleted the hakaba-hitoyo:patch-1 branch Oct 28, 2017

Gargron added a commit that referenced this pull request Nov 3, 2017

Revert #45, exclude instances with closed registration, show number t…
…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

hakaba-hitoyo added a commit to hakaba-hitoyo/joinmastodon that referenced this pull request Nov 5, 2017

Update actions.js
Precisely reverting tootsuite#45 (7082836).
In the API https://instances.social/api/1.0/instances/list, count=0 means ALL or INFINITY.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.