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.
@email@example.com are you part of the team? Running a fork? What say you on the maintenance mode?
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).
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.
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. @firstname.lastname@example.org 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.
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.
Recently was talking with someone and they said “fediverse and metaverse” in one breath and I was like whoa. I don’t think anyone wants to give Facebook even Meta let alone metaverse.
The two concepts share very little except the rhyme. I see the term as really up the air so I’d only use it if I wanted to confuse people.
You mention some quite different kinds of sites. Reddit and Lemmy are more social in nature. The value is less in searching the history for answers to common questions than in hanging out, joking around, sharing ephemeral links.
StackOverflow tuned their platform to the Q&A use case so I feel like they should have discouraged reposting in some way. If the question is a good one, many others will search for it later and some will have solutions to add.
Sounds like it’s kind of handled with Dessalines comment but given what I wrote above. No, unless…
Here’s where taking a more expansive and experimental view of open source can come into play. If you want toallow necrobumping, then I would ask what problem it solves. If that is a valid problem, then by all means fork Lemmy, add that as a feature to your instance and try it out. If it works, then you’ll have proven its value or lack thereof with its chances of being added upstream either bolstered or rightfully crushed.
Yep, one thing about a headset is that it monopolizes your vision and if you can build the virtual environment, you can choose what is and isn’t there. After getting bored with the apps and games on the Quest I decided to explore the most basic part of it, the home environments. In that environment it’s possible to open up multiple browsers so I opened one to a CryptoPad, connected a bluetooth keyboard and simply sat there noting problems with the environment and experience.
Since then, I found an app/framework called Lovr that enabled me to build the environment I want in Lua and to chip away at the issues I found. Forked a virtual development environment called indeck to suit my needs here https://github.com/weex/indeck/issues
I understand your concern and it’s a great issue to raise but I disagree that there’s nothing to be done. I look at it as a competitive landscape where we FOSS devs will create our own spaces and culture. If we want to provide an alternative that the masses will prefer then then that’s a specific goal that would involve a huge amount of investment, probably on par with what FB’s doing.
The open source way is slower, more viral and ultimately covers more of what people want to do all the time. I think there’s tremendous potential in pioneering how VR can be used for good and using open source software to do it. Maybe FB goes out and paves everything over and it’s up to us to grab what we can and be ready when their stuff crumbles.
100%. Everyone simply needs to clarify their reasons for using and working on FOSS. Last year I learned that building a community around a project is more important than the technical details. License matters as well because permissive means a company can take the code and compete with the community which is disheartening. Copyleft is therefore essential.
Forget the Metaverse. We’re at very early days with VR. Just spend some time using an Oculus, play some games, and then try to imagine what it would be like to have the thing on for longer than 30-60 minutes. First there’s making these things comfortable. Then there’s making these virtual environments useful for something besides games.
I’ve spent the last several days diving into VR, trying to see if I’d want to work inside it, if it would provide any benefits, and documenting the issues.
There are many issues. It’s so disconnected from our normal digital lives. Facebook buying Oculus screwed it up (there are scripts to de-facebook the device apparently) and resolution still isn’t great.
If you want to get involved with FOSS VR, check out Lovr. There’s a neat in-VR Lua editor (inDeck) that you can use to develop whatever you want. In my case, I feel a big strength of VR is control of attention since you can’t see anything that wasn’t intentionally put there. So, in pursuit of a better development and writing environment I started a new repo. Here’s a little video of what it looks like. https://c4.social/@weex/107556016704877363
Anyway, I wouldn’t worry. Code if you want. Write about your vision. Join efforts like Lovr or help me out with my repo. Let’s not get sucked into the shiny object they’ll be pedaling with their billions and just work toward the world, virtual or not, that we want.
I only considered about five projects, which was kind of silly considering there are dozens of projects out there and Hubzilla in particular I’ve heard about a lot. We could definitely use more different perspectives on how things can work in Magic Stone, it being so early, and with so much we don’t know. My perspective then was as a developer with a grand design for experimentation that has been replaced by the more incremental C4 process.
I love the symmetry implied by a universal gateway that speaks so many protocols and understands how to map from one to another. In that vein a project called the-federation once worked on testing various protocols in one place and I bet a lot of that still works. Could be neat codebase to play with. That being said, it’s best for our community if we get to a problem statement. In this case, it might be something about disconnection or tribalism or lack of a global view, one fediverse kind of idea.
It would be great to get your thoughts on this issue about pulling AP timelines together. Maybe once we solve that, or even in parallel, someone will pose another problem of collecting non-AP data and things will evolve from there.
Great question. The story started earlier in the year when I started thinking more seriously about social media and what a better future for it might be. I came to the conclusion that nobody really knows so experimentation was key. This led to a survey and looking at which projects were popular and established enough to be a good platform for experimentation, and could also use more development energy. Mastodon and diaspora* were the best candidates.
At that point, I realized it’s not only a problem of not knowing what better social media looks like, but that I don’t know how to run a successful open source software project. That’s when I found Pieter Hintjens and the Collective Code Construction Contract (C4) that he developed with the ZeroMQ community. The core idea there is that it is the community that is primary, not some codebase, or feature, or framework. Only with a strong community can software be developed and maintained long-term to meet the needs of the market.
It’s at that point that c4social was formed (later becoming Magic Stone) and Mastodon was forked. Once we realized the job of maintaining a repo under our process isn’t too difficult, we decided to also fork diaspora*. C4 hasn’t been applied anything in social media so part of the opportunity for this community is to test whether it can work, and a good experiment is reproducible so two projects is better than one in this respect. Since then we’ve just been solving problems that come to us through using the software and from those who stumble upon posts like this. The community is small, growing nicely and starting to yield interesting results as far as the software goes.
So that’s how we came to diaspora* AND ActivityPub! :)
As far as intention goes, we can’t say. We don’t have a roadmap, or assigned tasks, or releases. Our issue trackers are populated with problems and developers who get excited by any one of them are invited to submit pull requests. To your question about s2s, I would invite you to check out https://github.com/magicstone-dev/acropolis/issues/92 and share, comment, click emojis, whatever you want to do to help prove it’s value and raise the probability that someone will work on it.
tl;dr We do both, and we have no intentions either way but check out https://github.com/magicstone-dev/acropolis/issues/92
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.