weex Now • 100%
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.
weex Now • 100%
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
weex Now • 100%
Mining
weex Now • 100%
Is there a cowthink?
weex Now • 80%
Just be mindful of coercion paid or otherwise when voting takes place outside a polling-booth.
weex Now • 100%
@meloo@lemmy.perthchat.org are you part of the team? Running a fork? What say you on the maintenance mode?
weex Now • 100%
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.
weex Now • 100%
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.
weex Now • 80%
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).
weex Now • 100%
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.
weex Now • 100%
Are deepfakes a problem? I hadn't noticed.
weex Now • 100%
Have you considered looking at a web of trust? I've implemented one in python and intend to connect it to a fork of Mastodon at some point, but you may find it useful as a way to resolve trust links among a network of participants.
weex Now • 100%
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.
weex Now • 66%
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. @libre_warrior@lemmy.ml are you aware of any good rallying points? A new community perhaps or existing software project?
weex Now • 100%
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.
codeberg.org
It is with great pleasure that I can share the following two standards documents that were finalized this past week under the Fediverse Enhancement Proposal process: [FEP-400e: Publicly-appendable ActivityPub collections](https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-400e.md) "describes how ActivityPub servers and clients could specify collections to which objects created by their actors belong." [FEP-8fcf: Followers collection synchronization across servers](https://codeberg.org/fediverse/fep/src/branch/main/feps/fep-8fcf.md) "describes an optional mechanism for detecting discrepancies in following relationships across instances, with minimal overhead and without loss of privacy." It is hoped that documents like these can form the basis for greater interoperability between services on the fediverse. View these proposals, additional draft proposals and the proposal submission process at https://codeberg.org/fediverse/fep
weex Now • 100%
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.
weex Now • 75%
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.
weex Now • 100%
Those medical devices use state-of-the-art pen-tested cryptography right?
RIGHT?
weex Now • 100%
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.
Acropolis is fairly similar to diaspora* at this stage with the key difference being that being managed via the Collective Code Construction Contract which prioritizes the community around software over the technicals. Sign up at https://dogieda.org if you want to try the early results. 🛠️ If administration is your thing, #YunoHost is the easiest way to install #Acropolis. Version 2021.12.02~ynh1 still requires initial account creation via web interface and promotion to admin via command line but in the near future, admin account creation will be more seamless. Link to install on your YunoHost box: https://install-app.yunohost.org/?app=acropolis ⚠️ Please report issues at https://github.com/YunoHost-Apps/acropolis_ynh/issues
Hi folks, Just posted https://lemmy.ml/post/90538 and here I want to discuss if Magic Stone should make any efforts towards this kind of integration and if so between which platforms.
With yesterday's release of Lemmy v0.14.0 and all of the excitement around federation with Pleroma/Mastodon it makes sense to have a thread just about the federation and what it all means. Some questions: * Have you tried it yet? Why or why not? * How do you plan to use this new connectivity? * Any problems or friction? What could make such a feature more useful to you? I've tested talking back and forth in the comments, seen my Mastodon profile from Lemmy, and followed some subs from Mastodon. Since I get audible notifications on Mastodon, I suspect that following sublemmies can be good for jumping into Lemmy Posts in realtime. I was skeptical if cross-platform federation would find much usage, and it's still not clear which way it'll go, but there's no denying that this kind of development is unique to the free-wheeling fediverse and that this would never exist on CWeb without even bigger tech monopolies. Being able to try things out like this is one of the reasons I'm spending more and more time here. I mean, how can you not be excited about this kind of experimentation and development? Finally, I can't imagine all the work that went into this and want to give a huge thanks to the Lemmy team for making this work.
Case sensitivity was I think the extra bit of challenge that I didn't expect. The audio rendition was also only the first character. I don't see a related issue in the tracker and I'm not sure if this is local to lemmy.ml or global to all lemmys. But, first since I was able to get in, is this a problem that needs to b solved? Edit: Created issue https://github.com/LemmyNet/lemmy/issues/1640