skysight-inc/HackerNews huggingface dataset:
I definitely agree, but again, if you look at the app usage times across every single demographic, those type of use cases are such a minuscule portion that it's just some noise. In my opinion, GPT/AI will cause more changes in workplaces, than in casual consumer spaces.
At the very least claiming neutrality after baking that sub stack title needs an explanation or apology, and even still the authorities involved are absolutely correct to cancel or at least postpone her lecture out of an abundance of caution to avoid a hatch act violation.
I must be having trouble following your train of thought here - many large web services like Cloudflare and Akamai serve large volumes of content through round robin DNS balancing, what's absurd about their success? They certainly don't know every client that'll ever connect to a CDN on the internet... it just happens to work almost every time anyways. That very few clients might not instantly flip over isn't always a design failure worth deploying full load balancers. I'm also still not following why the decisions for whether or not you need a load balancer are supposed to be in any way equivalent to the decisions of when using DNS would make sense or not?
What parts are not available?

WebAssembly can call arbitrary JavaScript through imports. You could literally provide an `eval` function if you were motivated to.
I'm still amazed these stock images with highlighted text don't send off immediate red flags in everyone's mind that they're being tricked.

Especially ones that have children, veterans, or old people, usually with big frowns or drooping flags. "Don't disappoint this stock image! Vote no on prop blah-blah"

It works. This strategy actually works
It's a funny problem. Too expensive to pump it WAY out to sea, but too salty to be of any use?
The article: https://www.science.org/doi/10.1126/sciadv.adn3268

Part of the forward flow of the 'dancer' could be that combining novel information on the page with existing knowledge enables local minimum-escaping Stuart Kauffman-esque long leaps of recombination?

Lagniappe: https://www.youtube.com/watch?v=J0FEfS5PP3c
Rust executors don't have real preemption, sadly. I'd love to have in Rust what the BEAM has for Erlang, block all you want, the rest of the processes (tasks) still run in time.

Also, the IO and the execution being completely tied (the executor provides the IO) is a wrong choice in my opinion. Hopefully in the future there is a way to implement async IO via Futures without relying on the executor, maybe by std providing more than just a waker in the passed-in context.
The stay at home moms in those families have lots of free time and are often similarly capable and educated to their no-lifer dads. They just choose the mom job
Yes you are right that an "IP packet carrying TCP" is totally different from a "TCP segment".

Like I have explained, this is precisely the reason why we need two different terms, "TCP packet" and "TCP segment", to name the two different things. There exists no 1-to-1 mapping between TCP packets and TCP segments. It is frequent for a TCP segment to span multiple TCP packets.

Muddying the waters would be if the same term would be used for the two different things. When two different things have two different names, the waters are clear.

Likewise, there is a 1-to-1 mapping between the "Ethernet frame with IP stuff in it" and the IP packet contained inside the Ethernet frame (ignoring the distinction between complete IP packets and fragmented IP packets, which has been removed in IPv6). The IP packet is obtained by deleting or ignoring the Ethernet header & CRC, while the Ethernet frame is obtained by adding to the IP packet the Ethernet header and CRC.

Because of the 1-to-1 mapping, there is no risk of confusion when using a term like "IP packet", regardless whether you speak about the IP packet alone, as existing in the memory before being sent or after reception, on about the IP packet as existing on the communication links or in some tool for network monitoring/sniffing, where it is encapsulated in the Ethernet frame. Similarly for an ARP packet or any other kind of packet that can be encapsulated in an Ethernet frame.
org babel supports way more languages. Elisp (obviously), python, C, C++, Java, you name it
- The EULA absolves Microsoft of any liability whatsoever. So they share in none of the risk. Imagine if physical items were like this: hit one bump and your pickup is destroyed. Scissors fall apart irreparably once they contact any material that's not paper.

