Notices by Kate (katebowles@mastodon.social), page 17

@sargoth I'm always happy to see it again. It's a celestial body orbiting us peacefully.

@gdkar That, my goodness, that is a song that makes you wonder how we made it through the seventies. 🌹

@vfrmedia @RunningInCircles For me (so not a dev, not even close) GitHub/Discourse as an assumption reminded me of literacies we assume students have when they come to university. They're cultural and specific but we're inside them so they seem like breathing, not like specific know how.

Thinking about literacies in intentional communities generally. How is knowledge itself distributed, federation, decentred?

@maloki @Are0h Same here, exactly.

@Trussell Welcome! It takes a month or so I found, just crafting your following list until that's the timeline you mostly follow. When you have this set right, it makes more sense than the sprawl of a big home timeline.

For pets, my warmest recommendation is @jillybobww. Kevin and Maurice are without peer.

@RunningInCircles

Here's the thing. A community water pump is an engineering design marvel. But it's also a social wonder. And ingenuities of practice spring up around it, other social things are happening. A well is maintained by its village. The engineers aren't there when a dead animal falls in: the village has to figure out what to do. Then someone adds a shelf to steady a water container, or a place to keep pots, or some gravel to stop the whole well being a mud pit.

@RunningInCircles

All the community here are giving our free time and content (so much art!) to the service of something many of us think is making a big difference. And maybe we're all scratching an itch, a curiosity, a hope for a better world.

The cooperative side of this needs all our hands to the pump. But we do have to figure out how pump designers and pump operators learn together about the nature of water.

@RunningInCircles

Here's an aspect I think can get missed in community projects: the free contribution of user labour. Even commercial platforms depend on it. Content contribution is very often the engine for design innovation, but it's also the source of social viability of the design itself. Users bring utility.

So I see it as a coproduction in which both parties underestimate or are frustrated by the other.

Your reply got me thinking about users who also have itches.

@RunningInCircles

But at some level this is about inclusive practice. And I can't imagine how frustrating it is to deal with inexpert collaborators--but we're not wholly inexpert, just skilled differently.

I really appreciate that @Gargron has invited input. And I'm interested in what you're saying because I do think it's a barrier we need to look at.

@RunningInCircles I think (and I'm feeling my way a bit carefully here) the framing of this as "asking nicely" sets up a client dynamic that works in a lot of projects, but may not work so fluidly in community building.

I'm really thinking about how good community platforms can be co-produced.

Mastodon evolution, for example, still has some assumptions about GitHub as common ground. Also Discourse. Does that matter? Maybe not, if users are just non-tech clients.

@mappingcat Several of them have made their way here. I have I think 11 in my garden, a bit accidentally. I've lost a couple over the years -- the big ones.