Here is the ATC audio between the Tower and PAT-25. Helos that transition DCA's airspace use a separate VHF frequency from traffic landing and departing, but talk to the same tower controller.
* At 5:41 - 5342 is given instructions for circling to 33.
* At 6:45 - PAT-25 reports Memorial
* At 7:06 - tower gives PAT-25 traffic advisory about 5342 and PAT-25 reports traffic in sight and requests visual separation
* At 8:12 - tower asks PAT-25 if they have the CRJ in sight and tells him to pass behind the CRJ. PAT-25 again reports traffic in sight and again requests visual separation.
* At 8:28 - crash occurs, exclamations, go arounds issued
I tried this (among a bunch of others) about a year ago and landed on Gonic[1] for the server and Supersonic[2] on PC and Amperfy[3] on mobile. Yes it's a few different tools to maintain (plus beets etc), but it's the ideal set of features etc for me.
Self-hosting has been fun and I've started experimenting with local LLMs to build playlists which is helping discoverability.. or more /rediscovering/ artists that I haven't listened to in a while
There's a section of rail line between Senneterre, QC and Cochrane, ON in north-central Canada constructed as part of a quixotic federal project a century ago to link the grain-growing praries with an Atlantic port. It was barely ever used and then abandoned in the 1990s. It's the very fringe of the interface where North American industrial civilization reached, and has since rolled back. It's amazing how completely nature has swallowed everything back up. The bridges still stand but they won't in another thirty years or so. Even the railbed constructed to high quality with packed stone dust has trees growing out of it again. I've explored some of the route and I was reminded of who were the great engineers here before humans - beavers completely transform landscapes. They've dammed every causeway along the route, which only further accelerates the erosion. They've flooded a couple rail stops and old logging villages I had hoped to check out. Before long you'll have to know exactly what to look for to even find the line.
It was such an excellent show. I recently rewatched it. I wish they'd make more, or a follow-up set in another city. Instead of all this formulaic and totally unrealistic NCIS and CSI crap.
P2P Matrix is a dialect of Matrix where the server runs inside the client itself - see arewep2pyet.com for details. In other words, there are no servers (other than optional store-and-forward relays). It's insanely cool - you can see a demo at https://www.youtube.com/watch?v=eUPJ9zFV5IE&t=2192s. It's also unfunded and on hiatus until someone provides some $ so we can work on it again.
Right now, normal Matrix is a client-server model: you can't send messages from a client without it talking to a server (and then to another server, and then to another client). MatrixRTC VoIP and Video calls in Matrix 2.0 also go via server (for now), in order to support multiple participants and firewall traversal.
Obviously, both messages and calls are end-to-end-encrypted (other than in public chatrooms), which makes it less important that they go via a server today.
There's a hard physical limit (the Rayleigh criterion) on the resolution of an optical system by how big the open end is. You won't get "super zoom" capabilities without a satellite the size of a stadium. https://en.wikipedia.org/wiki/KH-11_KENNEN#Resolution_and_gr...
You can provision a VHDX on your pre-existing NTFS volume (IIRC VHDX overhead is <=1% for Hyper-V, not sure if that's still the case and/or applies to DevDrive). But yes, I would say an additional drive is ideal. I did just that to put games on DevDrive.
One killer feature is OpenAI’s vector database. I was surprised you can throw gigabytes of documents at it and chatgpt can see it all. It’s hard to simulate that via context window.
That’s not necessarily a moat, but OpenAI is still shipping important features. I wonder how hard it is for Claude et al to replicate.
Tails is an immutable distribution of Linux that runs entirely out of RAM, persisting nothing to long term disks. Typically used in a LiveCD like manner.
Notably no mention of Wireguard, managing your firewalls/routers/network architecture, IDS's/Intrusion response plans, key hygiene, and focusing on getting end users prepped for the infosec environment; noting that an ineffective infosec engagement with end users completely undermines everything you're trying to work for. Trying to go all in on most of those tools is a recipe for disaster for any org that actually has something else to do other than jumping through endless security hoops.
Tools aren't the be all end all. Educated and invested users are.
Every time I hook my dev NUC up to my HDMI cable and plug in a keyboard, just to decrypt the ssd en get back to working after a reboot, I will now be thinking of this story and feel better about this little nuisance. (Yeah I know there are better ways, I could ssh into the boot env with systemd, I could just encrypt the home dir, I could somehow use the TPM (but that is still pita) etc, I'll look at that the next time I set up the a dev machine...)
I can't wait for this to become usable. I love VR but the content generation is just sooooo labour intensive. Help creating 3D models would help so much and be the #1 enabler for the metaverse IMO.
It’s barely mentioned aside from the title, but I just wanted to say that 80 Days is a really wonderful game that is well worth your time if you’re into text-based games.
It’s more of an interactive story than a puzzle game, with some light resource management elements. But the writing is wonderful and there are hundreds of possible paths and storylines to discover. Its replayability is very high, whether you’re trying to find the fastest route, seeking out the most remote locations or unlocking hidden subplots.
It really does well to invoke the spirit of adventure in travel, and it was a particular delight during the pandemic days when that wasn’t possible.
Plus they’ve open sourced the language and tools used to create the branching narrative!
I'm really starting to hate the sub-community in Linux that tries to constantly change it.
I don't want to learn a new network config alternative with every update (Ubuntu changed its net config tool again with 24.04). I don't want an immutable os. I don't want to learn to write new config files. I just want to do what I've been doing but with new packages. If there's a problem with something, just fix it. Don't throw out the whole thing.
I moved to FreeBSD and am happy for its reluctance to change. If there is any, it's usually offering something genuinely new to me as a feature and to boot I only need to learn about it if I need it.
Hardware support is much lower but it's worth it IMO. I had the same irritation with macOS. Every release breaking something essential that was part of my workflow and i didn't want to change. Eventually I did change but away from Apple.
Void Linux is, to a first approximation, "Arch without the BS". Because it ships a musl version, and because Lennart thinks anything but Linux/glibc is a niche corner case which can simply be ignored, Void does not use systemd but rather runit. (Indeed, it's the only distro I know of to officially switch away from systemd to something else.) Also, there are few, if any, distro-breaking flag days. I once blindly typed 'xbps-install -Syu' into a Raspberry Pi 2 that had fallen 2-3 years behind, and everything just chugged along and updated without a hitch.
Settings> about Firefox> tap on the fox logo a few times> debug menu enabled> now you see "install ad on from file" under advanced in the settings menu.
> Amiga was a startup that was I understand set to work around the lack of a product development pipeline in Commodore
Amiga Inc. was founded in 1982 by engineers leaving Atari, at a time when Atari was still all-in on the aging 2600, and did yet not have a replacement product in the pipeline. So you identified the right problem at the wrong company.
Amiga's initial goal was to create a chipset for a next-generation console. While they were working on that, they generated revenue by selling 2600 peripherals (like the Joyboard [1]), but eventually got funding from Atari and negotiated a contract to license their new architecture as the basis for future Atari products.
In '84, Jack Tramiel left Commodore and acquired Atari, which Warner had put up for sale following the crash of '83. Tramiel brought a bunch of Commodore engineers over to a newly reconstituted Atari, and they became the core of the ST team.
This severed Amiga's relationship with Atari, and simultaneously left Commodore without an engineering team to design their next-generation products. After a bunch of lawsuits and back-and-forth negotiations, Commodore managed to acquire Amiga, and the rest was history.
So it's pretty valid to say that the Amiga was designed by Atari engineers and the ST was designed by Commodore engineers.
If 2 tons of steel hit you at 40mph+, you will die. You can be dead wearing a helmet if you wish.
Trying to find a way out of that situation is futile, you're trying to fight the laws of physics. The solution is to not be there in the first place, not trying to add 5cm of padding on top of your head.
The way to do so, at policy level, is building a network of dedicated cycling paths physically separated from motor traffic and protected intersections where bike traffic is priviledged over motor vehicles.
But regardless of the state of infrastructure, recommending helmets to cyclists has overwhelmingly negative consequences. The minor safety benefits pale in comparison to the damage done by the reduced amount of bicycle trips caused by the friction introduced by needing a helmet. Cycling has such immense benefits that virtually any reduction in trips due to helmet advocacy will have devastating health outcomes. This isn't a matter of comparable numbers that can be discussed either, we're talking orders of magnitude here.
If the above is unconvincing, some research follows (quotes presented to be read in order):
[1]: "Cycling UK wants to keep helmets an optional choice. Forcing - or strongly encouraging - people to wear helmets deters people from cycling and undermines the public health benefits of cycling. This campaign seeks to educate policy makers and block misguided attempts at legislation."
[2]: "Even if helmets are 85% effective (and assuming q = 0.5 as above), the number of cyclists’ lives saved will still be outnumbered by deaths to non-cyclists if there is a reduction in cycle use of more than 2%"
[3]: "Enforced helmet laws and helmet promotion have consistently caused substantial reductions in cycle use (30-40% in Perth, Western Australia). Although they have also increased the proportion of the remaining cyclists who wear helmets, the safety of these cyclists has not improved relative to other road user groups (for example, in New Zealand).
The resulting loss of cycling’s health benefits alone (that is, before taking account of its environmental, economic and societal benefits) is very much greater than any possible injury prevention benefit."
[...]
"Evidence also suggests that even the voluntary promotion of helmet wearing may reduce cycle use."
[...]
"Even with very optimistic assumptions as to the efficacy of helmets, relatively minor reductions in cycling on account of a helmet law are sufficient to cancel out, in population average terms, all head injury health benefits."
[4]: "With 290 cyclist fatalities in 2022, cyclists were the largest group of road casualties. Of these, most were killed by collision with a vehicle (206 bicycle deaths)."
[5]: "Cycling levels in the Netherlands have substantial population-level health benefits: about 6500 deaths are prevented annually, and Dutch people have half-a-year-longer life expectancy. These large population-level health benefits translate into economic benefits of €19 billion per year, which represents more than 3% of the Dutch gross domestic product between 2010 and 2013.3.
The 6500 deaths that are prevented annually as a result of cycling becomes even more impressive when compared with the population health effects of other preventive measures. In an overview, Mackenbach et al.11 showed that the 22 new preventive interventions that have been introduced in the Netherlands between 1970 and 2010 (e.g., tobacco control, population-based screening for cancer, and road safety measures) altogether prevent about 16 000 deaths per year.
Still, our results are likely to be an underestimation of the true total health and economic benefits."
[6]: "Riding a bicycle to work every day reduces the risk of premature death by 41% (risk of dying from heart disease: -52%; risk of dying from cancer: -40%)."
[...]
"Regular cycling boosts physical fitness and compares to 1 to 2 weekly gym sessions."
[...]
"Bicycle use not only improves physical health, but also has a positive impact on mental health and subjective well-being."
This article really shouldn't be allowed to be posted to Hacker News anymore. Anything with this many errors, and is essentially a mickey mouse investigation, isn't worth discussing again.
There is a vendor for this very thing in relation to business and government position called “zoominfo”