skysight-inc/HackerNews huggingface dataset:
you would be very surprised how difficult avionics are from even a fundamental level.

I'll provide a relatively simple example.

Just even attempting to design a starfox game clone where the ship goes towards the mouse cursor using euler angles will almost immediately result in gimbol lock and your starfighter locking up tighter than unlubricated car engine going 100mph and unable to move. [0]

The standard solution in games(or at least what I used) has been to use quaternions [1] (Hamilton defined a quaternion as the quotient of two directed lines in a three-dimensional space,[3] or, equivalently, as the quotient of two vectors.) So you essentially dump your 3D coordinate into the 4D quaternion coordinate, apply your matrix rotations, then convert back to 3D space and apply your rotations/transforms.

This was literally just to get my little space ship to go where my mouse cursor was on the screen without it locking up.

So... yeah, I cannot even begin to imagine the complexity of what a Boeing 757 (let alone a 787) is doing under the hood to deal with reality and not causing it to brick up and fall out of the sky.

[0] https://math.stackexchange.com/questions/8980/euler-angles-a...
[1] https://en.wikipedia.org/wiki/Quaternion
The vehicle in the video in the linked article appears to be a MG ZS EV. The wheels are distinctive.
Looks like an MG ZS to me.
I've scaled 300M rows in just one of many similarly sized tables to 1M users... in 2007... on a single box with spinning rust in it. Heck, my laptop could handle 100x the production load.

It amazes me that my comment (while admittedly flippant) got voted down.

It really is true that your phone can update a 50M row table about 10K times per second!

That people are incredulous of this is in itself a stunning admission that developers these days don't have the faintest idea what computers can or cannot actually do.

Just run the numbers: 50M rows with a generous 1 KB per row is 50 GB. My iPhone has 1TB of flash storage that has a random access latency of something like 50 microseconds, which equates to 200K IOPS. An ordinary NVMe laptop SSD can now do 2M. Writing even 10K random locations every second is well within mobile device capability, with 50% headroom to "scale". At 1 KB per row, this is just 10 MB/s, which is hilariously low compared to the device peak throughput of easily a few GB/s.
Not really. If someone logins as user A on the machine, and caddy runs as user B, then unless A has sudo access, A cannot modify caddy. But with this admin HTTP endpoint, user A now can arbitrarily modify caddy.
Tor can tunnel any protocol, including IPFS. The normal IPFS network and the Tor IPFS network can't really interface without nodes bridging the gap by speaking both protocols. There are a few PoCs out there for adding Tor support to IPFS.

Tor2web makes the claims a little suspicious, but technically speaking the system could work.

