@Codeberg is down due to an upgrade :( Wishing them luck for a quick recovery. 🚑

The visual cortex has arrays of neurons (or neuronal columns?) which detect specific orientations of objects in the visual field.

Scientists could see this because they could push this electrode into the tissue while showing the live animal subject lines of various orientation. What's unclear in the lecture and in this image is whether what they're measuring was a single neuron or the spikes from a handful. Is each of these vertical slices a cortical column?

This pertains to feasibility of bio-based AI/ML modelling because there are many fewer cortical columns (150k) than neurons (20b) in the brain. Still more interested in developing a small component with feedback loops, etc but thought this was interesting.

Video: youtube.com/watch?v=ePP0G7FJGP

"In order to understand bird flight, we have to understand aerodynamics; only then does the structure of feathers and the different shapes of bird's wings make sense." -David Marr

A key principle of aerodynamics is Bernoulli's principle which relates speed of a fluid and pressure. This principle can be derived from conservation of energy but also directly from Newton's Second Law of Motion (F=ma).

Marr said the above quote in relation to studying the brain and how it works, which begs the question, what principles like conservation of energy are also in action in the brain? Conservation of energy is probably too broad since Bernoulli's principle breaks down if there's turbulence or thermal radiation and it's hard to imagine anything like laminar flow in the brain.

Working on a new AI/ML project partly to learn but also to see if something interesting will arise from "scratch."

A missing piece this morning is that of a reward system. I don't know how to tell this thing what's good and what's bad programmatically. Seems like the perfect time to "do things that don't scale" and execute the reward function myself. I figure I'll let it ask me after each step for 👍 or 👎. An app would be cool so it could just be taps but I'm a cli-guy so maybe I'll go with vim bindings.

There's nothing quite like finding and following your internal passion. It takes some doing to strip away the noise of life but it's so worth it.

Problem, then Solution

Educate yourself and others to focus on problems not features. Every
patch must be a minimal solution to a solid problem. Embrace experiments
and wild ideas. Help people to not blow up the lab. Collect good
solutions and throw away the bad ones. Embrace failure, at all levels. It
is a necessary part of the learning process.

Ten Rules for Open Source Success

The launch of Spread Mastodon has me thinking again about two contrasting views of decentralization that I see operating on the #fediverse

One you could call Just Nodes: Instances are just how you connect to the larger network, and how they're run matters for sustainability but not much else.

The other is Networked Communities: Instances are valuable for the relations and interactions they facilitate locally AND for their ability to connect you to other parts of the network.

Thinking about a greenfield project for Magic Stone. Has to do with Nostr, web-of-trust and the idea of a global town square.

I really need to learn how to write short updates and not get all epic. 😅


Hi Fediverse, it's been a while. How've you been?

Haven't been on social media much but I'm starting to feel a need to return, especially to help people flourish outside the purvey of the algorithm.

Hope you're well.

Feedback requested on Fediverse Enhancement Proposals going stale before finalization.


Look who I’m with!

@evan@cosocial.ca, the co-author of #ActivityPub!

He and I had a long conversation about the future of the Fediverse, and upcoming developments!

Here’s the biggest news:
@evan@cosocial.ca is actively working on ActivityPub again, specifically the spec! He’s excited about #FEP too!

These next few years for the Fediverse will be great!

Just pushed an extensive update to FEP-fffd (Proxy Objects), which explains the process of merging posts with their proxies and removes the need for extra context entries. This should hopefully be the final syntax for this feature.


#FEP #Fediverse #ActivityPub #Nostr

If it seems like the world of "AI" and "AI ethics" is moving too fast, I'd like to point out that the fundamental problems are in fact relatively unchanging and keeping an eye on the people involved can be a good anchor. Two cases in point:


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 http://demo.fedilist.com 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.

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.