skysight-inc/HackerNews huggingface dataset:
Gift link: https://www.wsj.com/sports/boston-marathon-prize-money-dopin...
Just fantastic!!
Loved it.
So instead of standardized element that works pretty much the same on every browser, that can be inspected and controlled by virtually every tool that works with web I, as a user, get a binary blob, correct?
would really like to know how this was made.
Yeah, I'd be interested in the bandwidth as well. Can R2 saturate 10/25/50 gigabit links? Can it do so with single requests, or if not, how many parallel requests does that require?
So, yeah, my read is you are basically arguing that it was the first time "science" was used to try and justify slavery. I meant my "defensible" statement to be that I think that argument is defensible. But, largely because the scientific revolution was so recent. Before that, it was divinity that set up hierarchies of people. It was still based on "blood and soil," all told, though? In fact, I largely view that as trying to use the new tool of "science" to justify what the old system had setup? (Again, I think this argument has legs, so I'm not trying to completely "debunk" it.)

I'm far too removed from any time in my life where I was reading history documents, but the christianity slant is still odd to me. Specifically, I remember reading back in the day that some anti-slavery groups were instrumental in converting slaves to christianity in an effort to undermine it. That, in turn, was itself coopted, such that it was not necessarily a success. (And I'll throw in the caveat that I didn't find history that engaging.)

My gripe on the "nowhere else had hereditary slavery" is that this is complicated. Firstly, many places basically ended bloodlines of their slaves. Castration and executions were the norm. So, hard to see that this is really a comparison that you'd want to stake a "which is worse" debate on. They are both abhorrently evil. (And, not shockingly, serfdom has its own curve ball to this debate. That was hereditary and while slavery has obviously worse aspects, I don't understand why people seem to think serfdom was mostly fine.)

Bringing it fully to this general topic. The slave narratives being a US literary thing is largely because that is allowed in the US. Do I think the US should get a pass and kudos for amplifying voices of people that they used to enslave? Complicated question.

Well, sorta complicated. I can firmly say "get a pass and kudos" should be dismissed as a silly statement. But, it is frustrating that places that almost certainly did worse things heavily censor their histories. This isn't even really debated. But, because people hear the US criticisms and the others are largely silenced, so many people take the view that there are only US criticisms.

Edit: Meant to say thanks for the opening. I know this is a topic that is prone to yelling way too easily. I'd also be interested in reading any texts you recommend reading.
BananaPi dont make anything from what I see. SinoVOIP is one manufacturer but who will make up the boards Device Tree Overlays????

Leave it to poor saps on a Wiki to do it for them...

Raxda has tried to support some but they use a shitty old u-boot Linero tree like many of these joke boards.

Hello. Please upsteam your work and get rid of the 2017 Uboot tree.
Geez
Even if you believe this, it's still nonsense.

Let's say you believe that trans women are men. And you believe you need to protect cis women. The number of trans women is so vanishingly small, that you've spent a huge amount of energy to prevent the 0.5% case. Legislating always has an opportunity cost, putting forward a bill means not putting forward other bills.

Women suffer domestic violence and sexual violence. 33% of women in the US report experiencing domestic violence. Protect women from that!

Because there are so many ways women suffer in this country, it's very difficult to take on good faith that anyone is protecting them by legislating against trans women. You could choose to solve any problem that affects women orders of magnitude more, but those problems see orders of magnitude fewer bills, if any at all.

No, the data shows this isn't about protecting women, it's about hurting trans people.
I did about 10 4x4s and 6x6s and they were all solvable.
I believe what he wants, is the usual C trick of defining a struct which represents the wire format (with all the usual caveats). Then cast a char pointer to be an instance of a pointer to that struct. Sort of like this:

https://github.com/danos/vyatta-dataplane/blob/master/src/ecmp.c#L108-L116

It sort of works on x86 chips, but is not so effective on MIPS, PPC, etc where misaligned access are either unavailable, or slow, or even trap and are slower still.

