Requested features from GlitchSoc

[marrus-sh]

The following features were requested for GlitchSoc but never implemented :—

• Out‐of‐body hashtags: tagging improvement as a robust feature glitch-soc/mastodon#5
• Disabling the local or federated timelines for an instance
• Thread collapsing (this is imagined as a frontend feature): Thread collapsing glitch-soc/mastodon#28
• Decrease post visibility on federation: allow post visibility to decrease when federating glitch-soc/mastodon#79
• Notification merging: Notification merging for favourites / boosts / new follows / ... glitch-soc/mastodon#130
• Card prefetching: Card prefetching glitch-soc/mastodon#187
• Load about pages from a file: Specify files to load about pages from glitch-soc/mastodon#251
• Reactions: [idea] reaction feature glitch-soc/mastodon#323
• Flavour‐specific configurations: Flavour-specific configuration through theme.yml glitch-soc/mastodon#350
• Limiting number of followed accounts; providing time estimates: Make Mastodon/glitch-soc less addictive glitch-soc/mastodon#597

Are we interested in any of these?

[aescling]

my thoughts, which i guess TL;DRs to “i like most of these ideas” lol

wants

• monsterfork actually did out of body hashtags and i always thought it was a good idea
• i’ve personally always wanted to be able to disable the public timeline (there was a time when i thought that if i was gonna admin an instance, i would hack away support for the public timeline lol). if i were going to run a a single user instance (not that i would) i’d definitely make use of that
• thread collapsing would be a great feature imo

things i think are worth supporting

• notification merging is a good idea imo
• i feel like card prefetching is a must have feature for post previews, which is the feature i would actually suggest here
• loading about pages from a file is a good idea a think
• i think the fire demon was working on reactions for monsterfork but never actually finished it; personally i was never big on the idea but it like, makes sense. generic favourite is probably actually the worse idea though so
• flavour-specific configuration makes sense to me
• time estimates and/or post frequency data both seem worth making available to users to me

questions

• why would you want decreased last visibility on federation? i think it’s a neat idea though

[marrus-sh]

Mainly the idea behind decreased visibility on federation is to have federated posts which don’t show up in public timelines elsewhere, but show up in public timelines locally (public → unlisted), or posts which can be boosted by local users but not by just anyone (public/unlisted → followers-only).

[aescling]

i feel like monsterfork actually did that one too at some point now that i think about it

anyway regardless i can see how that could be desirable and i would be up for implementing it

(i am getting very worried by the number of features i would like to see added lol)

[marrus-sh]

wow imagine if over the past half‐decade eugen had implemented any of this!! 🙀

(i jest but the list used to be even longer and some of the requests to glitch-soc actually have been implemented in upstream now.)

[marrus-sh]

for real though the answer to this worry is to recruit developers and work in solidarity with other forks / instances lmao 😂

[marrus-sh]

I could have sworn this got merged but I guess it never did? glitch-soc/mastodon#257

It’ll need to be re·implemented now, probably.

[aescling]

oh i like that