skysight-inc/HackerNews huggingface dataset:
1/ needs authenticationless way to search. all other ip look up tools don't require an account for me to test this. I'm not going to register.

2/ I've tried blocking vpn or proxy users (by ip hosting provider), but found too many false positives. Using a VPN is common for IT professionals or consumers trying to 'protect' their privacy and this impacted the growth of my app.

How is your tool better at detecting a bot vs a human using a vpn?
> Again, where did you see that?

https://doh.wa.gov/sites/default/files/2022-02/421-010-Cases...
I wrote about this a few years ago on my blog when I re-fitted my old Commodore Amiga with a floppy drive after years of using SD-card floppy emulators: http://www.markround.com/blog/2019/12/30/back-to-the-floppy/

There really was something special about labelling the disks, the deliberate act of sorting through your collection and selecting one... To me, it feels much like picking out a vinyl record to enjoy rather than having everything "on tap" with Spotify. And then there's the scene it generated which reminds me of the tape trading days of the 80s:

"...Later on, when I eventually got involved in The Scene, floppies brought us together in a way I think is now sadly long-gone. Because we traded disks with each other - and groups typically had members whose sole “job” in the group was as a “trader” or “swapper” - we also wrote to each other. As a particularly awkward teenager (with a bunch of the usual teen issues and a healthy side-order of angst), some of the closest friendships I formed during those years were with the other members of my group. Alongside the floppy disks we’d write long, rambling letters to each other full of everything and nothing. We’d fill our envelopes to each other with “Jiffy Junk” - little trinkets we’d collect and swap: Kinder surprise toys, trading cards and the occasional mix-tape... Even though I think I only ever met one of the guys from my group in person, I still think about them often to this day and wonder what they’re all doing now.

As the Amiga scene gradually died and the BBS (and later, the Internet and FTP sites) became the primary means of obtaining software I think a lot of those friendships were broken. Even though The Scene is still a very close-knit community, I’d be interested to know whether those same bonds exist today when most communication is probably electronic in nature..."
I don’t care if you name them descriptively or weirdly, just please name them distinctly so when I have to do searches for them I come up with the right thing. The worst is Apple’s “Pages” and “Numbers”. Try doing a search for how to do something in either of these products. These are far from the only examples.
For the most part nobody "should" anything.

In general, if you're entrepreneurial, yeah, work a part time job and build something.

If you're all in in developing professionally for the corporate ladder, go grab a full time job.
> The thing about sixel is it's only supported on old DEC glass terminals, xterm with a non-default configuration, mintty, and several emulators that are fairly unlikely to be preinstalled anywhere

Uh, no?

Just start xterm (say from another xterm) with the correct flag.
Sixels are also supported on the BSD console.

The lack of support in the likes of gnome-terminal is a willful and ugly political decision that I've already documented.

> Images are a different matter, where the compromise makes more sense.

Indeed, I love to do remote gnuplots

> I can write a script that vomits a jpeg to some vague common denominator standard and it'll probably work for all my coworkers using a smorgasbord of emulators.

This is the idea of tmux-sixel https://github.com/csdvrx/sixel-tmux : intercept sixels sequences and, if your terminal doesn't support it (or if you use the scrollback buffer, to save or RAM), render a unicode representation instead (like Chafa), but if it does, pass through the original sixel sequence.
Wikipedia is fine for scientific topics. But for history, living persons, and any potential source other controversial it can be very slanted depending on who has ownership of the page. It can be interesting to open the talk tab on a page and get a sense of the kind of bias the page owners have.

Often there's more content on the talk page than the article itself, one example I have on hand: https://en.wikipedia.org/wiki/Talk:Ada_Lovelace/Archive_1
We job hop for a number of reasons. The primary one being compensation when their current job isn’t keeping up with inflation. Another is lack of promotion when you went above and beyond (as you were coached to by your manager, for that promotion).

Another reason (which is why I do) is that life for some of us isn’t as stable. I move. I’m forced to sometimes because of rent. Sometimes that means having to find a new, cheaper, city to live in. Sometimes it’s to relocate for that new position.

Next time you see someone who has worked at several companies over a decade, ask why and understand their reasoning. I would love to work at a company for 20+ years. I can’t stay put in the same position for that long.
Nearly all their arguments as to why prefer plaintext versus HTML apply for this media as well. Having this page as an HTML document instead of plain text increases security risks and can reduce accessibility.

They argue you do not need HTML formatting to get a point across, but then rely on HTML formatting to get their point across. Why did they bother using bulleted lists? Why did they use links and anchor tags instead of just having the URL written out in plain text? Why would they bother embedding an image into their page instead of just giving us the URL and letting us choose to fetch it if we wanted to after reading the message? Maybe because its better to look at and read using HTML formatting instead of just plain text.

