skysight-inc/HackerNews huggingface dataset:
I agree that the lack of nuance and effective choice sucks in politics, but the root of the issue is that inevitably each individual vote is all-or-nothing for that politician's or party's agenda.

In our everyday life we have plenty of options for most basic purchases, and can pick-and-choose whatever combination of goods/services we want (though there are of course market failures, but let's not get sidetracked).

Imagine if you could only pick either prepackaged life choices A or prepackaged life choices B? It would be a dystopian hell (and only marginally improved by additional packages).

Yet that's what we've got when it comes to politics.
The more things change the more they stay the same. Thanks for this short anecdote.

Wondering what kernel version you run that old device on :)
If a software startup assembles a bunch of open source hardware together and packages it as a product, would you say they don't "make" software?

No, I'd say they are more of a software company than a hardware company though. All software runs on some kind of hardware, but these days it is pretty rare for that hardware to be very unique or custom.

I was mostly just curious what custom hardware you had, since that was the topic at hand. My curiosity comes from working in the surveillance AI space for the last ~15 years, and having done a number of custom (as in we made the whole thing) cameras with AI, but now there is a trend more towards using a lightly OEM'd camera with custom firmware in many cases.

Considering the availability of cameras with advanced SoCs capable of doing edge inference, I wanted to ask more about your hardware and your design choices in this market, but I think I'll just bow out. Good luck with your startup!
> They're taking for granted that superintelligence is achievable within the next decade (regardless of who achieves it).

If it's achieved by someone else why should we assume that the other person or group will give a damn about anything done by this team?

What influence would this team have on other organizations, especially if you put your dystopia-flavored speculation hat on and imagine a more rogue group...

This team is only relevant to OpenAI and OpenAI-affiliated work and in that case, yes, it's weird to write some marketing press release copy that treats one hard thing as a fait accompli while hyping up how hard this other particular slice of the problem is.
Not OP, but I'm very familiar with both.

Luxonis is way more powerful and has an Intel VPU (Movidius). It's not really meant to be a standalone platform, so it needs a host board (Linux SBC like the Pi). It takes a lot more power, but it can do 60fps on small Yolo models. Its resolution is a lot higher as well.

ESP32-S3 has a pretty small memory capacity, and doesn't have H264-H265 hardware encoding, so you'll be on low-res, low-fps. It only does MJPEG (AFAIK) streaming, so you'll also have to deal with high latency if you want to send that data somewhere. The big bonus is that it's low-cost and low-power, and you're running it directly on the core without an OS.

This means you can do stuff like sleep the cores until something wakes it up (like a PIR sensor that detects people), and it will start streaming in a second or two.

TL;DR: Luxonis stronk, but needs big batteries or plugged in. ESP32-S3 can run on small batteries or solar.
I took some classes as a kid, but never got past level 101 in BASIC, C++ and Visual Basic.

In my 30s I picked up ruby and then transitioned to JavaScript. Now I am a principal engineer.
The difference between code and data only exists in our minds. There is no distinction. Both code and data make the computer do things (and, yes, both code and data only make the computer do things if other conditions are permitting, for example if executed with the right interpreter, or loaded with the right type of viewer). Anything that can be expressed as code can be expressed as data, and vice versa.
For personal development, it was merely shipping things. The more I published, the better I felt about myself. The more I published, the more I had learned and had to refer to. Now when I'm taking on tasks I can instantly recall how each of the pieces of the problem can be stitched together from things I did previously (or at least know where to look for foundations to build from)

For the confidence? It was working with others. The first job I had I got to sit down with one of the company's programmers as part of my on boarding and watch him work through tickets. After I saw just how flawed everyone was I felt a lot better about myself. I suppose that's a weird thing to say: Oh he was pretty shit, so I shouldn't feel bad about my poor performance...but that's not the point I want to make really. More that, it is wrong to compare your efforts to learn and grow against the final product of others. Once you sit down with the experienced devs and see how they shape and form the product and all the bumps along the way it doesn't feel so bad to struggle on your own.

