@blindscribe Were currently the same as upstream in this respect for both projects but would welcome this being brought up in our issue trackers. I created a sort of placeholder issue for accessibility since it's hard to know what's broken without a formal analysis. More broadly I'd be interested to know if you find github usable enough to search for existing issues and create ones for any kind of problems you experience. github.com/magicstone-dev/ecko would be the first place to visit.

@kaonashi696 Love this game. Too bad the C4 got you but, why the camping anyway? 🤣

@emacsen Great question and one that needs revisiting from time to time. The core difference is in development philosophy in that code addressing any valid problem gets merged.

Typically this question is more about features so probably best is to share a feature comparison: fediverse.town/t/what-features

What is missing from that comparison is that we've made it possible to change many of the static settings (post length, # of poll options, minimium bio length, max profile fields) from the UI. We've recently added five more themes and today we merged markdown/html support.

If you want to test it out, c4.social is open for registration and it typically not far behind the latest commit.

@tychosoft I'm pretty sure. You can configure whatever domain names in YunoHost that you like. I have one setup as yunohost.local which works fine with self-signed certs. If I were to open ports on the router, I don't see why I wouldn't be able to access from anywhere.

Our Community Q&A session starts in about 15 minutes! Time to

Reminder: you can hear it on our Discord (discord.gg/pine64) or TILvids (tilvids.com/a/pine64tilvids/vi)!

You can ask questions in the Discord chat, or on our IRC (irc.pine64.org). Channel name
on either platform is "#q-and-a".

See you there!

If you'd like to try running your own instance of Ecko, our community-driven Mastodon fork, or Acropolis, same for diaspora*, YunoHost is the easiest way.

You can install YunoHost on an old laptop, raspberry pi, virtual machine, or remote server and learn what it's like to self-host these apps or one of many others (CryptPad is another favorite as Google Docs replacement).

Have you already tried? I'd love to hear about your experience getting any of the above setup. What didn't make sense? What took a long time? How can we help make it smoother and easier to provide what your community needs?

@celia It's great to have the flexibility to go off-routine when it feels right. Often driven by curiosity, I like trying different life process management algorithms. These days I've settled into a morning routine plus visiting various issue trackers.

Blocking out focus time has worked, pomodoro timers have worked, I've used a google doc to list current projects and weekly goals.

At this point, I'm happy with what I'm doing but if it gets boring I'm sure there are 100 task management books I can choose from to try out a new time management format. I say enjoy the process of discovery and exploration about what works best for you!

@weex We're one of those Ecko servers - just wanted to say a big thanks for what you & the other contributors are doing 🙏

Here are some stats for Ecko. It's fun seeing things that look like exponentials even if it is super early.

ecko.fediverse.observer/stats

According to Fediverse Observer, the fedi just passed 4.5m users on nearly 15k servers, who've sent more than 500m messages. fediverse.observer/stats

Ever think about how tacos are just burritos with commitment issues?

As an editor on the Fediverse Enhancement Proposal team I'm pleased to share a new proposal on Web Monetization from Diogo of GNU Social!

Find the draft proposal here codeberg.org/fediverse/fep/src

Feedback is appreciated at socialhub.activitypub.rocks/t/

Codeberg is a non-profit run code repository. I like it as an alternative to GitHub for new projects that may be come core to a fledgling community.

Magic Stone now has an org there at codeberg.org/org/magicstone should we want to do a greenfield project.

One of the things I love about buying used over the internet is the assortment of notes and cards that are sometimes included.

This one feels like one of those little objects that could be the center of its own story.

Maintainers SHOULD close user issues that are left open without action for an uncomfortable period of time. (2.4.19)

Buried in the Collective Code Construction Contract is the clause above. I'm not sure what an uncomfortable period of time is, but early on it's probably not long, like a month or two.

Early on we tried to populate the issue trackers with what we thought were valid problems, but today we have something better. Problems being raised by our community of user-admins!

It's truly awesome to see this feedback loop in action. We've already got some good problems to solve, like being able to handle Markdown and LaTeX and working better with Debian packaging.

Learn more at magicstone.dev

Docker/Ruby guru wanted!😍

We use docker-compose for deployment of Ecko at c4.social but for a couple of weeks haven't been able to build a docker image that would pass health check. What's strange is that it seems to be due to a change in one of our docker build dependencies with the result that bundle can't be found! Even build of earlier code fail. 😭

If you're excited by FOSS and container builds and want to take a crack at something that has flummoxed the few of us in Magic Stone, or if you have a radically better way to run this Mastodon fork, the issue is here for your input github.com/magicstone-dev/ecko 🙏

@raboof Nope, and Ecko is installed on 17 instances so far!

@humanetech @MediaFormat @zap @weex@mstdn.social We have a related issue and some work has been done on it but as there are many other problems to solve it needs a champion (i.e. Ecko user or admin) to help drive it to completion. github.com/magicstone-dev/ecko

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.