You can do this with an application called patchwork that uses a p2p protocol called ssb (secure-scuttlebutt)
> I still can't communicate with people sitting literally meters away from me
That doesn't seem like a problem that software can solve.
During today's Slack downtime, we just communicated with each other use that old, reliable, uniquely human analog method.
If you're on the same network you can use multicast-dns (like what Chromecast uses)
Absolutely. ad-hoc networks, using sound/bluetooth as a transport. Connected to the same network in general. We have all these things available for us to use, but we haven't so far. (well, there is experiments, but no big application like Slack has actually built something solid and usable with it)
Re:Slack is down
by stephensonsco on Tuesday January 09, 2018 @03:22PM
(#16109635)
build it, you'll have a hit
Re:Slack is down
by decentrality on Tuesday January 09, 2018 @02:49PM
(#16109261)
( Technically an on-premises install solves the originally stated problem, and here the scope increased. P2P doesn't solve the real problem domain either, as soon as you aren't in the same room, a lot of the internet variables return )
It does not. My point is that me and another persons laptop could send packets to each other. But with the on-premises service, I still need to be directly connected for the client to work.
P2P networks can also work even if you're not connected to the same network. Point being that it's a direct connection to the person that you're communicating with, with no indirection.
So you really think there is a serious need for a solution that handles the 1 hour per year or less that services like slack are down? Or are you trying to solve for a location that has spotty internet? Because I have a problem with neither.
Problem still stands, when your self-hosted instance/software goes down, I still can't communicate with people sitting literally meters away from me, connected to the same WiFi. It's incredibly stupid.