Ultimately the skills that I honed that gave me the best boost in confidence were not really the direct programming parts where I put letters and numbers in files. It is the debugging. Understanding how things move and where to look for problems makes me feel like I can solve any problem with the right tools.
> Because the brine is hyper-salty compared to ocean water and takes a while to mix back in, essentially creating a new ecosystem, brackish, where the outlets are.

How large would those brackish areas near the outlets be? It seems to be that would be a big problem in an enclosed bay, but much less so on a shore facing open ocean.

Could they run pipes out a few kilometers with small, regular holes (maybe some modification of oil pipeline technology) to spread the discharge out and mitigate the concentration problem?

Could they make the waste output less concentrated? Maybe by either running the desalination process less (would that also increase energy efficiency?) or by pre-mixing the waste with some un-desalinated intake water?
I wouldn't care about an expiration date, but I avoid the hand-me-down car seat market for the wreck reason. The carseats are only designed to be in one. I personally wouldn't know how to definitively say it had never been in one.
This isn't an endorsement of any specific one, but you can get the list of all of them on Netflix at: https://www.netflix.com/browse/genre/3652

I'm not sure if there are direct URLs like that for other streaming providers.
My perspective is different than what has been posted, so here it goes.

I knew I could outwork everyone and brute force being a better programmer by a function of continuous improvement through hours of work. (btw I was wrong, there is always someone out there that will outwork you...and they will be smarter than you, but hey it made sense to me).

I didn't realize I made it until

a) People would recognize me in meetings because of my code

b) New programmers started to ask me for advice

...now I'm in the Sr Devs, Tech Leads, and Lead Architects ask me for advice level. Honestly, I still have the same attitude, if I work effectively, I can keep getting better. Notice that I remove the "work harder" part.
If you can document how to make this show a calendar from Office 365 that would get you so many sales.
If you'd like to understand what Google is actually doing with the news, it's outlined here.

https://www.ourcommons.ca/Content/Committee/441/CHPC/Brief/B...

And Jeff Elgie provides an informed view:

https://www.linkedin.com/pulse/village-medias-c-18-update-je...
Your case wouldn't be about style, it would be about specific elements that you posit were memorized and regurgitated by the model. The fact that you're creating art in the same style/medium as the author is what negates the "sufficiently transformative" fair use defense.

Basically, that world ignores the AI model completely. If your resulting work wouldn't be fair use if you directly were working with something from the training set, it wouldn't be fair use if you fed it through an AI model first.
> […] but they’re commenting on Facebook based on the headline.

People have been not-reading and commenting since the early days of Slashdot. See also Reddit and HN. :)
Nifty!! Good luck :)
Military command and control is already performed via input and output of token streams.
This reminds me of when telomere extension was all the rage in futurology forums... Turns out it's a recipe for cancer.

I can't help but wonder if this wont have a similar result.
Thank you! Would welcome any and all feedback you've got!
- Location: Mount Prospect, IL

- Remote: Yes

- Willing to relocate: No

- Technologies: JAMF/JSS, Atlassian, AD, Okta, Azure, MS Exchange, API, Bash, Python, mySQL, SSO, SAML, SCIM, iDPs, Linux, Documentation

- Résumé/CV: https://drive.google.com/file/d/16Sghx_ddLFWJ5pFoal5Hd4voyHP...

- Email: shurkin18@gmail.com
Googlers: why isn't this in Android's weather app yet?

You'll give me warnings, your data source gives AQI (with details! PM2.5, CO, NO2, O3, PM10, SO2), but you think people are more about dew point, pressure, and humidity? I mean do most people understand these numbers? What percentage actually understand humidity?