Maybe I want a bulleted list in an email. Maybe I would like to have a link instead of just having a giant URL as plain text in my email. Maybe I'd like to have the image I'm talking about in my email in the email instead of being some other resource for the person to fetch. Its condescending for them to say "You should never use bulleted lists, here's a bulleted list of reasons why you shouldn't use bulleted lists!" Its condescending for them to say don't use links when they use loads of links. If its better to just put the full URL out there plainly, then they should have done it. They didn't because its not better, its nice using links.

If the alternative is perfectly acceptable, why didn't they just use the alternative? They didn't, because the alternative isn't perfectly acceptable all the time. There's a good reason to mark up your writing.

Its condescending for them to say:

> Rich text isn't that great, anyway

in a rich-text document. If rich text isn't that great, why are they using it? Because the alternative isn't that great!
POST is intentionally not idempotent. If you want impotence, that's what PUT and DELETE are for. Sadly, browser support for those two methods is somewhat lacking. You can't specify that a form send a PUT request, for example, only GET or POST.
Ask HN: How do you use computers faster?
I noticed something weird today by websearching "world's fastest computer user". I had to search "fast computer use", "how to interface computers faster", and a few others.

There appears to be absolutely nothing mainstream about the slowest part of the computer experience: the users.

This leaves me with so many questions:

* why does everyone want computers to be faster when their sludgy brains are the weak point in the process?
* how DO you get faster at computers? my theory is that the faster you are, the more you get done, so what does it take?
* how come FAMGA isn't on this beyond brain interfacing? isn't there an easier way that uses present technology and just a teensy bit of education?

Not really sure where I'm going with this, but just wanted to throw that idea here.
It's not far fetched to say a Senator's pilot could drop their airplane into the Delaware.

It's not far fetched to say a the line cook at a Senator's restaurant could poison their food.

It's not far fetched to say that a Senator's financial advisor could run off with their money.

It's not far fetched to say the teachers who instruct a Senator's kids could fill their heads with lies.

Humans have all sorts of ways to wreak destruction on one another but it mostly doesn't happen, and when it does, we have many, many systems in place to detect and punish. And we tend to scale the weight of these systems to the size of the perceived threat - that's why doctors and pilots are more burdened than bankers who are more burdened than cooks.

How likely is someone to actually take over these accounts (what's to gain)? How much damage would it do (not too much, people get hacked on Twitter all the time and that's baked in to the credulity of each tweet)? How likely is that employee to get caught (high), and how much punishment would they face (huge fines, possible jail time, unemployable in many industries for the rest of their lives).

Technical safeguards are not our only safeguards, especially for insider threats, which long predate the Internet. External hackers do dramatically change the calculus here (unlikely to get caught or punished) but that's not what's being alleged.
I'm not a semiconductor engineer so I could be totally off here but.

My guess is that for AMD and likely Intel the reason the IO die is so large is because of all the PHY's on it (DDR, USB, etc) which would give a minimum size of the IO die for chiplets.

Which if true explains why you wouldn't care as much about the process node for the IO chiplet as it has a minimum physical size anyway.
Earliest capture of this guy's original site:

https://web.archive.org/web/19980623131044/http://www.diskdu...

Earliest capture of his site on floppydisks.com:

https://web.archive.org/web/20030330102403/http://floppydisk...

Floppy duplication prices from these pages:

June '98: $0.59 @ 500

March '03: $0.39 @ 500
It's great to read that on HN. Every time I look at the HN background colour I think of the 1541 disk drive - I'm near certain its colour was either a conscious or unconscious influence.
I remember actually exchanging floppy disks containing images (made in Paint, of course) with my friends via snail mail. It was the original version of Snapchat. Horrible latency.
i was wrong, this doesn't work in perl
I think the boundary makes a lot of sense. Cluster autoscaling only responds to scheduling pressure; if there are pending pods, a new node is added to the cluster so those pods can run. Meanwhile, horizontal pod autoscaling is a totally different system; it adds pods for that service when system-level metrics indicate that it should. Vertical pod autoscaling is again mostly unrelated; if metrics indicate that a certain pod should be bigger, a bigger version is scheduled.

I do see why more integration would be useful, though, including disruption budgets. Mostly for consolidating the incremental cluster autoscaling results onto one node from time to time, without waiting for the workload to naturally disappear or decrease in scale. Also, it would be nice to say "hey if ARM spot nodes are cheaper than AMD64, just reschedule these workloads onto ARM". Basically, it's still the very early days of optimizing cost, latency, and throughput.
I think treating "execs" as a category upon which judgment can be passed is a mistake.

