za_creature

They run linux and offer ssh but with a custom shell that mirrors the "web shell" in usefulness.

Ubiquiti sucks nowadays but Microtik is simply insane.

50 years for large models is a stretch, though TI did have smaller, real-time field-trainable neural nets almost 40 years ago:

https://en.wikipedia.org/wiki/FGM-148_Javelin#Seeker

It was featured in one of the Modern Warfare games from around 20 years ago, and I looked it up because back then, I called bs on the fire & forget aspect.

N different proofs will not be linked to each other

Please sign up to continue

Is it okay that by default [...] ?

Yes. IP addresses by themselves are not PII and may be logged indefinitely. It's only after you start correlating them with other shit that you're collecting that they become subject to GDPR.

Same for cookies really. If you *only* operate a shopping cart, you don't have to display a cookie notice for "only technically required cookies". The point of the cookie notice is to dark pattern users into granting more access or just to annoy them enough that they continue not caring about privacy.

401(k)s are self directed

Citation needed

I just logged in to post this

https://silicon-valley.fandom.com/wiki/The_box

I made no mention of anyone being politically sympathetic or otherwise. A private investor is _private_ and thus not subject to a government bailout. The argument for government bailouts used to be that "grandpa would lose his pension", I merely stated the terms that would make this non-applicable.

If pensions invest in the stock market, then they are de-facto acting as a bank. And last I checked, in the land of the free, you get to withdraw your 401k should you vibe with the decision to do so [please don't do this based on this post alone].

And these equity-investors, do they use their own money to buy the (presumably non-voting) stocks?

Cause if that's the case, I see no reason for a government bailout should things go south. Nobody's pension would be affected by some private investor losing money on a bad investment.

But if that's not the case, then someone somewhere along the chain is acting as a bank, subject to a vibe-driven run.

They're not profitable either, so the money has to come from somewhere, no?

Most bank runs tend to be driven by vibes, not numbers though.

The good news is that these folks seem to be in possession of a vibe-rator.

I'm not a systems guy, but you're probably right. A mutex requires an atomic variable which triggers the same cache coherency mechanism under contention.

What Justine probably meant was an apples to oranges comparison: in userspace, you can sometimes add constraints that allow for a faster algorithm whereas the cpu generally has to assume the worst.

That being said, if you look through this thread you'll find similar issues with OP's phrasing. A fine engineer / hacker, but too much 4chan troll in my book.

Introducing the new

iFerrari XS

It's 140% better than the previous Ferrari Enzo

And 20% thinner

With a brand new Magnesium case

It's the fastest Ferrari we've ever built.

There is a theorem that (...) multiplication requires unbounded memory

What theorem is that?

The multiplication of any two integers below a certain size (called "words") fits in a "double word" and the naive multiplication algorithm needs to store the inputs, an accumulator and at most another temporary for a grand total of 6*word_size

Sure, you can technically "stream" carry-addition (which is obvious from the way adders are chained in ALU-101) and thus in a strict sense addition is O(1) memory but towards your final point:

Theory is important, but engineering is also important.

In practice, addition requires unbounded memory as well (the inputs). And it's definitely compute-unbounded, if your inputs are unbounded.

I dislike the term "we muddle along". IEEE 754 has well specified error bars and cases, and so does all good data science. LLMs do not, or at least they do not expose them to the end user

So then, how exactly do we go about proving that the result of chaining prompts is within a controllable margin of error of the intended result? Because despite all the specs, numerical stability is the reason people don't write their own LAPACK.

The size difference between the local LLM and all of the above is about... the size of the local LLM.

If you stood on the street corner and asked every passerby what they would change...

... the answer would depend on which street corner you asked.

people seem so unaware of how idiosyncratic their preferences are

Yes, they are. They also tend to state that "most people" agree with them. This is called subjectivity.

The video is about a 2x1 link, which the author hopes to eventually scale up to 3x4 using 40 gig transceivers. I'd say thunderbolt is probably safe in the near future.

Just to put some context into what _never_ means here:

If a website offers me the choice between "accept cookies" and "more options", I'll manually edit the DOM to remove the popup from the offending website. Some sites disable scrolling while such a "We value your privacy" popup is shown, so I wrote a js bookmarklet to work around most common means of scroll hijacking.

Google is currently waging a war against adblockers, especially on youtube. I currently have a way around that too but should they start baking ads in the video bytes, I'll stop using youtube altogether (though I am willing to look the other way for content creators shouting out their curated sponsors).

There is simply no universe in which I pay for certain types of digital content, and while I can't stop the data collection that ultimately pays for it, I can at least make damn sure that it's unlawful.

With respect to Spain and sports, stadiums are littered with ads, players wear ads, the commentator stream itself has ads baked in and people buy tickets and tapas to watch the game live. If that's not enough, go fuck yourselves!

Github: https://github.com/luckyPipewrench > Pipe-layin' mastermind, code slayer supreme. Typin' fire across the screen, layin' pipe through the night. Bustin' blockages and bugs with no mercy.

HN: > created: 1 day ago

https://asciinema.org/~user%3A281302 > Joined on February 9, 2026

pipejosh is totally a real person!

Because a plumber would definitely first and foremost plug his AI software and not his plumbing company, which definitely exists!

How does this make it to the frontpage in <1 hour from posting?

P.S. https://pipelab.org/ has a bad cert

Ah, I meant that for a classic heap, it's convenient to assign h[0] to the limit of your goal function (e.g. -inf for a min heap) cause that way you can skip the while i>0 check and just do while h[i>>1] > min(h[i], h[i+1]), asserting that the condition is definitely false when i < 2

I guess that it's not as important when you're explicitly willing to pay the piper and run the full log2n iterations just for the sake of branch predictability.

Thanks for the algo though, before today I never would've thought about doing a branchless downheap with i = i<<1 + h[i<<1] != h[i]

That's a nice niche you found (spoken from one heap fan to another) but I have to say I strongly disagree with your use of *roughly* twice as much

At best you were off by one but in the context of performance, you'd want to assign that extra to a super-root of ±inf in order to save log2n extra range checks per heap-up, no?

When you know what you are doing with C pointers, the compiler just doesn't get in the way.

Tell me you use -fno-strict-aliasing without telling me.

Fwiw, I agree with you and we're in good[citation needed] company: https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg...

Same idea, as a shareable static html page. It never made it to the front page though:

https://news.ycombinator.com/item?id=38365892

Thank you for the impromtpu audit. I agree that localStorage is overkill for the discord use-case, but wanted a bit more leeway for async forum posts.

I might tweak the UI to let users explicitly opt into no-storage operation, though now I wonder whether opening it in incognito is the correct UX approach for that behavior?

funny you should mention that

I initially wanted to go with inplainsight dot net cause that felt more fitting, but that's parked and the owner won't let it go for less than the low 4 figures, which was outside my budget for a hobby project

Did you learn anything while building this?

My main takeaway is that, for all of its footguns, React has solved a lot more problems than it created: Even for this rather simple app, the number of invariants that need to be preserved is large enough that doing jQuery-style UX feels like hand-writing assembly. I know from other projects that React's performance is quite a thorny issue, though I now wonder if that's because we're treating it as a library (as advertised) when instead we should maybe treat it as an optimizing compiler for a far too liberal language (there's only so much you can optimize when some <script> you have no knowledge of can pull the rug).