But seriously, give me the AQI. The official app has 5+M downloads and all the weather apps have it. Even Apple has it! (actually their weather app is great. Take note). Seriously, why is this not here? You would think it would be a common feature given all the fires California has and the increasing number country wide the last few years. Low hanging fruit here...
Sizing > Realistically, the seat fits average kids up to 3 years. At the 95% percentile on height most kids will outgrow a rear-facing car seat at 18 months (the growth of the torso is the limiting factor). From a labeling perspective we have to be careful, though, because the US regs on sizing are really terrible. Keep in mind the regs were written in the 1970s when we were still teaching Americans to wear seat belts. So there are 2 "options" in the US regs: 22 lbs 12-month test dummy, and 39 lbs 3-yr old test dummy. Lots of manufacturers claim their seats fit the 39 lbs mark, but they squash the test dummy's legs into an unrealistic position for a child (passes the test by the letter of the law, but misses the spirit of the law). Basically, we designed this seat to fit kids until they are ready for a front-facing seat.

Pricing > It isn't for everyone. The Kioma seat is like a Maserati, but some people prefer a Ford Taurus. We have to charge a price to cover our production and design costs, and there is a quantitative and qualitative difference in the materials and performance of a Kioma car seat.
Has to be fixated (unchanging) and in a tangible medium.
If someone didn't read the article, then why would you expect them to spend time on your website?

This seems really odd to me.
> This means you can enable Zstd compression by default, and if the data isn't compressible, it aborts the operation and stores it uncompressed, avoiding the extra CPU use

This was already implemented for all compression algorithms since ZFS was released as open source in 2005, at least (and even though zstd didn't yet exist then, it still benefited from this feature when it was integrated into ZFS).

The feature you describe only saves CPU time on decompression, but still requires ZFS to try to compress all data before storing it on disk.

This new early abort feature actually seems to be even more clever/sophisticated, because it also saves a lot of CPU time when compressing, not just descompressing.

Usually you are forced to select a fast compression level so that your performance doesn't degrade too much for little benefit, because if you had a higher compression level, ZFS would always be paying a high CPU cost for trying to compress data which often is not even compressible (since a lot of data on a typical filesystem belongs to large files, which are often not compressible).

However, with early abort, you can select a higher compression level (zstd-3 or higher) without paying a penalty for spending a lot of time trying to compress uncompressible data.

The way it seems to work is that ZFS first tries to compress your data with LZ4, which is an extremely fast compression algorithm. If LZ4 succeeds in compressing the data, then ZFS discards the LZ4-compressed data and recompresses it with your chosen higher compression level, knowing that it will be worth it.

If LZ4 can't compress the data, then ZFS doesn't even try to compress with the slower algorithm, it just stores the data uncompressed.

This almost completely avoids paying the CPU penalty for trying to compress data that cannot be compressed, and only results in about 9% less compression savings than if you had simply chosen the higher compression level without early abort.

The actual algorithm is even more clever: in-between the LZ4 heuristic and a zstd-3 or higher compression level, there is an intermediate zstd-1 heuristic that is also done to see whether the data is compressible.

This intermediate heuristic seems to almost completely eliminate the 9% compression savings cost while still being much faster than trying to compress all data with zstd-3 or higher, since zstd-1 is also very fast.

In the end, you get almost all the benefits of a higher compression level without paying almost any cost for wasting CPU cycles trying to compress uncompressible data!
You were quibbling about how 1,000 liters per day does not adequately account for all usage. Freshwater withdrawals is on average going to be a overestimate and the US is one of the worst outliers with significant agricultural exports which are one of the largest contributors to differential water withdrawals. Despite this, it would only be $2.00 per day for a fully desalinated water supply even if we safely overestimate usage. Despite it being 4x higher than the person you replied to said, that is still incredibly cheap.
$1000 is too much for Target and Walmart, but for Beverly Hills, the Hamptons, etc. that's nothing. If your living room has space for a Peleton bike, this will fit right in.
I believe the problem is that the situation you describe occurs on a much bigger scale. It’s no longer you and your friend in the cafe; it’s millions of people looking at the headline on the screen.
I have a similar story except the confidence came when I landed my first on-site job. Once I got in the team, the same realization came to me - I am not any worse than these guys here.
In your example the cafe isn't monetizing the fact that you view the headline and comment, which inherently increases the advertising value of the cafe (i.e. more people won't come to the cafe because of the headlines and their need to comment on it) and which captures significantly more value than everyone else involved. You just read the headline, a few people buy the paper and everyone is equitable and happy.

