lixtra

It’s reckless hacking. Should be punished like reckless driving.

For the interested.

According to this source[1], RMS wrote:

> plausible scenario is that she presented herself to him as entirely willing

[1] https://web.archive.org/web/20190913103059/https://medium.co...

How do you verify the ‚beauty‘ of a result. There have always been infinite provable Theorems around. Only some are interesting and beautiful.

> You set up an HTTP server that literally sends people the data when they request it. Don't do that if you don't want people to have the data.

By the same argument I could say: If I send you an exploit and you execute it, don’t complain that your setup fell for it. Just don’t download and run random data from the internet.

In reality there’s a consent and expectation beyond the pure technicals.

Would that large trial have shown the cancerous effect of smoking? If not, do you then agree that some possible adverse effects were not checked for and could have slipped through?

Of course, all the generated code has to reviewed and vetted for by a senior developer. Of course, this has to be re-done every now and then when new classes of vulnerabilities appear that the previous generation didn’t have in mind.

Or do you just trust the AI that was trained on a lot of bogus code?

Hand in your paper when you’re on vacation or even better on a conference in Europe. GDPR will apply. Of course it will take so long that you won’t benefit from a decision for your studies. And one possible outcome is that your college won’t allow submitting from EU and won’t admit EU citizens (similar to US citizens having difficulties opening accounts in EU banks).

While there was some intent to cause harm their attempts were amateurish. The actual damage was done by the agent setting up aws infrastructure not on the demands of the owner.

Ideally, you submit your own project as https://news.ycombinator.com/showhn.html

Yes, there are also many other lucrative illegal activities.

> The cleanest mitigation is to return results in a canonical order, such as lexicographic sorting.

And hope that the sorting time cannot be used as a side channel.

I agree it’s awkward. But I don’t find it creepy per se. It was a tradeoff to which all parties consented.

In one case there was just that one room available stranded in the middle of nowhere.

In other cases it was due to lack of financial resources.

Example Finland. Could you end up in a nude Sauna with your superior? Yes, especially if it is same sex.

Example Germany. Which law would be broken? Internal compliance rules, yes, that would be often the case.

HN guidelines say: Assume good faith. We should apply it to Sheryl here as well.

In Europe several of my acquaintances shared a bed with their professors/superior for various non-sexual reasons. It’s also a cultural thing.

As you would expect from a state press release, not a tabloid publication.

The 4% rule is considered safe for a 30 year retirement period. So at 50 you might want to withdraw a little less.

Somehow this code lacks the magic I‘m used from rails:

    class BooksController < ApplicationController
    def show
        @book = Book.find(params[:id])
        add_breadcrumb("Home", path: root_path)
        add_breadcrumb("Books", path: books_path)
        add_breadcrumb(@book.title)
      end
    end

Only the title is specific to the show method. Home should be set by the application controller and Books by the books controller code.

Layer8 DID the thing though, skimmed through the code and thought about security issues.

The requested feature is more like list-unsubscribe headers for mailing lists[1]. Instead of categorizing the mail as spam (blocking) you send a clean unsubscribe back to the sender.

[1] https://www.twilio.com/en-us/blog/insights/list-unsubscribe

Yes, you could use union. But then you have to pad the columns of the other tables with NULLs to arrive at the same output and carefully count. And we all hate counting.

You might even split them so that k out of n trusted people are needed to restore them.

For example https://shamir.securitytools.io/

A naive approach could still leak information through side channels. E.g. if you search regularly for foobar, the answer might suddenly get slower if foobar appears more in the document base.

Depending on the context it could be relevant.

Maybe thought provoking. But sad to read ai garbage. It’s easy to imagine a better world. But you also need to provide a way to reach it. For example a lot of things are wrong with docker. But it enables us to run yesterday’s software in the cloud. Tomorrow’s software is not written yet.

Spock in the Wrath of Khan:

“As a matter of cosmic history, it has always been easier to destroy than to create.”

It’s like putting

curl -sSL https://example.com/install.sh | sh

In your action. For sure happens.

(2014) [1]

[1] https://web.archive.org/web/20140901000000*/https://www.cut-...

Intermittent fasting could work.

And time.

> It makes writing the happy path slower, but is writing the happy path _programming?_

The happy path is just fine for many cases.

Your home isn’t built to withstand a determined attacker with a tank. But we live in a happy world and a lot of stuff exists because people can cut corners.

Good managers/programmers know where they can be sloppy and where they have to be super careful.

The beauty of technical debt is that it only has to be repaid in case of success.

What’s the advantage of INSERT-only table over having a normal table and all normal users only have INSERT privilege on that table?

As admin I can still recreate the whole insert table with modified data, etc.

Law is not about logic. It’s about hermeneutics. It’s closer to religion than to math.