Now that Veilid is out (https://veilid.com/), that seems like a much better base to build a messenger on top of, but it probably doesn't support the IPFS features this thing requires. Maybe a v2 can use it to get the privacy features it needs.
Many forms of life may be detectable using telescopes. A jungle planet will look different in many ways than an ice world.l, ways that are detectable. A billion LED street lamps would similarly make the night side detectable.
If it's anything like our gas giant, the radiation of the satellites will neutralize all life on the surface.

https://en.wikipedia.org/wiki/Colonization_of_Europa#:~:text....
wolfSSL is an excellent clean implementation.

LibreSSL is the drop-in replacement for openssl that everybody should have embraced back when heartbleed happened.
Funny you ask, I was wondering the same thing last night so I went through the rust-for-linux mailing list archive. This thread is pretty telling:

https://lore.kernel.org/rust-for-linux/bddea099-4468-4f96-2e...

https://lore.kernel.org/rust-for-linux/c61a60ef-fa9d-44ea-98...

The above thread is really strange that they picked such a niche thing in networking to contribute to, as sockets don't have many uses within the kernel itself other than NFS or dhcp or stuff like that. They should have aimed to add things to the QoS layer, qdisc, classifier, whatever, there's tens of those and you can easily add another. Start small.

The problem really is that the people who want to see Rust in the linux kernel have next to no linux kernel background and have a poor understanding of how Linux works and how things are generally done.

Also the people who contribute big things to the linux kernel usually have a clear business case behind them and a big company paying them to work on it full time.

For example I could imagine Microsoft eventually contributing in this regard, say they want some more Hyper-V virtual hardware drivers in Linux and they decided to do that in Rust. They've been lately using Rust in the Windows kernel so it's not that unrealistic to think it may happen.

A filesystem written in Rust would be cool... but it's probably going to have to be a new one rather than a rewrite, I can't imagine people going through the trouble of rewriting btrfs in Rust. And big names like Facebook could actually back that effort.

I really love using Rust for middleware things, however right now I can't convince myself to use it on low level things like OSes or microcontrollers since it seems to be a lot of trouble with getting Rust to play nice with FreeRTOS for example, and there seems to be no production ready rtos written in Rust either.
> I think my <initial><last name>@<well-known provider> actually looks more professional on my CV

It doesn't. It looks amateurish and unofficial.
Pocket Hansei – A new way to learn
Pocket Hansei is your Personal AI Assistant that offers instant answers by connecting you to trusted, well-sourced topics such as renowned books, research papers, reliable articles, and trending topics. Simply ask your questions and receive well-researched answers.
But you realize that getting all possible apps to look the same and have same behavior is very hard, you have GTK2, GTK3, GTK4 with their limited customization, then you have Qt apps, KDE apps, Java with their different GUI frameworks, node apps, Wine apps, other smaller toolkits used in Python etc.

But as you admit in Linux you have infinite more power to attempt setting up a global menu, but this feature is not something a mainstream distro offers by default so IMO is not a fair complaint.
Most of the times that's because we find it hard to imagine how it would "feel" being ourselves entangled with the thing we observe. Accepting that there is effectively a copy of you that is effectively fully casually disconnected from you goes strongly against our instinct that wants us to be "us" unique and objectively existing
It is probably too early for standardised EV batteries, because we still don't know if there are innovations that will end up being useful but which won't fit whatever standard you come up with.
It is bad taste, unprofessional.

Taints the pool with the vibe of "We can do this; we will do this and you schmucks can't do anything about it because it's in the EULA".

Regardless to how harmless it is. It's still an unprofessional quality to implement such and then deny the ability to disable it.

Same example as if when you honked your cars horn it tooted the car model. You'd be annoyed right?

Sure, its harmless because how often do you use your car horn but you expect a car horn to horn not advertise the model your driving.
A rewrite might simply make it more resilient through changes in the base architecture. However, I know nothing about Linux's bluetooth stack and I assume that it's probably taking into account a lot of those glitches already.
> "aren't people who poorly break up service boundaries going to go do regardless if the interface is a network endpoint or a function call/dependency injected class?"

Today there are several tools we can use that enforces boundaries in a monolith (Spring Modulith for example). If the project uses one of these tools, it is harder to accidentally cross boundaries and you get many of the same benefits as you get with a micro service.

The big advantage is that if you find out that you made a mistake, your only dependencies are within the same service and is easier to refactor. In a micro service oriented architecture, changes might impact several services and teams that needs to be coordinated. I'm not saying that refactoring a monolith can't be time consuming, but you have at least a better control of the flow of data between modules.
Do you want to be livestock? (Most animal mass is livestock).

We'd be lucky to be treated like bugs.
I don't agree that you need feature parity to be an alternative though. If your use-case is only text chat and file sharing, then it is an alternative.

LibreOffice is still an alternative of Microsoft Office without having all the features. Firefox is an alternative of Chrome without WebHID or Web Bluetooth.
I had the same experience at university.

Then, say 5 years later, it "kicked in" and I kept wondering "why isn't this implemented in prolog?" at many, many points.
Seems strange to me too, can't think of anything that would need it functionality wise that can't be done in less, let's say, problematic, dependencies.

If you want to run on Tor, fine, just run Tor.
Would like to hear more about using Android for everything!
IPFS is a resource hog. Not sure if it's just the implementation or if it's because of architectural limitations, but it gobbles up CPU and RAM much more than you'd expect it to. I shut down my self-hosted IPFS server because it kept pegging a CPU core doing what seemed like nothing (no new pins, barely any network traffic, just sitting there).
Perhaps we should write it all to optical disk and keep a few readers in faraday cages.
"""
Time dilation is the difference in elapsed time as measured by two clocks, either due to a relative velocity between them (special relativity) or due to a difference in gravitational potential between their locations (general relativity). When unspecified, "time dilation" usually refers to the effect due to velocity.
"""

https://en.wikipedia.org/wiki/Time_dilation
Can you dive into this a little more? I think I understand what you're saying but it's a very interesting idea and I'd love to understand it more if you don't mind. :)
Presumably this was just downloading the source file, not the linked images and any other heavier aspects of the page.
>Also pretty comical that Google's Project Zero policy is to release details when a public exploit is known to exist, yet the details are kept under wraps when their own software is vulnerable

That is not true please stop spreading misinformation.
I get that. I was trying to describe a small path from monolith to microservice without inventing yet another student and teacher database. But the even the step you mention matters. going to a third party service is very similar to reaching out to your own internal service. Make it a "customer" service.

Is the pain in microservices (or APIs and mTLS) or is the pain in managing a team that now has to do customer stuff only ? or email stuff only?
> Which communication methods leak no metadata?