If Meta wants to pay 100% tax on their ad revenues to fund journalism, all they have to do is say so.
Oh god, comment threads on news sites are some of the worst things on the internet. Never well designed, properly threaded, each requires a different login, etc.

If that's the business they want to be in then they (and every other news site) completely sucks at it and there's a reason people want to talk on FB/Twitter instead beyond network effects.
Assuming an orders-of-magnitude smarter serf doesn't appear overnight, the king can train advisors that are close to matching the intelligence of the smartest serf, and give those advisors power. It's not a foolproof solution but likely the best we have.
For me the moment was a year or so into my first programming job, this was in the 90s. We were debugging some device driver issues and found that we'd made bad assumptions about the order in which things happened between our interrupt handlers, device driver thread and application threads. Once I took the time really mapping out what all can happen in an asynchronous environment and then setting up long-running stress test with multiple clients it clicked in place that you really have to continuously test your mental model against what could happen in the real world.
er, right, what other people call quals we called prelims. our quals were a presentation of early stage work, so when the deadlines rolled around, they didn't have an advisor, or hadn't been working with them long enough to have any results.
Assuming that weights are not copyrightable, how much restrictions can you put on output through API from those networks/weights?

Ie. if ClosedAI says you can't use output of their API to train competitive models - is that enforceable or not?
Reminds me of hackernews. I'm doing it now (commenting) without visiting the site because I'm aware of the story.
i'm importing from js cdns instead of adding them here

FWIW this seems counter to llama.cpp's philosophy.
A lot of public goods are that way. What you’ve stated is practically a tautology. “Government subsidy” just means the public is paying for it. Other things that fall into that category are universal education, the military, and police.
This is important so it deserves many more comments: it's not a two party system, it's a first past the post system. So long as we continue to use an inferior, outdated voting system, having two dominant parties is inevitable. Talking about overthrowing the two party system is pointless and misguided; it's a red herring.
The purpose of the medallion is to create a guild. In practice, the coexistence of ride-sharing defeats that purpose, subjecting all drivers to the risk of unlivable wages, and penalizing guild members with dues.
Man this is cool. While I really enjoy my own solution of using a custom SQLite vfs that stores your db transparently in dynamodb[0], this really is a compelling alternative.

I wonder how viable this would be to use from aws lambda? It seems like the way lambda does concurrency probably doesn't play all that well with litefs. Maybe it's time to move some workloads over to fly.io.

[0]: https://github.com/psanford/donutdb
I'm not sure if this is what you're getting at, but the tilde[0] and SDF[1] communities are going pretty strong still. Both of them amount to getting a shell account on a shared box with a bunch of pre-installed/hosted utilities. Much more hobbyist-centric than professional though.

[0]: https://tildeverse.org
[1]: https://sdf.org
Having two completely polar opposite group-thoughts is how we retain nuance (largely through compromise). If you want gray, you mix black and white; you don't go around throwing red, blue, green, etc. into the mix. Multi-party is not the solution.
So all the climate scientists in the 1980s who said that the sea levels would be a meter higher today did not ruin their credibility?

I think if you asked the average person about that they would not think they are very credible.
"Have them ready" for what? The school had computers, in the computer lab.
Software engineers have full-time managers (which are a lot more overhead to pay for but kinda serve that purpose from the client perspective) and are paid well enough and consistently enough to usually only work one job on a given day. Subcontractors sometimes do decide not to show up to your job site because another employer offered them a bonus to do theirs that day instead. The point isn't (only) to humiliate or do a show of power to the workers, it's to counter an economic incentive they have.