Once one has to handle that sort of situation, and actually copy the data, the lack of language support for such type-punning becomes immaterial.
Who is everyone? Outside of very online tech enthusiasts like ourselves, nobody cares.
this is great, especially the design. but, as some of the comments have stated, it will prob get annoying.

Instead, I think it would be better to incentivize people to use their phone/social apps less.

Touch Grass. Earn Points.
I mean, it may be true in practice that most S3 workloads are throughput oriented and unconcerned with latency.

But if you look at https://aws.amazon.com/s3/ it says things like:

"Object storage built to retrieve any amount of data from anywhere"

"any amount of data for virtually any use case"

"S3 delivers the resiliency, flexibility, latency, and throughput, to ensure storage never limits performance"

So if S3 is not intended for low-latency applications, the marketing team haven't gotten the message :)
It doesn't sound like you have an architecture that is particularly conducive to renderer-based programming, but that's not to say it's a difficult or complicated port. That all depends on the details.

When going to a dedicated graphics renderer, the biggest "change" from standard dev is "unrolling" your loops. So, right now, you have a bunch of parents and children and parents inform children. This is not, at all, different from a game engine which allows nesting of render objects (very common). Usually, the "transform" of a parent mesh is added to the transform of its children, for a very basic example.

If you're working in 3D, there's a bit of a complication with alpha channels because not only do you have to worry about blending, but you also have to deal with the intersection of alpha objects - simple front-to-back-then-back-to-front rendering won't cover that. But since you're just doing forms, you can be sure that all of your alpha content will be rendered after all of your opaque content, and blended according to its mode at that time, so it's a fairly straightforward version of "unrolling" that you would need.

But all of that is to say: no, WebGL (or any graphics API) won't have any kind of built in way to manage nesting objects. Those relations would have to be defined by you and uploaded to the GPU and then referenced separately, rather than looping through each parent and drilling down into the objects. It's just a different type of problem-solving. Rather than dealing with things per-object, you're dealing with them per-pixel (or pixel group). So you tell each pixel how it should render, based on what objects it is expected to describe at that pixel, and then let them all do their work at the exact same time. It's less "layer painting" and more "arrange and stamp".
I am also surprised that 4chan is using Cloudflare captcha and bot protection
Getting Real eBook for Free
Everyone says this, but do we actually have data to back that up?

I feel like I spend so much time working around CloudSQL for postgres support in GCP at work, to a point where I'm not actually sure I'm saving a ton of time over running and managing it myself. That's probably not true, I'm sure there are edge cases that I'm not accounting for, but I'm a little tired of everyone acting like AWS and GCP and Azure are the "set it and forget it" thing that they advertise.
I've had very similar thoughts about lawn-cutting, but hadn't related it to technology-related trends!

I couldn't agree more. In a broad sense, it's like we've lost contact with our own lives, communities, and cultures. I don't think those things are "dead", but they mean things now which are totally different than what they meant even only a couple of decades ago, and the people living through it sort of know that and kind of say it out loud sometimes even, but can't really wrap their heads around it at the same time and continue to ape the old behaviours (no offence, anyone, I do it too).