Every company has different standards. Execs as a general population aren't genius or clueless. You have to get specific about the sub-group.

For example, execs at Amazon are likely to be significantly above average in competence. Execs at a 6 month old startup might be anywhere across the spectrum, hard to know.
Around 8 years ago we chose Scala for some random microservice, because there was ONE guy in the team that loved Scala and wanted to do something with it. I said, sure go for it, it will be interesting to test the technology. After he implemented the microservice, it was rock solid for like 5 years. Said dev left 3 years later after implementing the service. Two years after he left, we needed to do something to the microservice... but nobody knew Scala in the team, so we have one or two "brave" guys who struggled to modify the Scala code.

The same thing happened years later in another startup in Elixir. I arrived to this startup and there was some random microservice that someone had implemented in Elixir because it was "the new cool language that solved all scalability issues". Again, the person that implemented it had left years ago, so nobody knew anything about Elixir or the microservice. Because I've dabbed with Elixir for fun, I volunteered to work on it. In the end we decided to supersede it.

I've learned to stay with boring technology. For me the sweet spot of productivity and team versatility is TypeScript and Javascript. Using these two technologies devs can do backend, frontend and mobile. The only thing missing is good bindings for Machine Learning.
Especially in the last 5 years. 2-5% bumps for 10-20% inflation… gotta love math.
Well, golang is a tough language.

I am stuggling with helm/kubernetes and the new company's ecosystem where everybody is new in the team. We are expected to deliver according to a plan while we keep hunting for relevant info.

I would say the second point is a lot more nuanced than stated.
Yeah, I'm myself one. My job requires from me only 20 hours a week and it's well paid too.

It's uncommon I know, but youd have to look in places like AsyncOK.com or similar.
This thread is that though... The OP above you talks about how much time and energy is spent moving humans to specific locations to do work that doesn't depend on being in those locations. In any world where that had not been normalized it would be considered highly inneficient and similarly wasteful.
I never got into the fighting fantasy style of branching story game books, but then I discovered the Fabled Lands series by Dave Morris and Jamie Thomson. They're essentially open world game books, you can roam freely from location to location over most of the geography, with local branching adventures. Each book covers one region or kingdom. They also use a system of code words that set flags that enable quests that involve multiple locations, and changes to the world and events, so if you visit a location eventually you might trigger a change that means you go to a different version of that location that reflects your changes. It’s a very different experience, to me anyway.
Eh. It depends on the context for me. I try to only compare me to me. An easy way to do that is to compare me to a ~6 month version of me. I started a job about 6 months ago. Comparing today me to that previous me is straightforward. I knew little about React when starting this job. Now I've shipped multiple react projects.

I started doing bjj about 6 months ago. Its obvious to me that if I was wrestling against myself from 6 months ago it would be easy to beat myself.

This becomes harder as you have more experience in something, comparing your 5.6 years of exp to your 5 years is less obvious than 6 month and 0 months, but its still possible if you are tracking your achievements.

I have a "hype" doc where I write down my accomplishments every three weeks. Sometimes there are many. Sometimes there are only 1 or 2 things to note.

Do I still feel very silly and incompetent when pairing with a significantly more senior engineer? Do I still get smashed by more experienced grapplers? Sure. But I dont have to dwell on it because I know I'm making progress of my own.
There are some older algorithms like <snip> which "learn" rules that look more like ordinary code.

See also, "Rule Induction"[1].

[1]: https://en.wikipedia.org/wiki/Rule_induction
I've not heard this, it is interesting. Do you have information on source/methods/study groups etc?
> The total fleet in use is around 6000 baremetal nodes and 1000 VMs in AWS spread over various DCs and regions. There are over 1500 developers actively using the Kubernetes clusters every day for a total of 2500 applications running in production.

Seems like they are quite successful already.

> The struggle I'm having is "how to drive focus" and avoid to die of operations. The team is large making the Scrum process ineffective.

Drive focus to where? As stated above, the platform team seems to have achieved what every platform team other there is struggling to achieve. What does "die of operations" mean?

And above all, who cares about Scrum?
Dear reader, please keep in mind that this isn't just about the most political virus of all times, but many other diseases.

mRNA vaccines against many diseases are researched as we speak, including the elusive HIV vaccine, which could lead to the eradication of the most stigmatizing virus in the world.