- MS putting backwards compatibility (mainly done for business customers) above everything, at all costs. The peanut butter factory in Indiana that's been running WFW since '89 must never be inconvenienced, even if it means tens of thousands of people have to take their brand new computers to the shop (at their own cost!) multiple times per year because of spyware infections.

- Not valuing innovation. A culture where engineers are just a necessity to keep the money-making machine running. All the excitement was drained about the end of the '90s. They made a couple nominal hits with the Surface, Xbox, and Azure, not going to discount that.
Most "gold" people trade are derivatives.
> using "untrusted" userspace software and accessing a USB webcam

Windows only requires escalation for this if you want to install that userspace software to a non-user location,* or if you want to install a driver for the webcam.

If you just want to run the program, this is not required.

A long time ago, in the pre-Vista era, when running programs as administrator was the default, many programs would not work if they were not run as administrator. This is no longer case for programs written after Vista. From Vista onwards, older programs that assume admin rights and attempt to change admin-only files get their reads and writes redirected to a VirtualStore folder within the user's profile, so that the program still works without administrative permissions.

* The exception is with some installers where the UAC installer detection kicks in and demands escalation straight away, even before you select an installation location (which could be a user-writable location). Turning this off requires using the Group Policy Editor or the Registry Editor to flip the EnableInstallerDetection registry key.
Yep, for example hearing Jinja tells you right away what the package does.
If the speedup is due to fewer open/close syscalls and space savings due to avoiding block padding, tar would achieve the same yes?
You can argue that, but there are legitimate "AI" workflows that have already been adapted in workplaces where things function well enough. I'm sure 99% of it is just slop, most companies will fail, but some things will survive, become commoditized and taken for granted in about 5 years.
The fundamental accounting equation is:

Equity = Assets - Liabilities

Borrowing (i.e. liabilities) is a way of adding leverage to your investments. This makes higher returns possible, but correspondingly higher risk of losses.

In my experience, people often do not understand the latter point. They will say it is unfair that Bob made a lot of money, but discount the risk Bob took to enable those returns. Lots of investors go bankrupt.
Hey this looks interesting!

If my setup is db-per-tenant can I push/pull all data into a single database that would have an additional 'tenant_id' column?

For sake of simplicity, let's assume all tenant dbs have the same schemas.
> AMD doesn't need to duplicate everything NVIDIA provides, they just need to duplicate the parts relevant to most of the $3T spend the market seems to be expecting.

In effect, they already have. Both AMD, Apple and a number of smaller OEMs all wrote GPU compute shaders to do "the AI inference stuff" and shipped it upstream. That's about as much as they can do without redesigning their hardware, and they've already done it.

Nvidia wins not because they have everything sorted out in software. They win because CUDA is baked into the design of every Nvidia GPU made in the past decade. The software helps, but it's so bloated at this point that only a small subset of it's functionality is ever used in production at any one point. What makes Nvidia fast and flexible is integration of compute in hardware at the SM-level. This is an architecture AMD and Apple both had the opportunity to reprise, even working together if they wanted, but chose not to. Now we're here.

I tend to steelman the idea that it was AMD and especially Apple's mistake for eschewing this vision and abandoning OpenCL. But apparently a lot of people tend to think that AMD and Apple were right despite being less efficient at both raster and compute operations.
Everyone here knows sort of any kind is an algorithm. And everyone knows when we speak of social media algorithms, we refer to the selective boosting or removal of content.

It is not helpful or necessary to point any of this out.
It includes retests from 2022.
Researchers have grown brain cells in a lab that have learned to play Pong(2022)
What you're talking about, trancending government orders, is inherently illegal. Any tech that enables it must be distributed, untrackable, and private. You're basically describing the darknet.
The 432 was far too slow to be competitive, which was a consequence of bad implementation decisions rather than the approach itself. See https://www.princeton.edu/~rblee/ELE572Papers/Fall04Readings...
True, this needs clarification that currently doesn't exist for large models where training costs heavy millions and binary artifact is both precious and malleable – unlike ordinary compilation.