"Traditions" live on in a sort of zombie state... we cut the grass, we present the gift cards. It's an odd and fun(ny) moment to be alive.
uh yes? Was this supposed to be some clever "gotcha!" that ended up being really stupid? Might want to run your clever comments by ChatGPT before you post next time chief
Good to know. Please make an uncontroversial list of all the human activities that you think shouldn't be allowed on cloudflare (or perhaps in general). Then we can all agree to abide by it, and human conflict will end!
Interesting to see Zoom essentially rebrand again. Felt like during the covid era they were angling more for an all-in-one remote work platform with calendaring, hot-desk features for hybrid workplaces, etc - guess that didn't work out so well!
"...Created the World’s First Writing System" that we know of. They used burned clay, which lasts forever. I am sure there have been writing systems before, they just rotted away.
The manufacturer can't control or even predict purchase dates, so that leaves potentially unbounded support lifetimes. I'd be comfortable with the 10-year timer starting from date of last manufacturer though
Largely this problem which is core to Emacs in the sense it literally is "An Elegant Weapon For A More Civilized Time" due to its age. There is no concept of sandboxing anything in Emacs. You do get an alert sometimes when you change Theme's since they have a notion of totally executable code. Maybe a better solution would be to make a subset of elisp that artifacts be coded in which are sandboxed.
That's what they... er, you... er, somebody wants you to think?
This device looks interesting. Given the coloring of the "mouse buttons", the lack of trackpoint is disappointing, though. And the "AI" in the name is a bit of a turn off.
But does it actually work that way? If I `await fetch_from_api()` in the first component before returning the tree with the second component that fetches from my backend, `fetch_from_api()` has to resolve before Htmy finds out about the second component.
> The company also managed to acquire full rights of the Redis trademark and project stewardship from antirez after hiring him

How did that happen? He must have given/sold it to them, right? I remember him making an announcement that he was done with Redis and stepping away from involvement.
They are verbose but correct. I've caught some errors this way.

I usually don't think of None as a potential return value (= voids in C) but the LSP code analysis usually picks up on code paths that don't return a value.

I don't find Python's typing valuable for Jupyter type explorations, but they're immensely valuable for catching little issues in production code.
Looking at that blog post, I find it illustrative in how people who like strong types and people who dislike strong types are addressing different form of bugs. If the main types of issues comes from bugs like 1 + "2" == 12", then strong types is a big help. It also enables many developers who spend the majority of time in a programming editor to quickly get automatic help with such bugs.

The other side is those people who do not find those kind of bugs annoying, or they simply don't get hit by such bugs at a rate that is high enough to warrant using a strong type system. Developers who spend their time prototyping in ipython also get less out of the strong types. The bugs that those developers are concerned about are design bugs, like finding out why a bunch of small async programs reading from a message buss may stall once every second Friday, and where the bug may be a dependency of a dependency of a dependency that do not use a socket timeout. Types are similar not going to help those who spend the wast majority of time on bugs where someone finally says "This design could never have worked".
> But yes, Kubernetes is configured in YAML, and YAML kind of sucks, but you rarely do that.

I'm sorry, citation needed on that. I spend a lot of time working with the damn YAML files. It's not a one-off thing for me.

You're not the first person to say this to me, they say "you rarely touch the YAML!!!", but then I look at their last six PRs, and each one had at least a small change to the YAML setup. I don't think you or they are lying, I think people forget how often you actually have to futz with it.
Yeah, I think this may be a good option when actively working on a project. Sadly at the moment, it's mostly a case of "I just need to make a couple of bug fixes in this old project, why is my editor shouting at me?"
I agree and liked your comment. I just want to add that I was specifically disagreeing with this:

> What they say should not calculate in what we believe to be true

rather than thinking about definitions of trust.
Ask HN: Successful products that (in)famously lacked "table stakes" features?
The first iPhone didn't have copy/paste.

X still doesn't have functional search.

What are other great examples of hardware or software products that succeeded despite missing seemingly "table stakes" features at first / for a while?

Inspired by https://news.ycombinator.com/item?id=42257324
Putting aside the increased delays, the padding on its own is good for us, right? Having a more conservative estimate makes planning easier, especially when connecting flights.
I have a couple of favourite ones but one I always think of immediately is a time when I was tasked with fixing some dashboard.

Sometimes students scores would be appearing as zero despite their average score being not zero.

Turns out it was some very simple averaging that didn’t filter out tests with a score of zero. That zero would then basically poison the entire calculation and only produce zero.

I don’t know how interesting that one is though.
> The logic of type hint is not bad but sadly I think that type hint are making python source code messy and unreadable.

Compared to legacy Python, yes.

Compared to verbose language like Java, no. Python typing is equal or less verbose than Java (unless you use "var" in Java).
> My favorite phone interview question? “What’s your favorite language?” followed by “What are it’s weaknesses?”

