in the discussion for fep-5624, the use of `context` to represent a conversation was raised. and the intention was to allow "reply" and "comment" systems to understand each other. but it's possible to reframe the problem entirely. rather than focus on "is this reply-link valid?" we might instead consider, "does the linked object's replies collection contain this object?" or alternatively "is this post part of a conversation/context collection?"

Show thread

AP has turned a corner. It's standardized and in wide use.

Building extensions on top of AP is useful and necessary, but starting over with incompatible protocols is a bad plan.

Blue Sky in particular is a bad project. It started after AP was standardized. The team had access to many many people's time and all the docs and experience of the fediverse.

But they opted to make a snowflake protocol instead. I think because they want to capture value at the protocol level.

Don't use Blue Sky.

@p I have FediList feature request.

At there is a "TOR?" dropdown menu containing "TOR only" and "Exclude TOR" items. Could you add a new category that represents clearnet instances connected to Tor federation? An instance belongs to that category if it has a clearnet domain name AND its peer list (api/v1/instance/peers) contains at least one .onion instance.

This should help people on Tor network make new connections.

In an attempt to apply Hintjens' ideas around problem-focus more broadly, I invited ChatGPT to provide input on my World Problems issue tracker. is an example.

Feel free to add more or comment.

@trwnh It's a fair stance. I'm sure you know the options well.

@trwnh More power to you! To the extent that you know/like a forked codebase, why not Ecko?

If you like the idea of voice assistants but it's gotta be open source you've probably heard about MyCroft AI and their Mark II device. Neon is an alternate OS build based on OpenVoiceOS.

I made this video showing some of NeonOS and my experience getting it to do a couple things on the Mark II.

@chipzel Seems like an obvious idea and one that's probably been discussed many times so I wanted to share a way to help make it a reality.

Ecko is a fork of Mastodon that is community-driven in the sense that we solve problems vetted by the community. If you can phrase this as a problem, then it can go in the issue tracker and perhaps someone will find it interesting enough to create a patch.

What makes Ecko different here is that we merge code without nitpicking or conflict with some grand vision. We trust the community to be thoughtful about problems and contributors to be responsible.

If you're interested to nudge this idea forward, check out

h/t @RyunoKi for sharing this thread

Instagram closed my account and I'm really not sure why. Community guidelines they say but I don't even know what I posted weeks ago. I couldn't find the account when trying to appeal. Maybe I shock-horror mentioned the fedi. Unsure.

Bottom line: Instagram closes accounts without reason or recourse. Good.

🥳 I'm pleased to announce that "FEP-1b12: Group federation" has just been finalized. Find the document at

👆 This FEP (Fediverse Enhancement Proposal) describes how groups are implemented in existing Activitypub platforms using `Group` actors. This is the fourth standards document to be finalized under the FEP process and continues efforts to help interoperability across the fediverse.

🛖 View other proposals and submit yours at

@mro Do you have a link? Was that a Hintjens piece?

📽️ A big misunderstanding on software quality (from a Pieter Hintjens talk)

The old model of collaboration in the ZeroMQ community was like this. There was a guy who was the main author. He would write code. It would be very clever. A genius man. There was a friend of his who was the main maintainer and he could understand git and branches and merges and packages and makefiles and autoconf and all this very complex stuff and he could talk to the first guy.

Their brains would synchronize with this amazing shared state which involved lots of beer and meetings in strange locations. These two were a very good team. They made amazing software which was very fast and didn't crash. It was amazing and good.

Then there were all these other guys who were using it and contributing to it, but the contributions had to go through a mailing list to one of these two guys here, who would then look at the mailing list patches and say, "Hmm we don't like your patch. We don't agree with your patch. We think your patch is.... We don't like it! You know it's basically our baby so if we don't like it... well we'll think about it. Your code is badly indented. Hmm, no."

Video continues:

Pieter Hintjens talk at EuroPython 2014 is a must watch. So glad to have found a higher quality version to add to the Magic Stone video library.

@RichardNairn So THAT was what laid the foundation for the 90s. 😅 The time may be ripe for an extension.

What is the internet?

A stack of protocols.

That stack is defined among thousands of RFCs. One of the first (RFC 3) is about writing RFCs.

Kind of a fun to read in light of and .

Been taking notes on videos and books for a while. Figured it was time to start publishing some of them starting with favorites, meaning stuff I'd listen to or read more than once to get the most out of it.

Here's legendary processor designer Jim Keller on Lex Fridman's AI podcast.

New PeerTube instance, new video.

This one about the MyCroft AI Mark 2 hardware and why I wanted to check out an open source digital assistant.

@x I thought this was commentary but now I see it's advice. Got one setup and I think this'll be close to single user, or at least watched carefully.

Working on one for Magic Stone but that'll be limited to Hintjens/C4 and Magic Stone-related projects. Would be great to learn of one for personal/variety vlogs.

Show thread

I'm sad that went down. I had rehosted some Hintjens videos there. Any suggestions on a sustainable PeerTube/fedi video hosting platform to move to?

Show older
Ecko /

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.