Regardless if – once OSI establishes their definition(s) – Meta will choose path of adherence or not, they still deserve a paragraph of praise for what they're doing.

As a side note OSI should also recognize that in the era of giant cloud providers protection from predatory market participants is also a thing and should exist as clear licensing option. Mongo, Elastic and Redis drama could be avoided in the future if there was a clear option to protect author side sustainability without affecting open source spirit for end users.

ps. I also believe that "Open <something>" should be protected phrase similar to how "Police", "Federal", "Government" or "Organic" is protected to not mislead the public so we don't have things like "OpenAI" nonsense.
> Please make sense.

They do make sense. You're missing something critical in the argument.

> So what’s interesting is MS say that UAC isn’t a security boundary. Which is some users to admin.

This is incorrect. UAC is for already-admin users; it's not "some users to admin". The security boundary exists around standard users, not admin users.

This might not be what you like, which I totally get, but it does make sense. If you want a security boundary, don't create a user in the Administrators group.
even funnier, it looks like it's owned by wendys now, so when you zoom in it highlights wendys locations nearby
I remember that video where Mr Beast paid for cataract surgery for a few dozen people and restored their sight. Regardless of intent, that was an immediate and material benefit to many people. It’s fair to question the motives of altruists, especially those who rely on extravagant public shows to pull viewership. But more eyeballs means more ad revenue, which means the altruism experiments can continue. If this is the most efficient, targeted model for altruism, then I’ll take it.

Side note, the Mr Beast handbook is an interesting read https://www.slideshare.net/slideshow/how-to-succeed-at-mrbea...
What’s some of this disagreeable speech you’ve been shut down on.
Elsewhere you said you go where the argument takes you, but haven't responded to this one.

Please find us any professor of social sciences who is not also a "commentator". The purpose of these studies is hypothesize new viewpoints and narratives through which to understand the world. There is no unbiased or apolitical view of history.
I recently implemented a runtime for `__builtin_cpu_init()`, `__builtin_cpu_supports()`, and `__builtin_cpu_is()` for x86-64. Using these compiler intrinsics, or a higher level feature such as `[[gnu::cpu_dispatch]]`, you can write functions that behave differently on different CPUs. Fortunately the implementation isn't terribly complex. On x86, it's based around a neat `cpuid` instruction, and other ISAs have similar features.

https://github.com/Cons-Cat/libCat/blob/main/src%2Flibraries...
Could you please link the example? In the repo itself? There are quite a few. I want to be sure we get that fixed.
Well "SQLite is likely used more than all other database engines combined. Billions and billions of copies of SQLite exist in the wild."[1]

And

"SQLite has exhibited very high reliability in the field and a very low defect rate, especially considering how rapidly it is evolving. The quality of SQLite is achieved in part by careful code design and implementation. But extensive testing also plays a vital role in maintaining and improving the quality of SQLite."[2]

[1] https://www.sqlite.org/mostdeployed.html

[2] https://www.sqlite.org/testing.html#summary
Why not use the brine from desalination plants in Europe to increase salinity in the Iceland region as a way to combat AMOC collapse?
> We need to give up on the UAC/sudo/etc. style of user based privilege escalation and instead sandbox apps, not users, just like Android and iOS do.

> Those OS go out of the way preventing features that hinder usefulness of the devices.

But one isn't necessarily synonymous with the other.

Mac OS is slowly going in this direction. Their policy these days is that apps shouldn't be able to do dangerous things by default, but should have the ability to ask for any specific privilege, if and when they need it.

Instead of getting a generic "this app wants admin privileges" popup, you get a "this app wants access to the files in your Documents folder" popup. This makes a lot more sense, lets you deny specific permissions while allowing others, and actually tells the user what the app needs the privileges for.

The more dangerous the privilege, the more involved the setup process is. The most dangerous privilege of all, that of installing your own kernel extensions, which can do (almost) everything and are your final option when there's truly no API for what you need to do, is gated behind a reboot into recovery mode.

