@mike@shlee there are only 5 changes, and only 2 of them (local posting and exclusive lists) are things that a user encounters in their day to day. The other 3 are new themes, and admin-only setting to change max post length, and the ability for long rich text posts (like from write.as instances) to appear behind a cut.
@darius@shlee oh I realise how it works, I just don't want it. Is it feasible that it could become an option, or is it built in a bit too deep?
See, I've made a few minor changes to Chinwag and I'd like to make contributions to an existing fork going forward rather than maintaining my own ... but I don't want to divert too much from defaults really.
@darius@shlee what I'm looking for is a Mastodon fork with maintainers that are open to implementing changes as options. This is my major gripe with the main project - the assumption that what the flagship requires is the only way any other instance will be run.
I'm prepared to do some work on this front, but I'd like to work with an already established fork and you've always struck me as a decent and reasonable person.
@mike@shlee thanks -- my scope for hometown is very very specific: I want to demonstrate that my ideas for running small federated communities (and specifically coherent communities of people who like each other) have legs and can be an important piece of the future of the fediverse. Exclusive lists specifically grew out of the work I did allowing Hometown feeds to render more kinds of content and to be used more like a feed reader, for example.
@darius I just read your neighborhood gist, love the idea. I see you say at the end you are trying to make it into a standard that is not specific to mastodon and can be used with other fediverse/activitypub software. have you talked you other AP devs about this yet or are you building it all in private.