still think that a firstbits thingie would be better^^
Firstbits on Instawire = bad ideaIt has actually been discussed on the two previous pages.
Topic: [ANN] You liked instawallet.org ? You'll love instawire.org ! (Read 6167 times)
It has actually been discussed on the two previous pages.
November 09, 2012, 09:30:25 AM
No worries! You forgot to mention that a lot of times the reference field will not only get uppercased but also truncated. But that's covered too.
The simpler the service looks from the outside, the more magic happens behind the scenes
The simpler the service looks from the outside, the more magic happens behind the scenes
still think that a firstbits thingie would be better^^
November 09, 2012, 09:29:37 AM
No worries! You forgot to mention that a lot of times the reference field will not only get uppercased but also truncated. But that's covered too.
The simpler the service looks from the outside, the more magic happens behind the scenes
The simpler the service looks from the outside, the more magic happens behind the scenes
November 09, 2012, 09:24:19 AM
this is doomed to fail.
why?
[...]
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
why?
[...]
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
Thank you Einstein, please have a look at this little bit of code.
Code:
class Sale < ActiveRecord::Base
[...]
def self.sales_for(full_btc_address)
Sale.where("(full_btc_address = ?) OR (? LIKE UPPER(CONCAT(received_btc_address, '%')))",
full_btc_address,
full_btc_address.upcase
)
end
[...]
end
[...]
def self.sales_for(full_btc_address)
Sale.where("(full_btc_address = ?) OR (? LIKE UPPER(CONCAT(received_btc_address, '%')))",
full_btc_address,
full_btc_address.upcase
)
end
[...]
end
I assume I don't need to show you the door.
naaaays.
see, you done thought of that, I like.
sorry if I came across rude, that's just me.
good luck with your endeavours.
I hope everyone remembers to copy their adress in there^^
November 09, 2012, 08:57:39 AM
this is doomed to fail.
why?
[...]
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
why?
[...]
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
Thank you Einstein, please have a look at this little bit of code.
Code:
class Sale < ActiveRecord::Base
[...]
def self.sales_for(full_btc_address)
Sale.where("(full_btc_address = ?) OR (? LIKE UPPER(CONCAT(received_btc_address, '%')))",
full_btc_address,
full_btc_address.upcase
)
end
[...]
end
[...]
def self.sales_for(full_btc_address)
Sale.where("(full_btc_address = ?) OR (? LIKE UPPER(CONCAT(received_btc_address, '%')))",
full_btc_address,
full_btc_address.upcase
)
end
[...]
end
I assume I don't need to show you the door.
November 09, 2012, 07:12:36 AM
this is doomed to fail.
why?
because some banks convert the comments field to UPPERCASE
so my adress 1nceWUfH23934kxbwqxn238940
will look like 1NCEWUFH23934KXBWQXN238940
which is NOT AT ALL THE SAME
bye bye money.
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
why?
because some banks convert the comments field to UPPERCASE
so my adress 1nceWUfH23934kxbwqxn238940
will look like 1NCEWUFH23934KXBWQXN238940
which is NOT AT ALL THE SAME
bye bye money.
It would probably better to integrate a firsbits or btc.to-generator and have THAT code pasted in the wire text field
November 09, 2012, 07:03:13 AM
The first refund was rejected by the bank systems for some reason (they could not use the bank information provided): a resend was completed today to the bank account of origin. I hope it will go through without any further delay.
November 07, 2012, 04:14:23 PM
Hi!
I've cancelled a payment on 2012-10-27 08:49:04 UTC and it's not been refunded to my bank account yet. Could you please look into that?
Thanks!
~drekk~
Yes, we'll look into it and send your transfer tomorrow if it hasn't already been done.I've cancelled a payment on 2012-10-27 08:49:04 UTC and it's not been refunded to my bank account yet. Could you please look into that?
Thanks!
~drekk~
Refunds are not automated yet. So it has probably just slipped through the cracks. Sorry about that!
November 07, 2012, 08:22:00 AM
Hi!
I've cancelled a payment on 2012-10-27 08:49:04 UTC and it's not been refunded to my bank account yet. Could you please look into that?
Thanks!
~drekk~
I've cancelled a payment on 2012-10-27 08:49:04 UTC and it's not been refunded to my bank account yet. Could you please look into that?
Thanks!
~drekk~
Fair enough, now you only see obfuscated e-mails and IBANs, no names anymore. Also since day one we limit the number of address inputs per hour and per IP to 3 making it quite hard to bruteforce.
Good call!
That's the other part that confuses me... I can see someone being able to attach a name/address to a bitcoin address if they had access to the wire transfer data, but how would a random person on the internet be able to make that connection?
I was just going by the following:
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.
I understood this to mean "If anyone inputs any bitcoin address into our system, they will be able to see the person's name and IBAN, so it's a good thing we don't allow firstbits, because some people's firstbits are available to the public and bitcoin addresses are not, and people might start seeing other people's personal information if we allow people to input firstbits".
I wasn't looking for a feature, I just thought that you could tell me roughly what exchange fee you charge your customers. I can figure it out myself by observing your price changes and what the price is on markets such as Mt.Gox. at that time, I just thought that maybe you could save me the trouble.
Well, the truth is that humans set the price. There really is no algorithm. Sometimes we'll be a little more expensive than others, and sometimes we'll be a comparatively cheap. 
Still, I'd like to know what the price was at Mt.Gox. at the exact time that the exchange rate was set, so that I can compare them.
Instawire offers no such feature, there are no plans to implement it. That's how we roll.I wasn't looking for a feature, I just thought that you could tell me roughly what exchange fee you charge your customers. I can figure it out myself by observing your price changes and what the price is on markets such as Mt.Gox. at that time, I just thought that maybe you could save me the trouble.
That's the other part that confuses me... I can see someone being able to attach a name/address to a bitcoin address if they had access to the wire transfer data, but how would a random person on the internet be able to make that connection?
I was just going by the following:
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.
I understood this to mean "If anyone inputs any bitcoin address into our system, they will be able to see the person's name and IBAN, so it's a good thing we don't allow firstbits, because some people's firstbits are available to the public and bitcoin addresses are not, and people might start seeing other people's personal information if we allow people to input firstbits".
That's the other part that confuses me... I can see someone being able to attach a name/address to a bitcoin address if they had access to the wire transfer data, but how would a random person on the internet be able to make that connection?
I was just going by the following:
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.
I understood this to mean "If anyone inputs any bitcoin address into our system, they will be able to see the person's name and IBAN, so it's a good thing we don't allow firstbits, because some people's firstbits are available to the public and bitcoin addresses are not, and people might start seeing other people's personal information if we allow people to input firstbits".
My take on it was that people would more easily use firstbits familiar to them, possibly ones that had been previous posted on the internet. It's a bit of a heavy-handed approach, but I can't deny that users are generally stupid, and protecting them from themselves is sometimes appropriate.
Not using firstbits is already a good idea (since firstbits offer no protection against typos and practically guarantee that any mistake means you'll pay the wrong person).
But the revelation that one can see someone's identity and personal banking details by providing nothing more than a Bitcoin address and that this is by design, if true, would indicate... well... I'll leave it up to others to draw their own conclusion as to what that means.
My take on it was that people would more easily use firstbits familiar to them, possibly ones that had been previous posted on the internet. It's a bit of a heavy-handed approach, but I can't deny that users are generally stupid, and protecting them from themselves is sometimes appropriate.
Not using firstbits is already a good idea (since firstbits offer no protection against typos and practically guarantee that any mistake means you'll pay the wrong person).
But the revelation that one can see someone's identity and personal banking details by providing nothing more than a Bitcoin address and that this is by design, if true, would indicate... well... I'll leave it up to others to draw their own conclusion as to what that means.
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.
How does requiring the full address lessen this exposure? If the reason you don't support firstbits is because you divulge personal information given a bitcoin address with the assumption that only the correct account holder will be able to provide the entire bitcoin address, how do you reconcile that with the fact that anyone can look up the full address for any firstbits on the internet and query with that instead? In fact, the total set of bitcoin addresses ever used is very finite and publicly available, and someone could just query your server for every bitcoin address that has ever been used since your service started and datamine your entire database.
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.
How does requiring the full address lessen this exposure? If the reason you don't support firstbits is because you divulge personal information given a bitcoin address with the assumption that only the correct account holder will be able to provide the entire bitcoin address, how do you reconcile that with the fact that anyone can look up the full address for any firstbits on the internet and query with that instead? In fact, the total set of bitcoin addresses ever used is very finite and publicly available, and someone could just query your server for every bitcoin address that has ever been used since your service started and datamine your entire database.
Good points regarding firstbits davout, thanks for the reply!
Note that I was specifically addressing the page you get when your coins are "Ready to deliver" and the confirmation page that you see after your coins have been delivered.
Fair enough, this should now be fixed. Thank you very much for the report !From what I understand the exchange rate is set once a day, therefore the information on the page doesn't "update often". That's a pretty convenient thing, IMHO.
We usually update it once in the morning (unless wild price swings happen during the day), sometimes you'll end up paying a little less on Instawire than the average price on bitcoin charts, sometimes a little more. At the end of the day that's not what Instawire is about. Instawire is about bridging the gap between the traditional banking system and the Bitcoin world in the most possible elegant way 
Still, I'd like to know what the price was at Mt.Gox. at the exact time that the exchange rate was set, so that I can compare them.
Instawire offers no such feature, there are no plans to implement it. That's how we roll.Do you support firstbits addresses?
We will probably never support firstbits addresses, think about it for a minute, by inputting someone's address I can instantly find out whether this person transacted with Instawire, what this person's IBAN and name are. Probably not the best idea when firstbits are often part of forum signatures.Additionnally, we rely a lot on bank wire references, these references can get truncated along the way, with a regular address that's not an issue, you can immediately see if it's valid or not and complete it at the moment the user inputs his full address. Truncating firstbits could be catastrophic since truncated firstbits could possibly resolve to a completely different address than the one originally intended.
Jump to: