skysight-inc/HackerNews huggingface dataset:
It's not weird, is typical Apple playbook.

Year 0 of cool thing - Nothing and silence

Year 1-3 of cool thing - Maybe, if you're lucky, a mention on some hardware thing related to it

Year 3-5 of cool thing - Hardware or software launches that uses thing, no mentions of this besides the earlier one if any.

Year 5-6 of cool thing - Next part of hardware or software launches that uses previous launch, no mentions of this besides the earlier one if any.

Obviously, the time-frames differ, but that's generally how they do things.
I always figured it was a play on King Kong. Right down to the trope of the giant gorilla absconding with the girl.
If you don't have the C extension then you can't run off the shelf Linux distros such as Fedora, Debian, Ubuntu, Arch and are limited to what you compile yourself e.g. Buildroot / Yocto.

However the actual academic paper says it's RV64G, no C.
> Target audience is a big factor too, I think the article failed to emphasize this. And, secondly, the nature of what is being documented.

Right, I'd say screenshots are crucial for certain kinds of documentation and terribly amateurish for others. A guide walking you through a user journey in a UI should definitely have screenshots.

But there should be "real" documentation for things like APIs - if the only kind of documentation that exists for an API is guides with screenshots, you end up with a bunch of useless "hello world + a feature" documentation that doesn't help you understand the big picture, or how features/options interact.
Working in security on the operating side (albeit not in Poland):

No, pretty much just the manufacturer loses. Short term the operator loses, but I'm sure that the courts will award damages.

For me, this incident is a welcome argument with which I can tighten the screws on manufacturers in the next round of train buying (at minimum, they will agree to heavy contractual fines for anything like this; at best I get full source code for every train).