All leak something, but there are differences in what and how much.

> If two people are communicating, the message always needs to know where it's going and in most cases where it's coming from.

Yes, but in this case it'd be actually better to use something like Signal. You want something that's plausibly used often, is always encrypted, and is used for random chit-chat all the time, so that it's hard to tell if anything odd is going on from the outside.

GPG just screams "an important conversation is happening"

> Not encrypting the email subject is an implementation detail really.

And it's still unfixed, despite being a serious problem (it's easy to slip up and put something interesting in the subject).
Criticism can be helpful indeed; it's the form that triggers this kind of response. Let's try this one more time:

> Very impressive project! It's neat that you can get this far without relying on any central servers at all. Personally though, I'm missing a couple more features – this only has textual chat and file sharing, while Discord or Slack have a lot more niche features. Achieving feature parity is a prerequisite for getting any user base nowadays, so I hope it is something team would account for before the 1.0 launch :-)
If we detected their planet, and they're significantly more advanced than us, then it follows that they know a lot about our planet already.
.....

How do you propose getting a probe to something 120 light years away and getting an answer within a human lifetime, unless you're going for a ride on the probe? Do you have some new physics?
Disagreed.

The "MiFi" is one more thing you need to keep charged and have to put up with shitty firmware.

Region locking isn't a big concern - as far as I know no iPhones are region-locked (the appropriate one might perform better in certain areas, but nobody is outright locking you out?), and Macbooks are already region-specific anyway based on keyboard layouts.
tangential topic: does hail affect panels in any way? is there a way to protect the panels against it? (i mean apart from insurance)
OpenSSL 3 seems to be largely compatible (it's a much easier upgrade than previous big ones) but the part of this that breaks clients is odd.

If your peer closes the connection without sending close_notify, you get an unexpected EOF; 1.1.1 ignored this, 3 passes the error to the client, which needs to set SSL_OP_IGNORE_UNEXPECTED_EOF to recover the old behaviour - but this is only safe as long as the client checks for truncation attacks. This peer behaviour seems to be pretty common for google servers, so if you use google logins or APIs it'll trip you up (from doing these upgrades at work, almost all of the errors I saw were talking to google)

What's odd to me is most of the patches I saw for this were just setting that flag, and not doing anything about truncation attacks? I'm sure this will bite us all somewhere down the line.

Anyway, some notes for admins of old systems who got to this too late:

It was noticeable that this patch got backported into ppa's that maintain old/deprecated versions of some software. eg the ondrej php ppa has this backported to EOL'd versions of php. But, this is not the case for the python deadsnakes ppa - I didn't look at python 3.8, but 3.9 was fixed at source, and it hasn't been backported to the (EOL'd) 3.7 anywhere. You should be off 3.7 anyway, but if you're not, it's now urgent.

Another notable backport is openresty. If you're using nginx with lua and oauth, it's a popular choice; but lags the latest nginx by a long way. The latest version is 1.21.4.2 which means it's based on nginx 1.21; but nginx is on 1.25 and nginx only released with openssl 3 support in 1.22. If you proxy to https servers, this is a concern. However, digging I found the openssl3 support was backported to openresty a few months ago, so the _current_ version does work without falling over.
service oriented architecture is a disaster even in large companies. without a monolithic database and normalized schemas you always end up with a bespoke ad-hoc never-consistent data store. data and results are unverifiable and continually incorrect and the performance is abysmal.

a really large company can waste hundreds of millions of dollars papering over the inherent deficiencies of the architecture but it is an exercise in building additional stories on a house where the ground floor is made out of cardboard that happens to be on fire. soa was created purely for business organization needs. any technical justifications are post hoc rationalization. from a technical perspective it is pure trash.

a much better architecture is to keep services but have them all built on top of a single monolithic db. at scale the monolithic db can be a facade and then you disaggregate the database into horizontally scalable services so that you can scale your monolithic db facade to whatever you need.
That's another really good point, even if it's less common these days to see this type of shared machine.
Seems to be reported by Apple and looks a lot like this security update: https://support.apple.com/en-us/HT213906
Caddy was the first to default to https.. because it was new. Nothing special about that.
That's CVEs in general it seems

"if you set input parameters of curl to absolute nonsense, something bad will happen" 9.8/10

https://daniel.haxx.se/blog/2023/08/26/cve-2020-19909-is-eve...

https://daniel.haxx.se/blog/2023/09/05/bogus-cve-follow-ups/
I don't think we're talking about that kind of software, though. This big was in code that needs to parse a line defined by named points and then clip the line to the portion in the UK. Not trivial, but I can imagine writing that myself.

But regardless the more complex the code the worse idea it is to maintain three parallel implementations, if you won't/can't afford to do it properly
You're right, after looking it up I found that the time period for actively exploited bugs is seven days. I must've misremembered.
The tweet says "arxiv is a cancer". It's obviously reasonable evidence that some people don't like arxiv. You are splitting hairs.
How to Improve Rails Caching with Brotli Compression
Fix OOB write in BuildHuffmanTable

https://github.com/webmproject/libwebp/commit/902bc919033134...
That "obvious" distribution is actually the worst, three points are in a line so have area of zero.
Show HN: I made a Twitter account which shows news in chronological order
A while ago, I built a site to display news sources (articles, YouTube, tweets) chronologically. I felt social media, as a news source, often provides a skewed view of reality. Scattered feeds and out-of-order articles confuse our perspective.

Despite my efforts, the website didn’t gain traction.

Now, I've pivoted to a similar idea with [x.com](https://www.x.com). Check out [@x_hindsite on Twitter](https://twitter.com/x_hindsite). Each top-level tweet represents a news event, with replies giving sources in order.

I'm considering splitting it into multiple accounts due to the vastness of topics.

I'd love to hear your feedback on this approach and any reflections you might have.
> Also pretty comical that Google's Project Zero policy is to release details when a public exploit is known to exist, yet the details are kept under wraps when their own software is vulnerable.

Project Zero treats Google like any other vendor (much to the annoyance of other internal teams).
p2k23 Hackathon Report: Chasing memory corruptions
I'd take a Delphi/Lazarus UI over most Electron apps.
They started fast, took little RAM or disk space, used very little CPU, had fast response times, supported standard UI conventions.

Today, we have endless options. But most are not as comprehensive as what Delphi is/was. I'd rather write a UI in Delphi/Lazarus (LCL/VCL/FireMonkey) than any other UI framework even today. The trouble is, I don't want to use it for anything else other than the UI.

UI design and data binding should be a simple mouse driven activity. That's adequate for most designs. Why do we need code? It's like expecting everyone to use LaTeX than RTF. Sure, it's more flexible, but an overkill.

I wish there are more integrations with modern languages than 20 types of grids with overlapping functionality. I'd write my code in a language appropriate for the task and just use Lazarus for the UI. Currently, Python (Python4Delphi) seems to be the only one with components for that, but even that needs more polish (and largely stagnant for over 20 years). Most I can do is do shared libraries and call in.
DO use a your own domain. Advantages far outweigh the disadvantages.
Instead of being at the mercy of whatever email provider you choose, you're free to move your domain where ever you want, without updating "a million" senders.

DO NOT host your own email server though. A couple of decades ago it made perfect sense to do so, but these days it's simply not worth the trouble.
Instead use Google/Outlook/Apple/Whatever to host your custom domain and use their offerings with your custom domain.

My personal domain is hosted by mxroute.com, which has served me well for a lot of years by now. Unlimited email accounts and the only restriction is storage, which i can upgrade. Very little downtime (none i've noticed).

All that's left is to make a backup with regular intervals, which i to do a small local machine using imapsync, which then in turn makes backups of the emails (and regular data) to a local drive and a cloud backup.
The engineering controls don't independently make systems safe, they make things more reliable and cost-effective, and hopefully reduce the number of times the process controls kick in.

The process controls do however independently make things safe.

The reason for this is that there are 'unknown unknowns'—we accept that our knowledge and skills are imperfect, and there may be failures that occur which could have been eliminated with the proper engineering controls, but we, as imperfect beings and organisations, did not implement the engineering controls because we did not identify this possible failure mode.

There are also known errors, where the cost of implementing engineering controls may simply outweigh the benefits when adequate process controls are in place.
Within Google Chrome, WebP images are decoded by the renderer, and therefore any exploit can only get renderer code execution - which is inside a sandbox.

Since the renderer is very complex, there are lots of exploits discovered each year for it. However, when someone manages to get code execution in a renderer they don't get much more access than a webpage would normally get. Specifically, they can't see or leave files on the filesystem of your machine, nor even read cookies for other domains.
> Upgrading GPUs out of cycle seems like it might make sense but you probably should just use a desktop PC for anything using a GPU.

There are external GPU enclosures, so no need for a desktop, even for that case.
I have always wondered about this rule.

It is tautologicallly true; if no such C or Fortran programs exist, the law stands true with a level of complexity above anything written.

But otherwise... how does it hold true? Via some ad hoc string/config parsing logic?
The vast majority doesn't need to deal with FIPS garbage.

Those can do can make their own security holes for it.