10 ms·
When things like this happen, I start thinking how much we got some things wrong, especially things like chat. Here I sit, with my colleagues, connected to the
by diggan 9y ago
When things like this happen, I start thinking how much we got some things wrong, especially things like chat.
Here I sit, with my colleagues, connected to the same network, with the same application open, but we cannot write to each other, because some backend server in the US have a problem.
How in the world could this not have been fixed yet? Our internet backbone addiction is seriously crippling us when things go sour. Not thinking specifically about Slack, but other more mission-critical tools that just... stops working because they cannot ask the time from their backend server.
We seriously need P2P systems (without blockchains please) that can be used by normal applications to solve issues like this. Offline and local network communication should be obligatory today.
- rwmj 9y agoWhy not simply use IRC?
- ben174 9y agoAt TiVo we used IRC. It was so nice.
- diggan 9y agoMy fear is not about Slack specifically, but in general the tools we're using today. They all assume that you have a internet connection at all times, and they just break when I don't. Even though when it's just about passing a few JSON objects around, that could easily be sent locally.
- cgag 9y agoemojis
- strictnein 9y agoASCII art > emojis
- cgag 9y agoyeah but doing gifs is brutal
- MaxLeiter 9y agohttps://sr.ht/lP5u.png https://sr.ht/lP5u.png
- throwanem 9y agoBecause, while you can by dint of extreme effort produce a user experience with IRC that's broadly comparable with what Slack offers out of the box, doing so requires so much relatively rare expertise, and so much more support investment, that it's not cost-effective to do so.
- walrus01 9y agoWe have an IRC server that lives in private IP space and is only accessible by VPN. It was not rocket science to set up. If you think that running ircd-hybrid on debian requires "rare" expertise, then your definition of rare and mine do not exactly match.
- throwanem 9y agoRunning an ircd doesn't require rare expertise. Running an IRC infrastructure that your sales team can and will use, that's as reliable as Slack is - well.
- u801e 9y agoIs using an IRC client any less intuitive compared to using a locally installed Slack client (or, in the past, using something like AIM, MSN Messenger, Yahoo Messenger, Google talk, etc)?
- walrus01 9y agoin my opinion, no, there are a lot of perfectly usable GUI IRC clients. technical teams can use irssi from the command line.
- throwanem 9y agoNo, as long as you pick a client that supports automatic image unfurling, file sharing via some cloud storage service or other, a broad range of emoji including customizable ones (people care more than you think!), and run a bouncer so your users don't lose their entire scrollback every time they disconnect. I'm not saying that an IRC experience comparable to Slack can't be achieved. I'm saying that it is so much work to do so that, for many organizations, just paying Slack a few bucks a user makes a lot more sense than sinking scarce and vastly more expensive engineer time into reinventing that particular wheel.
- wmil 9y agoIt's blocked by 90% of corporate firewalls. So trying to get started on using IRC requires big buy in from the network admins.
- saltcured 9y agoI now use the same XMPP client to talk to Slack that I previously used with our own local chatrooms hosted on ejabberd. However, others in my team are very dependent on the part of Slack that is less like XMPP or IRC: the built-in persistence that lets them scroll back or search for stuff that happened while they were away. This is clearly important to some people, who also bodged together persistence for XMPP or IRC using various bots or artfully deployed console clients in screen/tmux sessions on remote servers. I always found it strange, since I expect chat to be ephemeral. For asynchronous communication, I wish all these folks had learned how to use email or usenet properly, since I think threaded discussion on mailing lists or newsgroups was far superior to what we have now in any of these popular replacements. I still don't quite understand whether there is a majority opinion that "rooms", "channels", or serialized message boards are somehow a better UX for the average mind, or if it's really just the distortion of rent-seeking businesses always building this form that is easier to control and monetize for some reason.
- u801e 9y ago> I now use the same XMPP client to talk to Slack that I previously used with our own local chatrooms hosted on ejabberd. Have you had issues with your client taking a long time to negotiate a connection over Slack's XMPP gateway? I had that issue with Thunderbird's chat client and ended up having to switch over to the IRC gateway instead.
- decentrality 9y agoSelf-hosted ( if you want that ) but not P2P: https://about.mattermost.com/ https://about.mattermost.com/
- diggan 9y agoYeah, not solving the problem really, unless you run the software locally/in a intranet. 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.
- decentrality 9y ago( 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 )
- diggan 9y agoIt 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.
- jjeaff 9y agoSo 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.
- castis 9y ago> I still can't communicate with people sitting literally meters away from me That doesn't seem like a problem that software can solve.
- Sodman 9y agoI'll still take a cloud service with rare outages over an on-premise solution that I need to manage, host, and maintain myself any day.
- diggan 9y agoFair enough. What about having both? Slack could by default communicate via their backend, but if the client finds peers on the local network, prefer those. When the connection to the backend dies, only use the local connections. We can have the best of both worlds.
- Sodman 9y agoWhile the redundancy would be nice, I can't see it being worth the effort/money for anything but the most critical of systems (which should probably be self-hosted in their entirety to begin with). If the internet (or some major swath thereof) is down, that's going to cripple a lot of businesses these days regardless. I just don't see it being worth the extra effort of self-hosting a redundant copy of the system, and then keeping that system up to date with the latest software for security patches / features / bugfixes. Especially when the cloud version has n x 9's of uptime.
- s0l1dsnak3123 9y agoJust curious - does Slack offer SLAs? To many businesses, especially remote businesses, Slack is becoming more and more integral to day-to-day operations.
- yono38 9y agoYes, they do on their Plus plan >If we fall short of our 99.99% uptime guarantee, we’ll refund customers on the Plus plan 100 times the amount your workspace paid during the period Slack was down. Source: https://get.slack.help/hc/en-us/articles/204113126-Plus-plan-Service-Level-Agreement-SLA- https://get.slack.help/hc/en-us/articles/204113126-Plus-plan...
- cortesoft 9y agoThere are P2P systems already, plus you can run an IRC server locally. But you don't. Using a service like slack has downsides, as you are seeing now, but running your own service or using P2P has other downsides that we have deemed are even worse. Maintenance, lack of client support, network access requirements, lack of features, etc. Obviously right now the downsides of a central service is front and center, but we can't ignore the downsides of the alternatives.
- diggan 9y agoI agree with you, and I also mentioned it in another comment. We don't have to chose P2P or hosted service, when we can have both. See https://news.ycombinator.com/item?id=16109202 https://news.ycombinator.com/item?id=16109202 As my full-time work is working on P2P systems, I would love to hear more about what you think gets even worse with P2P systems compare to hosted services. Lack of client support, features and so on is more a sign of lack of adoption, rather than something fundamentally worse with P2P than hosted services.
- cortesoft 9y agoBiggest issue is connectivity issues. Corporate firewalls don't allow incoming connections, and limit outgoing connections to specific ports (in most cases). Maintaining history is also tricky in a P2P system. Can I search and view all chat history from when I am not there? A hybrid system could, but then you would still be limited by the host being online and accessible. Also just the amount of moving parts. With P2P, you can get strange issues where some people can talk to some people and not others. It can be hard to track down where those connectivity issues are. My company moved from self-hosted IRC to slack a few years ago. No one had time to maintain the system (backups, updates, troubleshooting, etc), and it was cheaper and easier to pay slack than to hire someone to maintain an IRC server, or to pull someone from their actual job to maintain it.
- Johnny555 9y agoPlus one on this -- it would be nearly impossible to make a P2P chat system work on our corporate network since we have layers of isolation between users (not to mention about a dozen small branch offices, each with their own independent office, so even if I can Slack the coworker next to me with P2P, I couldn't reach the coworker in Germany that I really need Slack for). So we either need a central chat server on our network, or we use a cloud service like Slack. We used to run Microsoft Communicator (OCS) and availability of that service was far worse than what we've seen with Slack.
- sprkyco 9y agohttp://moose-team.github.io/friends/ http://moose-team.github.io/friends/
- dvanduzer 9y agoP2P does not solve and cannot solve a number of problems associated with business communication. If you are sitting in the same room with your colleagues, what do you do when there's a power outage? Sometimes there really isn't anything to do but wait. If those kinds of outages were less rare, you'd need to figure something out to smooth productivity. Whether that is buying a generator, or finding things to do regularly that don't require electricity depends on your business. We have distributed systems that are used by normal applications to solve issues like this. When we need to, we put an ActiveDirectory replica in every satellite office. Frequently organizations forget why they spent the money on so much redundancy in the first place, re-centralize stuff, and it might be years before they experience a big enough outage that reminds them why they were "wasting" those dollars on redundant systems. As you say, there are plenty of systems that could be made less fragile than they are. Slack is specifically interesting because they made a number of "more central" design decisions, even though chat as a protocol is easier to make "more distributed". What did they get out of this tradeoff? A ton of well packaged features and integrations with other systems. Could the same thing be recreated in a more decentralized fashion? It is theoretically possible, but it could be years before we see a product/system anywhere near as functional. I would love to see an on-prem Slack product. Atlassian offers the closest suite I've seen that fits this bill. It is not easy to operate these systems at scale.
- thomastjeffery 9y ago"There exist other edge cases, so let's change the subject."
- dvanduzer 9y agoAre you calling my cases edge cases, or the parent commenter's cases? There are a lot of tools that should work better offline. But a remote collaboration tool is not a good example of that. I've done work on secure private P2P messaging systems, and when you want that feature set, you really want that feature set. But when I use Slack, it's because I don't want to have to be in the same building as all the people I'm working with. There is no way for this to gracefully degrade with a network partition. My argument is that central coordination and audit (with Slack) is not an edge case, it's the primary case.
- gumby 9y agoThe funny thing is that even with p2p systems many people use them only in a centralized mode. At my last company we kept our code in a private github repo. When our internet connection went down two devs found that they “couldn’t collaborate because they couldn’t get to github.” It didn’t occur to them to simply push their code back and forth between their machines.
- prophesi 9y agoReally surprised IPFS hasn't been mentioned yet. Though, it will eventually implement a cryptocurrency to help solve the hosting issue (think Storj or Sia but for websites). But, to be brutally honest, I doubt the backbone of our internet will change at all until we have a serious, blatant cyber war wherein the vulnerable aspects of our HTTP-based internet is taken advantage of.
- ashark 9y agoPeer-to-peer solutions, including IPFS for file storage/serving and various solutions proposed here for decentralized messaging, are no good for battery-powered devices, like cell phones. I don't want mine to burn battery maintaining P2P connections 24/7, or burn battery and my time re-establishing or confirming cached connections every time I wake it up. That puts us back to having a gateway or proxy, so... a server.
- prophesi 9y agoOn the other hand, a peer-to-peer solution would mean a better chance at connectivity when you're out in the field with your battery-powered device that's already consuming power to maintain what little connectivity it can get with the nearest cell tower.
- lucastx 9y agoAlso no good for data capped connections
- syrrim 9y agoContent on a p2p network would have built in guranteed of immutability. This would ensure that you wouldn't need to redownload the same content over and over, nor even check to see if you need to redownload it. If the GPs suggestion is followed, the resulting network could allow you to download content from a server just as you do now, so long as you pay the server to download from it. The advantage is that this server needn't be the original host.
- jiaweihli 9y agoThere's a coin for that: https://www.shiftnrg.org https://www.shiftnrg.org
- beejiu 9y agoSounds idyllic, but you will struggle to make a business case unless Slack is mission-critical to your business (which it probably isn't - you can simply email, phone or walk over and talk to somebody).
- vitaflo 9y agoYou do have a P2P system to solve this issue already. A literal person to person system.
- jekrb 9y agoYou can do this with an application called patchwork that uses a p2p protocol called ssb (secure-scuttlebutt). It doesn't use a global blockchain, but there is a more fractal internal append-only log structure that logs data from peers you've connected with. https://www.scuttlebutt.nz https://www.scuttlebutt.nz
- vuldin 9y agoHappy to see patchwork and secure-scuttlebutt mentioned. These apps and the people behind them are, in my opinion, looking at decentralization in the most complete way from an application standpoint. Now if we can combine these apps with routerless ad hoc or mesh networks, that would be a very good start towards an unstoppable communication platform.
- JdeBP 9y agoYou did actually have them once. * https://www.freebsd.org/cgi/man.cgi?query=talk https://www.freebsd.org/cgi/man.cgi?query=talk * http://netbsd.gw.com/cgi-bin/man-cgi?talkd http://netbsd.gw.com/cgi-bin/man-cgi?talkd (-:
- Thlom 9y agoJust a crazy thought, but what if Slack (just using Slack as an example) could provide a dongle or 1U server you can put in your server room which works as a proxy for Slack and fallback for clients should Slack be down. This could automatically be updated and maintained by Slack. If you have several sites and no VPN you could install this at all locations and connect them together so you can continue as normal whenever Slack is down and if Internet is down at least you can use it with everyone in your local network. Might be difficult to sync it back to Slack when everything is up and running again though ...
- Johnny555 9y agoMany corporations don't like to put a black box anywhere on their network -- they want to see inside it and monitor it to see what it's doing.
- shalabhc 9y agoUpvoted. We really need more systems that can do P2P well (centralized is just a special case of P2P - you need a few robust, replicating nodes with high connectivity). The routing, replication and persistence of messages is completely orthogonal to the physical nodes and TCP channels. Unfortunately systems are not usually designed this way. The problem has been solved to a large degree by some systems in the past - Croquet comes to mind, though there are probably others. IPFS is getting there is a roundabout way. Another interesting protocol/system scuttlebot.io.
- jjrh 9y agoIn the example of chat, XMPP is federated, it even has serverless messaging ( https://xmpp.org/extensions/xep-0174.html https://xmpp.org/extensions/xep-0174.html ) SIP for instance is perfectly happy to do ip<->ip calls (well ignoring NAT issues - one day we will all have ipv6 addresses....) This really is a solved problem, people for various reasons have decided to rely on external services they have no control over. I don't think we need to throw yet another protocol at the problem, instead we should focus on making what we have better and easier to setup and use.
- iak8god 9y agoHow about https://matrix.org/ https://matrix.org/ ?
- vesak 9y agoLooks promising but quite immature still.
- ptman 9y agoWhat specifically do you think is missing when compared to slack?
- vesak 9y agoUX mainly. This can be fixed with a non-trivial amount of work.
- ptman 9y agoMatrix has had a hard time during the past months as their previous funding was cut. They've been looking for new funding which is probably just around the corner. Hopefully stable funding will allow them to focus on polishing the UX
- shams93 9y agoSlack seemed to be having issues with maxing out their websockets services. The problem with pure p2p for slack is the customer trust. Their customers want them to lock everything into their servers, these companies don't understand or trust p2p, if they did they could just take a look at Muaz Khan's github pages and find a way to implement their own corporate chat with audio and video purely p2p and use their own corporate coturn server to lock down access. Setting up coturn isn't easy but you can connect coturn to active directory and ldap for enterprise level authenticated access control for a p2p webrtc chat app for your own company.
- ggg9990 9y agoThe failure rate and time to resolution for a box in your office is much worse than for Slack’s Service.
- flukus 9y agoFor the box in my office most "failures" and the time to resolve them can be scheduled outside working hours. Many critical systems don't need to be up 24/7, 10/5 is more than enough. They can also be scripted with automatic failover, automated restore from backups, etc so that very little downtime happens. With a hosted service you don't get that level of control, your software updates when the provider wants it to, not when you want.
- ggg9990 9y agoHoly Infant Jesus I have never wanted to set up automatic failover and restore from backup for an office chat server :)
- flukus 9y agoIt is a critical system where we work because we communicate worldwide often throughout the day, an outage in our messaging has a major impact. We probably wouldn't need backups (they're only useful for blame storming), but a failover or replication is important. Unfortunately we use Skype for business. Uptime is great but other features (like sending a god damn message) are frequently broken.