David Sterry @weex@c4.social

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

#MagicStone #nostr #weboftrust

https://davidsterry.com/blog/2023/09/the-global-town-square-is-for-everyone-not-just-blue-checks/

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.

@ChrisPirillo Right on, not from the EU but I try to skip the algo immediately. On YT I go to history, on twitter I have lists, but mostly try to be on federated stuff. I wouldn't mind an algo if I got to pick it.

Feedback requested on Fediverse Enhancement Proposals going stale before finalization.

https://codeberg.org/fediverse/fep/issues/101

#FEP

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

https://github.com/weex/Problems/issues/21 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.

https://video.davidsterry.com/w/ndkJkqh1CENYkT3cuABthM

#neonos #mycroft #openvoiceos

@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 https://github.com/magicstone-dev/ecko/issues

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 https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-1b12.md

👆 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 https://codeberg.org/fediverse/fep.
#fediverse #fep #standards #activitypub #socialhub

@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: https://peertube.magicstone.dev/w/4JSGy66bu1THNrmMY2UZjt?start=17m3s