NikxDa

But Kimi (at least say) will release their weights. So surely, if their prices are too high, somebody else will host it cheaper?

Seems like it, but since you can self host it, you still get a lot more control over the data than using one of the aforementioned hosted offerings

Super cool, especially that the code is annotated!

In case the author is reading: The decorative feather images are between 2MB to almost 5MB in size. Compression might be in order to save users time and bandwidth, and make the site look less broken while the images are partially loaded :)

It has simply become a "marker" for LLM style, so I'd argue authors caring about their text will now just use a different structure to get the meaning across. That's just part of being a writer. You can choose to write it, and it'll be correct, readers (including me) will just conclude its most likely an LLM and often stop reading.

Encryption at rest means they have the key. End to end means they don‘t. Huge difference!

And yet other people rely on it doing exactly the opposite. Aside from whether this behavior is useful, it is never warranted to change such an important thing unannounced.

From what I can tell, his argument seems to be that

1. no code was manually copied by a developer, and

2. all software in the same space copies off of each other

But the big giveaway here is the exact same layout/copywriting on both products. Telling an LLM "write this product and build a 1:1 clone" is still copying by all sensible definitions. The fact that he argues nothing was copied is ridiculous.

I can‘t help but wonder what goes on inside of the upper management of these big companies, and why nobody ever stops for a moment to think about whether what they are up to does any good for the end users beyond making more money.

But then again, this is very on brand for Meta/Zuck, so I‘m not surprised.

Even if they are not (which I most definitely think they are), a good writer would know and avoid them, as sad as it is that there is a need for this

directionally very bad

I spent the last few months learning about compositing and blending and this interactive blog post is the result.

I hope HN enjoys it, and I'd love to hear your thoughts (good and bad)!

Not what I'm saying, but this has happened _so many times_ and nothing has come of talking about it so far. I would love to see things change, but in this specific instance I'm not holding my breath

I believe this was originally explored by Sam Henri Gold, at least that's the first time I saw it a while ago :)

Links: https://samhenri.gold/labs/20250906-lid-angle-sensor/ https://github.com/samhenrigold/LidAngleSensor

He's also the person who originally came up with the creaking door: https://bsky.app/profile/samhenri.gold/post/3ly7252lx422d

German trains have very much to complain about, but honestly, their customer facing IT is pretty good. I've not had to deal with PDF tickets nor printed tickets in years.

The website and app work well, in my experience. It's all pretty sleek and modern, too. It's the one area they do a good job in, to be honest.

This is super cool, and I wish something like this existed at my place, as it enables information sharing without the need for phones/actual screens that shine in your face when the lights are low or tempt you to doomscroll.

That said, the large primary display this uses is $2000. That's very hard to justify for any "normal" household, and that's without any mounts, backend, services etc.

I‘m at https://nik.digital :)

Some others: https://samwho.dev https://www.nicchan.me

I appreciate the author being vulnerable like this in a public setting. It's easy to see why it would be scary, especially since admitting being wrong or not knowing something can easily be turned into questioning one's overall competence.

I wish we'd be more open about our flaws and knowledge gaps in general. I think we'd all benefit.

The suggestion to have the server return the table directly starts bringing presentational concerns into the backend, which I am not a big fan of.

Having the server return plain JSON means the APIs can be reused across products effortlessly and also means that all style changes can be done in the same codebase.

I get reminded of how important this is every time I get to work on an old project that has APIs return HTML that is then being inserted into the DOM by something like jQuery. Figuring it out and updating it is typically a huge mess.

Yes, China, the bastion of free speech...

https://freedomhouse.org/country/china/freedom-world/2025

I personally find the revised designs the author proposes worse than the originals. Sure, the extra space allows larger text and icons, but the overall design quality starts lacking in my opinion.

Maybe I am conditioned to like cards by their excessive use in existing designs, but it might also just be that cards look better, and therefore make the product appear more polished and the site more inviting to use and read. It might not be the most minimal possible design, but a site being pretty is great if functionality doesn't suffer.

Brave however is riddled with Crypto and AI crap. It doesn't have any useable support for multiple profiles, too: last time I tried it, it would end up showing various errors on every startup and you couldn't have two profiles in the same window.

Zen still has some annoying shortcomings, like missing Widevine DRM or the dev tools opening up annoyingly slow. The potential is there, but it wasn't quite daily drivable as a developer for me just yet as of a few weeks ago.

Once it gets there, I too will finally leave Arc behind. Until then, while it is on life support, Arc actually works. I really wish The Browser Company would just own up to their fuck up and revive it.

An alternative that works very well for signatures too is Perfect Freehand (by the guy behind TLDRaw)

https://perfect-freehand-example.vercel.app/

The Top 81% calculation in the game is not as good as it may sound. Top 100% means you are at the bottom. You can confirm this by just losing immediately, which will place you in the Top 9X%.

The keyboard change is typical of Apple's meticulous attention to detail, even if it took more than a quarter-century to implement.

I thought this paragraph was absolutely hilarious. Especially if they had such meticulous attention to detail, it wouldn't have taken decades. The article is a joke.

Contrary to what npm states, this package actually depends on one of our aforementioned spam packages. This is a by-product of how npm handles and displays dependencies to users on its website.

For me personally, this is the biggest surprise and takeaway here. By simply having a key inside package.json's dependencies reference an existing NPM package, the NPM website links it up and counts it as a dependency, regardless of the actual value that the package references (which can be a URL to an entirely different package!). I think this puts an additional strain on an already fragile dependency ecosystem, and is quite avoidable with some checks and a little bit of UI work on NPM's side.

No paywall: https://archive.is/NyEQo

It is a reply to this tweet:

Could show the “Select your search engine for autocomplete or press enter” in the dropdown initially!

Halide is 2.99 a month, or 12.49 a year, and has been a subscription model since 2020. Sure, you have a one-time purchase option, but it is $70. I believe people who bought before the subscription got one year free, but things like widgets aren't supported. So unfortunately, that is likely the same fate for Kino.

This post introduces the subscriptions: https://medium.com/halide/introducing-halide-mkii-30f9f2bcea...