Conversation

Notices

1. Embed this notice
   Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:28:00 JST Luna ??? //nullptr::live

   • かき@GNUsocialJP

   Mmm since Mastodon’s discoverability is one massive issue for artists, etc. that might end up residing on our instance, I could potentially look in to making a bot that tries to promote interesting users of our instance that people optionally can follow.
I’m not sure how it would go down with the rest of fedi though, since a lot tend to be anti people-making-a-living-via-discoverability-giving-them-customers from what I can tell.

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:29:10 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP

     In general a lot, or at least a very loud minority of fedi wants to explicitly keep algorithms that could improve discoverability away.

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:31:03 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP

     For people who’s livelyhood depends on discoverability the fact that Twitter is a collapsing is kind of a threat on their life. Including for people like me who are not able to work a normal job without getting burnt out and as a result, suicidal.

     I want to try to see if we can carve out a space for people here so that such things don’t happen…

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:32:16 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP

     Ideally I’d add a (nice) algorithmic timeline as a feature and submit it back upstream, but people have already tried and I know what fedi drama that has lead to in the past…

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:37:52 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • Tlapka (Arknights)

     @tlapka idea would be that we’d silence the bot so people will only receive those recommendations if they follow it, all it’ll do is boost posts at a maybe 15 minute interval or something.

   • Embed this notice
     Tlapka (Arknights) (tlapka@ak.kawen.space)'s status on Tuesday, 08-Nov-2022 19:37:53 JST Tlapka (Arknights)

     in reply to
     @LunaFoxgirlVT I think the real problem wouldn't be the people complaining but just the fact that bots and crossposters are really efficient at oversaturating things meant to be for discoverability
     
     mastodon has things like trends and hashtags but on a little-moderated instance the trending hashtags will be dominated by bots, hashtag search will return endless crossposters, etc.
     
     (which is part of what discourages people from using these features, and that also fuels people rooting for their complete removal)
   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:38:51 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • Tlapka (Arknights)

     @tlapka but of course, silencing does not transfer to other instances so it’s still a problem.

     Which is why it would be better as a feature that adds an algorithmic timeline. But again, a lot of people really don’t want that.

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 19:39:18 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • Tlapka (Arknights)

     @tlapka because hashtags are not discoverability, with enough users they are just a useless flood.

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 20:16:11 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • alexis

     @alexis afaik no, upstream mastodon is not really fond of that idea.

   • Embed this notice
     alexis (alexis@social.helvetica.fm)'s status on Tuesday, 08-Nov-2022 20:16:12 JST alexis

     in reply to

     @LunaFoxgirlVT do you think upstream might be more receptive to a general plugin system for instances? that way something like an algorithm timeline feature/plugin could be made and popularized kind of on the side so the core crowd doesn't start drama (they would anyway), but it'd be nice for those who would wanna use it and not want to worry about breaking their instance due to patch updates

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 20:27:32 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • alexis

     @alexis we already run a fork called glitch-soc, so

   • Embed this notice
     alexis (alexis@social.helvetica.fm)'s status on Tuesday, 08-Nov-2022 20:27:33 JST alexis

     in reply to

     @LunaFoxgirlVT hmm, that's a shame but also matches the (limited) vibecheck i've gotten from them so far. honestly i rarely contribute to foss because github project maintainers are always so possessive and holier-than-thou..

     i guess a fork would be the only option in that case, meh :/ instead of making one unified awesome solution we gotta have fragmentation hell

   • Embed this notice
     Luna ??? //nullptr::live (lunafoxgirlvt@vt.social)'s status on Tuesday, 08-Nov-2022 20:32:52 JST Luna ??? //nullptr::live

     in reply to

     • かき@GNUsocialJP
     • alexis

     @alexis good thing with glitch-soc is that features there do eventually land upstream in mastodon, so it’s a slightly more compatible fork

   • Embed this notice
     alexis (alexis@social.helvetica.fm)'s status on Tuesday, 08-Nov-2022 20:32:53 JST alexis

     in reply to

     @LunaFoxgirlVT yup i know! this is a little bit the problem i mean to describe. if there are 12 cool forks of mastodon, each separately with a cool feature you want, now you as a platform provider have to decide which one you want most, rather than being able to pick and choose features via plugin or config :(