It’s not just “seen as a bad deal by the company” - a business can’t give 100% of the value back to the employee because it has this pesky thing called “profits” it has to worry about :)
We've been doing a similar pattern already, because we have our web app iframed and communicating with outlook (via Office.JS) and gmail (via InboxSDK.JS) in order to read changes to the To: field and insert contents into the compose page based on that:
* stimulus encapsulates the javascript logic that "bridges" to Outlook and Gmail, including initializing the To: field listener
* stimulus actions can trigger the "bridge" as well
It's worked out very well - though I really hate dealing with native stuff in general - especially compatibility nightmares with older versions of Outlook. Probably less of a problem with iOS/Android.
Comment on the timing of this IPO: for a company to IPO "unfavorably" compared to previous valuations likely means ARM's hand was forced by timing considerations, unless they are running out of cash, which I don't think is the case.
My interpretation of this is that their investors suspect that whatever boost ARM is getting from AI optimism will likely peak soon, so the timing has to be now.
I know that's not fully rational because they're mostly unrelated, but certainly the optimism because of AI has to be good for them. Curious to see if this "signal" plays out - investors tend to be pretty savvy about timing.
> I know that's not fully rational because they're mostly unrelated, but certainly the optimism because of AI has to be good for them. Curious to see if this "signal" plays out - investors tend to be pretty savvy about timing.
The "investors" are SoftBank; they've been pretty much the stupidest money in the world for years.
While it's possible that they're being more savvy about the timing of this sale than about their investment decisions, I don't know that it should be the default assumption.
ARM was wholly owned by SoftBank. They did not have their own cash, it was all Softbank’s cash. And obviously SoftBank selling ARM means SoftBank wants to cash out, for whatever reason.
In fact, SoftBank is known for being the one of the stupidest big investors there is. They got lucky being an early investor in Alibaba, but have managed to piss most of that money away on getting left holding the bag on the peak.
What counts as “remote access”? Another device authenticated to Wi-Fi? Another device anywhere on the internet, with knowledge of the device ID? Another device anywhere on the internet with knowledge of email address?
These are vastly different criticality levels.
All the talk of IOCtl and assembly/bytes in the in the ButDefender report implies “another device on the Wi-Fi”, but I know wyze cams can be viewed over-the-Internet, ostensibly proxied via Wyze’s own servers, so maybe not?
I think part of that is the architecture and environment of the museum. They spend tons of attention to the high ceilings, sense of awe (a bit like a cathedral), and that can make all the difference compared to viewing something in your bedroom in the dark.
Moxie makes so many good critiques (some are so subtle, it might be worth a second read). I got the sense he’s trying very hard to be even handed and constructive about a situation he feels pretty badly about, but his true feelings are bleeding through in some of the side points / parentheticals.
One point that I disagree with is his almost axiomatic premise that decentralization is an inherent good and the implication that the Internet went wrong because it failed to stay decentralized. To hint at great cryptography as the solution, as he does im his conclusion, is baked deep in his bones as an amazing cryptographer, but I think he’s prescribing the wrong cure. The problems with the Internet are fundamentally not about decentralization - they’re about trust. It’s a people problem, not a technology problem. Because of this, cryptography (I do not mean crypto) simply cannot be the answer - even the best cryptography is, like a great legal system, only capable of dramatically reducing the overhead costs and risk of operating in a given environment. When it comes to what great cryptography can achieve, I think HTTPS and maybe some E2E stuff that’s happening with Signal is as good as it can get (interestingly, HTTPS is good in large part thanks to Moxie) - it cannot bring us back to some golden Internet age.
It’s pretty interesting to consider the intersection between what counts as “people” and “technical” problems.
For example, concurrent version control systems (like perforce) were horrible. This can be thought of as a technical problem, but it was actually right at the intersection of something technical and a people thing. What git understood is that having a canonical repo was a people issue, and it correctly abandoned a central “source of truth”… basically no amount of technology can fix what is a people problem, so no repos are “special” or “the one” from a technical point of view. It then forced people to sort their shit out. However, because of this insight, git was able to get the technical aspects spot on. It correctly recognized that what was needed was the right data structure. Git is extremely simple software, that basically does two things really well: branch and merge, but it needed the right data structure.
I think talking about centralization (APIs and infrastructure) vs decentralization (protocols) as a people vs tech problem is exactly the same sort of thing, and to get the correct view on it you have to really mail in detail where the people/tech problems begin/end.
it's impossible to talk about trust without talking about cryptography.
from an implementation pov "trust" is a distraction where anyone can quickly derail any argument citing "Trusting Trust" or "the show me the root of trust" ...
So to avoid meta-discussions talking about cryptography instead of trust skips the noise and goes straight to the heart of the issue.
Consider this:
- Talking about cryptography is hard but it's unambiguous.
- Talking about trust is easy but ambiguous.
Cryptography forces us to look at the reality of implementation instead of a "meta-psychological concept" from meat space. Problem with talking about trust in engineering is that we like to lift things from meatspace and model it within the digital space.
But we forget trust isn't "a thing", it constantly changes, it's useful only as a tool to accept randomness/chaos of life. And so we'll perpetually fail when discussing trust in the digital space or try to pin it down in order to allow converting it into a spec or an implementation.
And I think Moxie understands this and so skips the noise by going straight to cryptography which is the only "tool" that is meaningful when we talk about the things we base trust assumptions on (cia triad).
we need to bring back "Clippy" but instead of a paperclip it's the ghost of Ken Thompson chasing your mouse pointer around and slapping it with a copy of "Trusting Trust".
To be fair, the vision of crypto isn't to revert the web back to when it was better, that is pretty much not possible. That doesn't mean it can't lead us somewhere forward, different from the past, that is also better.
> One point that I disagree with is his almost axiomatic premise that decentralization is an inherent good and the implication that the Internet went wrong because it failed to stay decentralized.
But isn't decentralization one of the points of crypto and Web3? It doesn't matter if Moxie agrees with decentralization or not. If the direction everyone is charging in is "decentralization", and it's not really decentralized, then it's a movement that isn't heading where it thinks (or where it claims). That's still true, regardless of what Moxie thinks the direction should be.
The golden internet age was innovation and community. You wanted your own X? Code it yourself. You looking for a certain subject? You may find a forum.
Web2 has been polluted by frameworks, modules, libraries and that the generic website now looks like the next. It hasn't gotten any easier its gotten harder. Where do you actually start if you want to create a new website or "app"?
My mother knows html, she has her own website. When it comes down to wanting a gallery to display her portfolio the easiest answer is to say "install wordpress". Which isn't easy in any shape or form.
And then if you wish to be part of Googles Search Engine you have to pay sponsorship.
The golden age was the innovation, the new, creativity, surprisingly freedom. Folk putting work in to developing a new platform.
Sadly we are now surrounded by walled gardens and one of the caveats are that if you want it on display, you have to pay.
Isn't the fundamental discussion we should be having if decentralization embodies trust? Is something decentralized automatically trustful? Or can trust only be established in a decentralized way? Which way is it?
The only thing I see people agreeing on is that centralized setups are never (infinitely) trustworthy.
This is insightful, but a bit depressing. How do you propose solving these problems if cryptography is not the answer? At least Moxie is suggesting that there is a viable path forward by focusing on solutions that decentralize the infrastructure.
We have centuries of data and precedent from human legal systems. How could human and machine governance be improved with the aid of modern technology, including but not limited to, revision control of legislation and public caselaw, graph databases for threat analytics across time/space/network, automated identification of gaps in machine governance which require human intervention, and yes, all the tools of web3/crypt0.
> revision control of legislation and public caselaw
Even in pseudo-democracies, even in many outright autocracies, the information needed to build such a thing exists and is public. I don't know if anyone's built a git repo for all US federal law, but the information is there if you want to do it and it'd probably be a really fun project.
A quick search suggests there are repos but not with all the history.
I wonder if anybody has tried modeling real-world legal systems in a DAO. Probably too complicated, but I think you could pretty much cover the US constitution just as a thought experiment.
Watch some of the games and it might change your opinion. The thesis that "AI in Starcraft will only win via improved mechanics" is false - the AI was making some fascinating decisions / fundamentally different meta strategies.
Or watch [this game](https://www.youtube.com/watch?v=vUfwb4nOL84) between the top StarCraft AI (outside of AlphaStar) versus Serral, one of the top humans players. Unlike AlphaStar, this AI is not APM-limited; IIRC the top bots tend to play with about 100,000 APM, compared to 400 for the top humans. Serral won easily, despite the AI's vastly better mechanical skill.
PKC Security | Senior Developers | ONSITE | Full-time | Huntington Beach, CA
PKC Security is a software consultancy focused on solving impossible problems. Custom software, MVP's, and design sprints are our primary offerings at this time. Cybersecurity has become a smaller part of our offerings, but we still definitely do code audits and white box penetration tests.
We're going through a growth spurt right now and are looking for developers. We're focusing on using Node.js in the backend and React.js in the frontend as our go-to, but are always in search of the best tool for the job in general. Due to this there are less specific technical requirements as to experience with certain stacks, and we are looking for strong developers in general.
Check us out at www.pkc.io, or if you're bored, try our "Choose your own adventure" game at https://game.pkc.io. We built this at one of our monthly in-house hackathons!
Finally, feel free to reach out to our hiring team with any questions at jobs@pkcsecurity.com - please attach your resume and cover letter if you intend to apply for a position!
PKC | Huntington Beach, CA | Full-time | Onsite |https://pkc.io
PKC is looking for a Senior Frontend Developer with experience in React. You will be a critical member on our team of high-caliber, driven individuals. We value responsibility, learning, and ingenuity. We will be asking you to mentor our engineers and help them make wise decisions in
our front end code.
PKC is a consultancy focused on helping visionaries achieve positive social impact. Our mission is to “solve impossible problems”, which we define as constrictive, coercive, and complex. We use our combined talent and creativity to accomplish this for our clients.
Just a few of our benefits
- Monthly hackathons
- Challenging work in a supportive environment
- Healthy work/life balance
- Professional development
- Unlimited vacation
- 100% Company sponsored medical, dental, and vision insurance for you, spouse, and
dependents
- SIMPLE IRA 3% company matching
To learn more about our company, please visit www.pkc.io. Or, if you're just bored, checkout our "Choose your adventure" game that one of our hackathon teams built recently at https://game.pkc.io/
