@taariqlewis Sure, though from a security standpoint it seems they would prefer to hand out read-only tokens as opposed to user/pw pairs.
OAuth is 9 years old, yet it seems all financial services integrate with banks by requiring your user/pass for full read/write access.
@QuickenLoans myQL - connecting my NCSECU account w/30 char pw failed multiple times. Shortened it to 10 chars & integration worked.
Once again I’ve had to shorten my bank p/w to get a financial service’s integration to work w/my bank. /cc @FormFree @Fidelity @QuickenLoans
Because “security reasons.” (┛◉Дâ-pic.twitter.com/87dMRhwLFFs://t.co/87dMRhwLFF
@el33th4xor I agree; I’ve taken issue with a number of Cobra’s actions but at the end of the day, I guess it’s their site to administer.
@el33th4xor Can’t we judge them upon the merit of their contributions as opposed to their lack of government registered identity?
Looks like @civickey works as promised! pic.twitter.com/uGkYkzCAZN
@AegisFS Not really; using Bitcoin over Tor is something you’d want to do for sending transactions as opposed to receiving them.
@mraz_sic However, while it’s possible to configure a node to only receive & relay blocks, I’m not aware of a way to only relay txns.
@mraz_sic Sure, but in order for that to be possible, someone has to be running Bitcoin hidden services that will accept & relay txns.