Note that this list is list of places where if you are enterprise starlink customer SpaceX can provide you with physical ethernet port to plug your cable into when you want to handle your traffic yourself instead of that just going directly to the internet. That is kind of obscure service that even land-based PLMN operators offer but usually do not document in this way in publicly available documentation.
From the perspective of network design, the fact that this certainly is not exhaustive list of places where SpaceX has physical DC presence and physical reality it comes that some of these datacenters are selected based on the fact that the ground station is somewhere nearby (I would be surprised if there is even just one place on the list where nearby means "on the roof", because there is a lot of technical, logistical and administrative reasons why you do not want to put such a thing at a roof of a datacenter).
None of the original 5 buildings at Telehouse in London have any dishes on the roof but the new Telehouse South a few hundred yards to the South seems to have some on the roof but they don't look like they are for a SpaceX groundstation.
SpaceX groundstations look a bit different, they are a bunch of white domes about 1-2m in diameter, usually 8 or 9 of clustered together.
It's handled by Arqiva here in the UK it seems, so no SpaceX branding on anything.
SpaceX also applied for two new grounds station sites in the UK, one a few miles West of Telehouse, south of Rainham. The other site is up in Harlow, Essex.
(I don't think any of this is secret, all of the info above can be found with some googling and scrolling in maps.)
I used to have private peering with a satelite provider at telehouse, one which downlinked from GEO in Amsterdam and presented traffic direct. They simply backhauled it over their own network (tagged as mpls I guess). Indeed it would arrive on that link even when downlinked on other stations around the globe.
> when you want to handle your traffic yourself instead of that just going directly to the internet
Isn't that skipping over the more sensible middle ground of a VPN, which is what is more common for at least small or medium sized business customers of mobile networks.
Very much depends on your applications. Some critical communications you don't want to trust to the internet at all. Some communication latency is important and so you can save a few MS by locating in such a data center. Some communication takes a lot of bandwidth and both of you want a cache in the data center to avoid use of the large pipes (youtube for example has servers in various colocation points just to cache the popular videos). Many small/medium businesses don't have a good data center, they outsource that to someone else, and starlink is just as good as anyone else (check all the fine print on the contract to see if this is true for your needs)
I haven't checked recently, but the FBI/CIA (I'm not sure which, but probably both) had 4-5 completely isolated networks, no connection to any other network. Once a computer was connected to an isolated network it would be destroyed when the lifespan was up - thus ensuring that classified data could not leak off the network. When they needed to connect to other locations they bought a separate fiber connection the entire way - the fiber would be in the same bundle as internet traffic, but otherwise isolated. (There are several cases where a virus got onto such a network despite the isolation so this isn't perfect, but...)
It's more sensible if your goal is to not go "directly to the internet" which was the original statet motivation I replied to and also what I'd expect to cover most use cases. If you have additional requirements then sure something else might make more sense.
Why is that more sensible? It's worse, more expensive and has more moving parts. The only reason you'd use a VPN is if you're small enough that Starlink won't give you a PNI, or you can't afford it.
That depends if the goal of handling your own traffic is integrity (which a VPN can give you) or availability (which requires dedicated pathing through a leased line).
The "two E10Ks" part is the important part there, as you need a very powerful server to support SunRay users running Solaris. At my university there was something like 200 SunRays supported by cluster of T2000s (7 nodes IIRC), it was fine for CDE, Firefox and few dtterms, completely unusable with Gnome (it took Gnome like 10 minutes to even start).
On the other hand I have heard of some success stories about using SunRays as RDP clients, which is actually supported configuration (you still need a Solaris box that manages the sunrays and translates RDP to ALP).
In washing machine application the locking action is quite fast as the heating element is PTC connected more or less directly to mains, pretty substantial amount of energy gets dumped into the wax over few AC line cycles. In that application (and also in most industrial automation situations) ~100ms is more than fast enough because when most of the effector components are AC powered you end up with ~40ms worst case actuation delay just from the physics of AC electricity. On my washing machine it is quite noticeable that when you press "start" the door gets positively locked well before the capacitive sensing "button" finishes playing its haptic feedback non-sense. (the fact that front panel of cheap-ish toploading washing machine is actually a huge touchpad with haptic feedback that is designed to look and behave like five physical buttons says many things about economics of manufacturing stuff for that somewhat hostile environment at these scales)
oh interesting - I didn't realize PTCs can be used that way safely. I thought it hits a target temperature and then will continue heating at that temperature (which in your scenario would be unsafe). Maybe for my usecase it'll be hard to find a suitable actuator b/c I have a 5V system running of battery (looks like 12V ones do exist though)
You are assuming that the forgers care about the machine readable part at all. Vast majority of forged EU ID cards I have seen are trivially recognizable by the fact that the MRZ contains something that kinda-sorta matches the human readable part, but is syntactically invalid and has wrong checksums.
The problem there is that this is exactly the class of bug that does not exist in GNU coreutils because of philosophy of that project. Non-existence of such bugs proves that the impementation is not copied from AT&T code.
At a first glance passive RFID would be a perfect match for ride photos, the whole mechanism is ridiculously fast so speed of the ride would not matter much (the technology works at highway speeds just fine) and can work over ~15 meters.
But there are two somewhat significant issues with the radio layer in this application: the geometry of tag antenna is somewhat critical (making it into a band would be problematic) and the back scatter is attenuated by salt water blobs (ie. people) almost perfectly.
I suspect that is not an inherent limitation of the dual-ISA design (the HotChips slides mention some sort of bidirectional thread state mapping between arm and z), but just about there not being z/VM release that supports that (building such a thing is probably SMoP, but another question is whether that makes business sense).
IBM's mainframes do not really have a reset vector, the CPU gets initialized by some external means into whatever state the OS expects and then the clock gets enabled, so that distinction is quite moot.
They were always required. IIRC early AMD64 CPUs did not support x87 instructions in long mode at all (causing #UD), and that support was Intel's extension in first EM64T CPUs.
LAHF and SAHF are an interesting rabbit hole themselves.
If you ever dug into x86 assembler programming... at first they make no sense at all. They only save/restore a tiny part of the available flag registers. The mnemonics themselves make little sense - load/store are not really used in any other base x86 mnemonics (unlike e.g. 6502 mnemonics, which use LD?/ST? instead of MOV like x86).
It only clicked when I read an Intel document about porting assembler code from the 8080 to the 8086.
LAHF/SAHF are basically convenience instructions to make porting easier. Many 8080 instructions did not alter the flags, unlike their 8086 counterparts. Substituting an `INX` instruction with `LAHF; INC; SAHF` made it possible to mechanically translate assembler source code.
And yeah, 8080 mnemonics had LDA and STA like the 6502...
Basically the only thing interesting about the ConcertMaster is that Carmack used it (and that it looks somewhat cool). As for the keyboard itself, it is just a basic OEM membrane keyboard and not that good one even. The speakers are lets say adequate for the time and size.
Interestingly, the speaker part and the keyboard part are completely separate. The "cable" consists of four separate cables (keyboard, power, line out, mic in) in a thin sleeve. Mine was supplied with AT plug on the keyboard cable and Y-adapter that converted PS2 into AT DIN and barell jack for the speaker power. The keyboard label indeed says it is powered by 9V DC, but I guess that never really happened as PS/2 is 5V no matter what various devices say.
Edit: And as for the supper hard to find nowadays part: I suspect that part of the reason is that the keyboard module inside the thing is ridiculously sensitive to even minor spills.
I have one! It's fun for retro PCs that don't have speakers or a mic, as it provides everything you need right there without having to setup the Altec Lansings.
Also LOL:
> it has the advantage of packing the best sound system I have ever come across on a keyboard
From the perspective of network design, the fact that this certainly is not exhaustive list of places where SpaceX has physical DC presence and physical reality it comes that some of these datacenters are selected based on the fact that the ground station is somewhere nearby (I would be surprised if there is even just one place on the list where nearby means "on the roof", because there is a lot of technical, logistical and administrative reasons why you do not want to put such a thing at a roof of a datacenter).
reply