David Sterry @weex@c4.social

Been writing a lot more recently and it's just good. One trick to try is stream-of-consciousness, not stopping or going back to edit. I found myself still using backspace and stopping so made this single pager to help turn it into an exercise.

Write Without Stopping:
https://codeberg.org/weex/write-without-stopping

If you maintain open source software and don't use C4, I'd be really interested to hear your thoughts on this talk by the late Pieter Hintjens. The talk doesn't depend on video much so it works as a podcast. https://peertube.co.uk/w/2cw9QGY51ey6SiF3zPPtvW

A new version of Acropolis was just released for YunoHost. Version 2022.01.29~ynh1 adds email confirmation for new accounts and creates the initial admin account during installation making it the smoothest installation method of any diaspora* fork.

#Acropolis is Magic Stone's fork of #diaspora, one of the first federated apps ever made which is built around "aspects" or circles of people that you want to share with. Sign up at https://dogieda.org to try it.

⚠️ Please report issues at https://github.com/YunoHost-Apps/acropolis

Created an intro page and a few issues for the social network moderation backend. https://github.com/weex/wot-server/wiki

The idea is to leverage emergent social structure to shun bad actors without needing to explicitly ban anyone or create collateral shunning of folks who seem to have joined the wrong server.

My favorite book about writing is Writing Down The Bones. https://nataliegoldberg.com/books/writing-down-the-bones/

It motivated me to write a lot more and with less purpose. Very freeing.

If you're interested in learning how writers write, check out The Paris Review Interviews series. For decades they've been talking with some of the best: https://store.theparisreview.org/products/the-paris-review-interviews-i

For someone like me who's can get a bit obsessed with process, these interviews read themselves.

Social media companies now are deciding if board members have enough skin in the game.

What's more interesting is who all governs how these systems operate.

For Twitter, that's the corporation and increasingly governments.

On the fediverse, it's the users and admins.

Thank you @PaulaToThePeople for including me in your #followrecommendations. I just reached 100 followers which doesn't sound like a lot but feels like 10-50k bird site equivalent. One of my motivations for coming to the fedi was to have an impact and it's been heartwarming to see the response from so many real people from the work I care about.

This whole episode is confirming for me that the migration to the fediverse is inevitable and that every action taken in cweb is good for us.

What's particularly exciting about this is that nobody can know the result of thousands of communities molding the software to suit their needs.

If the the human story is one of engineering a better world, then the fediverse is a collective effort to engineer a better online world.

Thinking how great it is that one rich dude can't buy the fediverse.

Preparing some thoughts on the first 6-8 months of Magic Stone's existence. Ecko, Acropolis, themes, plugins, new contributors... it's been a blast!

If you maintain open source software and don't use C4, I'd be really interested to hear your thoughts on this talk by the late Pieter Hintjens. The talk doesn't depend on video much so it works as a podcast. https://peertube.co.uk/w/2cw9QGY51ey6SiF3zPPtvW

The best feature of Git is that decentralization is baked right in. upstream is just a label, and one that doesn't come along in a clone. This clean slate of context makes a first class citizen of every single copy of the source code. When you clone a repo, I feel like git should say something like "You now have the ball. What will you do with it?"

As the git/pull request flow becomes the norm, innovation in development process would seem naturally to look toward tooling for forks. How could we make forks interoperate more seamlessly? By perhaps making tools that transplant PRs from one repo to another with higher success.

Is it possible to develop better techniques for merge conflict resolution? I'm sure better understanding of the source of conflict could help.

How could we make package managers more flexible about which fork of a package to link into a stack? Working protocols and API specs seem promising avenues.

#FOSS #random #development

Been writing a lot more recently and it's just good. One trick to try is stream-of-consciousness, not stopping or going back to edit. I found myself still using backspace and stopping so made this single pager to help turn it into an exercise.

Write Without Stopping:
https://codeberg.org/weex/write-without-stopping

Join Magic Stone. It's a good community. You should contribute. Visit the website. Say hi in the Matrix. Discuss problems. Write code and get it merged. It's very simple and we can have some fun making accurate software.

#magicstone #ecko #acropolis #c4