Comment A old mystery explained (Score 2) 33
> meaning one button can do multiple things.
At last, we know how the console buttons of Padme's ship work.
> meaning one button can do multiple things.
At last, we know how the console buttons of Padme's ship work.
I think Microsoft promised investors they'd make an impossible amount of money with copilot and have realized that the only way they can follow through is to rename their entire offering.
Considering the current bloodbath over at CISA and the ongoing sabotage of the rest of the nation's cybersecurity infrastructure at the behest of Comrade Trump, I'd say the government is the last place to look for help keeping your secrets out of the hands of the competition.
This is what APIs are for, surely?
We've learned complaining only draws more calls.
It's been a long time since I read The Invisible Man, but I seen to recall that his mechanism was chemical as well; something he ate or drank that turned his cells transparent.
Because Zonai devices are magic.
Seem to be a number of down sites right now. Larger AWS issue perhaps. It's almost like recentralizing the decentralized internet was a bad idea!
I feel like Firefox continues to exist despite the foundation's efforts rather than because of them.
There's a few other things which are worth taking a look at on the topic at http://internetofagreements.co... - the HBR piece is short, and this is not a topic that is particularly easy to compress.
There are two things in particular that didn't come across well. Firstly, we expect this to be a five to ten year process. We're well aware how much there is to do, and how far this all has to come. We don't dream you can just digitize a body of law through natural language processing and then have an AI make legal rulings any time soon. But narrow areas - product labeling comes to mind - might be high value and tractable quite soon. And Internet of Agreements blockchain. Blockchain is a *how*, but IoA is a *why*.
Second thing is that IoA's intention is to get people with various pieces of this picture into direct contact with each other, with a rough sense of the goal state in a decade or so, to start building the bits that are currently financially possible to do real engineering on. As time passes, more and more of the vision should become manageable, and things will pick up speed and come together.
Hope that helps.
Heh, unless you work for a GM dealership, you have NO idea how bad GM is at IT. Their dealer-side website still does not officially support anything other than IE8. Business reporting relies on ActiveX integration with Excel, and only works properly with Excel 2000 and 2003. It can be made to work under 2007, but they don't support anything higher. Parts of the service-related workbenches still use VBScript. It used to be accessible only over a super-slow satellite link, but they changed that a few years ago, thank god.
To be fair, though, Toyota's web back-end, Dealer Daily, is even worse. IE-only, accessible only through a dedicated T1 which may not be used for anything else (but which you still pay full price for, of course). Blank page under anything other than IE.
Come to think of it, a lot of dealership stuff is locked on IE. Dealertrack (intentionally locks out non-IE browsers), Dealersocket CRM (featured-limited under non-IE browsers). ADP is the biggest supplier of dealership management software in the US and most of their stuff is entirely reliant on IE.
It's a pathetic state of affairs.
As long as it doesn't break Noscript, I'm ok with this. It really IS folly to try to use the modern web without any javascript at all, but with Noscript I can still pick and choose which sites are allowed to run it in my browser.
Sorry, I don't use slashdot very often these days, it used to auto-link URLs - didn't realize it wasn't doing it these days!
Sorry, didn't realize I wasn't logged in!
I should start this with a disclaimer: I'm the founder of the Hexayurt Project, a Free Hardware building system aimed at refugees and in widespread use at Burning Man. It's those silver pod things (http://hexayurt.com)
I think Wikihouse is exciting technically, but it's *incredibly* expensive to build - something like 7000 EUR of CNC cutting time for a single room. The parametric design aspects of the project are great, however, and I can see a future in which the components are mass produced at reasonable price and then assembled according to plans generated from the parametric design software. But without some kind of standardization, this kind of production is going to remain incurably expensive and therefore just another architectural demo. It's not a technology until costs are estimated. This has happened before: Architecture For Humanity's Open Architecture Network (http://openarchitecturenetwork.org/) rapidly filled with impractical technology demonstrators and student projects - 10000+ designs, but how many practically buildable?
Actually getting buildings that people can build is hard. Architects are trained to think about custom work, one-offs and impressing other architects. Mass producing housing at a price people can afford (hello, Mortage Crisis, goodbye Mortgage Crisis) requires a radical rethink of how we do construction: modularity, prefabrication, standardization - all the same things we did for every other technology we wanted to be cheap, easy and reliable.
It's often said that home building is the last truly-madly-deeply inefficient global industry. Imagine if they built cars by having people come to your garage to hand-assemble them! Whether the radical change is mass manufacture of entire houses Buckminster Fuller style, interchangable modular components (structural insualted panels) or something like 3D printing with insulated concrete, we can't keep buliding houses by hand in a world where everything else is efficiently mass produced with near-zero defects and not distort the shape of our societies.
Hexayurts are dirt cheap and designed for modular mass manufacture. But they look weird. Such is life
"If you want to eat hippopatomus, you've got to pay the freight." -- attributed to an IBM guy, about why IBM software uses so much memory