Just because this company has suffered challenges doesn’t mean the efforts are slowing. Anyone interested should look into OpenVoiceOS and/or NeonOS and start hacking. Internally the Mark II is a Raspberry Pi 4 with 2gb of RAM. The case they made is nice but not essential for the hackerish state of the whole idea.

Went ahead and created a fork which is deployed with Vercel just as the Nolan’s was (live at https://pinafore-silk.vercel.app/). I enabled issues and plan to maintain it under the Collective Code Construction Contract (C4). Feel free to create an issue or submit patches at https://github.com/weex/pinafore

Just such a mess could be a great test case for C4. Super tempted to setup repos and get it to the point of where a maintainer can press the nice green merge button.

Mining

Is there a cowthink?

Just be mindful of coercion paid or otherwise when voting takes place outside a polling-booth.

@[email protected] are you part of the team? Running a fork? What say you on the maintenance mode?

Not just open source but optional as well. It won’t happen because it would hurt the bottom line but I’m glad it’s being talked about.

More of a high-dimensional trust vector but I get your point. We won’t know the consequences until we try it. Some of the potential advantages are scalability, transparency, optionality, automation, resistance to bots, and decentralization.

My theory is web-of-trust-based moderation can fix this but not on Twitter because they won’t allow such an integration. So we should try it on the fediverse. One of these days I’ll hook this kind of thing up to Mastodon (watch https://github.com/weex/wot-server if you’re interested in knowing when that happens).

I suspect sponsorship on the fediverse is going to be better measured through something at the point of conversion rather than user surveillance. Promo codes instead of impressions.

Are deepfakes a problem? I hadn’t noticed.

On the forks aspect, FOSS culture hasn’t quite got things abstracted enough here. Yes, forks would happen but a lot of value would be destroyed in a sale of the upstream. Our goal should be to make it totally pointless and that’s usually best done with copyleft and many copyright holders. Apt sources could also be more fluid and reputation aware about which repo they distribute from.

We should take inspiration from tiktok from what it does right.

I agree with this. If anyone’s interested to work on a tiktok replacement, let’s find a way to join up and work on making these various right things work in a privacy-respecting, fun, and FOSS set of projects. @[email protected] are you aware of any good rallying points? A new community perhaps or existing software project?

Obviously ridiculous that people put up with this kind of infringement but not unexpected either. Manufacturers access to data should work like it does in open source. A choice given to the user to share anonymized data or not. Remote start and maintenance alerts can be done with privacy if we make it a condition of purchase.

This is fantastic. Reproducible builds help solve the issue of uncertainty that binaries were generated from the specified source code. It’s a key piece of developing more secure software. Thanks for sharing.

I wouldn’t call NFTs a movement. I reserve that word for phenomena that attempt to drive positive social change. NFTs are just a natural product of the digital scarcity that blockchains provide. There is some overlap between FOSS and NFTs in that they share some technology and process. Both depend entirely on the internet. There are some shared motivations some that are unique to each but they operate in such different ways that I don’t see the comparison as being very useful.

Those medical devices use state-of-the-art pen-tested cryptography right?

RIGHT?

Thanks for the share. I didn’t mean to argue. It’s a tough and very broad topic to approach as a technologist, but definitely deserving of study.

I see. Guess I’m looking forward then to hearing more about solutions which don’t use tech.