That said, for a lot of subcontractor trades, it's so hard to find anyone that I'd worry about the reverse: you get known as "the freaks with the cameras" and no one good bids on your stuff anymore, and then the delivery is even more delayed.
Cool, so can the author build a browser - all the requirements are in the w3c specs, or just look at Firefox/chrome so it should be no problem. Oh, and and build it for <100k, that's another requirement. In 6 months, that's another requirement too. Since I did the hardest part, I expect a 90/10 split. And no one else better copy my requirements or I'll sue.
at least you have a family.
> "but [FreeBSD's] rock solid"

Curious to hear your feedback of FreeBSD v5-8. Since many consider those releases (years) very bumpy.
For the past 2.5 years, I've published summaries of each month as it ends, so on 2023-06-30, I published a summary of June 2023. Each post has the following:

- Narrative Introduction;
- Podcasts reviews (each review is 25 words or fewer);
- Nerdy Software (25 words or fewer on a piece of software I like);
- Bougie Products (25 words or fewer on a product I like);
- Personal Finance and Investing (advice in 25 words or fewer);
- Reading (each review is 25 words or fewer);
- A List.

The name of my blog comes from a quote that inspires me: "In music, as in everything, the disappearing moment of experience is the firmest reality." (Benjamin Boretz)

It's hosted on Buttondown: https://newsletter.disappearingmoment.com/archive

Posts that don't fit my monthly format are hosted on Sourcehut (via Hugo):

https://disappearingmoment.com/

My favorite post is about getting to know a song that a friend recommended:

https://disappearingmoment.com/exposure-loss-jacqueline/
Shipping and getting to see customers using and enjoying what did not exist before I typed it into being.

A simple CRUD app is magic to the average user, if it does something they haven’t seen done in software before - and that could be as simple as some calcs in a custom domain.

The first customer who tells you “this is great”, if it’s anything like my experience, changes everything.

It also helped that some of my early forays were to clean up code by a guy ten years my senior which was rammed with bugs - fixing those one by one was satisfying and helped me earn trust with my team and in myself.
That's more or less the correct way to run anything energy intensive, scavenge as much of the waste heat as you reasonably can.

Theoretically, continuous distillation can be extremely efficient, as, you're removing as much heat as you're putting into the system. In reality, you get into diminishing returns fairly quickly, because insulation, pumps, heat exchangers, etc, are all far from free, especially at scale.
3.5 or 4?

And did you also try the problem with Co-Pilot?
I built one large scale system in my career (when I worked at Google, I made a folding@home screensaver that used up idle cycles in production).

When I built it I ignored 95% of what Google knew about large scale system design because that knowledge was really about building scalable web services and storage systems, while I needed to build a batch scheduler which could handle many millions of tasks simultaneously. We depended on a few core scalable resources available in production (borg, chubby, bigtable, colossus) and tried as hard as possible to avoid spamming them with excessive traffic without adding lots of complex caches and other hard-to-debug systems. In fact, "simplicity" was the primary design goal. The system worked, it scaled, and if I'd followed all the normal Google guidelines, it wouldn't have (because scientific computation and web load balancers differ). Not sure what to take away from that.

These days in system design interviews I usually focus on limiting the use cases for the system so that I can architect something that: linear resource consumption for linear workloads over 2-3 orders of magnitude, is simple enough that a small group of engineers can understand the whole system and debug it when it breaks, and not try to optimize for future use cases (clearly documenting the limits of the system) or try to accomodate too many oddball one-off user requests.
Oh, sorry, to clarify, I meant: HTTPS that works automatically. By starting the server, it's starting HTTPS by default. It gets or generates a certificate for you and renews it, etc.
You just saw it happen in OP. Just do as others do and don't sweat this stuff. The principle is code sharing and an offer of a thing you've done.

Don't overthink it.

This is fantastic. I love the way he handles his project. Just great for adoption and contribution.