20 years ago I could answer the favorite language question pretty quickly without thinking about it. Back then it was Ruby. Now? I don't really have a favorite language anymore. They're all flawed in ways and they're just tools to get the job done. Which one to reach for depends on the problem domain.
I know linking to videos on a tangent joke is frowned upon here, but I'll risk the downvotes for a worthy cause:

You really need to watch this Key & Peele & Rocket Jump colaboration: https://www.youtube.com/watch?v=IHQr0HCIN2w

Actually, since I'm actually undercover as you, and I've already watched it...
The "nano" questions are silly and tell you nothing useful about the candidate other than I guess their level of candor in being subordinate to obsequious lines of questioning.

However, the rest of the questions are just as pointless too.

As a hiring manager and product owner, the level of familiarity that an engineer has with using debugging and diagnosis tools (e.g. as simple as how to attach and effeciently use a debugger) is 100x more valuable to the predictable delivery and quality of the things they're building than Programming 101 trivia.

Writing code is quite possibly the easiest, least fraught time-sucking milestone-missing part of software development. The morass of the entire rest of the SDLC is where ambitions and dreams go to die. Version control expertise, build system esoteria, correct configuration & setup of dependencies, understanding how to test, being able to do more than printf'ing your way out of a Russian nesting doll inspired paper bag. That sort of thing.
> It's too easy to defeat the purpose of these things if you're even slightly driven.

Things like the OP and LeechBlock are tools for people who have already mostly conquered their addiction, to help keep them from relapsing. On their own, they're not sufficient to turn an addict into a non-addict.
Show HN: Django Protego - A Flexible and Dynamic Circuit Breaker
Hey HN!

I'm excited to share a project I've been working on: Django Protego, a dynamic and configurable Circuit Breaker for Django applications.

What is Django Protego?

Django Protego is a library that helps to protect your services from cascading failures by providing a Circuit Breaker mechanism. It's simple to integrate, dynamic, and works seamlessly with Django-based applications.

Key Features:

- Dynamic Configuration: Configure failure thresholds, reset timeouts, and half-open retries at runtime.

- Global Registry: The circuit breaker state is shared across views via a global registry, ensuring centralized control of your application’s fault tolerance.

- Easy to Use: Just decorate your views with @protego.protect to wrap your views in the circuit breaker logic.

- Flexible: Supports multiple circuit breakers in the same project, all configurable independently.

- In-Memory: Implements a highly efficient in-memory circuit breaker with no external dependencies.

How It Works:

- Protego Client: For each service, the circuit breaker maintains its state (open, closed, half-open) and tracks failures.

- Thresholds and Timeout: You can dynamically adjust failure thresholds, reset timeouts, and half-open retries via a central configuration in your Django app.

- Global Access: Protego ensures that circuit breakers are initialized once and are accessible globally in your project.

- Graceful Failures: When the circuit breaker is "open", instead of hitting the service, it automatically returns a failure response (e.g., 503 Service Unavailable).

Future Roadmap for Protego Circuit Breaker

To further enhance Protego and make it even more powerful and scalable, here's a roadmap that focuses on integrating it with Django, Redis, and databases for advanced fault tolerance, persistence, and distributed systems.

Link: https://github.com/grandimam/django-protego
Show HN: SRE/Ops Podcast Summarizer
Kvrocks is pretty substantially different, from my understanding. It only shares the protocol.
Disappointing that "rust lol" is the top option in the poll, and none of the other options are about usability or utility.

No one gives a single shit what language the thing is written in. What users care about is how monstrously complex and difficult it is to use OpenWRT.

Anything more complex than changing SSID and password requires trawling through two different outdated wikis and years-old forum posts. That's if your search engine can even find something other than thousands of people asking the same question over the years.

OpenWRT needs to be usable and approachable. Any random person off the street should be able to walk up and configure their network. Even for highly technical users it's a struggle to do anything.

It does not matter one single bit whether there's rust in the codebase if it's never run because no one can figure out how to use it.

