3 ms·
It's also a (moderately) higher barrier to entry, so it's less likely to be aggressively used by heavy-handed copyright holders. Though in practice, fax has tu
by Firehed 14y ago
It's also a (moderately) higher barrier to entry, so it's less likely to be aggressively used by heavy-handed copyright holders.
Though in practice, fax has turned into this bastard child of excessive analog-to-digital conversion, at least among newer companies. Senders email their attachment to an email-to-fax service, which sends it over POTS to a fax-to-email service converting it back into a PDF and emailed as an attachment to the recipient.
- icebraining 14y agoIf a company sells both services (hardly unusual) and a client of theirs sends a fax to another, I wonder if the system calls itself... ;)
- Firehed 14y agoBased on my own experience... yes, at least to start. Depends how easy (and fast) it is to detect that both parties exist within the network.
- icebraining 14y agoReally? I can't say I have experience building such a system, but to me it seems the solution has already been built: fast off-the-shelf DNS servers, using phone numbers as virtual (sub)domains.
- Firehed 14y agoMy experience is in the context of payments - when charging someone's payment card, check whether it's one we've issued and just run it as an internal balance transfer rather than run it through Visa (read: free). When doing the whole "build fast, iterate quickly" thing, it's easy to forget about such optimizations, especially when it's a relative edge case and works just as well if you leave it alone (arguably better, since there's less conditional logic in the code) So by "network" I more meant database (i.e., network of users).