skysight-inc/HackerNews huggingface dataset:
These videos always give me an unpleasant feeling that I don't know how to express in a useful way. Almost everything in this one is oversimplified, misleading, or wrong, yet I feel like any attempt to argue for this would come off as pedantic; any individual complaint could be countered by either "it's technically true" or "it's just entertainment".

Like, the "cowboy hat" example is wrong on multiple levels - GPUs are not SIMD machines, model-to-world translation doesn't work like that in practice - but you can maybe excuse it as a useful educational lie, and he does kind-of explain SIMT later, so is objecting to it valid? Or: the video claims to be about "GPUs", but is in fact exclusively about Nvidia's architecture and the GA102 in particular; is this a valid complaint, or is the lie excusable because it's just a YouTube video? Or: it overemphasizes the memory chips because of who's sponsoring it; does this compromise the message? Or: it plays fast-and-loose with die shots and floorplans; is a viewer expected to understand that it's impossible to tell where the FMA units really are? Or: it spends a lot of time on relatively unimportant topics while neglecting things like instruction dispatch, registers, dedicated graphics hardware, etc.; but is it really fair to complain, considering the target audience doesn't seem to be programmers? And so on.

Did you actually get anything out of this video? Any new knowledge? The article seems like a much more useful intro, even if it is also specific to Nvidia and CUDA.
moles should know better than to utilize mountweazels!
https://en.wikipedia.org/wiki/Fictitious_entry
I bet a lot of that hands on knowledge is long gone now. The last people who actually did it were several generations ago.
Because companies like Google are a cancer and I don't want to give them data they didn't pay for.
> whenever it comes time to upgrade

curious why that time comes and how often?

I've been living with the same router/modem combo (Fritzbox) for around 11 years, and I don't plan to replace it before I get FTTH. (Otherwise I would have.)

Nothing against OpenWRT, I have used it in the past, but I doubt I would have switched routers more often if I was still using it...
OT: The publication (Spectrum by IEEE) has some really good content.

It's starting to become a common destination for when I want to read about interesting things.
The long-tail of Backrooms & SCP fanfic is whats cringe, like the article describes.
> we

If by "we" you mean anyone else than Google and the select few other LLM provider they choose to associate with, I'm afraid you're going to be disappointed.
This is information-theoretically guaranteed to make LLM output worse.

My reasoning is simple: the only way to watermark text is to inject some relatively low-entropy signal into it, which can be detected later. This has to a) work for "all" output for some values of all, and b) have a low false positive rate on the detection side. The amount of signal involved cannot be subtle, for this reason.

That signal has a subtractive effect on the predictive-output signal. The entropy of the output is fixed by the entropy of natural language, so this is a zero-sum game: the watermark signal will remove fidelity from the predictive output.

This is impossible to avoid or fix.
I applaud this person for disproving conjectures and think disproving conjectures is important, but the reason why the conjectures he disproved didn't get much attention is that they're all relatively minor conjectures, and he probably would have gotten just as little attention if he had proved them.

If someone disproved the Riemann hypothesis, it would be the biggest math story of the century -- certainly since the proof of Fermat's last theorem, I am sure.

I also think that working out the consequences of a conjecture being true is _indistinguishable_ from attempting to disprove the conjecture. How could you possibly work out something like a proof (or disproof) by contradiction without doing that? Really working toward a proof in general is the same as working toward a disproof in almost every case I can think of. An exhaustiveness proof is also a search for a counterexample, etc.
> ... any door ... wouldn't lock behind me.

You are not alone with that precaution. Ages ago, before plastic gift cards were ubiquitous, I used to quest/urbex with shims of thin aluminum trimmed to door jamb size (making them harder to detect).

The buddy system also was used - "You stay on this side, I'll go through and test it can get opened from the other side."

Extremely useful when entering campus/city steam tunnels that may not have another good door for hundreds of meters (the tunnels were secured to prevent access to the structures they connected).
They have an official advanced search as well:

https://www.imdb.com/search/title/
We Shall Fight in the Buttery – Oxford's War 1939–1945
They probably meant readings, as the cognate for "lecture" in romance languages generally means both a lecture and a reading
> I don't know anything about adversarial-to-human information

I also don't know this particular term, but my it reminds me of https://en.wikipedia.org/wiki/Roko%27s_basilisk and the related
https://en.wikipedia.org/wiki/Information_hazard - though the latter deals with "true" information, if I understand correctly, so the fan-fiction site wouldn't fit, I think?
Pro OG:Image for Your Website by AI in 10s
Have you camped there?
The basis of HOAs is a history of racial covenants. While facially racial covenants are illegal, the enforcement of HOA restrictions is based in racism so the entire concept is rotten to the core.
> There is only one reason why...

Not true. Assume for the moment that you're the CEO of Golden Insurance Co., and you're still writing fire insurance policies in Burn County, CA. After Yet Another massive fire - and loads of "100% loss" payouts - from your balance sheet - the experts in your Risk Estimating Dept. say the premium to insure a $600K house in Burn Co. needs to be $200K/year - because they expect to pay out to replace that house ($600K) every 4 year ($150K/year), and they need the other $50K for overhead and temp. relocation benefits and rebuilding-cost inflation and a bit of hedge - just in case they're wrong, and things burn down even more often.

Now - if the fire insurance for a $600K house costs $200K/year, how many of the homeowners can and will actually pay that much for fire insurance? Perhaps a number that's falling like a rock? Meanwhile, Wall St. is howling about the horrible risk that your balance sheet is facing, if there's another big fire season. And the 99% of homeowners who can't afford those premiums are bitterly angry, and in a mood to string up the bearer of bad news (meaning you) from the highest tree still standing.

SO - why wouldn't you, as CEO, make the unfortunate decision to just stop writing fire insurance policies for properties in Burn Co., CA?
I really like imcdb, or The Internet Movie Car Database. Want to know what cars were in a movie? Check imcdb!

https://www.imcdb.org/
Back in the day I booted the live CD, and I bought a magazine ages ago because the cover disk promised a similar environment.