I've also learnt that post-html5 web specs are still annoying, inconsistent or downright missing. I guess that the committee is mostly happy with that outcome but it's almost 2024, can we get TypedArray.to/fromBase64() already?

How do you plan to monetize it?

I don't, not really. Pushing ads, even if it could be done without compromising security, might trigger paranoia in some users for example when the interested in private communications data point leads to the user seeing ads for other encryption solutions, some of which may be formulated as they're always watching you!.

On a tangential matter, I'm currently looking for contracts. Send me a message if you like what you've read and are willing to retain LLC external contractors (US east coast or EU time zones). My services are not cheap, but (I like to think that) they are top shelf.

How do you plan to keep this running in the future?

It's pretty cheap as there's no real infrastructure to speak of. All cryptography is done in the browser and while there is a server, it is only used to deliver the static html page (~12KiB when gzipped). Most of the distribution cost is currently offloaded to the proxy provider and while they are well within their rights to pull the plug at any time, my current choice has a proven track record of doing the opposite for the internet equivalent of public infrastructure: <https://blog.apnic.net/2021/06/17/how-a-small-free-ip-tool-s...>.

Other than my time, the only thing I've paid for thus far is the domain name, and I can likely personally afford the renewal fees for the foreseeable future.

You mentioned repudiation. What's that about?

Because all secrets are deleted upon (successful) use, both parties can claim to have no knowledge of any secret exchange since there's no hard evidence that can pin them to it. They can argue that either their respective platform accounts or their user agents were compromised and those statements are irrefutable without further evidence. That being said, the exchange itself is part of the public record and may (I am not a lawyer!) constitute reasonable suspicion for an officer of the court to issue a warrant that could lead to the discovery of said evidence.

I want to buy you a coffee, how do I go about doing that?

Accepting donations is something that I have considered, but have currently decided against because profiting from this feels unfair to the proxy. While this is subject to change in the future, it will only do so if the projected donations can cover the distribution costs (e.g. via a paid plan or self hosted).

With no opinion on whether this is a good thing or not, the blockchain as described by the original author(s) does allow (as long as the hash function holds up and there's financial incentive to crunch the numbers) proof of public delivery of a message, thus negating the need for notaries.

there is no such thing as good code.

nor is there such a thing as a good love letter

The one thing you can expect to receive in exchange for said significant donation of your time is recognition for your work.

If your work consists of half-finished code that you then attempt to pass off as a usable product, the expected reward is shunning.

There's a difference between pushing your CS101 homework to github and publishing your package to npm. As with academia, once you publish you implicitly vouch for the quality of your work, and your reputation is permanently tied to it.

If they're renting them, I think Romania has a higher need at the moment :)

The thing is, tail calls aren't _just_ about emulating iteration via recursion:

  def foo():
      raise ValueError

  def bar():
      return foo()

  bar()