If we're looking for federation (at least one-way from this site to the website being linked) in Raddle, we should go Webmention IMO instead of ActivityPub. It's a W3C standard like AP, and you don't have to deal with JSON or XML or whatever!
]]>as of now, IPFS and FIlecoin are completely separate-- files on one cannot be accessed on the other.
]]>Any question, please take a look here you might find the answer.
Thanks!
]]>Also I'm wondering if it's worth it if I'm using mastodon already. What sets it apart?
]]>It is time to take action, and that doesn’t mean signing an online petition, upvoting a Reddit post, or calling your member of Congress.
Read More: Sorry, Ajit Pai: Americans Won't Forget Net Neutrality Over Thanksgiving
Net neutrality as a principle of the federal government will soon be dead, but the protections are wildly popular among the American people and are integral to the internet as we know it. Rather than putting such a core tenet of the internet in the hands of politicians, whose whims and interests change with their donors, net neutrality must be protected by a populist revolution in the ownership of internet infrastructure and networks.
In short, we must end our reliance on big telecom monopolies and build decentralized, affordable, locally owned internet infrastructure. The great news is this is currently possible in most parts of the United States.
There has never been a better time to start your own internet service provider, leverage the publicly available fiber backbone, or build political support for new, local-government owned networks. For the last several months, Motherboard has been chronicling the myriad ways communities passed over by big telecom have built their own internet networks or have partnered with small ISPs who have committed to protecting net neutrality to bring affordable high speed internet to towns and cities across the country.
A future in which ISPs are owned by local governments, small businesses, nonprofit community groups, and the people they serve are the path forward and the only realistic way of ending big telecom’s stranglehold on America.
In Detroit, the Equitable Internet Initiative is building community-owned wireless internet infrastructure in towns that big telecom won’t touch. Hundreds of towns have built their own internet service providers. Rural communities are putting wireless internet antennas on top of mountains, grain silos, and tall trees. The fastest internet connections in the United States are provided by local governments, not big telecom. In Southern California, Tribal Digital Village is using unused television spectrum to deliver internet. All over the country, big telecom is being rejected and subverted, and you do not need to have a pile of money, an army of lawyers, or a degree in network engineering to take action.
Motherboard has and will continue to celebrate and amplify these projects, but that is not enough. Starting immediately, we will:
Begin researching and publishing technical articles and videos that explain how new wireless networking hardware and software works, how to use it, and how to use currently available, affordable technology to start your own small internet service provider.
Speak to activists, entrepreneurs, lawyers, technologists, networking engineers, and politicians who have navigated the technical, legal, and political hoops required to start community-owned internet service providers. We will use those conversations to create clear instructions for how you can empower yourself to do the same.
Begin creating a comprehensive guide to the various new technologies and methods of creating decentralized internet infrastructure, which will be released next year.
]]>Hello everyone! We have a lot of news to cover, but I’m going to jump right into the thick of it: we’ve been working hard on a new federation (as well as client to server) standard called ActivityPub (formerly ActivityPump). We’ve made tremendous progress, and I was just recently at a face to face meeting at TPAC, the W3C’s big technical conference.
The good news: ActivityPub is aiming to hit Candidate Recommendation status by October 11th. (That’s less than a week away!) However, in order to enter that stage, we need your review! If you have any interest in the decentralized web, you can help. All you have to do is read the latest editor’s draft and provide feedback. (The earlier the better… maybe a fun weekend project?) You can do this by any of the following:
The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.
]]>Enter CRDTS, Conflict-Free Replicated Data Types
CRDTs are one of the hot interesting topics in distributed systems. They provide a conflict-free manner of replicating data across multiple nodes without ever having to elect a leader or use another type of centralized authority to reach consensus. They even allow nodes to reach the same state without being connected to the network at the same time.
CRDTs were first introduced in 2011 by Carlos Baquero, Nuno Preguiça, Marek Zawirski and Marc Shapiro. You can learn more about CRDTs in the IPFS research collaborative notebook on CRDTs.
By forming ad-hoc sets of nodes (ie. using pubsub) and using CRDTs, nodes can come in and out of a cluster and participate in a higher level protocol.
Use case: Collaborative Text Editor
One set of use cases for CRDTs is when nodes need to collaboratively write to a shared data structure. In the past, this has been achieved by relying on a centralized service to coordinate updates. This centralized approach encourages the wordlwide web to grow in a way that relies on a few private entities to control the the content and delivery of the web. This is neither safe nor scalable. We must move away from centralized services, instead relying on truly distributed peer-to-peer systems that are not controlled by a single entity.
In this 10-minute video I show you how we can use the js-ipfs library and conflict-free replicated data types (CRDTs) to build a simple text editor that allows several peers to collaborate in real-time. The resulting interactions between the nodes are conflict-free, support offline use, and allow nodes to come in and out of the network while continuously converging data to a single state in all the nodes.
https://www.youtube.com/watch?v=-kdx8rJd8rQ
Final Remarks
Real-time collaborative applications are in their infancy but in the future they will be the norm. Achieving this will be a huge challenge since, in reality, the majority of the devices on the internet are poorly connected, relying on (often mobile) networks that offer little to no reliability.
Any node should be able to perform changes in a shared data structure even if the underlying network is not reliable. The system should be able to converge these changes into all participating nodes. Nodes should be able to enter and leave the network (either by their own will or because of network conditions) while the system ensures that this does not lead to losing data or threatening convergence.
What protocols and data structures will allow participating users and their nodes to form ad-hoc networks for spontaneous or planned real-time collaboration without any centralized coordination?
Peer-to-peer networks can rely on special replicated data types that are distributed and conflict-free, and were built specially for these scenarios.
If you’re interested in this subject and / or would like to learn more, I invite you to join the conversation in the research-CRDT repository, poke around in the available articles and lectures and contribute.
]]>What equipment could be utilised for this? It would need to be long range but low watt and weather proof.
]]>