For too long the only priority in OT was safety (fine in the 80ies, but the second you integrate an IP stack that posture doesn't work anymore). This has been changing in the industry thanks to EU-regulation; this incident will accelerate the change.
The idea that today is an age of shopping as entertainment is kinda goofy. I mean, sure, but wasn’t that also true 30 years ago? The mall era? It seems that articles that reference Cory Doctrow’s enshittification are likely to have a rosy view of the past and quality of goods in the past.

Tangentially, I do a lot of the blah blah blah, repair my clothes (it’s mostly easy, but sometimes hard) buy used clothing, and try to buy from companies with transparent supply chains. SHEIN has low quality goods and likely poor labor practices, but spending 10x isn’t a guarantee of transparent supply chains and good labor practices. Some expensive brands are not better. You gotta look a little.
Wondering if I should zip all the pics i save on my paid g drive and uploading to s3.
>I just don't think I would then proceed to believe that what they described was a reality on the other side of that horizon.

Does the physicist believe that? If we get past popular culture which mangles modern science, the physicists are throwing around lots of random "what if" ideas and seeing where they go. If one is good, their idea is popular enough other physicists spend time thinking about if. If one gets lucky, then someone comes up with a way to test the theory (using the layman version of theory). If one gets REALLY lucky, the test doesn't lead to it being rejected.

Sometimes there an be a long gap between when a physicist first thinks of a theory and someone finds a way to test it. Some ideas are still untestable, but may be interesting enough that physicists will still try to dive deeper and see where the idea goes.

But do they believe it is the truth? While some might, I think most keep a sort "what if, maybe" vibe, even on the theories they spend time looking into. They are invested, but that doesn't mean the believe it is the truth, only that it is the model worth spending their time investigating.

One key idea to consider, science does not give truth, it gives the model that best fits all known data without any claim to if that model is true or false.
I never thought such a hyperfocused channel would be this fascinating!
Scaling vulnerability management across services and more than 150
Everything gets out in the end. My Italian hometown had a "golden age" of silk manufacturing for a while, thanks to bugs smuggled out of China. It lasted for a couple of decades and then they were again smuggled out to other Italian towns. And then of course you have the nuclear shenanigans.

If European countries wanted the tech bad enough, they would find ways to get it. The problem is not the know-how but the massive investments needed to productize it.
It is 64bit. Specs here: https://www.t-head.cn/product/c910?lang=en
I could add more but on a newish local stack I was trying: I spent a good amount of hours on duckdb this week to process personal data from data dumps (social networks, etc) and now I'm back to the combo of postgresql in containers + sqlite.

After the initial imports and some massaging with queries that felt awesome, I found hard to step-up the game building the relationships I wanted. The last stroke before switching was the lack of managing foreign keys without recreating entire tables again. I can go over other examples.

It can be done, but it just takes you out of the flow when you're analyzing the data + cleaning it, specially because I know that I can do with psql and sqlite in a blink of an eye.

Since many etl tools don't care about the target database being these old and trusty fellas, I felt losing a lot of time just to get rid of a postgres install that is right now consuming only 200 mb of ram on a docker/podman container. Or working around some sqlite ingestion issues with simple notebooks + pandas/polars/etc.

in my pov it seems a shaky ground for an entire new stack

I appreciate duckdb taking me out of the comfort zone tho.
> factually wrong claim

Yep. Hamas pretty much pegasus'd Broda's iPhone and sent out those tweets.
> prediction doesn't and can't contain information (in the technical sense) from the future, since by definition it's based only on what we know in the present

In the technical sense the future _is_ driven purely by the information available in the present. It’s a function of t-1.

The only reason future should be different from prediction is if the set of information available to the predictor about the present is different from the actual set of information about the present.
I honestly don’t think it would have made a difference - he was going to drill it anyway after I stopped him, I had to ask him to please use the respirator.

In the commercial case we had also very clearly told them that it was asbestos containing but there was some miscommunication to the workers, so they just drilled all these holes…

Anyway, at the end of the day, while there are rules for commercial buildings to have asbestos registers, I wouldn’t expect every homeowner to know what every part of their house is made of, but at the same time, basically every building built for a period of more than 60 years in Australia contains (or contained) asbestos containing materials - so it’s a pretty scary lack of training or ignoring of the risks for somebody working in the building industry to not take even basic precautions when at least 1/3 or so of the houses these people are working in contains asbestos. For the solar guys, the eaves are the most likely place for it to exist, because even when houses have been pretty extensively renovated inside and had a lot of the AC sheeting removed indoors (as mine has), or might not have had asbestos sheeting inside originally (plaster was more expensive, so a more premium finish), it’s one part that was very likely to have still been AC sheeting (since it was mould resistant) and much less likely to have been replaced with non-asbestos fibreboard in the meantime.
It seems it must be interpretation of the article rather than the position held by academia. Most of our earliest known cities had walls, suggesting that defensive fortifications were essentially a requirement for any large concentration of resources (cities) to exist. And we also know that wooden palisades were a common feature amongst North American indigenous villages, indicating that hunter gather societies thought a lot about defense.
Agreed. Twitter used to be terrible and now it's actually gotten pretty good as I appreciate having different viewpoints on a single platform. You do have to block the conspiracy spam but I don't see how that's any different than having to block the fanatically woke posts that used to crowd the conversation.
OpenAI Leaked GPT-4.5
I somehow do not think the 'hallucination' (or confabulation) problem, as defined by common people should be theoretically hard to solve. It may need a lot more computations though.

We start with quasi-random initialization of network weights. The weights change under training based on actual data (assumed truthful), but some level of randomization is bound to remain in the network. There would be some weights which settle with low error margins, while some which would have wide error margins. Wider error margins are indicative or higher initial randomness remaining and lesser impact of the training data.

Now when a query comes for which the network has not seen enough baking from the training data, the network will keep producing tokens based on weights that have a larger margin. And then, as others have noted, once it picks a wrong token, it will likely keep on the erroneous path. We could, in theory, however, maintain metadata around how each weight changed, and use that to foresee how likely would the network confabulate.
Wanted to play with typesense.

The tech behind building something like this isn't hard. Marketing and traffic is. No point in monetizing with no users.
Hi! We are developing a tablet-based Math tutoring app that helps adults do a better job of tutoring K-4 kids in real time by leveraging multi-modal AI. We are submitting an R&D proposal to IES in mid-January for work that would start around June. We are looking for people who can help us with backend data pipelines. If you are interested or know some who is, please email me at markroselewis@gmail.com.

Have a great day!
I have a website that has a sloth on it, with blocky gradients. Does that invoke trust? https://mitta.ai

Joking aside, anything you use with AI should have a clear privacy and terms of use.
Seems they've released a bunch already?

Image-to-text models, filtered by "Microsoft": https://huggingface.co/models?pipeline_tag=image-to-text&sor...
https://github.com/LedgerHQ/connect-kit/issues/29

^ the actual github issue.
So sign your UUIDs and combine them into “$UUID:$HASH” strings for the same benefit. Or a more structured JWT-like payload that still verifies auth against the DB (as opposed to carrying authorization within the token).

No need to reinvision the rest of the auth flow if you just want to add hashing to reduce DB load.
I think your statements are really opaque in this conversation. It took until this post here before I had a clue what and what direction you were even going. Your other posts could have been read to indicate exactly the opposite of the one I'm responding to.
Any examples of projects that do it like that?
This is on the general topic of right to repair and freedom of fixing and so forth so naturally HN hates the train company.

On the other hand, trains that refuse to start don't immediately kill everyone on board, and trains that have fall off the tracks do tend to kill people. So when a train fails and people are dead, and people go in search of who is responsible, it seems decently likely that ambiguity between the third party repair shop and the company responsible for the train is a problem.

Further, if your company is financially liable for a product failure, and another company is not, that second company can totally fix it more cheaply than you can. As it's not their liability.

There should be an opt out system - something where the train operator contacts the train supplier and says "we want to use this cheaper repair shop, and it's now our problem when the budget train fix kills people" - that seems totally legitimate to me.

Or to bring it closer to home, say one of us breaks into our tesla to exercise our God given right to change the software stack, and then it kills the driver and various people around it, to what extent is that Tesla's fault? Say Tesla made all reasonable steps they could take to detect third party mods and refuse to start the car, do we hate them too?
Could you perhaps quote exactly what statement I made which is malformed?

In any case the picture of time and space switching places inside a black hole is at best a rather deceptive simplification. The most important thing about the event horizon is that locally (i.e. to one falling in to it) nothing at all interesting happens at the event horizon.

Edit: The "swapping" you are referring to is an artifact of coordinate systems, not of space-time. Thinking something wild happens to space-time as you pass through the event horizon is the same as thinking that something wild happens to the Earth's geometry as you reach the north pole. Sure at the north pole there is no longer any meaningful direction other than "south" but thats an artefact of the coordinate system you're using, the pole is a normal point just like any other.
JWTs are nice because you can skip a DB call completely if it doesn’t validate, furthermore it provides a very convenient method for embedding a tiny bit of date (role and/or tenant id) for use both on the back and frontend.

For myself I use short lived JWTs with a refresh token that I can invalidate. Yes, this means if there is a breach you have wait the refresh period but honestly I’ve never seen someone move faster than my refresh time to invalidate a session (on the rare cases I’ve ever seen it done professionally) so I’m not very concerned about the potential hole. It’s just not in my threat model and I have to say I question some people who say it’s in theirs.

I’m not saying there isn’t a use-case for immediate revocation but that a lot of people who talk about it don’t actually need it and/or have no good method for using it. Unless you have automated systems that revoke a token then I fail to see how 5 more minutes after a request worms its way through support is the end of the world. The damage is either already done or 5 more minutes isn’t going to be the end of the world (again, by this point it’s been going on for hours if not days/weeks).

Even if I wanted immediate revocations I’d just use an ID in a JWT and compare against a list since I still find the benefits from having role/tenant in the auth token very valuable. Then all I need is something like memcached or DynamoDB to hold a TTY’d ID for 5-ish minutes. But like I said, my threat model doesn’t require that.
> so what is preventing these companies from forcing the uber/delieroo drivers to be freelance solo classification?

Right now nothing, that's why they want to change it.

You just have to set the rules. For example when I get an uber I often check the driver profile, someone with 27 000 trips in 3 years isn't a gig worker. When you have a student delivering food 3 hours a week to pay his friday night bar trip it's completely different. Right now both are in the same category
We’re discussing the notion of ‘environmentally clean’ energy sources. Your red herring of known dirty energy sources is the “FUD”.

Nuclear is not environmentally clean. I remain mildly amazed that this is debate worthy.
If I'm not mistaken, this will be the first commonly-available MoE model available for the general public?
> could just as easily have a "Follow us on the Fediverse" link pointing straight to their AP address

Ah! I do agree there. I mistook the op I replied to. I was assuming they were referring to the website itself being the source of content and discussion, not simply a referral to AP/Threads/X/whatever.
I think we just don’t know, really.

It could be replacement of some sort - car usage has gone up continuously, and we inhale a lot of exhaust in cities. Maybe it was exhaust the whole time?

I’d also be interested to see the data you’re referencing on lung cancer rates in non-smokers.
That's not science, that's making assertions and yelling 'fallacy!' at other people
> There's an 80GB GPU out there that costs about six times as much as an equivalent Mac with 96 GB of shared RAM.

Those are not equivalent in speed. macs RAM are much slower than these GPUs.
Only partially. Building a 100 story high rise is only reasonable if property values are very high - there is presumably high demand for that area and thus density, and the high values mean you have to spread the cost across a lot of people to make it affordable for anyone.

Even in very low demand small towns though there is demand for some density - a 3 story apartment will often exist in those towns and have no problem renting to people who want/need to live in the small town but don't want a single family for whatever reason. These smaller low rise buildings are the cheapest housing possible - they are small enough that they don't need expensive elevators and the like, though of course they don't make sense in high property value areas.

Which is to say that even on the low end of property value density can be justified to some extent.
Yup I was about to write something about how I quite literally clone & grep code bases after GitHub search fails probably half the time.
I have a friend that runs a business, where he hires Polish developers to do his coding.

He absolutely raves about them. It sounds like he's got some good coders.
Is it possible that the walls around Jericho were there to keep out wild animals?
Idea to App Store in 7 days
Last week I started a new project to scratch an itch. Something simple but useful. And in just 7 days I launched a web and iOS app to the App Store. This is the story of Daily Log, and Ruby on Rails and Turbo Native iOS app.
Some settings changes happen are effected via undocumented registry changes that you have to make directly, and can be a pain to track down.

Sometimes you can do something via PowerShell, but only by using PowerShell to directly call some 'raw' .NET API.

Sometimes there's a native CLI utility that'll do what you want, but it's one of the DOS-like, pre-PowerShell commands, and the PowerShell equivalent is missing or unsuitable.

Even when a native PowerShell API exists, it can be difficult to find the documentation for it because Windows culture is to document GUI solutions first (and often GUI solutions only).

Try as one might, Windows remains a platform inherently hostile to automation. Doing automation and/or configuration management on Windows sucks.
Of course, the visual reference can help clarify things that text alone can't explain. For example, take a simple task like 'fill in these fields in the config file'.

For someone with software development experience, it's pretty obvious what the needed format might be there, whether it's a JSON file, PHP file or in any other language you can think of.

But a new user might not know that. They might not know what's valid in a JSON structure, or that leaving out the quotes in a PHP variable's value will break things (especially if there's a space in the value they enter!)

Pairing somewhat detailed text instructions with a screenshot or diagram can help avoid this, and make it obvious how the information should be provided.

You could also use video footage along with the screenshots too if you have the time for it. It's a lot more work for sure, and I understand why most documentation creators don't do it, but it helps shows steps you might have forgotten while writing the docs, since it's very easy to leave info out or skip over things because they're like second nature to you.

Honestly, all three formats being available is probably the ideal here, but having at least the screenshots will make things significantly easier to understand at least.
I crushed on her then before it was cool... and then uncool

Regardless, I knew she'd be "a thing" when I saw that movie
Stereogram Tetris
LinkedIn shelved plan to migrate to Microsoft Azure cloud
Out of curiosity, what makes people prefer desktop apps for mail over just visiting the browser version? The idea of downloading a desktop app for something I can do in the browser makes no sense to me. At least on mobile, the ergonomics of apps tend to make the experience better than the mobile-web version.
kdrive is this alternative X server, I suspect: https://www.irif.fr/~jch/software/kdrive.html
My thinking from a digital system point of view is that double entry book keeping is the beautiful concept. This concept can easily be expressed using computers but it loses its beauty at each abstraction layer.

The beauty is lost because the user is using a device for double entry book keeping but many other back ground tasks could fail that are not directly related to the task of book keeping.

The user is now faced with needing to understand their goal book keeping plus anything that makes the book keeping device function.

I think a digital aesthetic can be found by creating simple digital devices that are highly specialized but would need something similar to phone to add all the fantastic features that a network device provides.

Imagine how great cars would be with physical buttons but an optional screen to mirror one's phone like device.

Finally I'm actively working on this idea with an 8 unit mixed use building.
I'm trying to make it as sophisticated as possible with very simple circuits that don't relay on the internet to function.

The idea is that the industry is overly focused on the internet and completely ignoring all the very simple things that can be done digital devices. I think by establishing a digital aesthetic we can start to say something simple that requires the internet or an operating system is ugly.
It should be obvious what "evolutionist" means considering that it's explained in the sentence you quoted starting immediately after the word. If anything, it seems like you might actually want creationists to own the word. Crazy warning, indeed.
Immediate Reaction: Um, yes? Only the naive, self-deluding, and techno-utopians would have expected otherwise. Vs. an experienced teller from a well-run 1950's podunk bank could tell you that no security technology is worth crap if the managers don't actually care, or are crooked themselves.
It's easily lost that development best practices are a function of scale.

What's absolutely necessary to get anything done in a large mature project with many developers and a sprawling code base may be cumbersome in a small single-developer project.
Misleading title: Xorg may be removed from rhel10

So this may not be a big deal
> What is the BOM for the challenger tank - how many chips in there that are made by whom

In today's world, it would seem more sensible to just stockpile enough of all the components for 5-7 years of tank production, knowing that if your enemy tries any evil tricks then you have half a decade to figure out how to redesign or make the components yourself.

Keep a close eye on anything that looks like an antenna and it isn't so bad having the enemy backdooring your chips either.
This is great info. Can you elaborate or point to a link on the distinction between paging and swapping? I’ve always treated them as synonyms but clearly there are some differences on earlier systems.
SunOS and VMS were two of the most common workstation/minicomputer-class OSes out there, and rather less exotic than IRIX.

I'm old enough that my college-freshman "intro to computers" and Fortran classes were taught on a CDC Cyber running NOS.
No sarcasm, just in total disagreement with the (initial/apparent) HN consensus. I've put a top level comment which is hopefully clearer.
thank you, this is interesting and a great point for further research