Hacker Newsnew | past | comments | ask | show | jobs | submit | vetrom's commentslogin

The illegal side of hosting, sharing, and mirroring technology, as it were, is much more free to chase technical excellence at all costs.

There are lessons to be learned in that. For example, for that population, bandwidth efficiency and information leakage control invite solutions that are suboptimal for an organization that would build market share on licensing deals and growth maximization.

Without an overriding commercial growth directive you also align development incentives differently.


The only trims I see online at gmc dot com are RWD. Would you elucidate on this 4x4 option please?

There was some noise about an "Outland Edition" coming out in 2026 but all I can find now is AI slop, so maybe that's not real or maybe that's not done yet.

It could also be just a further deal with Quigley. You can already order from a dealer with the 4x4 option, and your vehicle will go factory->Quigley->dealer and be sold to you as "new", with good warranties.


If you can read a modicum of German wasn't this sort of thing on the timetables in a standard way pretty much forever?


Launchpad does this for everything, as does sbuild/buildd in debian land. They generally make it work by both: running the build system in a neutered VM (network access generally not permitted during builds, or limited to only a debian/ubuntu/PPA package mirror), and going to some degree of invasive process/patching to make build systems work without just-in-time network access.

SUSE and Fedora both do something similar I believe, but I'm not really familiar with the implementation details of those two systems.


I’m only familiar with the Fedora system. The build is hermetic, but the source input come from fedpkg new-sources, which runs on the client used by the package developer.


A medium range trail/offgrid camera is perfect for this application. All the other solutions in the space are sdcard only, or dependent on some variant of LTE/5G.


I don't think most people really understand the compute complexity required for LTE and 5G terminals. It's telling that pretty much every discrete-ish full-speed LTE or 5G modem I've lain eyes upon is actually an embedded SBC running its own OS, with attendant power requirements.


The companies do that because by far the largest market for LTE/5G modems is smartphones.

They could make a more cut-down modem chip, but why would they? They already make hundreds of millions on smartphone SoCs. Just rebadge that silicon as modem ICs, no one cares that an LTE stick runs full Android.


Not necessarily -- with tricks like https://github.com/Manav1011/webrtc-vpn you could import/exfiltrate data easily.


We already have the UK intimating they can exercise parliamentary supremacy over American citizens, so we already have this today. (Reference: https://prestonbyrne.com/2025/10/16/the-ofcom-files/)

Without limitations on authority and control, I worry more that the world will devolve into a multilateral legal hellscape, even moreso than exists today. Given how much is dependent on software, you are going to have the governments of pretty much any country with multinational exposure trying this in the next 10 years if recent UK and EU developments are any indicator.


The early MacOS era as well as pretty much the entire classic Mac OS era was infamous for being a more-or-less do it yourself environment for adding bits the OS didn't have or did sub-optimally for given use cases.

The wisdom of such a freewheeling ecosystem in today's era is maybe debatable, but given how user-hostile the mainline OS and software vendors can be, I say there's still plenty of room for that ecosystem and it should be preserved.


I guess I do remember adding drivers here and there for scanners and printers back in the day


The old OS was awesome in that way. As extensions loaded the would appear in sequence at the bottom of the screen when a driver failed the boot would lock-up and one could reboot with extensions off change the boot order or remove the driver from the system folder. Very easy to mess with.


You'd have to burn more die space for the duplicate but different ram controller logic and cache trees, I bet.

If the internal bus architecture is anything similar to QPI, getting the 'different' parts to communicate reliably is probably also a pain.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: