fh973

This is very similar to FLARM devices (https://en.wikipedia.org/wiki/FLARM) for ultralights, gliders, etc. This is already broadly deployed (at least in Europe).

You could check for any lessons learned there. I think you can discount any flight users, because they would like to be seen too by other airplanes.

Towards which conclusion? Backdoors are common practice and so we have to assume their existance in foreign equipment? Or we did it first, so let's give the others a chance to deliver backdoors to us?

Apparently these problems are very hard to avoid. See here for some stories in context of the Space Shuttle: https://waynehale.wordpress.com/

As a remedy, they use tools that are tracked by RFID and tool cabinets that monitor that all tools are back in place.

How about "Californian Roulette"?

There is a spectrum of "open". The Google offices I know are not wide open areas but team offices or areas.

Consider that companies may prioritize team productivity over individual productivity. Communication and density could be beneficial towards that.

No, you are not allowed to do an ILS landing with zero ground visibility. And I doubt you get the flare right without any visiblity.

All available categories have a decision height > 0ft: https://en.wikipedia.org/wiki/Instrument_landing_system#ILS_...

Consider that car sharing, when run by one of the car manufacturers like BMW, DB or VW might be a way to tune financials (overproduce and dump) and their fleet mileage numbers by producing more small cars.

If one of these reasons goes away it might become much less attractive to them.

I think it is just policy of the German Research Network (DFN) for accounts. These accounts are valid Europe-wide for WLAN access in educational institutions for example.

Great, it's a toy! Seriously, with 249g, drone laws do not apply (start with 250g) and you can do whatever you want with it in public.

Here is its homepage: https://www.bokniseck.de/de

... or block storage systems in container environments, where the user somehow has write access to the block device.

WhatsApp has shown that you can actually build large-scale system infrastructures very efficiently. And they had global service, Uber could profit from sharding as you suggest.

With some exceptions like teco.edu...

TCP latency is on the order of dozens of us, not ms.

Valid question I'd say.

In many countries, it is illegal to land outside designated airfields without getting a permission first.

What's the difference to say something like Unity?

Isn't auto one-off to save a few grams of average CO2 emissions on paper to save the customer some tax money in countries where CO2 emissions are the base for taxation?

QUOBYTE | Santa Clara, CA and Berlin, Germany | Full-time | Onsite | https://www.quobyte.com/

Quobyte is developing a software storage system for file, block and object, built around a parallel file system core. Customers use our Data Center File System for HPC clusters in industry and academia, container and OpenStack infrastructures, postproduction, origin and CGI clusters, and as a scalable backend for SaaS products.

The Quobyte Data Center File System is a full-stack storage system, which means that engineering work covers everything from kernel development over database design to distributed systems engineering. In short: lots of challenging and fun problems!

Engineering:

* Senior Software Engineer - Berlin, Germany

* Junior Software Engineer - Berlin, Germany

* Test Engineer - Berlin, Germany

* Support Engineer - Berlin, Germany and US

Sales:

* Channel Manager, EMEA

* Sales Engineer - EMEA, US West / Central / East

* Enterprise Sales - EMEA, US West / Central / East

For detailed job descriptions please visit https://www.quobyte.com/careers.

We are looking forward to receiving your CV via work@quobyte.com.

In context of Apple this was often referred to as the Stockholm Syndrome.

https://en.m.wikipedia.org/wiki/Stockholm_syndrome

This is usually solved by encrypting and throwing away the key or seed to effectively delete.

Tape is no excuse to violating data retention policies.

This is usually solved by encrypting and throwing away the key or seed to effectively delete.

This would be 9x per year. What are examples of companies with such a growth rate?

Do all types emit RF noise? What to look out for to avoid it?

Quobyte | Berlin, Germany | Full-time | Onsite | https://www.quobyte.com/

Quobyte is developing a software storage system for file, block and object, built around a parallel file system core. Our customers use this data center file system for HPC clusters in industry and academia, container and OpenStack infrastructures, postproduction, origin and CGI clusters, and as a scalable backend for SaaS products.

Quobyte’s data center file system is a full-stack storage system, which means that engineering work covers everything from kernel development over database design to distributed systems engineering. In short: lots of challenging and fun problems!

We are currently looking for:

* Senior Software Engineer - Berlin, Germany

* Junior Software Engineer - Berlin, Germany

* Support Engineer - Berlin, Germany

* QA Engineer - Berlin, Germany

* Sales Engineer - EMEA

* Sales Engineer - US West / Central / East

* Channel Manager - EMEA

* Enterprise Sales - US West / Central / East

For detailed job descriptions please visit https://www.quobyte.com/careers.

Send your CV to work@quobyte.com.

The same goes for Google Checkout / Pay / ... or whatever it is called this quarter.

Reminds me of multistatic and passive radar, which were the entry subjects to my Wikipedia deep dive today.

While storage generally not a simple problem, Kubernetes' design makes it even harder. Why Kubernetes went this way is not entirely clear to me. One of the reasons could be its owners' focus on cloud infrastructures and tutorial-level developer use cases, where you want to show how to dynamically create and consume a file system backed by GCE persistent disks or EBS. Also getting a secure and usable Kubernetes setup running is currently a lucrative business model.

But as the OP writes, the standard case it should support is secure access to existing storage, and Kubernetes fails there on all levels. Simple things should be simple, hard things should be possible.

In its API design, it hides storage under abstractions like PVC, PV, StorageClass that most users have not seen before in their career (where do they come from btw?) and which do not re-use general system architecture concepts. Worse, these abstractions do not have exact definitions as their semantics can be massaged with access control rules.

Consider the most simple case: mounting an existing file systems and authenticate with a Kubernetes secret. You should be able to do this in 3-4 lines in a pod defnition. Instead you need to create several yaml files, whose content is strongly dependent on how your Kubernetes was set up, so no general tutorial will help you (but others are, see above).

And this is just for getting the basics going. Secure access / user authentication is still unsolved after two years (https://www.quobyte.com/blog/2017/03/17/the-state-of-secure-...), and does not seem to be high on the agenda neither in Kubernetes nor CSI.

There are other basics missing (like file systems do not have necessarily a "size"), but let's not go into detail there.

That's why runway designations are updated periodically to reflect the magnetic change.

This "law of duality" is not very convincing. He does not offer criteria where it applies not does he argue why it would apply for the examples given. How does his adoption curve apply to coke?

Especially in the cloud market, I see rather more players in the future as the underlying technologies become commercially available or even commodity.

In the other side customers value support and services, which does not scale well, and smaller players have an advantage.