TIL getting an elevator tech to just come out to look at your building's elevator is about $1600. If it's an easy fix, that's all you need to pay. If it's not, it goes up significantly....
(a) cars have forward-facing cameras/computer vision for lane tracking
(b) infotainment systems have always-on cellular internet connections
(c) billboard impression counts can be tied to the vehicle
IIRC infotainment systems are already showing ads in some form. And location + driving performance is being captured + monetized and shared with insurance companies.
Unless this results in an EV car that I can rent for less than $100/mo, this really needs to be stopped.
tinc (https://tinc-vpn.org/), a OSS mesh vpn that has existed for a long, long time, is another great solution with no central server. You can manage the public key distribution yourself, or just keep them checked into a git repo (my preferred solution), and it's been solid for years.
Even if it only had RX-only RF capabilities, that means that is a vector for an inbound wireless attack. At the very least, the kind of places that restrict wireless devices probably do not want any pictures or other artifacts to exist tagged with precise location metadata.
I think that way back when, there were SO MANY variants of the theme because the core parts of the software were pretty easy to get going. A lot of developers, new to the scene, would make a discussion forum. The devil's in the details, though, making sure things are secure, scalable, moderator tools are on point, etc.
Nowadays, a LLM could probably generate a new, functional forum software system in an hour, since their training have probably ingested a ton of variants of the same software.
I got my RTL-SDR to see what I could listen to, and by the time I tuned in, nearly all the short wave stations I could tune to were just broadcasting evangelical religious stuff, or other crazy conspiracy stuff. It's remarkable that these powerful stations spend most of their broadcast day transmitting that content.
The problem arises when there are contradictory truths, and defenders of one or both sides refuse to dig deeper to both self-reflect on what they believe to be true, and perhaps come to a deeper more correct understanding.
That's kinda what happens with DNA -- a random mutation will make the resulting organism 'incompatible with life' -- or it will create a change that gives a huge advantage for survival.
This is the leg of the cycle when we go back to mainframes & centralized computing? With all the datacenter build out; why wouldn't you want your services adjacent to the LLM processing centers?
I'd wager that in the next 96 hours, with a LLM, someone could create a translator that would 'pack' a nginx or caddy configuration file into the relevant code that zeroserve could use. Or even more simply, just pickup all the Ingress manifests in a kubernetes cluster and rebuild the pack. The point being, the interface between the tool and the configuration is just another API, system operators are already describing the state of the system at higher level constructs, and the specific bytes that make up the configuration are an artifact of that.
Don't want to go too far off topic; but the interface in question was a uniquely named internal network interface for a Hyper-V VM. Considering it's MS all the way down, I'd expect them to get it right.
Also, thank you windows for not having consistent interface ids after reboot. I had to rewrite a configuration file every startup with powershell in order to tackle this case.
MS got involved, and they are web servers that you send SOAP requests to, (to support MFC devices, of course) and the Windows stack uses UPNP to discover them, and register them by their UPNP names, and they tend to be sticky to their temporary IPv6 addresses, and often fail to rediscover when their temporary IPv6 address changes. Oh and the windows UI doesn't give you any ability to edit the 'port', failing instead with some incomprehensible "operation not supported" if you dare click the 'edit' on the port.
These devices have the wifi/ethernet bridge functionality being discussed, (as well as a bunch of other stuff) and are OpenWRT based. Built in openvpn/wireguard as well. We bought a bunch for our team way back when (IIRC they were < $20 USD then) Gl.iNet has other similar more powerful devices as your use case may need.
The killer app was conceived as early as the 1980s: an agent running on your computer, organizing your files, your schedule, your messages, your bills, bank accounts, etc. All the parts of your life that were routine drudgery should be able to be offloaded to a smart agent, based on your preference, to bring you the information you needed with natural language queries, contextualized to what you were doing at the time, when you need it.
What's being delivered now is, an agent running on someone else's computer, copying your data to someone else's database, with zero responsibility, or mandate to protect that data and not share with with anyone else (in fact, they almost always promise to share it with their thousand partners), offering suggestions and preferences based on someone else's so-called recommendations, influenced by paying the agent's operators, and increasing pressure to make using someone else's computers + agents the only way to interact with other people and systems.
There is no doubt that LLM's can do amazing things, but the current environment seems to make it nearly impossible to do anything with them that doesn't let someone else inspect, influence, and even restrict everything you are doing with with these systems.