This is combined with new, more secure APIs, so that privilege escalation is often entirely unnecessary. For example, most things that were formerly accomplished via kernel drivers can now be done with sandboxed, userspace processes, and there are APIs like the photo picker, where the user picks what photos to share in a system-managed window, that require no extra privilege because the system knows that the user just clicked on a photo in the context of that app.
There's no such thing as "text changes". Only publishers lying about URLs and response bodies. This should stop.
In the case of Windows, a lot is about compatibility. You can design a different system, but then a lot of existing software that users care about won’t properly function on it anymore.

However, if you read the article, the vulnerability is enabled by a race condition in a Windows security component, so really just a bug here, even if Microsoft is trying to deflect from that.
Yah, I guess you could use WebRTC or some other way of exchanging messages now that I think about it.
"trampoline business"?

It supports nearly arbitrary imports of anything you want. How much more flexibility do you need? You could provide an `eval` function to run arbitrary code with a small amount of effort.

Is the problem that Emscripten and/or Rust haven't laid it all out on a platter?
> redefining the words

you missed the "100%" modifier in front of the words

> What is the point?

1. Clarity

2. Understanding stuff from the first principles

3. Oaktree Capital claims that there are only two asset classes, I argue that there is an infinite continuum of asset classes: from 100% owning something to 100% being owned
Dragging down is human nature. When optimizing metrics is always easier to push down than up
Focusing on the GUI applications: There have been a few GUI automation solutions over the years - since the post's software is from MS, I'll take UI Automation as an example. Works well with Win32 controls, not sure how well it works with the XAML-based toolkits.

But not all software is written with those UI frameworks. Some use different widget frameworks, some immediate GUIs, others just render a webpage and either use HTML or fully render the controls themselves. And without everybody using the same standard, the only standard we have for parsing their output is the pixels they render to.
Show HN: I Made a Free Personal Assistant API – Order an Uber W Natural Language
I was going to make a whole ChatGPT-generated post filled with emojis and junk, but I hate reading that stuff so I'll keep it short and sweet. I wanted a personal assistant that could do things for me -- I want to order an Uber using natural language. I want to buy food using natural language... etc. But I couldn't, so I made my own personal assistant that could.

