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).
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?
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 think most people understand that some things need to be secret aka private, like their passwords. I wonder if there are any old folktales about gossip in towns and villages that would be fun to rewrite for now. I named the open source community !magicstone based on one of those old stories and I think it helps get the idea across of building something great through community.
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.