Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
oneplane
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
31 ms
·
361.
▲
by
oneplane
3y ago
I don't know the context of why that is funny, but I believe having multiple viable modes of transportation is something densely populated areas should always have. Doing everything car-centric is just bad, plain and simple. If public
362.
▲
by
oneplane
3y ago
None of your points stand. Counterfeit prevention is not just some sort of 'this part is real but this other part is not', it is about system integrity. How do we in the world of technology prove integrity? With cryptography. It&#
363.
▲
by
oneplane
3y ago
I don't think I've touched on on theft as much as everyone else here seems to do, but in either case I'd still put that under the 'trustworthy to a degree' umbrella. I want to trust that a device in a known state be
364.
▲
by
oneplane
3y ago
You are confusing browser TLS and the trusted CA list with general CA in terms of PKI. So no, you are not in control and there is no list. > Does it really matter how is the DRM implemented? If you want to argue semantics instead of fact
365.
▲
by
oneplane
3y ago
It seems you have no clue what you are talking about. A PKI where the CA private key is not secret is not really a PKI now is it? As for asking buyers: I doubt 0.001% of buyers in any market segments has a clue about PKI or public key crypt
366.
▲
by
oneplane
3y ago
At yet here we are with nobody having a better plan. The issue is still the same as it has been for the past 20 years: making a (PKI-based) security feature means you can never share the secret parts or make it optional, otherwise it is imm
367.
▲
by
oneplane
3y ago
It's a huge thing because you can't really fit all the big speakers and audio stuff in tiny laptops and make them sound good. So we use extra steps (the DSP for example) to adjust how the speakers and amplifiers are controlled. Do
368.
▲
by
oneplane
3y ago
The public place doctrine is uniquely weird (and American) in that regard. Being seen or heard by others in a public place should not mean that you, as a private person, also gets recorded.
369.
▲
by
oneplane
3y ago
Well, you already mentioned it: the important updates that already have PoC in the wild that are somehow patched for RHEL but not for CentOS. The lag isn't always huge, but we definitely can't consider CentOS a RHEL bug-for-bug co
370.
▲
by
oneplane
3y ago
> That's not true. CentOS Stream is literally the testing ground for RHEL patches. So CentOS gets patches much earlier now than it ever did as a community project. It definitely is true, in our RHEL subscriptions we get patches that
371.
▲
by
oneplane
3y ago
Strong disagree. Fedora and CentOS Stream (well, C8 Stream is dead, but the other stream-position I suppose) add no value to me whatsoever and working with it is a net negative. The only reason we're still touching it is because vendor
372.
▲
by
oneplane
3y ago
But that's the thing, there is no good thing going. CentOS used to be a community rebuild of RHEL, and you could then use that if you didn't want support from Red Hat. But that is no longer the case since Red Hat killed that. Cent
373.
▲
by
oneplane
3y ago
Odd, what devices do you have? All of the NUCs, Toptons, Kingvoys, Qotoms support at least two disks, most more.
374.
▲
by
oneplane
3y ago
Already did, click the link. Better yet: any NUC will be better, except maybe the first three generations lowest end models if you want to go that far back.
375.
▲
by
oneplane
3y ago
Oh come on, not again. https://news.ycombinator.com/item?id=37819114 In short: this is just re-packaged underperforming SoC overstock and neither special nor worth the money. The same money buys better things. A little bit
376.
▲
by
oneplane
3y ago
There is no 'the internet'. As much as my cypherpunk heart would want there to be, in the end you have hosts (clients, servers) and subscribers (people) and those are located somewhere , and the laws of that place dictate what yo
377.
▲
by
oneplane
3y ago
Screw everyone who wants to enforce their sovereign laws when you do business on their turf? That seems a bit shortsighted.
378.
▲
by
oneplane
3y ago
This is very common. It's mostly due to the long-life programs where a large surplus or older SoCs are available. It's also why there is a large amount of C3000 based hardware suddenly.
379.
▲
by
oneplane
3y ago
Yes. But not a universal or easy way. You can't "tell" in the sense that you would just run MagicKeyloggerFinder on your computer and it will show you all the keyloggers, that's not how it works. In essence, it's th
380.
▲
by
oneplane
3y ago
It's not like that is a unique set of IO features, even for the SoC that is used it is somewhat sparse. Granted, bolting on more IO on such a low-end chip would have limited use, but SATA and PCIe have been rather common on small singl
381.
▲
by
oneplane
3y ago
Zima is average-good at branding and maybe styling and that's about it. The hardware is pretty much random ODM low power designs, but based on ancient 2016 era releases. Maybe it's just a company in Hong Kong trying to offload old
382.
▲
by
oneplane
3y ago
What you propose is computationally rather expensive, and on an API level really hard to implement uniformly. And thus the state was born. Trying to do it without state has been tried plenty of times, and it's bad. (Chef, SaltStack, An
383.
▲
by
oneplane
3y ago
Only if the infrastructure you target has no concepts of versions, and if it only has monolithic environments (which still holds true for much of the older infrastructure). But if we just take the GitOps branches problem, they are indeed no
384.
▲
by
oneplane
3y ago
Yes, because tags do not express where in a graph a node might be. It also gives you a new problem, because to find out what the previously known state was, you now have to read all tags on all resources. In Kubernetes, the state reconcilia
385.
▲
by
oneplane
3y ago
Because the source might no longer exist. Same as the current state might no longer exist. You can't diff something you don't know about and thus cannot create a transaction to deal with it. Three examples, but first context: You
386.
▲
by
oneplane
3y ago
State is required for a three-way comparison: the desired state, the last known state and the current state. And since not all information about the last known state will be expressed in the source configuration files, you need a secondary
387.
▲
by
oneplane
3y ago
Browser fingerprinting, probably network fingerprinting as well. Neither require client persistence.
388.
▲
by
oneplane
3y ago
Check https://news.ycombinator.com/newsfaq.html and https://news.ycombinator.com/newsguidelines.html In general, even if it's submitted, it's up to a bunch of clicks on the small arrows to keep it
389.
▲
by
oneplane
3y ago
I wonder how hard it would be to port this over to a Karpenter variant. I suppose the Proxmox API won't do the same things as an AWS EC2 API so an operator-in-the-middle would still be required.
390.
▲
by
oneplane
3y ago
This makes me wonder if there is research on pathways that 'cause' autism, or perhaps how we can find the 'vulnerability' which then is 'exploited' by something using those pathways. I'm using a bunch of q
More ›