1,444 karma · joined May 28, 2008
[ my public key: https://keybase.io/imajes; my proof: https://keybase.io/imajes/sigs/wGOGcjbP_peYxMh9PgqbnNt6rCukmAps21TBzfZe6aI ]
- All teams will henceforth expose their data and functionality through service interfaces.
- Teams must communicate with each other through these interfaces.
- There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.
- It doesn’t matter what technology they use.
- All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
- Anyone who doesn’t do this will be fired. Thank you; have a nice day!
still kinda works.arguably they aren't close to each other in tiers of the stack, and don't really overlap. The sorts of libraries you might choose to use to do something could differ, (e.g. json processing - in the front end, you'd pick usability and security over a lower level more optimized transcoder for the api).
That said, I agree with your core premise- not understanding, and chasing a nail with a hammer, but geekily named repos per language just sounds like someone who doesn't understand how something git works...
I'd also say I have a bias, as I've also used avalara a couple times before and found it to be quite a bit superior in making it seem quite a bit more effortless -- taxation is so byzantine I don't have any expectation that I could understand it, so I want to trust that the provider i use is very confident they do.
not sure if that helps a lot, but it was also a few months ago ;)
Seems spectrum maxes out at 120mbps, whereas they used to sell 300mbps. (or is that just me?)
that alone creates plenty of noise to wade through...
Why does Google profit from HTTPS over HTTP?
Amazon.com (HTTP) redirects to (HTTPS), via a 301 - that's Permanent Redirection.
This also isn't Mozilla, but Chrome.
And honestly i don't even know where to begin, but you should look into HSTS, and the vulnerabilities that exist transitioning between the two modes[1],
as well as looking at the issues (data bleed, etc) that happen with a http+https web and mixed content.
Finally the bigger issue to ad rev is likely to be cross origin content rather than https.
and, er, semantically there's a gulf of difference between "Not Secure" and "Insecure".
Also, arguably, the shift to a https first web is what's helping us shine light into bad CAs and deeper audits that are finding the esoteric bugs -- so it's only a good thing, in the long term.
[1]: http://michael-coates.blogspot.com/2009/02/compromising-http...
For example:
This photo-
http://www.gettyimages.com/license/515020819
is actually this photo:
https://www.flickr.com/photos/library_of_congress/2178341487
which was taken by a now dead photographer called Russell Lee, and owned by the Farm Security Administration.
PS: this same person appears to have about 500k listings for prints etc on amazon.com..... why aren't they a co-defendant?
if i read 17 U.S. Code § 201 (d) clearly, it suggests you can transfer ownership of copyright in any normal legal way of executing a contract.
I think your confusion is around the idea of works falling into the public domain via expiry of copyright, and/or works that do not have an explicit declaration of rights ownership.
In this case it seems she was pretty clear about her transfer of ownership. I don't believe you can rescind that just as you prefer, at any time.
that seems pretty clear cut to me. Conditions for reproduction only seem to express the general ways the content should be available for users of the library. Nothing limiting availability, in fact it's promoting methods of being available.
So that leaves the question of a: whether or not getty et al were able to sell works in the public domain. My quick read of it seems that if they can come up with some kind of argument that they are selling derivative work (including perhaps some kind of unique identification layer, or meta data perhaps ... ?), OR that they are selling a reproduction. tenuous, but that may be their justification.
as for requesting a license fee, well that's on LCS and Alamy (who I don't think have had an issue in the past 3 years of this stuff, so the multiplier doesn't apply here)
NB: Alamy being a uk company, so they can hide behind a corporate shield if their assets are mostly offshore...
this is the settle page, from the first exhibit: https://settle.lcs.global/103173853953 -- that's what she got sent. It doesn't appear that they argue they are the exclusive license holder, and especially if they argue they are holding a license to derivative work -- well. that's a whole ball of wax.
Thinking further, since she no longer holds the copyright to these images, and the United States is not listed as a co-plaintiff, I'm not even sure she has standing to bring this case at all -- but, on that, IANAL. :P