> Alternatively, don't commit passwords/API-keys/sensitive-info to your repo.
This is, of course, the right answer.
However, it's frustrating that several frameworks make this very easy to get wrong. Anything that has an application.yml, database.yml, or similar configuration file that normally lives within the same directory as the source code, and which is intended to contain credentials, means that lots of people will make that mistake.
It's one of the fundamental errors that you see so often in web frameworks like Rails, this whole idea of mixing application code and configuration files into one big tree. I don't know how this practice caught on, but it has, and it so frequently causes mistakes, both big ones like accidentally publishing credentials, and simply frustrating ones like confusing the difference between application code and configuration in ways that make it more difficult to have multiple local configurations and updating the application code independently.
Different versions of this slideshow have different information. The table titled "ME Core Evolution" (slide 15/16), for example, shows two generations in the version on slideshare, but three generations in the PDF on recon.cx. There is also more discussion of the SPARC architecture in the PDF version.
I did wonder if SPARC refers to the Sun architecture, or if it's an evolution of ARC that simply collides with the other name. He doesn't mention having successfully disassembled any of the BayTrail/TXE versions' firmware yet.
The author clearly believes it's SPARC in Bay Trail, since he seems surprised by it. A coincidence does seem pretty likely but you'd think Oracle would object.
You can hail a taxi by hand, and pay with cash, and no one will have your information in a database that can be used against you later.
While I don't agree with all of his reasoning here, he is correct that taxis offer you substantially more privacy than Uber, and Uber has been known to abuse the data they collect on passengers in several instances, so it's far more than just a theoretical concern.
> You can hail a taxi by hand, and pay with cash, and no one will have your information in a database that can be used against you later.
No you can't. Plenty of taxis record the backseats of their cars, and you have no way of knowing which do/don't.
Taxis don't offer you enough privacy over Uber, and the reason he's coming after Uber is because he wants to stay relevant, not because Uber is particularly bad.
But if you pay by cash, there's no easy way to match that recording to you.
Also, I'm pretty sure RMS doesn't give a fig about "relevance". He's just applying his principles to the world as he sees it, and he's been doing this literally for decades:
Looks like a digital remake. https://www.hq.nasa.gov/alsj/a11/a11-fltplan.htm contains a high-resolution scan of the original, plus this version with the annotation "Re-formatted by Thomas Schwagmeier".
If you compare them, the styles are very different; different fonts, color graphics instead of line art, etc. Looks like this is just entirely recreated based on the originals, not a dump of any data from the originals; I'm willing to bet that most of the originals were drafted by hand, not digitized in any way.
I don't want to own a self-driving car. I want the self-driving equivalent of a taxi or Uber. Press a button on my phone, the closest one shows up, drives me where I want to go, and then hangs out nearby for the next person or goes back to the closest designated parking location.
These self-driving cars will be cheaper than even UberX/Lyft/whatever, as there is no driver to have to pay. They can be smaller than a cab, taking up much less parking room (they can park too close for their doors to open, and they don't need to including seating for a driver), which can actually be a fairly significant cost in the city, where convenient parking spaces can sell for as much as a house does elsewhere.
I don't understand why they don't just change the District of Columbia to consist only of the federal buildings, and give the rest back to Maryland (I don't believe there are still any residences on the Virginia side of the river, but if so, give that land back to Virginia).
Then there can be the constitutionally mandated federal district, that consists simply of the federal buildings, and everywhere that people live (outside of the White House, Number One Observatory Circle, and maybe a few other formal federal residences) would actually be within state jurisdiction.
Does that really matter? Couldn't you just say "Federal Buildings are in the jurisdiction of the District of Columbia, everything else is in the jurisdiction of Maryland"?
If that doesn't work, it doesn't really matter that much if you sweep up a few commercial buildings into DC. Most of those federal buildings are mixed in with retail, hotels, convention centers, offices, and the like, which doesn't cause disenfranchisement if you include them within DC. The big problem is residential areas.
The district would be subservient to the state for taxes, lease contracts etc. but it's entirely possible to treat the individual buildings as "sovereign territory of the District of Columbia" just like how the little townhouse in London is Ecuadorian territory, and thousands of other embassies around the world like it.
Once you walked off the sidewalk, or off the third floor elevators, or through that door, etc, you would be on "federal turf" so to speak. It's not about a geographical circle.
None of these are particularly new questions. There are federal buildings and federal leased space in every major city across the US. The feds have their own Federal Protective Service Police that respond to incidents on federal property in major cities nation wide. Fire/EMS is usually handled by the locals.
The core national mall area is already protected by US Park Police, it would be possible to create a core DC area as a national park and return the rest of all land to the states. Federal buildings on land returned to the states would be treated like any other federal building in a state. There are plenty of federal buildings in NoVa and Maryland already.
It's probably a good idea for DC to not be inside the territory of any state. Maryland would have the power to severely disrupt the federal government otherwise, and it could be seen as a conflict of interest if Maryland asks for a bunch of money to improve their roads or emergency services, since some of it will trickle back down to benefit the federal government.
It's also open source. Can we stop with this fucking red herring already? He's talking about a service, right now, under the direct control of the US military. You're talking about grant funding for an open source tool.
No, he's not. He's talking about a single research laboratory MIT runs on a military base. Which somehow makes the entire university under direct control of the military?
This is, of course, the right answer.
However, it's frustrating that several frameworks make this very easy to get wrong. Anything that has an application.yml, database.yml, or similar configuration file that normally lives within the same directory as the source code, and which is intended to contain credentials, means that lots of people will make that mistake.
It's one of the fundamental errors that you see so often in web frameworks like Rails, this whole idea of mixing application code and configuration files into one big tree. I don't know how this practice caught on, but it has, and it so frequently causes mistakes, both big ones like accidentally publishing credentials, and simply frustrating ones like confusing the difference between application code and configuration in ways that make it more difficult to have multiple local configurations and updating the application code independently.