Rust is not a feature. It's an implementation detail that absolutely no one cares about and does not affect the user in any way. I'm really sick of this shit.
no, a lot of things aren't likely, and yet they just need to happen once for a lot of the ensuing process to be very different.
First thing you need to do is change your LinkedIn to “AI evangelist” then go to your boss and say I want triple the pay. Then let the chips fall where they may. Oh also rename all your GitHub or personal projects to have AI in the name. You don’t actually have to do much else.
I found video lectures of “Advanced NLP” course by Mohit Iyer very useful to get me started: https://people.cs.umass.edu/~miyyer/cs685/
5 ccTLDs have been deleted https://domainincite.com/30406-five-times-icann-deleted-a-cc...

https://news.ycombinator.com/item?id=41781827
I hate etcd probably more than most, but that 8Gb seems to just be a warning, unless you have information otherwise https://etcd.io/docs/v3.5/dev-guide/limit/#storage-size-limi...

I'll take this opportunity to once again bitch and moan that Kubernetes just fucking refuses to allow the KV store to be pluggable, unlike damn near everything else in their world, because they think that's funny or something
Don't assume things not stated. https://en.wikipedia.org/wiki/Affirming_the_consequent
Personally my prior is that companies are always trying to manipulate you, and people only sometimes. On the other hand it can be easier to get away with false statements when you don't have a large audience and deep pockets.
I have no doubt that VSCode has a much less risk of executing code by opening something. Ironically however, it seems that VSCode's extension is the most effective channel to distribute malware in the history of code editors. [1] [2]

Not that MELPA couldn't be used to distribute malware either, I just think, as another poster mentioned, these problems are almost more social than technical.

[1] https://www.bleepingcomputer.com/news/security/malicious-vsc...
[2] https://arxiv.org/html/2411.07479v1
It's certainly a well meaning article, but:

After studying more than 2,000 pairs of twins and administering the Grit Scale, researchers concluded that the hereditability of the two factors contributing to Grit is as follows: Perseverance: 37% Passion: 20%

This idea of quantifying "grit" into separate components with ratios as if it's a freaking cookbook is patently absurd.

I'll throw my general advice into the mix - raising a dog can also help teach young children responsibility, follow-through, and this ephemeral quality "grit".
Raymond Carver, the Art of Fiction No. 76
Yes, they absolutely can [1].

1: https://blog.cloudflare.com/how-cloudflare-auto-mitigated-wo...
Sublimely arrogant nonsense. I want good products. Am I in numerous company? Why would I care?
I believe you meant `strings.Split(s1, s2)`, but I would have also accepted `s1.split(s2).collect::<Vec<&str>>();`

Kidding aside, I agree completely that syntax isn't the important part. For interviews I think of it more as a sign the person is "warmed" up in a language. If they code in Go or Rust all day currently, then I expect a bit more of the syntax to be known for that language, but it's more a tell on what they actually do all day then what they can do in a week or two of learning.
The only thing that would benefit this company is another round of lockdowns.
Bulldozers also come with keys that stop random people walking up and turning them on though
The Cassava Saga Ends
Attended Sysupgrade seems like the solution for this. It looks at your packages, does a cloud build for your board with your packages and you can push a button to update.

Be aware if you're on snapshot, that the packaging situation is iffy right now. opkg is being replaced with apk, and there's some rough edges. I had a sysupgrade build that ended up with neither package manager, and the automatic tool doesn't currently work for doing new builds from an apk system.

My wishlist item would be less churn or at least replacements should integrate as well as the old version.
"The entire simufilam story has been a complete waste of time, money, effort, and the hopes of desperate patients, and what's worse is that along the way there were so many big, bright, flashing warning signs that that's exactly what was going on."
There is a ton of them now, especially on the more consumer "body double" side. I remember a few years back there was Beulr on Shark Tank doing bots for remote students so they could sleep through their classes...

I am working on an API for devs to build Zoom agents currently, so definitely banking on this being the future! https://www.agentstation.ai/