If all of those required LNP and we find out that LNP are very, very unhealthy, that would be very, very disappointing.
Who cares if it's out of style? Sounds like an excuse to kill creativity.
>All the superstars at my current company have been here for a while.

Exactly. And isn't that memorisation by repetition? If you will come across something often you take a good guess on how it works.
H2 can be transported over natural gas pipelines. At least as high as 15% hydrogen / 85% Nat Gas.

Maybe that's not enough for the long term, but that mix/ratio should be sufficient to bootstrap the fledgling H2 industry.

If Syngas / synthetic diesel becomes more efficient in the future, we switch to that. I'm not against experimentation or tests.
I didn't want to assume Chicago or Detroit, but wiki says Dixie mall is in Chicago. Timeline matches my preconceived ideas.
You'd need enough backing to fend off a company that earned almost $40B in revenue in 2020 from an attempt to capture one of its fastest-growing revenue streams. Good luck finding a serious investor that would be willing to try it.
AOSP is open source, but Android itself is far from it - just ask Huawei. More and more code is in proprietary bits of Google code. And Chromium is not Chrome, most people use Chrome builds which are proprietary.
I can just about tolerate this for brand names, as there's an additional set of requirements there, but for everything else, it's just gatekeeping and unnecessary obfuscation. If the purpose of something changes, fork it off into something new or just rename it if possible. Apache TinkerPop Gremlin might be fun for the creators, but not for anyone trying to understand what it does.
The problem is the direction they will tend to head. Politicians see a centralized power center and think "we need to control that", and so will just create laws aimed at reforming the centralized service rather than breaking it up.

While what we really need is API access, data portability, privacy ala GDPR, and other laws that will foster competition between services, to straight up end their current playbook of creating mini-monopolies via Metcalfe's law. The standard tech-literate workflow to interact with Twitter should involve a third party client that abstracts over all such publishing services, and not defaulting to Twitter's proprietary web/mobile apps.
The "Why I hate Wikipedia" YouTube video discussed at the other thread you link was made by YouTuber and journalist J. J. McCullough. You wanna see something funny? This discussion is from 2008:

https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...

The J. J. McCullough biography was created and deleted a total of five times on Wikipedia (with two different spellings of J.J.):

https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...
https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...
https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...
https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletio...

I believe he may not be telling the whole story in that video.
Oops, I didn't see your response; I'll shoot you an email from connor[dot]labaume[dot]etc.

I've never interacted with UpWork. My experience is that smaller companies pay fairly well, the interview process is usually easier, and you can learn a lot more about development, and that particular industry. The down side is that office politics matters more, you might have challenges with setting realistic expectations, and you might have trouble with comparisons to the last programmer they hired/fired.
I'm on the same line of thinking as you.

I've been hitting the gym, doing mostly heavy lifting 2-3x a week and easing off on my calorie restriction. The weight is going back on fairly quickly but I'm also seeing good gains and progression in my strength & lifts.

For instance, when I started, one arm curl was at about 35 lbs, now 3 months later I'm curling 55, bench was 120, now it's 160 (but I'm not pushing hard on gaining bench) and squat machine has gone from 175 to 280.
I disagree. I found the comment on how Häute Couture stores like YSK were closed yet people were lining up at Macy's to buy underwear a very telling emotional response to 9/11.

She doesn't write about the fashion of the victims at all. Rather she talks about about the trauma. She talks about how the delays for fashions show. Hints at controversy with some designers dropping out and hosting their own releases.

She's writing this article on September 20 so it's not like she can talk about long term effects either.

Edit: Reread your comment and I realized I misunderstood. I think we're in agreement that there wasn't any immediate effects to the fashion industry that she could write about. Although... Now I'm curious what the long term impacts actually were
I reserve emoji for cases where the language's compiler fails to do type inference and forces me to create a temp variable.
It's more reliable this way. N number of pods are scheduled on M number of nodes, and if there are multiple sets of pods that each have their own scaling parameters (target utilizations, scaling cooldowns, etc), there is not always a one-to-one mapping with how many nodes are needed.

The cluster autoscaler already has a fairly complex logic just in its own control loop. It uses predicate logic and a simulated scheduler to determine whether a pending pod, based upon node selector, affinity, anti-affinity, taints, tolerations, qos, priority whether expanding a nodegroup would make the pod schedulable.

So it's actually easier (at least for me) to reason out what might happen, with two control loops that work independently in adjacent dimensions than a single one that tries to cover everything. I would not want HPA, VPA, and cluster-autoscaler to be one thing.

I have never used VPA, and in our use-case, we do a different kind of vertical scaling. (Different deployments that target different nodegroups with differently-sized number of cores on the base machine)