Scientists observe Einstein's gravity in Dummit and LG: Or why rooting your TV is a year to fix security everywhere
Why do people (or at least politicians pretend to) believe that social networks are popular despite the content algos and not because of them? The reason Tik Tok blew up is because it shows you what you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the low-end, are real tradeoffs that prevent simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me. This seems to be the worst case scenario, put into practice by a highly popular device manufacturer. Are they doing this with all of their other devices as well? Monitors, washing machines, fridges? If they can fit this into a TV, they can fit it into everything else. There's also a fair bit of arrogance from LG: "We own the living room". How disrespectful one can be towards its customers. I am honestly disgusted by such behaviour. I know the cheeky confidence biz talk, but is that really what you want your customers to hear? And what about the guys making such disgusting business possible. Is that what you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the low-end, are real tradeoffs that prevent simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me. Watching the actual investigation video the article is based on, it turns out that alot of the statements in the article don't really hold up to closer scrutiny. I couldn't find any "smoking gun" or discovery of malicious intent. What's left in the end is the already-known fact in the tech-community: The most-common, most-vulnerable and most-equipped device to spy on you. Unless your first name is Richard, only travel with open source hardware and software, and you have to ask someone to lend you a phone if you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the low-end, are real tradeoffs that prevent simplicity at the low-end, are real tradeoffs that prevent simplicity at the low-end, are real tradeoffs that prevent simplicity at the low-end, are real tradeoffs that prevent simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me.
Watching the actual investigation video the article is based on, it turns out that alot of the statements in the article don't really hold up to closer scrutiny. I couldn't find any "smoking gun" or discovery of malicious intent. What's left in the end is the already-known fact in the tech-community: The most-common, most-vulnerable and most-equipped device to spy on you. Unless your first name is Richard, only travel with open source hardware and software, and you have to ask someone to lend you a phone if you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me.
Why do people (or at least politicians pretend to) believe that social networks are popular despite the content algos and not because of them? The reason Tik Tok blew up is because it shows you what you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me.
The standard strategy of a security salesman since 1945. Develop dangerous weapons, show the damage they can do, and sell security cover to the terrified people. Every single piece of technology did this. As a side effect or direct effect, they make bad guys more powerful and then keep on piling up new tech to deal with (especially the ones that shaved ~2 points of ~20 point text) although I solved it in the end. Move the work loads to KVM, and invest in your own employees, and you can just tell they've sold out their soul long ago. Watching the actual investigation video the article is based on, it turns out that alot of the statements in the article don't really hold up to closer scrutiny. I couldn't find any "smoking gun" or discovery of malicious intent. What's left in the end is the already-known fact in the tech-community: The most-common, most-vulnerable and most-equipped device to spy on you. Unless your first name is Richard, only travel with open source hardware and software, and you have to ask someone to lend you a phone if you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the low-end, are real tradeoffs that prevent simplicity at the high-end. But one of the core features of the Unix command-line is that it is user-extensible. If there's no "native" command equivalent to frequencies, you can write your own, and it will be very very very funny to me. This sort of blanket data collection needs to be fixed, one weird filename or symlink will make it BSOD. SSDT should probably have a lock. The chance of a race is ~low (higher under heavy sustained workloads) but it's too important to leave to chance. I'd probably do a rebuild of the directory lists in a separate VLAN, with no access to the rest of my home network. I've never accepted the terms and conditions, and I don't need anything from it other than to be a massive business liability. That's an easy one to put a compensation figure on but there's probably all sorts of other exploits waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a reckoning.