I actually talked a co-worker at a previous job into using it (he was doing Mac OS X development at work, didn't have a Mac at home, and was able to use GNUstep for this after a fashion).

I do have a Linux box which I can use for it as well, and experimenting with it there is something I want to do now that my MacBook stopped supporting my Wacom One. My next tech purchase will be a Raspberry Pi 5, and I hope to experiment with GNUstep on it.
Separate rates already exist. Try buying an investment property and you'll see the rate is higher because there is more risk to the lender.
> The only real downside is data control (ie - the company has less control over how a developer manages assets like source code).

I've worked in a remote, secured development environment and it sucked, but to their credit the company did it for exactly this reason - control over the source. But bear in mind that source control is a two-way street.

Losing proprietary source can be harmful (especially in compiled languages where the source might carry much more information than the distributable). But they were mostly worried about the opposite way...that something malicious gets INTO the source which could pose an existential threat. You'd be correct to say "well that should be the domain of source control, peer review etc", but in this case the company assessed the risk high enough to do both.
> The difference here is Gitpod being stateful, which is notoriously hard on Kubernetes, though easier now than ever before!

We've always had issues with stateful kubernetes setups. Can you share what makes it easier today than before? Genuinely interested.
AT&T (Again) Caught Cheating Federal Subsidy Program for Poor People
> You have to go really high up the chain in those offshored manufacturing jobs before you see anyone actually interacting with an employee in the US.

And how are those not the same jobs...?
I see no scenario where there won’t be an LLM that is deliberately tailored for that purpose, possibly even built by an “intel” agency for the very purpose of having blackmail over someone that may become useful later in their career.
My own experience is that the Go stdlib has resulted in worse security than, for example, rust.

The reason for that is that both the Rust and Go stdlib have a stability promise, so anything built into them can't change if it's insecure.

For example, the 'tar' package in go by default returns unsanitized paths, and has led to a bunch of CVEs: https://github.com/golang/go/issues/55356

The go stdlib can't change the tar package to make it secure by default because it would be a breaking change to do so.

Rust, on the other hand, has a tar package outside of the stdlib, and so it can evolve to be more secure and over time find a better interface.

We've seen that with various other packages, where the Go stdlib HTTP implementation defaults to no timeouts, and thus makes it easy to DoS yourself. Ditto for tcp. The tls package has similar backwards compatibility warts that make it less secure by default.

Forcing backwards compatibility with network protocols by baking them into the stdlib has largely not been a security win in my experience.

You can argue that people can build packages outside of the Go stdlib too, like if the stdlib "image/draw" package is so bad it can't be used, they can make "golang.org/x/image/draw", or if the stdlib crypto package is bad, they can make "golang.org/x/crypto"... and they did, but people still reach for the stdlib because it's easier to, which makes it an active security trap.
I do this sometimes to avoid invoking any stereotypes. Telling someone which country you're from opens you up to "of course that's what an X would say" replies, or worse.
Would love to see exactly this but running on an ESP style board (with Ethernet). As well as an API or web interface to trigger manual WoL calls.

Nice project, thanks for sharing!
Not heard of OMDB before, thanks, will give it a go
1 yard is 91.44 cm, so a better approximation for yards to meters would be "add 10%"
Really? War paint, mob mentality, tactical gear, and many of the police that engaged with them ended up wounded or dead. People were climbing the walls, smashing through windows. Can you imagine these people doing any of these things if they weren't riding a surge of adrenaline that justified any risk to further the cause? Can you imagine them being alone, without the (presumed) support of the sitting president, and doing these things? I can imagine them standing outside with signs, and if that's what they did we wouldn't be having a conversation now.
infrastructure-as-code? maybe this is in same vein?
Sounds interesting, but it also sounds like something that could very well be circumvented by using a technique similar to speculative decoding: you use the censored model like you'd use the fast llm in speculative decoding, and you check whether the other model agrees with it or not. But instead of correcting the token every time both models disagree like you'd do with speculative decoding, you just need to change it often enough to mess with the watermark detection function (maybe you'd change every other mismatched token, or maybe one every 5 tokens would be enough to reduce the signal-to-noise ratio below the detection threshold).

You wouldn't even need to have access to an unwatermarked model, the “correcting model” could even be watermaked itself as long as it's not the same watermarking function applied to both.

Or am I misunderstanding something?
AIs and LLMs have an extremely uphill PR battle to fight right now. Anything that is deemed AI generated is assumed to be borderline trash (lots of exceptions, but you get the point). So, I can see that if someone uses LLM to generate text, they don’t want it to be marked as “low effort content”.
Location: Paris, France (moving to San Francisco soon)
Remote: Yes
Willing to relocate: Yes (especially if you're in the Bay Area)
Technologies: Javascript/Typescript, Python, React.js, React Native, Next.js, Node.js, AWS
Résumé/CV: https://valentinfoucault.com/resume
Email: valentin at valentinfoucault dot com

Product-Minded Engineer with over 6 years of experience, specializing in the JavaScript/TypeScript ecosystem.

I've worked with a wide range of companies, such as the startup studio eFounders/Hexa, the SaaS Mogi.ai, the digital agency Business Continuum, the eyewear brand Jimmy Fairly, and the auction site Drouot.com.

My generalist profile enables me to transform any idea into a concrete solution. I distinguish myself with a very "product" oriented approach, using code as a tool to solve problems and create value for the end user.
Making a robot that can work outdoors seems a lot easier than making a farm that can be worked indoors.

Even if you need to do some prepwork like levelling paths for a robot to traverse, that's still cheap compared to a building.
Long term, yes, everybody dies.
I am planning to move to Hugo for the rendering part, because WordPress is becoming a "wobbly" ecosystem in my humble opinion.

If the business around WordPress become fragile or too much exposed to backfire from Wordpress.com, a lot of company will see little incentive to proceed on this direction.

A lot of themes/plugin could start moving away. It is just a possible outcome but it is becoming a bit real every day passes without a clean solution of this litigation.
Agreed. But further on the how-to-get-there:

Quoting works of Phillip Armour [0], circa 2000-2003:

... software is not a product but a medium for storing knowledge, and software development is not a product-producing activity, it is a knowledge-acquiring activity.

... the real job is not writing the code, or even building the system - it is acquiring the necessary knowledge to build the system... Code is simply a by-product of this activity. The problem arises when we think the code, rather than the knowledge in the code, is the product.

... When we use models and mindsets that are rigid and deterministic to manage an activity that is fluid and variable, it is not surprising that people get disappointed.

------

so, IMO, it's the nature of Software (=knowledge) that spoils the (most) practitioneers - there's no gravity (or reality as such) there, so everything is (or seems) possible. And once you learn that "easy" way.. hard to unlearn.

The software as engineering discipline needs a set of substitutes for the missing nature/reality's "laws/rules". i.e. Resiliency might be one.. All the titles of the chapters of the textbooks [1] might be candidates (correctness, maintainability/ repairability, flexibility, portability, understandability, ...). And then, depending on the domain / importance, choose smaller or bigger subset, with looser or tighter conditions.

Easier to say than do it.. Most systematically-thinking people would do it implicitly - but that as well may (or will) contradict the business goals.

Just thinking aloud..

[0] http://www.amazon.com/Laws-Software-Process-Production-Manag...

[1] https://software-engineering-book.com/
I'm fascinated that this approach works at all, but that said, I don't believe watermarking text will ever be practical. Yes, you can do an academic study where you have exactly 1 version of an LLM in exactly 1 parameter configuration, and you can have an algorithm that tweaks the logits of different tokens in a way that produces a recognizable pattern. But you should note that the pattern will be recognizable only when the LLM version is locked and the parameter configuration is locked. Which they won't be in the real world. You will have a bunch of different models, and people will use them with a bunch of different parameter combinations. If your "detector" has to be able to recognize AI generated text from a variety of models and a variety of parameter combinations, it's no longer going to work. Even if you imagine someone bruteforcing all these different combos, trouble is that some of the combos will produce false positives just because you tested so many of them. Want to get rid off those false positives? Go ahead, make the pattern stronger. And now you're visibly altering the generated text to an extent where that is a quality issue.

In summary, this will not work in practice. Ever.
New biotech startups are working on an alternative to alternative protein
The article says it's better to have blank space instead of the header, not next to the header.
Reflective listening doesn’t mean to parrot back what someone says, but it is an artform to transform what they say to add clarity and precision, for example by representing assumptions of the other person accurately as such and help differentiate them from facts (and much more). You also ask questions to help the other see different perspectives in and about themselves. Systemic approaches add a huge repository of potential questions, such as „what would your life look like without that problem“ and such.

You also do not repeat every single thing, but pick what you think is essential. The other person will then immediately see if something is missing from the summary, which overall leads to weeding out what is important from the not important, and eventually escape thinking loops. Without you adding anything, just by selective removal, you end up with the essence of the problem. It’s a process of distillation.

Known techniques for example are nonviolent communications and Focusing. That is a multi year accreditation process.
This is a problem which Literate Programming can solve:

http://literateprogramming.com/

getting folks to actually use that is a totally different problem. I've been using a custom .sty file to do this in a native fashion: https://github.com/WillAdams/gcodepreview/blob/main/gcodepre... so that the source isn't a sea of grey comments: https://github.com/WillAdams/gcodepreview/blob/main/gcodepre... but it's early days yet, and the project is niche and my coding style quite prosaic.
Quotes are for direct speech. Never, ever, ever for paraphrasing. The entire point of quotes is to indicate that the thing is not paraphrased, but what was said verbatim.

So it kind of is worth getting hung up about. But hey, today you learned this! :)
https://news.ycombinator.com/item?id=42048358

The levels of buying internet service simplified:

1. Pay for best effort traffic level. E.g. A residential user paying for 1gbps service

2. Pay for guaranteed traffic level. E.g. a business paying for guaranteed 10gbps. Often this maps to paying for a dedicated frequency on a cable, but that's hidden from you, you are just provided an Ethernet port or two.

3. Pay for a dedicated frequency on a cable. Also called "lease a wave". As you noted this is the most common way to go undersea. But it's common over terrestrial cables too. In this case the purchaser is often responsible for their own optical networking equipment, and the service provider muxes together all their customers. Sounds like you know more about this than me. The service provider's equipment doesn't have protection if your neighbor is accidentally stepping on your frequency range?

4. Pay for an entire cable. Also called leasing dark fiber. It's 100% your responsibility to "light" it. To make it worth it you're usually using optical networking equipment to mux together several different waves, just like the above scenario undersea, just all different waves belong to you. Commonly used by big tech companies and ISPs to connect their datacenters and points if presences in big cities. Lots of times the company you lease the cable from is also your contractor to repair cuts and maintain the amplifiers every ~50km.
It's always been my assumption that we wash our hands when we go to the bathroom for two reasons:
1. Wiping your butt can lead to feces getting in your hand. A lot of diseases can come from feces.
2. It's a good frequency to wash off whatever else you've been touching that day.

Assuming you go to the bathroom 3-7 times a day, that's that many opportunities to wash off the dirt you were digging in, trash you picked up off the street or someone else's hand you shook.
Mostly because it's a multi-dimensional spectrum and because exceptions extend the rule and society deals with most exceptions via some form of adjustment 'therapy' and that requires a framework that the bulk of the people learns to be convincing enough so that the exposure effect supports/complements the (re-)adjustment.
The Developer of Acorn on Apple's Pixelmator Acquisition
'Miracle' weight-loss drugs will change the world
If Google locks in enterprise clients using Google Workspace to Gemini then they won't really have a choice. It is selling it as an "add-on" already: https://workspace.google.com/solutions/ai/#plan

Suffice to say it is evident that no other LLM will come close in integration with Google Docs and other Workspace apps as Gemini.
>I absolutely can and I don't think it is at all contrived to think that the recent consolidation in the industry is linked to a recent decrease in the building rate.

>This doesn't mean that land use regulations (and permiting processes and the other NIMBY tools) don't have an impact, but it does mean that we cant look at that impact to expain the increase.

Stroller isn't just adding his theory (corporate consolidation) into the list of factors, he's explicitly denies that NIMBYs are a factor.

>the problem of housing prices and construction is about consolidation of homebuilders, not an upsurge in annoying people who want to maintain neighborhood character.
> And indeed, a trip to StackOverflow never ends at StackOverflow for a person with much curiosity.

My favorite variety of SO question is "how do I do X in $LANGUAGE," because inevitably, people pile in with various answers, and then someone starts benchmarking all of them and providing graphs. Occasionally someone even breaks down the assembly instructions for each solution and explains why one is superior to the other. All in all, a fanatical obsession over something small and relatively unimportant, because they like to learn, and they like to share what they've learned.
Test a Server with Docker Compose on GitHub Actions
If you find yourself reading this review and somehow forget which machine they are talking about, fear not: the phrase "ThinkPad T14 Gen 5" shows up 21 times in the text.
>How does "you cannot be fired on the spot for no reason" prevent them?

At the very least, getting fired is a sign of no confidence from your boss.
I think you are right regarding lactate threshold but im not sure how they factor in running economy as it's difficult to calculate. You need an accurate VO2 measurement. I guess they use HR as a proxy but in practise I find HR isn't such a good measure of metabolic output for various reasons; hills, unrelated stressors, heat, aerobic decoupling, etc.