RE: https://mastodon.social/@staff/115849914607258480
This is not a bug of #Fedilab if the local or public timelines are empty on mastodon.social.
We will check if we can detect through the API when timelines are disabled to avoid that bad UX.
Post
RE: https://mastodon.social/@staff/115849914607258480
This is not a bug of #Fedilab if the local or public timelines are empty on mastodon.social.
We will check if we can detect through the API when timelines are disabled to avoid that bad UX.
@apps i wonder if this will become the new norm across the fediverse?
@finickydesert_1
Since we work on Holos, we questioned the usefulness of the public timeline.
There are so many create/update/delete activities that nobody can keep up with. People need messages related to their hobbies, not random ones.
@apps While it is rare, be aware that there are instances (like chaos.social) that "curate" the instance's public timeline by strict rules and moderation, e.g. guide on what should be public vs unlisted and strictly enforcing content warnings. While you may opt to change defaults, users on those instances do rely on the public timeline; such instances are from common hobbies / clubs / associations already.
@fedicat
Yes, we fully missed this update that will need some reworks.
@apps hopefuly a easy fix
@finickydesert_1
Well, yes and no. Detecting disabled timelines through the API should be straightforward. But the whole UX has always been designed around the local and public timelines being available. When they're gone, it changes quite a lot in terms of navigation and discovery.