Bitcasa forums update#
Bitcasa forums license#

I believe the root of my problem is not understanding where what specific wires were supposed to go inside the IC1 555 Timer. May you please help me on my second attempt to simulate the circuit. It did not work out so well because it did not become animated, like it was supposed to have simulated electricity flowing through it. Here's my first attempt at doing the circuit: I just need to build the circuit, there really is no relevant equations as this is a project for assembling a circuit, not some help on homework or studying for a test. Here's the circuit I'm supposed to simulate: Here's the app I am using to simulate the circuit: The final steps of the project is to build the project on a breadboard, which I can do with my dad, and build it on a perf board, which I can do with my dad as well. I've already selected a project and I have already gathered parts thanks to my parents, but I need help on simulating the circuit. So yes, to your point the DMCA reduces liability but I maintain that it is still a potential flaw (which is what the title of that paragraph is).The assignment for me is to simulate a circuit. Certainly Bitcasa doesn't have any special deals like that.

Bitcasa forums license#

Note that google makes copies of your music (in GMusic) instead of hash matching for similar reasons where Apple secured an expensive license to do this. I am familiar with the DMCA which would reduce the scope the companies liability for #2 however, it does compel them to be compliant which hurts users (covered in #3) and there a variety of subtle situations where the DMCA wouldn't help them. #3 is the downloading/user possession aspect. So uploading was covered in #2 in the post. This is a class of 'side channel attack' (look that up for more on the subtle issues introduced). For example, if you keep statistics on the largest file a user has, then it dramatically reduces the number of files that the user's 'true' file can hide in. Keeping quotas and logs leaks information about what you are storing.

Bitcasa forums update#

I'll add an update to clarify #1 as that is important.Įdit: Convergent encryption link is fixed in the post (thanks for the tip)įlaw #3 and the 'shortsighted solutions' for #1 address this. The reason for my focus on them is they did many things exactly how I would have wanted them to, but it is dangerous to advertise a certain level of encryption that is generally understood and then provide something that has a variety of subtle flaws.

I will gladly update this as more information surfaces but I believe my assumptions are plainly explained and are likely to be true. I agree it is strong, though I wouldn't call it an attack piece. Even if you did nothing wrong that is more exposure than 'client side encryption' would lead most people to believe. For example, if you own a CD and they get you downloading something from bittorrent you'd have to argue that point in court.

That is true but that isn't how copyright lawsuits generally work. What I hope to come out of this is discussion on ways to reduce the legal exposure a company has in this privacy-centric model.ģ. I am not a lawyer, but part of this post is to focus on the viability of the model. If dropbox does that they don't subject their user's to any (more) security risks as they don't make such a strong assertion.Ģ. The problem is that for them to deal with it they have to sacrifice their user's privacy (quotas and stats open clients up to attack). The issue isn't that bad guys exist and everyone has to deal with it. (Also, the 'convergent encryption' link is broken.)ġ. Bitcasa can tell whether I have a particular file, but (at least in the general case) can't tell whether I'm licensed or authorised to have that copy. 'any provider of this service could be legally responsible' (my emphasis) is just weasel words.ģ. Preventing them rejoining is tricky, but no harder for Bitcasa than any other internet service (from some tiny 10-user internet forum via Dropbox right through to Amazon), so why single them out?Ģ. Bitcasa can kick/cancel abusive or uneconomic accounts. It seems strange to write an attack-piece on this new player, rather than on the industry as a whole.ġ. Instead, after a strong introduction, you switched over to discussing these 'Potential Flaws', which are no different than those facing every cloud storage vendor. The piece would probably have been improved by staying on your initial course and focusing on Bitcasa's business model, and the impact that certain specific technical choices have on the running costs.