Yahoo Triples Estimate of Breached Accounts to 3B
191–200 of 311 posts
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#192Re: Yahoo Triples Estimate of Breached Accounts to 3B
#193Re: Yahoo Triples Estimate of Breached Accounts to 3B
#194Earlier quoted context omitted.
Alternatively, if it's truly an asset, can it be taxed as an asset? If I give a company a car, that is taxed. If I give a company my data which is worth more than a car, it isn't. Is it possible that current accounting/tax law can be interpreted so that these are viewed similarly?
The asset concept is interesting. If you introduce taxes into the mix then you will also need to value your asset. If you sell your asset then you need to record a fair value price for which you bought it and when... that way you can record a short or long term capital gain. The problem with digital assets is that you can easily copy them. So what does it mean to sell an asset which you actually still own/have a copy…
Record companies forced plenty of DRM related BS down our throats to drag us into a "license not own" rental model. I suggest we return the favor.
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#195Earlier quoted context omitted.
It is when you have 3B records
If one company sells anything to another company, that sale is taxed as income like any other sale. So yes, if Yahoo sold 3B records, that would be taxed, and the recipient company can choose to book that purchase as an asset on their balance sheet and will likely expense the purchase. Hell they could even choose to depreciate the value too for as long as they follow GAAP. OP mentioned his data alone, which isn't wor…
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#196My question: Now I assume that one way or another they got that from Google or from one of the many hacked forums /websites (yeah, I used the same id+password in many sites). Do they try to login manually or try 10000 at a time via bots? I doubt they they went manual since they must have millions of accounts. id my user name was cpowell or hclinton I suppose but....
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#197Earlier quoted context omitted.
Alternatively, if it's truly an asset, can it be taxed as an asset? If I give a company a car, that is taxed. If I give a company my data which is worth more than a car, it isn't. Is it possible that current accounting/tax law can be interpreted so that these are viewed similarly?
The asset concept is interesting. If you introduce taxes into the mix then you will also need to value your asset. If you sell your asset then you need to record a fair value price for which you bought it and when... that way you can record a short or long term capital gain. The problem with digital assets is that you can easily copy them. So what does it mean to sell an asset which you actually still own/have a copy…
Yet we manage to sell IP (or just some intangible right to use it)
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#198I mean "safe" in the sense of being unlikely to cause confusion or problems with less-than-well-written software (or humans).
Obviously .com is okay, and I haven't heard of problems with .edu/.gov/.org/.net, but I'm a little afraid of getting a domain for email addresses that isn't a well-established 3-letter TLD, on the off chance that someone has hard-coded a requirement like this in their code. I'm not sure if I'm just being paranoid about this though. Any suggestions on what's considered safe?
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#199Earlier quoted context omitted.
If that's the case, I think the bigger news then is that yahoo actually had 3B users!
Nobody ever said they are active users or unique individuals. I know for example I personally created hundreds of accounts on Yahoo! over the years.
Re: Yahoo Triples Estimate of Breached Accounts to 3B
#200Somewhat off-topic, but does anyone know what top-level domains are in practice "safe" to use for email addresses if we're going to migrate to our own domain? I mean "safe" in the sense of being unlikely to cause confusion or problems with less-than-well-written software (or humans). Obviously .com is okay, and I haven't heard of problems with .edu/.gov/.org/.net, but I'm a little afraid of getting a domain for email…