News for hackers. Stuff that matters.
Re:Programmable Fax – API for sending and receiving faxes by kevinburke on Friday March 31, 2017 @11:35AM (#14004837)
This has been kicked around for a really long time and I'm happy they finally launched it.

Around 2013 or so, one of the junior engineers on the Twilio Voice team pitched his innovation week project with a single slide saying "Fax: The time is now." The time has finally arrived! Congrats John.

Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @11:56AM (#14005068)
Guessing this will kill Phaxio. Compare the pricing:

https://www.twilio.com/fax/pricing

https://www.phaxio.com/pricing/

Re:Programmable Fax – API for sending and receiving faxes by kevinburke on Friday March 31, 2017 @01:42PM (#14006158)
Rumors of the demise of telecom services based on their competitors' feature set and pricing are greatly exaggerated.

https://kev.inburke.com/kevin/six-years-of-hacker-news-comme...

Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @04:11PM (#14007693)
This is a smaller, more niche market though. Not just the "fax" or "online fax", but specifically "fax API" slice. There are not many players.
Re:Programmable Fax – API for sending and receiving faxes by Thieum22 on Friday March 31, 2017 @03:54PM (#14007527)
Some of our customers have been using foiply : https://www.foiply.com/pricing-monthly/

The difference in pricing will certainly make them consider a switch.

Re:Programmable Fax – API for sending and receiving faxes by beaconstudios on Friday March 31, 2017 @12:16PM (#14005264)
it's amazing that phaxio have gotten away with such high prices for so long.
Re:Programmable Fax – API for sending and receiving faxes by rabidonrails on Friday March 31, 2017 @12:31PM (#14005420)
Phaxio founder here.

Our pricing might seem higher (and may be in certain situations), but it works a bit differently that Twilio's. Twilio charges you the 1c _plus_ the costs of the call. Phaxio is an "all in" rate _including_ retrying the call. And, at Phaxio, if the calls all fail there's no cost to you.

I'm not saying that we won't adjust our pricing (#competition), but there's a difference in the actual unit cost.

Re:Programmable Fax – API for sending and receiving faxes by joering2 on Friday March 31, 2017 @11:37PM (#14010265)
Long time user of Phaxio. We tried many other services and your seems the be the best when it comes to crunching documents - Word, PDF, Images, you name it.

I don't know how Twilio does it, but unless one day in 100 years from now we will be sending 1 million faxes, we will be reluctant to switch and probably save ourselves a headache just to save few bucks a month.

Re:Programmable Fax – API for sending and receiving faxes by IgorPartola on Friday March 31, 2017 @12:38PM (#14005507)
How long does it take to send a page of fax? Their pricing is 0.007 per minute. I haven't seen many fax machines take more than a minute per page, but they would have to take 10 minutes to catch up to your pricing.

Edit: Fixed time to comparable pricing.

Re:Programmable Fax – API for sending and receiving faxes by kelnos on Friday March 31, 2017 @01:07PM (#14005803)
I'd be surprised to see more than a couple minutes for even a complicated fax page. I've seen 45-70 seconds average for a not-too-complicated page.

It also depends on the baud rate (never thought that term would come back, eh?) negotiated between both ends. A 14400 baud transmission will of course be faster than 9600.

Re:Programmable Fax – API for sending and receiving faxes by nojvek on Friday March 31, 2017 @01:31PM (#14006035)
I paid $10 to send a 28 page fax. I absolutely believe utility and govt companies still use fax because they want to make somethings very hard for the average customer. There's no reason why I shouldn't be able to send an email a pdf to show good credit so they don't charge me a deposit fee.

Twilio please build a mobile app so those of us who don't live with typewriters and fax machines can deal with our nasty govt.

Re:Programmable Fax – API for sending and receiving faxes by karlmdavis on Friday March 31, 2017 @01:41PM (#14006149)
Where in the government do you still have to fax things?
Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @07:58PM (#14009483)
This had me curious, so I tried googling for

  site: *.gov fax
Was surprised at the results. It may not be the only conduit, but it is there for job applications, VA benefits, applying for a headstone in a national cemetery, court filings, IRS documents, and much more.
Re:Programmable Fax – API for sending and receiving faxes by generj on Sunday April 02, 2017 @04:26PM (#14018872)
The FBI recently stopped accepting FOIA requests online and now online accept them via fax and snail mail.

They did it deliberately to reduce the number of requests.

Re:Programmable Fax – API for sending and receiving faxes by rabidonrails on Friday March 31, 2017 @12:51PM (#14005639)
Quick answer is that it depends on what's on the page. It can be as quick as a minute or significantly longer if there are images or lots of data the page.
Re:Programmable Fax – API for sending and receiving faxes by IgorPartola on Friday March 31, 2017 @02:14PM (#14006442)
That's fair but how many pages take more than 10 minutes?
Re:Programmable Fax – API for sending and receiving faxes by bluesign on Friday March 31, 2017 @01:11PM (#14005837)
10 minutes not 1000 minutes
Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @12:32PM (#14005434)
How long does it take, on average, to send a page?
Re:Programmable Fax – API for sending and receiving faxes by rory096 on Friday March 31, 2017 @12:30PM (#14005417)
I'm not sure the Phaxio pricing is all that much higher than Twilio. They're covering failed faxes, cancelled faxes, faxes that require multiple retries, and faxes that just take a long time — only charging per page delivered. Those will all eat up minutes that you'll pay for with Twilio.

In any case, their pricing model has been far preferable to their old competitor, Interfax: https://www.interfax.net/en/prices

Re:Programmable Fax – API for sending and receiving faxes by kelnos on Friday March 31, 2017 @06:20PM (#14008865)
We (Twilio) are also only charging for successful delivery. Failures to not incur any billing. Retry is (currently) on the customer to implement, but since we don't charge for failures, that doesn't affect cost.

Yes, we're charging per-minute fees, but for US, at least, it's sub-1-cent, and with my testing so far, I haven't seen it go more than a couple minutes per page for something fairly complex, and that's worst case.

Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @06:39PM (#14009019)
Someone else in this business says they see 1 minute for 1 page faxes, but faster for longer faxes...Because the first page has the initial handshake.

http://www.faxage.com/learn_faxing_by_minutes_versus_faxing_...

I'm sure some pages take longer, but it doesn't seem odd that most pages aren't complex.

Re:Programmable Fax – API for sending and receiving faxes by nck4222 on Friday March 31, 2017 @01:53PM (#14006258)
After reading these arguments I was expecting something in the range of dollars per fax.

Is 7 cents per page really that much? I'm not very knowledgeable about this stuff, but are there really that many places out there faxing thousands of pages where 7 cents per page vs 5 cents per page is really going to make a difference for them?

Re:Programmable Fax – API for sending and receiving faxes by tyingq on Friday March 31, 2017 @04:13PM (#14007711)
There isn't consensus on the 5 cents per page part. Some think it is closer to 3. If that's true, generally, I'm concerned if a competitor launches at less than half my price.

Even if it is 5 cents, that's a 30% discount, which seems significant.

Re:Programmable Fax – API for sending and receiving faxes by dublidu on Friday March 31, 2017 @04:24PM (#14007820)
It makes a difference at high volumes.
Re:Programmable Fax – API for sending and receiving faxes by robbiemitchell on Friday March 31, 2017 @12:19PM (#14005289)
All the eFax providers have been doing this.
Re:Programmable Fax – API for sending and receiving faxes by DaiPlusPlus on Friday March 31, 2017 @12:29PM (#14005406)
When your user-base is comprised of doctors, lawyers and blue-chip companies with ancient business processes you can get away with charging what you like.
Re:Programmable Fax – API for sending and receiving faxes by toomuchtodo on Friday March 31, 2017 @12:44PM (#14005568)
And when your user base is developers without knowledge of the underlying fundamentals, you can charge how Twilio does. The knife, it cuts both ways.

Until you know the use case, pricing is a nebulous concept.

Re:Programmable Fax – API for sending and receiving faxes by carlosdp on Friday March 31, 2017 @12:46PM (#14005585)
Actually though! This has been an internal meme since then, there's been PRs for implementing it just hanging around for years =P I had to check the date to make sure it wasn't an April Fools joke.

Congrats Twilio!

Re:Programmable Fax – API for sending and receiving faxes by kelnos on Friday March 31, 2017 @02:22PM (#14006521)
Depends on what time zone you're in ;)
Re:Programmable Fax – API for sending and receiving faxes by briankwest on Saturday April 01, 2017 @01:11PM (#14013053)
Or download FreeSWITCH and roll your own. :)
Re:Programmable Fax – API for sending and receiving faxes by jenamety on Friday March 31, 2017 @02:14PM (#14006437)
I have previously integrated with eFax in 2010, so an internet fax provider is not new to me, but forgive my ignorance as I haven't visited the space in a while. Which innovation are you excited about and referring to? From the comments it seems to be 'developer friendly API' or 'Simplicity in pricing' as the to big draws, just curious what has changed since my last days?
Re:Programmable Fax – API for sending and receiving faxes by pyre on Friday March 31, 2017 @03:12PM (#14007139)
Being "developer-friendly" can be a big draw. Take Stripe for example. It's an HTTP API with bindings in a number of languages. Previously I worked with a payment processor that required we run some sort of Java application even though we weren't a Java shop. Someone had to setup a way to wrap the Java application to interface with the payment processor (not even getting into the issue that now we have to deal with running a JVM-based application). Some companies are actively developer hostile in their interfaces.