Show newer

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 . 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.

Show thread

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

Show thread

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.

Remember Twitter's super uber-secret project Bluesky? They finally explained what they're up to, and it's spicy 🌶️

So spicy that I had to write a 1,200 blog post one what exactly it entails. Key learning: Twitter doesn't like Mastodon. 🧵 blog.peerverse.space/lets-talk

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!

@weirdwriter@writeout.ink @darius @humanetech
I never considered that people don't caption out of laziness. I mean they're taking the time to share the content so I would assume they want as many people to understand as possible, but that they simply don't know that captions are essential for some.

On Twitter, I never even thought about it. At least here we're talking about it and making issues that can be addressed.

My personal favorite solution to this issue is a nag on posting if you didn't caption. People tend to click through such nags automatically after a while but at least at the beginning it would help to raise the issue more widely.

@blindscribe @humanetech @darius @weirdwriter@writeout.ink For the Ecko fork which follows C4 process, we convert feature requests into problems that leave the How open to the implementer.

In this case, one way to state the problem is that there's no way to suggest a caption for undescribed media. To the extent that a reply or DM could serve that purpose, I suppose you might add language like "no easy way" or "no integrated workflow for" this.

You mention administrator so one question I have is, what have you seen administrators doing manually to correct these situations?

@mariusor
Hi Marius, I'm excited to see more work on moderation. What's the best way to follow this effort?

If implemented it seems like it could help with codeberg.org/weex/the-fedivers

log link & snippet 

@nerd I didn't see anything there pertaining to an error thrown by postgres. A stack trace would be good if you can find it. I think a command something like journalctl -u mastodon-web or journalctl -u postgres might get you closer.

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. peertube.co.uk/w/2cw9QGY51ey6S

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.

@nerd Would be great to see logs. The bookmarks csv seems too simple a file format to have anything messed up.

@rosano Never underestimate a well positioned zip tie.

@renatolond @crossposter Cool, I'm not a user and d don't mean to add any pressure :)

I'm getting interested in helping more people transition away from Twitter and crossposting seems really important for continuity so thanks for what you're doing!

@crossposter @renatolond

Is there an issue in the tracker or more information that might let others jump to help?

@kev The benefits of self-hosting are easy to discount since they're rather hidden, but as a member of the FOSS community I appreciate that it's not always about the easiest way to get a job done.

I enjoy mixing in the testing and problem solving to maintain the onramps and tools so others who are have less time or interest can still install these things.

I really like that this little incentive can drive thousands of us to build this FOSS life together.

@fnord Unfortunate choice by Thingiverse. I don't even lurk these days. 3d printing was fun and some designs improved my space but after a couple iterations they're all set, no further designing needed. Maybe if I get a new space I'll have a need to find another model library site.

Show older
Ecko / c4.social

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.