3 ms·

The campfire model specifically is even worse; it becomes a liability to maintain that I can’t request of the vendor, but have to take care of myself. The burde

by 9dev 2y ago

The campfire model specifically is even worse; it becomes a liability to maintain that I can’t request of the vendor, but have to take care of myself. The burden of actively looking for vulnerabilities, and fixing them, is on me. The idea may be venerable, but I don’t quite understand who would think you could consider a networked online chat server as finished…

TeMPOraL 2y ago
> who would think you could consider a networked online chat server as finished… What about a phone service? What about cable? WAN? Recent "smart" insanity notwithstanding, those things are not updated on end-user side; every now and then, some hardware or wiring might get replaced, but the infrastructure part on the customer side is generally one-and-done, and customers pay only for the actual telecommunication service.
- 9dev 2y ago
  Now that's just moving the goalposts. Comparing a chat server application with copper wiring isn't just Apples to Oranges, it's Apples to a Torx Screwdriver. The chat server requires constant network communications with various devices that change over time, suffers from possible supply chain vulnerabilities it needs to defend against, talks to databases, mobile apps—suffice to say, there's a million interactions that may be failing in the future due to unforeseen changes in the outside world. A phone line introduces but a fraction of the complexity on-site, and thus doesn't need as much caretaking. I mean, ...duh? And even if you want to pull through with this analogy; phone service customers still have an ongoing subscription to cover for the eventual repairs and wiring replacement. Just think of the transition to fibre in recent years. You pay for the service on the phone line and the maintenance of your infrastructure. It's a bundle.

3 ms·

The campfire model specifically is even worse; it becomes a liability to maintain that I can’t request of the vendor, but have to take care of myself. The burde

by 9dev 2y ago

TeMPOraL 2y ago
> who would think you could consider a networked online chat server as finished… What about a phone service? What about cable? WAN? Recent "smart" insanity notwithstanding, those things are not updated on end-user side; every now and then, some hardware or wiring might get replaced, but the infrastructure part on the customer side is generally one-and-done, and customers pay only for the actual telecommunication service.
- 9dev 2y ago
  Now that's just moving the goalposts. Comparing a chat server application with copper wiring isn't just Apples to Oranges, it's Apples to a Torx Screwdriver. The chat server requires constant network communications with various devices that change over time, suffers from possible supply chain vulnerabilities it needs to defend against, talks to databases, mobile apps—suffice to say, there's a million interactions that may be failing in the future due to unforeseen changes in the outside world. A phone line introduces but a fraction of the complexity on-site, and thus doesn't need as much caretaking. I mean, ...duh? And even if you want to pull through with this analogy; phone service customers still have an ongoing subscription to cover for the eventual repairs and wiring replacement. Just think of the transition to fibre in recent years. You pay for the service on the phone line and the maintenance of your infrastructure. It's a bundle.