Hacker Newsnew | past | comments | ask | show | jobs | submit | sureglymop's commentslogin

> strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering

Sounds fever dreamish. Thank you sincerely (not) for creating it!


Misconfigured database that was publicly accessible, vulnerability/exploit dropped around the same time.

Does anyone know e.g. a small systemd-nspawn oneliner to SSH in securely?

There's nothing dangerous about SSHing into an untrusted server unless you're using the same keys for everything.

Remote resources only get your public key. It’s meant to be shared! Hence the word “public.”

The threat is having a private key stolen, in which case, having multiple keys can mitigate the amount of damage a threat actor can do. However, to steal your private key would involve a successful attack against your client, not against any server you might have given the public key to.


There is also the threat of the server sending a data sequence that exploits a vulnerability in your terminal. It has happened before, but it’s rare.

Always encrypt your SSH private key! It shouldn’t be so easily stolen.

I wonder if we would still call it "knowledge work" if no human knowledge/experience is required or in the loop anymore. And also if we will stop looking up to that generally.

Because AI stands at odds with the concept of meritocracy I also wonder if we will stop democratically electing other humans and outsource such tasks as well.

Overall I'm not seeing it. Progress is already slow and so far I personally think what AI can do is a nice party trick but it remains unimpressive if judged rigorously.

It doesn't matter if it can one shot code a game in a few minutes. The reason why a game made by a human is probably still better is because the human spends hours and days of deep focus to research and create it. It is not at all clear that, given as much time, AI could deliver the same results.


I think running and managing and possibly misconfiguring a keycloak java monolith would be exactly what I'd want to avoid which is why it's cool that they offer this.

There are a lot other identity providers around you can pick from, I merely mentioned it as I personally use it, as it's so easy to run and integrate with social auth - and comes with features such as simple password-less auth.

The forward auth/proxy auth is not a keycloak feature, it's a proxy feature, which just need some identity provider. If you look for the mentioned term via Google or AI/llm you will find multiple options, some of which are as easy to setup as a simple docker run cmd with an open port

I.e. https://docs.goauthentik.io/add-secure-apps/providers/proxy/...


That's true in general. But default view is still subjective. The challenge probably lies in recognizing the larges subset of your user base that would like it to be a certain consistent way.

Have you explored the ideas explored for the Vale language: https://vale.dev/

May be an interesting approach. That language seems very academic and slow moving at the moment though.


I think Vale is interesting, but yeah, they have had some setbacks, in my understanding more to do with the personal lives of the author rather than the ideas. I need to spend more time with it.

I don't think they pay any taxes if they make $5 per hour.

I graduated high school less than a decade ago and I had to read about 90% of those books. And those are just the German ones, there were at least half as many English and French ones too. I have younger cousins who are in the school system now and I am fairly certain that it is still the same. Actually I think it is probably mandated by the curriculum.


WASM is just a bytecode format for a stack based vm. Granted it is weirdly named, the actual "Assembly" equivalent is WAT.

But the point is, it is a format specification, which has nothing to do with safety. You can implement a totally unsafe WASM runtime if you so choose. Personally I think it's not a bad thing, at least we have something like it that can run in a browser environment. But I am curious to know why you dislike it so much.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: