David Sterry @weex@c4.social

Isn't it funny how often things that should be simple can get flipped and become anything but?

Here we have a simple faucet with hot and cold water, but in the common case that it takes a while for hot water to appear, one wonders which way for cold?

Is it up because the handle should go in the direction of the blue dot or down so that the blue dot is brought into some position relative to the base?

streaming a hintjens talk, coding more on web of trust, but mostly hanging out

https://www.twitch.tv/aptact

When compared with centralized services, federated social networking has brought you _______ conversations which are of _______ quality.

#fediverse #social

Had a really nice hangout this morning with folks from @ohn and it was really fun! It's great to meet new people and realize that maybe I'm making new friends.

It also got me thinking about richness of social interaction and humanity where at one extreme we operate in text and emojis while at the other end we can spend time together in the same physical space with no tech required.

In this light, Open Hospitality Network (https://openhospitality.network/) is taking on perhaps the hardest kind of technology project where people use this tech intentionally to connect with real people.

What if the social platforms we use, instead of suggesting we follow celebrities to increase engagement, saw that we're spending an unhealthy amount of time in a low-quality medium and suggested we pick up the phone or arrange a video chat or meetup?

In the interest of furthering standards discussion and development on the Fediverse, I'm proposing a change to SocialHub.

https://socialhub.activitypub.rocks/t/move-fep-under-a-new-standards-category/2039

Two books for the C4Social library!

5yo intermittent testing problem

https://github.com/c4social/diaspora/issues/39

I lik this post from @agateblue@mastodon.technology in the ActivityPub library titled "Getting our hands dirty", which is about project governance, the problem that sent me off on the search that found C4 and spawned C4Social.
https://library.activitypub.dev/shelves/web-2.html

C4Social was created to solve two problems (not enough developers on the fediverse and slow development pace) with the hypothesis that the Collaborative Code Construction Contract (C4) offered a compelling solution.

Core to the C4 is that code is merged not on its content but on the problem it addresses. So from the first moments, feeding the process meant finding code which addresses valid problems. Upstream is therefore the first place you look… and there we found and merged 35 PRs between the two forks.

As people joined, some concerns were raised with this practice:

* First, that such PRs might be work-in-progress and that by merging code before upstream maintainers, we would be taking on additional risk on a patch which may still receive comments and changes.
* Second, if more changes are made and then the code is then merged upstream, we may have conflicts to resolve which might make merging not worth the extra maintenance.
* Third, the author of the patch may be surprised that their code is used on a fork.

Today, there are another dozen or so PRs to look at so this is a good time throw a question out there. Are there other concerns that should be raised about this practice? If you make PRs, would you want to be pinged by a fork?

Maybe dumb question but should forks be completely renamed? Is prefixing enough?

https://github.com/c4social/mastodon/issues/231

If anyone wants to play around with some web-of-trust scoring code, here's https://github.com/weex/wot-server/blob/a3497dc5ba40e1b6958367860254aac1131fd5a8/weboftrust/__init__.py.

Test with `python test.py`.

Extremely curious to see how this would work on an anonymized stream of values, perhaps generated by events like block, ignore, follow, boost.

My daughter has been doing portraits and sketches since she was old enough to hold a colored pencil. She just sent me this for the C4Social project so... meet Charles, our new mascot/logo/protocol robot. 😍

Hello `fetch chromium` my old friend.

STIILL running after four and a half hours. Looks like you're done downloading and now "running hooks"... wasm_fuzzer, that looks interesting.

BREAKING NEWS

Subprocess failed with return code 2!

47GB of data on disk and we've run out of space. Will have to pick this up later in the VM.

Thanks for playing!

Now that wasn't so bad honestly. I chose the Artifact mode which apparently downloads pre-built binaries for the c++ code. This one is apparently better for front-end/ui work. I wanted to start simple and now after `./mach run` I'm looking at a working browser (with the sponsored links that started all of this).

Two hours including a VM install isn't bad overall. Maybe I'll tackle one of the first bugs I saw in Codetribute.

In the mean time, Chromium's fetch continues...

Meanwhile the `fetch chromium` is giving alarming messages about fatal early EOF and index-pack failed. Still have 21gb of free disk space and internet has been fine so hopefully it retries. 🤷