Author

Topic: bitcoinnotify finally down? (Read 981 times)

sr. member
Activity: 286
Merit: 251
December 18, 2011, 08:31:05 AM
#2
I was pretty disappointed when I came to work on my nascent-site development and found nothing worked and then found out why.

I still think this is THE way to accept Bitcoins. Hell, lets go further, lets write some php code or whatever and share it so that others can easily use it.

So what did BCN do right and what did they do wrong?

In my (humble) opinion:

1) there was no way to dynamically register an address. You had to register a bunch through their website. They encoraged you to register all the addresses you might need. This is a mistake in my view. You should register what you need for the next few minutes or days, not forever.

2) They packed their bags and went without so much as a cheerio then.  As a  service user, this would be really bad news. Even an hour or two's down time would hurt me pretty badly. So I am going to suggest that we need multiple service providers providing the SAME service and that a website would use several of them for redundancy.

3) Liked the security model.

4) I need to be able to tell customers before they send me funds that I cannot receive them. Should have thought of that one myself. Had my site been live, it would just have carried on say, Nah, havnt received your funds yet. How crap that would have been!!!

Others, your thoughts?

hero member
Activity: 488
Merit: 500
December 13, 2011, 07:53:37 AM
#1
At least since monday morning https://bitcoinnotify.com/ seems to be down.

Somehow I expected it after following the various not-amusing threads about it's selling. Still I would have preferred to get at least a short warning to all registereed users that it will go down instead of just nothing,  not even a post here in the forum Angry

Maybe the new owner (whoever that is right now as the last thread has been deleted: https://bitcointalksearch.org/topic/--53297) can shed some light on the situation? Will it come back or is it down for the foreseeable future?  (Anyway i started working on my own implementation already ;-))
Jump to: