The is occasional discussion surrounding the classification of different versions of the #web, such as #Web01, #Web02, #Web03, #Web04, or #Web05, this is not merely an academic exercise but an aspect of understanding the evolving nature of the digital landscape. However, the proliferation of these hashtags leads to confusion and contribute to the spread of fear, uncertainty, and doubt (#FUD) among users, people and communities.
In response to this confusion, proofer to use the hashtags #openweb and #closedweb which offer a clear and concise way to delineate between platforms that embrace openness, transparency, and community control (#openweb) and those that prioritize proprietary technology, centralized control, and lack transparency (#closedweb). By using these hashtags, we foster a better understanding of the ideological and technical underpinnings of different web platforms and paths.
Projects like #indymediaback and #OMN exemplify grassroots efforts to promote decentralized, community-controlled media and communication platforms. These initiatives can become vital in challenging the dominance of large corporations in shaping the digital paths and in offer an inclusive, diverse, and community-controlled approach to technology development.
At the heart of this discussion lies the #geekproblem, which highlights the tendency among technologically people to prioritize technical solutions without considering their broader social implications or the needs of ordinary people. By recognizing the #geekproblem, we begin to address the inherent biases and limitations of tech-centric paths to problem-solving and can then move to advocating for solutions that are inclusive and community-driven.
The solution to this “problem” lies in developing social tech that transcends the #geekproblem and focuses on the needs and perspectives of communities. This needs a diverse group of people in the development and decision-making process and promoting open-source code, open standards, open governance, and open data in technology development. By embracing this #KISS path and principles, we create a more equitable, transparent, and collaborative #4opens ecosystem.
However, this requires overcoming challenges, including the resistance of the status quo and the fear of change. By actively using the #4opens to judge projects, we challenge the prevailing narrative, call out pointless technologies, and compost the #techshit that contributes to the perpetuation of harmful social dynamics.
Moreover, it is essential to recognize that the struggle for a more sustainable future is inherently political. The dominance of large corporations and the perpetuation of #neoliberal ideologies pose significant barriers to any progress. Therefore, it is imperative to mobilize collective action and advocate for policies and initiatives that prioritize, balance the needs and well-being of communities over these profit-driven interests. Without this, the progressive tech dev will fall on barren ground.
In conclusion, the use of hashtags such as #openweb, #closedweb, and #4opens serves as powerful tools for organizing and mobilizing grassroots efforts to challenge the status quo. By embracing these hashtags and the values they represent, we work towards a future where technology serves the interests of the many rather than the few.
The Universal Mandate of SSL: A Critique from the #openweb path.
In the digital landscape, the ubiquitous presence of #SSL encryption, while undoubtedly enhancing security, raises questions about its compatibility with the ethos of the open web. The story around SSL overlooks its ideological underpinnings and the broader implications of its forced adoption. This article challenge the hegemony of SSL by highlighting limitations and proposing a more nuanced approach to internet security.
At the heart of the issue lies the distinction between the #openweb and the #closedweb, represented respectively by the ethos of accessibility and decentralization, and the closed-off, centralized web. While SSL undoubtedly offers security benefits, its imposition on all online interactions reflects not only technical considerations but also ideological stances. The insistence on universal SSL usage is symptomatic of what we term the #geekproblem—an inclination among technologically inclined people to prioritize technical solutions without consideration of their broader societal implications or the needs of ordinary people.
The universal mandate of SSL, championed by tech giants like Google, not only introduces complexities and barriers for ordinary people but also contributes to the unthinking centralization of internet infrastructure. Let’s Encrypt, an American #NGO and a dominant SSL certification authority, epitomizes this centralization, posing a significant risk of a single point of failure. If compromised, Let’s Encrypt could undermine the security of countless websites and services, highlighting the dangers of relying on centralized authorities for internet security.
Moreover, the imposition of SSL as a default requirement creates hurdles for community-run platforms and DIY enthusiasts seeking to establish their presence on the #openweb. The technical intricacies involved in obtaining, installing, and maintaining SSL certificates can be daunting for non-experts, leading to barriers to entry and discouraging participation in the vibrant ecosystem of the #openweb.
Critically examining the motivations behind the push for universal SSL adoption reveals a fear-based path rooted in a conservative ideology of control. By framing SSL as a tool to be judiciously used rather than universally mandated, we can challenge the prevailing story surrounding internet security and advocate for a more balanced and pragmatic approach.
In conclusion, the universal mandate of SSL represents not only a technical solution to security, but also an ideological stance that warrants examination. By advocating for a more balanced and user-friendly approach rooted in the principles of the #openweb, we foster a digital path that empowers communities, fosters innovation, and safeguards social freedoms. It’s time to rethink projects like universal SSL and embrace a more inclusive and decentralized vision of #4opens “trust” based securit.
There is a value miss match that is a core part of the #geekproblem and its relationship to “normal” society. One side prioritises the tech, the other the social, they then ignore each other. Both suffer and become pointless, or likely die out as a species in the era of #climatechaos. Build a bridge or be pointless, or more likely dead in the long term. #OMN#indymediaback#makeinghistory#OGB are bridges.
The recognition and resolution of the value mismatch between technology and society are crucial for addressing pressing global challenges such as #climatechaos. The #geekproblem encapsulates this divide, where one side prioritizes technological development while the other prioritizes social considerations. However, both perspectives are essential for meaningful progress. By building bridges between technology and society, initiatives like #OMN, #indymediaback, and #OGB serve as vital connectors that facilitate collaboration and mutual understanding. These projects recognize that addressing complex issues requires interdisciplinary approaches that integrate technological innovation. By bridging the gap between technology and society, these initiatives pave the way for holistic solutions that can effectively tackle the challenges of our time, ultimately contributing to a more sustainable and equitable future. Failure to build such bridges risks rendering both perspectives ineffective or irrelevant, potentially leading to dire consequences for humanity in the long term. Therefore, the importance of initiatives like #OMN, #indymediaback, and #OGB cannot be overstated, as they play a role in bridging the gap between technology and society and advancing collective efforts towards a better future.
#P2P projects keep failing socially because adoption is tiny. The #Fediverse succeeds socially because it keeps social #UX familiar. The path forward is a half-step strategy: bridge #fediverse + #p2p in real, usable ways until decentralised clients are socially relevant.
We need: Bridges & killer apps, seamless UX that makes federated + p2p content feel like one stream. A server that reads from both channels without making the user care about protocols.
A. what is happening with protocols:
* The #nostr crew are the children of #web3 mess, they are a bit reformed, let’s see. * Then the #BlueSky are the reformed children of the #dotcons * The #fediverse is the child of the #openweb * #dat is a child of the #geekproblem if it is reformed or not, you can maybe tell me? * #SSB was a wild child, now sickly/lonely with the #fashionable kids gathering round #nostr * #p2p was the poster child of the era of the #openweb it was caught in the quicksand of legal issues, the shadow that was left was eclipsed by “free to use” #dotcons Now finds it hard to come back due to mobile devices not having an IP address, thus most people not actually able to use p2p reliably.
Q. ssb has technical shortcomings. It cant sparsely replicate data and verify it. It needs to download all data ever created by a user to verify, which makes it infeasible for many use cases. The main underlying data format is also hard to fix and leads to performance bottlenecks. The main founder moved on and it seems most ssb people are also looking for a new home. dat’s time has not yet started as it approached things from a much more fundamental perspective. The initial vision was “git for any kind of data”, which means “version control for any kind of data” (peer to peer). The stack only now reached maturity to build proper tools on top of it. You have the dat-ecosystem with 2-3 dozen projects. You have the holepunch/pears project which built a phenomenal “never on a server” desktop/mobile p2p video conferencing messenger with built in file sharing. The app works flawless on mobile and is called https://keet.io Also https://dat-ecosystem.org just now released it’s new website. The https://pears.com runtime will be live in 5 days from now on the 14th of February for anyone to start hacking on p2p apps and some time later, the plan is to integrate it into the dat-ecosystem website, so anyone can start using p2p from within dat-cosystem page (which is an open source static website anyone can fork to get to the same) …no back ends required. pears 🍐will only start working on the 14th of february. You can set a reminder. The revolution starts then 🙂
A. will have a look, there are a few new #p2p projects reaching use at mo – the issue is none of them link to each other and likely thus non inter-op. This is the #geekproblem
Q. I don’t think there are any mature projects out there other than dat and ipfs. The former made by open source devs, self funded with a bit of help from public funding bodies, while the latter is the poster child of venture capitalists and got gazillions from investors. It’s the “big tech” of p2p. Then you have a few less general purpose p2p projects which popped into existence in the last few years, but both dat and ipfs go back all the way to 2013 and it takes a lot to get things smooth and stable and support all use cases and get enough critical adoption and nodes to make the p2p network work. That is why dat-ecosystem has a lot of existing projects that work and why it is reliable to build on top of it. I do think the new more recent p2p projects in research state might become mature as well, but it will easily take them a few more years. Many of those newer projects have people working on them part time only or focus on really special use cases and only time will tell if their approaches will bring something new to the table or not. 2024 will definitely be the year of dat, especially after February 14th, when pears.com goes live. This has been years in the making. What started 2013 as (git for data) will now finally become it’s own independent p2p runtime. Goodbye nodejs & co. …and soon goodbye github & npm 🙂
A. https://holepunch.to/ its a very sparse website with no company info or #4opens process – it looks and feels like meany #dotcons if these projects do not link to each other or inter-op then they will fail like the hundreds I have seen fail over the last 20 years of this mess making. it’s a problem we can’t keep doing this shit, but we do. #4opens is a shovel to help compost this, can you do a write-up for these projects please.
Q. dat-ecosystem is a 501c3 It’s Code for Science and Society And it is https://opencollective.com/dat And it is governed by a Manifesto. It is all on the website next to the “Info” button in the upper left corner. If you mean pears.com ….that will change on February 14th I didn’t mention holepunch. Holepunch is just one of the many dat-ecosystem projects. It is special, because one of the core developers of dat started it after he got a lot of funding and is currently maintaining many of the important code that powers dat and the dat-ecosystem projects. But it doesn’t matter too much. The stack is open source under MIT and Apache 2.0 License for anyone to use. If holepunch would ever decide to stop maintaining the stack (which we do not think), dat-ecosystem can find other maintainers.
A. they are the owners of https://keet.io always look for ownership in #dotcons 🙂 a few of the ones I have been looking at over the last few years https://www.eff.org/deep…/2023/12/meet-spritely-and-veilid and the was a another one funded by NLNET they recently whent live, but can’t find the link. None of them link or interop, not even bridges. This is the #geekproblem
Q. Spritely is a great project. It embraces the ocap security model (Object Capabilities). It does apply it in lisp/scheme, which is a great fit with GNU Guix. Their foundation is led by Randy Farmer. Randy Farmer co-created Habitat with Chip Morningstar (an MMORPG) in the 1980s. Chip Morningstar works with Mark Miller (Mentor of Christine Lemmer Webber). Their project is called “Agoric”, which is a blockchain projcet funded by Salesforce. They have their own Token and build a “Market Place”. They as well work with ocap security model (but in JavaScript). The JavaScript ocap version is what is known as SES and Endojs. They regularly talk to make sure things are interoperable. Ocap security is also what dat-ecosystem is embracing to pair it with peer to peer and bring it to the post-web. A version of the web not dominated anymore by big tech and big standard bodies.
#Veilid is a young and interesting project as well with a focus on anonymity over performance. This is a great use case that needs support, but dat was always about performance and any size of data and anonymity and privacy at all costs. I’m not saying that is an unimportant use case, but there are plenty of solutions for extreme cases where anonymity and privacy are at utmost importance. What is vastly more important imho is to have a p2p technology able to replace mainstream big tech services such as youtube, facebook, instagram, tiktok, google & co. because it won’t help us if we have a special niche technology that cant actually tackle big tech and surveillance capitalism but gives people some way to hide from it. …we need it too, but we also need a foundation on which to actually outcompete big tech imho.
Keet is a closed source peer to peer messenger & video conferencing app (might be open source in the future) and it is built on top of the dat stack. The dat stack is very modular and in it’s core consists of a few main modules. – hypercore, hyprebee & hyperdrive – hyperdht & hyperswarm – autobase Those modules are maintained by holepunch, an organisation started by one of the core dat developers afte rreceiving a lot of funding to develop keet and now the pear runtime, which will be open source and public under https://pears.com after February 14th 2024 (Valentine’s Day ❤) Keet itself is one of many apps, all part of the dat-ecosystem. Most projects are open source, but not all, but they are all built on top of the MIT/Apache licenses p2p stack, which started as `dat` in 2013 and matured many years ago. The stack is battle tested and really works. Of course – we all want everything open source and one day we might find a model, but if some closed source apps help bring in funding, it benefits the open source core. Basically, you can think of “keet” as some fancy UI/UX on top of the open source software stack. Now sure – would be sweet if the UI/UX was open source as well, but then again, it’s not essential and until we transition into fully automated luxury Communism or whatever else works, something pays the bills and enables the open source core to be maintained 🙂 At least it works without any “Cloud Landlords”. No servers, never on a server. No more cloud lords, a.k.a. Big Tech or #dotcons
A. The best we have currently is #ActivityPub DIY federated – this is community based (but fails in code to actually be this) which in meany ways is complemtery to #p2p based approaches – they are better together and if the can bridge or interop this is MUCH better, the #OMN is native to this.
Q. Yes. dat is very low level. It would be cool to see somebody implement an activity pub based tool on top of it. One dat-ecosystem project did it for nostr, but no activity pub yet. I’m personally more interested into a desktop, terminal, version controlled data and software packages. “Social” tools are just one type of tools to built on top of the more fundamental p2p network and p2p system infrastructure. I do think dat is good for laying these foundations, but “social” tools are a layer that dat as a stack will probably never focus on, but instead dat-ecosystem projects will hopefully take on that challenge 🙂
A. Some people are community based federated (the start of this conversation) others are individual, the #p2p world you talk about. This is not a fight they are both valid. As you say what we don’t won’t is more #dotcons 🙂 Good conversation on the state of #p2p I used to be much more involved in this side, but it failed with the move to #dotcons so got re-engaged when ActivityPub came alone the rebooting of web 1.5 😉 are you happy for me to copy this to my blog, can credit you or just use AQ anonymous format?
Q. any way you want. I dont think p2p has failed. the p2p of the past was naive kids playing and it took a decade of adults and all the law enforcement they had at their disposal to bring it down and despite that torrents still run and even the piratebay continues to operate, although heavily censored. Back then it was a few devs and a majority of users. This time p2p is back and will enter mainstream open source developers after February 14th 2024 (5 days now). This empowers an entire generation and anyone who wants to dive into p2p to build any kind of tool. What was once hard and reserved to a few will be available to everyone. We might see another nodejs/npm movement. It loads a bit slow, but load this and check “all time” This is the largest open source ecosystem humanity has ever experienced. http://www.modulecounts.com/ And while npm/github have been hijacked by microsoft, we will claw it all back soon Btw. regarding Spritely and the backstory behind OCap, even though extremely technical in description, here is a summary of the work by Mark Miller et. al. https://erights.org/history/index.html https://en.wikipedia.org/wiki/Mark_S._Miller > Miller has returned to this issue repeatedly since the Agoric Open Systems Papers from 1988 Mark Miller is Christine Lemmer Webbers Mentor. He works with Chip Morningstar (who with Randy Farmer did Habitat in the 80s) Randy Farmer is Executive Director of the Spritely Institute. Agoric is the Cosmos Framework based Blockchain now. https://agoric.com/team
A. Interesting to look back at all this stuff, reminds me I had dinner with https://en.wikipedia.org/wiki/Ted_Nelson in Oxford 20 years ago, he was a little eccentric with a clip on digital recording device, every convention had to be record. good to catch up with history https://www.youtube.com/watch?v=h-t405_JAJA that is more relevant today.
Q. Yes – peer to peer is hard. Not as a user, it is actually easy enough, but as a developer. Building p2p is not taught anywhere and there aren’t online learning resources the same way you can learn how to set up your react app, etc… This will change after February 14th 2024 when the pears.com runtime is released. It is powered by the same p2p stack that developed with dat since 2013. If anyone of you is a developer or has friends who are, you are all invited to dip your toes into the dat water 😛 …and start a new p2p project and join the dat-ecosystem 🙂 It will get quite easy in 4 days from now and it will again get a lot easier in the coming weeks when more examples and docs are publishes and others build as well. The Storyline around Mark Miller, Randy Farmer & Chip Morningstar is totally separate from it, but it is also important, because it is what powers 1. the Spritely project and Christine Lemmer Webber 2. the Agoric Blockchain Project backed by Salesforce 3. the Ethereum Metamask Wallet and Co. It also influences the big standards bodies and I see it two fold. It’s a story about philosophy, values and vision driven by the specific people in it. It is also a story about “object capabilities” which is a powerful perspective on security and will enable and inform a lot of p2p interaction which without would require some sort of centralized servers, but with ocap can do it on it’s own p2p
A lightly edited conversation between Hamish Campbell (A) and Alexander Praetorius (Q)
The #nostr crew are the children of #web3 mess, they are a bit reformed, let’s see.
Then the #BlueSky are the reformed children of the #dotcons
The #fediverse is the child of the #openweb
Q. Where would you put #dat or #ssb and in general the #p2p post-web tools?
A.
#dat is a child of the #geekproblem if it is reformed or not, you can maybe tell me? #SSB was a wild child, now sickly/lonely with the #fahernable kids gathering round #nostr #p2p was the poster child of the era of the #openweb it was caught in the quicksand of legal issues, the shadow that was left was eclipsed by “free to use” #dotcons Now finds it hard to come back due to mobile devices not having an IP address, thus most people not actually able to use p2p reliably.
A series of seminars to commemorate the death of J. R. R. Tolkien, to be held in 2023/2024 in the University of Oxford. The talks present an introduction and further background to Tolkien’s life, work, and legacy. They have an academic approach, but they are also aimed at those who have read Tolkien’s work but are interested in gaining a bit more insight into his life, career, and writings.
Week 1 – 19 January (MERTONCOLLEGE T.S. ELIOTLECTURETHEATRE)
Mark Atherton (University of Oxford)
The Arkenstone and the Ring: wilful objects in Tolkien’s The Hobbit’
Draft
Wilful objects in the Tolkien’s work, thinking about embedded AI in ten years, and mobile phone now. This world could become like Tolkien world after the #climatechaos claps in 50 years.
I have been in Oxford for the last month, attending university talks and seminars on subjects of interest. And I am seeing the normal issues of https://en.wikipedia.org/wiki/Mannerism this is an “art” way of expressing the issue but it’s a good description of much inward looking thinking. Their answers when questioned on this are https://en.wiktionary.org/wiki/Panglossianism#English in that, It’s not as bad as you think, “am more positive” etc.
We need to think of a serendipity view of how #hashtags work and how our coder kings implement them (#feudalism). Not saying this is a good aproch… i don’t know… but spelling hashtags “wrong” makes their use in categorization and sorting work differently. Might be worth thinking if this could add value or is purely negative? This depends on different views on federation and ideas of a universal truth or messy “truths”. Composting thought on this.
In the #OMN coding project, currently offline (unite.openworlds.info) we add word grouping flows, so you can say one hashtag is the same as another, ie. you can group different “meanings” to build category flows. This makes misspelled hashtags functional, and our current coding broken from the #OMN point of view.
It’s not implemented, is a speck projects so can’t test this. Over the last year I have put 5 #FOSS funding applications in to try and get this built, 3 turned down so far 2 more to be turned down (cross fingers and toes not) soon. Our #AP#openweb reboot is being destroyed by our #fahernistas and #geekproblem nothing new here, but we do need to do better.
That’s what we set out to fix 20 years ago, with the #OMN still digging, but my shovel has no handeal nor a head… says the man on his knees hands covered in shit… composting worthwhile however you do it, I could not make this shit up… but we keep making more #techshit
The#OGB is important to develop better ways of having “trust” based conversations and “trust” based “governance” in the #openweb. It is built on years of on-the-ground organizing and emphasizes the need for voluntary cooperation and collaboration. The project recognizes the problems in alternative tech, starting with the #4opens to remove complexity to building governance structures that are native to the #fediverse. The #OGB address the limitations of #mainstreaming approaches.
The #OMN (Open Media Network), is a decentralized network of media sites that share content and promote independent media. It aims to provide an alternative to mainstream media by creating a network of interconnected sites that prioritize openness, collaboration, and decentralization.
The #OMN project emphasizes the importance of grassroots community-driven media, where people and groups can create and share their own content. It seeks to challenge the dominance of #mainstreaming media and promote a more equitable and just society.
The project has been running for over ten years and operates with an #openprocess. Users can become mods after being involved for a certain period of time. The modding process is based on a clear project statement and encourages a respectful and inclusive community.
The #OMN project is closely related to the #visionontv project, which is a grassroots media project that creates and distributes independent video content. The two projects share similar values and goals in promoting alternative media and challenging mainstream narratives.
The #indymediaback project is a reboot of the original #Indymedia project, which was a decentralized, grassroots media network that emerged in the late 1990s and early 2000s. The project aims to learn from the mistakes and challenges faced by the original Indymedia, particularly the split between the #fashernitas and #geekproblem factions.
The focus of the #indymediaback reboot is to return to the path of the #fashernista, which emphasizes open media and decentralized structures, rather than control and centralization. The project aims to build an open media network (#OMN) that promotes direct democracy, open publishing, and anti-authoritarianism.
The reboot also acknowledges the risk of another split within the community, particularly if some members push for a control/encryptionist path. The challenge is to find a way to navigate this without succumbing to tribalism and power politics.
The #indymediaback project recognizes the importance of hashtags and semantic web technologies, which were not core to the original Indymedia project. Tags and metadata are being used to help organize and categorize content.
Overall, the #indymediaback project aims to revive the spirit of open media and grassroots activism, while learning from past mistakes and embracing new technologies and approaches.
Narrator: In a world dominated by #mainstreaming narratives and centralized control, there is a project that dares to think differently. Introducing the #OGB project, an initiative focused on developing trust-based conversations and governance in the #openweb.
[Visual of people engaging in conversations and collaborating]
Narrator: The OGB project is built upon years of on-the-ground organizing, shaped by long expirence of on the ground organization and a Keep It Simple and Sustainable (KISS) approach. To kick this off lets look at it as a native way of working within the #Fediverse, a decentralized social media network.
[Visual of Fediverse logo]
Narrator: The goal of the OGB project is not to dictate protocols and standards to the Fediverse, but rather to create voluntary cooperative and collaborative alliances. It aims to overcome the challenges faced by existing social platforms and build a platform that truly serves social good.
[Visual of diverse group of people working together]
Narrator: The OGB project believes in the power of self-organization and user-driven processes. It draws inspiration from the example of Couchsurfing, where a redesign that removed DIY tools led to disappointment among members. The OGB project advocates for letting members shape their own processes, in the #4opens path, to overcome the #geekproblem and foster hope for alternative technology to shape society.
[Visual of people using DIY tools]
Narrator: Governance is a key focus of the OGB project. It aims to build governance structures that are accountable, sustainable, and inclusive. The current governance of the Fediverse can at best be described as “herding cats,” but the OGB project seeks to change that by providing a sortation based framework for effective governance.
[Visual of people discussing and making decisions]
Narrator: The OGB codebase is not limited to the Fediverse; it can be used to democratically run any structure with stakeholders. For example, it can be applied to govern a local street market, with stallholders, shoppers, and affiliated groups all having a say in decision-making.
[Visual of a street market]
Narrator: The OGB project recognizes the unique power dynamics within the Fediverse and aims to build upon its differences rather than conforming to mainstreaming agendas. It emphasizes the need to empower people to do better in alternative technology and socierty.
[Visual of people breaking free from chains]
Narrator: The OGB project acknowledges that there are problems in alt-tech but believes that starting with the #4Opens principles can remove much of the mess and unlock the true potential for positive outcomes.
[Visual of 4 Opens principles]
Narrator: Ultimately, the OGB project is about challenging the status quo, questioning the mainstreaming narratives, and from this pushing to creating a more equitable and just society. It invites those who can think outside the box and are willing to challenge mainstreaming to join this movement.
[Visual of people joining hands]
Narrator: The OGB project is a call to action, a call to build a better future for the openweb.
#Mastodon and the wider #fedivers are native #openweb project based on the #4opens people who try to “harden” and “secure” these are completely missing where the value is at.
They are spreading #FUD and endangering real activists acting this way.
Anything that is not media should use encrypted p2p chat, there are many mature #FOSS projects for this.
At the moment as the #Fediverse is a #OMN based on the #4opens you have very low barrier to running or even developing an instance, this is where the value is.
Adding security generally makes a HUGE barrier to Dev and #DIY running an instance.
The #geekproblem has no idea of the damage they do when pushing their “common sense”. This creates a signal-to-noise issue that has been blocking alt for 20 years.
The #Fediverse is all #4opens so should not be used for anything that should be P2P encrypted. It’s important to keep this clear to users by not focused on the fig leaf of “hardening” security as the is non. It’s a very successful #OMN open media network, and it’s value lies in this.
Peoples pushing this are often not seeing the point that it’s designed #4opens this is why it works.
Both paths have value, but they are different.
And the push a different project (#closedweb) which is fine. But not a #OMN maybe they would be better off working on bridges as companion projects.
Good to think about this mess they talk about as it is not solved by more tech, we already have most of what we need.
* Open media is #4opens based on trust, the current ActivityPub is a relatively #KISS good example of this.
* Privacy is encrypted p2p chat, which there are meany good #UX mature #FOSS projects you can find
The change we need is social, getting people to use the different approaches for different needs, this is surprisingly difficult.
Bridges while dangerous are needed here, it’s good to talk about this in the sense of “security”.
This text reads like a vanguards path, based on #mainstreaming reading and narrow #geekproblem thinking. It’s missing the paths that hold value in #4opens horizontal activist paths we are building. But yes, we are getting lost in the growing #fediverse and the wider spread of #openweb reboot diversity projects.
What it does highlight is the need for social and political thinking is needed, the is value there.
It’s hard to stress how “nave” meany devs on the #fediverse
#openweb#4opens is about building human trust, hard security is a very slightly overlapping but easy to see different path for building non “trust” based connections.
Some surprisingly hard to build bridges might help with this ongoing mess.
