Cool idea! But the messages would be populated to all nodes - right? 4 million oO so I’m not 100% sure how scalable the approach really is (but for public feeds in the currently smallish network it would definitely be pretty cool!)
As far as I can see messages only get propagated to nodes that subscribe to that topic.
Please scan this page and let me know what you think.
Since autonomi uses libp2p, it seems like an easy option
Ideally it could just be enabled on the Autonomi nodes by people wanting to participate. Worst case it could just be done as a side messaging network with nodes that form their own network. I do think having it as part of the main network would be ideal though as it could integrate with the file uploading/editing to send notifications to those subscribed.
interesting - they don’t gossip the full content to everyone but just metadata to peers that are not subscribed to the topic - that’s pretty smart and should save a lot of traffic =)
it probably would be worth exploring and testing the nice thing is it would be pretty simple to integrate and would most certainly work for all clients that can connect to the network at all. =)
tbh I’m still a bit skeptical about scalability once we hit a certain point of traction … maybe we shouldn’t care before we hit that point
… (but I don’t think we’ll get the majority of node operators to run pubsub-enabled nodes if maidsafe doesn’t include it in their builds)
feel free to follow that path - I think it would work and would be great - and once the network gets so busy it becomes an issue then we should be important enough that either libp2p resolves the issue for us or we might have capable developers around here that develop a smart way to extend the libp2p pub-sub-standard for our purposes
(meanwhile I’ll follow my path of real p2p udp connections and how well that works or how many issues it surfaces … there’s probably reasons nobody does it out there…)
Why not use the power of Autonomi and store the data immutably on the network (or in scratch-pad if temp) and not on each node, even if subscribed. Imagine something like NASA, or a Soccer club, or …, and you then are filling up millions of nodes with redundant store of data. Yes, when Autonomi is more adopted.
Also you then require each person/device to have a node too. Maybe people want to use it without running a node.
Thanks for checking it out
Yeah it would be useful to have the full support of the libp2p team behind it, and with the size of our network I’d imagine it would get priority focus.
I guess the options would be to fork the autonomi network, add gossipsub and then gather a group of testers to test the limits. Then if that works out it could be integrated into the main network.
Not really sure how it would be decided to be added or not though as we don’t have a governance system yet - although that seems to be on the horizon.
I’m just assuming that writing data would be a lot slower than just propagating messages to subscribers throughout the swarm.
Using gossipsub would be free to use. The main benefit I see would be that you could listen for updates on specific topics - latest file releases etc.
I agree on the node aspect, but I guess the client cli could have features added to listen for messages from subscribed topics from selected nodes, and perhaps the ability to broadcast too.
Yes, much better option.
I’m not entirely sure that can be the case - because it adds burdon to all nodes.
Additional bandwidth usage, caching data for a while to give the network time to propagate the info everywhere before deleting locally again
But subscribers could e.g. Charged a tiny amount per subscribed topic
The thing is with pub sub I can subscribe and just listen for events - when those millions of ‘subscribers’ start polling for a new state every few seconds that doesn’t really sound so much better in my world…
And - as I hinted briefly - when nobody is interested in the content in an area of the network they just get metadata info about the topic while the content only gets delivered to active subscribers
I agree it’s a bit blockchainy… but only temp data and most participants only hold metadata and that probably not for very long
First video site Bitchute, now social media site Gab, blocked in the UK due to threats by the censors at Ofcom:
"The UK’s Online Safety Act isn’t about protecting children. It’s about suppressing dissent.
“The UK’s rulers want their people kept in the dark. Let them see how long the public tolerates it as their Internet vanishes, one website at a time” - statement from Gab
That’s a little misleading in that one of the ways to comply - according to Offcom - is to block UK IPs. I’ve followed a lot of expert discussion of these laws and the main concern has been the impact on small independent sites (eg a gardening forum) because the requirements of complying with this law are onerous (except for large orgs/biz), and the penalties for non-compliance terrifying.
It’s a terrible law though, the the security and privacy community at all levels are unanimous about that as far as I’ve seen.
Yes!!!
Transwomen are MEN.
a small outbreak of sanity.
Two Belgian teens arrested in Kenya, suspected of smuggling thousands of rare ants (VIDEO)
Literally came here to post this. Bet me to it.
The fallout from this has been hilarious.
Dummies are being bigly spat
For the avoidance of doubt, the no of laws changed today was ZERO
These are the people who asked us to “Just be kind”.
Honey give me some time, because somebody on the internet is wrong…
For Deaf Ears:
Reticulum
Reticulum is the cryptography-based networking stack for building local and wide-area networks with readily available hardware. Reticulum can continue to operate even in adverse conditions with very high latency and extremely low bandwidth.
The vision of Reticulum is to allow anyone to operate their own sovereign communication networks, and to make it cheap and easy to cover vast areas with a myriad of independent, interconnectable and autonomous networks. Reticulum is Unstoppable Networks for The People.
Reticulum is not one network. It is a tool for building thousands of networks. Networks without kill-switches, surveillance, censorship and control. Networks that can freely interoperate, associate and disassociate with each other. Reticulum is Networks for Human Beings.
From a users perspective, Reticulum allows the creation of applications that respect and empower the autonomy and sovereignty of communities and individuals. Reticulum provides secure digital communication that cannot be subjected to outside control, manipulation or censorship.
Reticulum enables the construction of both small and potentially planetary-scale networks, without any need for hierarchical or beaureucratic structures to control or manage them, while ensuring individuals and communities full sovereignty over their own network segments.
Notable Characteristics
While Reticulum solves the same problem that any network stack does, namely to get data reliably from one point to another over a number of intermediaries, it does so in a way that is very different from other networking technologies.
- Reticulum does not use source addresses. No packets transmitted include information about the address, place, machine or person they originated from.
- There is no central control over the address space in Reticulum. Anyone can allocate as many addresses as they need, when they need them.
- Reticulum ensures end-to-end connectivity. Newly generated addresses become globally reachable in a matter of seconds to a few minutes.
- Addresses are self-sovereign and portable. Once an address has been created, it can be moved physically to another place in the network, and continue to be reachable.
- All communication is secured with strong, modern encryption by default.
- All encryption keys are ephemeral, and communication offers forward secrecy by default.
- It is not possible to establish unencrypted links in Reticulum networks.
- It is not possible to send unencrypted packets to any destinations in the network.
- Destinations receiving unencrypted packets will drop them as invalid.
The supported interface types include:
- Any ethernet device
- Almost all WiFi-based hardware
- LoRa using RNode
- Packet Radio TNCs (with or without AX.25)
- KISS-compatible hardware and software modems
- Any device with a serial port
- TCP over IP networks
- UDP over IP networks
- External programs via stdio or pipes
- Custom hardware via stdio or pipes
For a more detailed info, and a full list of supported interface types, please read the Communications Hardware and Supported Interfaces chapters of the manual.
Reticulum can also be encapsulated over existing IP networks, so there’s nothing stopping you from using it over wired ethernet, your local WiFi network or the Internet, where it’ll work just as well. In fact, one of the strengths of Reticulum is how easily it allows you to connect different mediums into a self-configuring, resilient and encrypted mesh, using any available mixture of available infrastructure.
As an example, it’s possible to set up a Raspberry Pi connected to both a LoRa radio, a packet radio TNC and a WiFi network. Once the interfaces are configured, Reticulum will take care of the rest, and any device on the WiFi network can communicate with nodes on the LoRa and packet radio sides of the network, and vice versa.
To install Reticulum and related utilities on your system, the easiest way is via pip
Being written in Rust is a clear advantage Autonomi has over Reticulum.
If Reticulum has any advantages over Autonomi, we should identify them and see how they might be incorporated into Autonomi.