I made this project totally free such that anyone can build on top of it. Wanna make a business on top of my API? Go for it. Wanna use it to make a personal home assistant? Go for it. If you want to create your own tools on top of Pal (let's say you want to enable Pal to control your Roomba), you can create your own tools in the dev portal. The only catch is that I've rate limited it to 2 requests per minute per user because I can only afford so many API credits.

I was going to charge people for this, but as a Developer, I know how frustrating it is trying to build when everything is pay walled. Go wild fellas, but please don't abuse it. I put a lot into developing this. If you'd like to support me, feel free to donate.

Anyways, check it out at https://www.meetpal.ai and navigate to the API subsection in the header.
We are not talking about "large web services", we are talking about small end users spinning up their own DNS-RR "solution".

LWS get away with it because of Anycast...

https://www.cloudflare.com/en-gb/learning/cdn/glossary/anyca...
Susegad in Goa.

https://en.m.wikipedia.org/wiki/Susegad
What they meant should have written was "tons of refined sugar". That's the chemical that makes you fat, through making your food over-calorized while not leading your body to realize you need to stop eating.

The fake lie answers that they will give might include zero calorie sweeteners because people hate the idea that you can "have your cake and eat it too" (no meta-pun intended).
One of the early proposed solutions for this was the SRV DNS record, which was similar to the MX record, but for every service, not just e-mail. With MX and SRV records, you can specify a list of servers with associated priority for clients to try. SRV also had an extra “weight” parameter to facilitate load balancing. However, SRV did not want the political fight of effectively hijacking every standard protocol to force all clients of every protocol to also check SRV records, so they specified that SRV should only be used by a client if the standard for that protocol explicitly specifies the use of SRV records. This technically prohibited HTTP clients from using SRV. Also, when the HTTP/2 (and later) HTTP standards were being written, bogus arguments from Google (and others) prevented the new HTTP protocols from specifying SRV. SRV seems to be effectively dead for new development, only used by some older standards.

The new solution for load balancing seems to be the new HTTPS and SVCB DNS records. As I understand it, they are standardized by people wanting to add extra parameters to the DNS in order to to jump-start the TLS1.3 handshake, thereby making fewer roundtrips. (The SVCB record type is the same as HTTPS, but generalized like SRV.) The HTTPS and SVCB DNS record types both have the priority parameter from the SRV and MX record types, but HTTPS/SVCB lack the weight parameter from SRV. The standards have been published, and support seem to have been done in some browsers, but not all have enabled it. We will see what browsers will actually do in the near future.
Wireless inductive charging also allows for a (more) sealed case design, which is helpful for a device that will almost certainly encounter moisture in normal use cases.

I can keep my phone somewhere dry when it's raining, I've never thought to take off my watch when it rains.
I don't think debt should be transferrable (same with intellectual property). If it is you end up with a tumor on your economy dedicated to shuffling it around in ways that prevent change and which crank out analysis like:

> The only two things that matter are these ones which we made up.

This may or may not be good advice, within its sector, but I question whether its sector is worth keeping around.
For ML it goes deeper, but unfortunately discussions about it devolve into an approximation of the Brouwer–Hilbert controversy.

If you think about it from the VC dimensionality lens, in respect to learnability and set shattering is simply a choice function it can help.

Most of us have serious cognitive dissonance with dropping the principal of the excluded middle, as Aristotle and Plato's assumptions are baked into our minds.

You can look at why ZFC asserts that some sets are inconstructable, or through how Type or Category theory differ from classic logic.

But the difference between RE and coRE using left and right in place of true and false seems to work for many.

While we can build on that choice function, significantly improving our abilities to approximate or numerical stability, the limits of that original trinity of laws of thought are still underlying.

The union of RE and coRE is the recursive set, and is where not p implys p and not not p implys p holds.

There is a reason constructivist logic, lambda calculus, and category theory are effectively the same thing.

But for most people it is a challenging path to figure out why.

As single layer perceptrons depend on linearly separable sets, and multilayer perceptrons are not convex, I personally think the constructivist path is the best way to understand the intrinsic limits despite the very real challenges with moving to a mindset that doesn't assume PEM and AC.

There are actually stronger forms of choice in that path, but they simply cannot be assumed.

More trivial examples, even with perfect training data.

An LLM will never be able to tell you unknowable unknowns like 'will it rain tomorrow' or underspecified questions like 'should I driven on the left side of the road'

But it also won't be able to reliably shatter sets for problems that aren't in R with next token prediction, especially with problems that aren't in RE, as even coRE requires 'for any' universal quantification on the right side.

A LLM model will never be total, so the above question applies but isn't sufficient to capture the problem.

While we can arbitrarily assign tokens to natural numbers, that is not unique and is a forgetful functor, which is why compression is considered equivalent to the set shattering I used above for learnability.

The above questions framing with just addition and with an assumption of finite precision is why there is a disconnect for some people.
Sure, the Wien bridge oscillator. But then, oddly enough, even sustained oscillations need to be controlled in their amplitude, and the Wien Bridge has a secondary feedback loop for that purpose -- the temperature dependent resistance of a light bulb.
Sudha Car Museum
<https://www.w3.org/annotation/>
I don't think so. I'm pretty sure sqlite relies on fsync barriers, something block devices don't have.
The type of plow used then is almost never used today. they used to turn the soil over butting top soil (aerobic stuff) under lower layers (anerobit stuff). Now they break up compaction but don't turn the soil over.
Just to add, there are tools in C/C++ that addresses some of these issues. For instance, I use meson as much as I could, and their project is really makes it smoother. I feel like it should have been used more in the ecosystem.