Show newer

@aescling *upstream mastodon, which is financed significantly by sponsors and instance operators who do not contribute code

@aescling as opposed to mastodon where most of the money comes from sources other than the instances supplying the development labour

@aescling it would mean glitchcat would offer the development labour it can spare and [some other instance] would offer the development labour it can spare and there would be no central financing of development; glitchcat pays glitchcat devs (your patreon) and other instance pays theirs.

so there is no financial incentive to the project itself; it isn't bringing in money or trying to market itself to new instances; its only obligations are to the instances providing its labour

@witchfynder_finder yeah i almost was like “this author is clearly a girl and not a lesbian if they don't know how obvious this is”

but yes, link does seem to be an enjoyer of the zelda behind, which i mean…

…yeah i can’t fault that interpretation at all

link is once again shocked by things he should have noticed and probably assumed by now (zelda not wearing a bra)

you don't keep a bow in your closet STRUNG

what i would like to see of mastodon dev is:

- instances finance themselves and make a determination based on their finances what labour they can offer. no central financing or donation mechanism for development.

- that means all developers are there on behalf of one or more instances, who form the stakeholders of the project.

- broad agreement across stakeholders on the purpose and immediate direction of the software (i.e., a single platform). ideally, multiple different forks with different platforms, but cohesion within any given project.

- initially, a very slow pace of development. very few new features. immediate focus on increasing maintainability of the software, improving documentation, and making onboarding easier. this is a hard sell; it's hard to get stakeholders (instances) to continue to finance development which does not give them anything new. in fact this work may introduce delays in acquiring upstream features. i’m not sure how to resolve this except with tangential personal incentives like: gaining a better understanding of rails, learning better development practices, personal satisfaction at making a complex software more easily understood…

- project longevity.

- good and active communication with users (of stakeholder instances).

Show thread

anyway if your instance is small and agrees broadly with the principles in our /about/more and you want to contribute development labour to making mastodon better then @ me i guess and we can at least talk about it

we are not interested in taking on additional stakeholders without associated investment of labour, though

Show thread

like for real though people focus too much on fedi alternatives when: we have mastodon, it is good for some things, lots of people use it, it’s open source, we can do a lot with mastodon

DON’T CONTRIBUTE UPSTREAM

Show thread

mastodon developed by people who actually understand what the software is good for when 😔

Show thread

all this talk of mastodon is making me want to fork mastodon 😔

@aescling @Satsuma yeah i just think it is funny that the people who develop mastodon and the people who don’t use mastodon have the same ideas and it is not at all the same as the ideas of the people who actually use mastodon

@aescling @Satsuma having instances be bland interchangable spaces with some community features layered on top as opposed to like, what darius describes in run your own social

@aescling which is hilarious because @Satsuma and i have been having conversations with people in fandom coders who are like “this is the way it should be” and all being like No You Don’t Understand Nobody On Mastodon Wants That

@aescling groups were originally a GNU social feature which used bangtags like !tea, i think working similar to how guppe groups operate now

mastodon staunchly refused to implement them

around the time when pleroma development was really kicking off i remember there were a lot of discussion about alternative ways of thinking of groups, but my understanding is that those discussions never went anywhere because there wasn’t good consensus on how they should be federated or administrated; i know @nightpool@cybre.space was involved in those discussions although i don’t know if they remember / want to say more

anyway this is very interesting because that blog post makes it sound like there is a Plan For Groups and i sure haven’t heard anything… is this being coordinated with other fediverse softwares? was there ever a consensus? am i just out of the loop?

@aescling eugen has opposed groups from day 1 so i am very interested in hearing more about this

:P 

@aescling i don't actually like the label platformist, but it's a better vernacular descriptor than any of its adjectives; i feel like i’m probably actually closer to especifist thought but that word belongs to a very particular political context

in any case the purpose of having a platform is it means you can tell the labels to take a hike (unlike synthesist anarchism where the label is the only thing binding you together)

sorry synthesists, libertarians, and (with sympathies) communists; mastodon is simply designed for small agile groups with high levels of internal cohesion and collective responsibility

Show thread
Show older
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.