If in the meantime you guys want to implement https I actually run
this: https://outboundip.com
I've just migrated it to droplets and popped in an SSL cert

I plan to grow the cluster and improve the service(s) when time permits
(UDP+TLS) but the goal is reliability and in a sadistic way I kinda
enjoy fighting off ddos attacks. (keeps me current with the kids these days)
haproxy themselves may get involved in the future as it's going to be an
open project.. anyway.. it works and a few people have been using it
over the years

I drop logs after 3 days, no more than 5 queries/s from a single IP -david

On 16/04/14 18:11, Eric Voskuil wrote:
> Yes - we are planning to get rid of curl as well as the independent openssl
> dependency.
>
> https://github.com/spesmilo/libbitcoin/issues/13#issuecomment-40609927
>
> e
>
> -----Original Message-----
> From: Libbitcoin [mailto:libbitcoin-bounces@lists.dyne.org] On Behalf Of
> Pablo Castellano
> Sent: Wednesday, April 16, 2014 10:07 AM
> To: libbitcoin@???
> Subject: [Libbitcoin] Would it be possible to get rid of curl?
>
> Right now curl is a dependency of whole libbitcoin but curl is used just
> to discover the public ip of the host running libbitcoin.
>
> I think it would be nice to get rid of it.
> Apart from that, none of the services used to get the public ip
> (whatismyip.org and checkip.dyndns.org at the moment) do support https,
> so it's easily replaceable by a socket and a GET request.
>
> Regards,
> Pablo.
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin