> Basically, I am never confident I am editing OSM correctly.
This is the case for the majority of users. The rules are complex and not always obvious or clearly defined. The world is complex, unfortunately, and so is describing it accurately.
One of OSM killer features for me is finding drinking water along the route when I'm hiking/biking/exploring. Unfortunately, there isn't a single, consistent label used for all sources of drinking water. So I have to check amenity=drinking_water, man_made=water_tap, amenity=fountain, one after the other.
I think StreetComplete has missions to add the label drinking_water=yes to all of those, so the situation might improve in the future.
> It sucks that Google is probably using OSM data to check what they are missing and adding it to their maps
No way they are doing this deliberately globally. My city has a lot of pedestrian stairs interconnecting roads, and not a single one is on GMaps. If you navigate on foot, it will send you on walks 2x-3x longer than necessary.
OSMand and CoMaps reliably find the shortest way. And can tell you the pavement type, number of steps, stroller ramp and hand rail situation of every single one of those stairs.
Google has a really hard time adding roads without frequent car traffic, I think.
The thing lacking even more is a good search engine. Doesn't matter how complete the database is when search keeps missing text appearing verbatim in a label.
You can edit existing trails, but directly adding new ones is not intended. What you can do is create a GPS track, and then upload it with a note describing the problem.
I use the app Vesspucci for actual editing, it works well (but larger changes to OSM is a "full PC" kind of task). Notes from StreetComplete (from all users) show up on a TODO list in the app, so the more advanced users can decided on whether they want to create a node on the map from the note.
> it was originally alternate firmware for the Linksys WRT54G router from 25 years ago
There's a couple of fun examples like that. xda-developers is named after the O2 xda, a smartphone from 25 years ago that not many people ended up developing software for.
> we'll ditch phones altogether in 10 years when smart glasses will replace them instead.
Billions are spend right now to make sure the glasses also run Android or iOS. So far, Google, Samsung, Magic Leap, RealWear and Vuzix are working with/on Android XR, and obliviously Apple is working on AR/VR iOS.
Meta and a couple of smaller startups are doing something in-house, but I don't give them much chances to get an ecosystem going.
There's much to criticize about the dev, but there's really no way to make it significantly easier. Most robovac companies just don't want you to flash the firmware.
The dev opposes selling the connector PCBs, but people have always ignored that and sold them online. They're not hard to find, but having the PCB is really only the first step.
Reminds me of a fix I wrote a decade ago. My Laptop would sometimes start emitting a high frequency whine when on battery. I figured out it only happened when the CPU went into performance states lower than P2 for power saving.
So I wrote a bash script that auto-started on battery mode and then calculated a hash every few seconds. Boom, whine solved. Terrible fix, but I never measured how much battery it cost me, so it was... fine.
Not really. Can't really map a touchpad as an analog stick. Can't map a gyro as a joystick. Can't take XBox rumble and map it to the Steam Controllers haptic feedback.
Can you hack it together in theory, get something working but making sacrifices left and right? Sure. But why would Valve want to do that? Use experience would be incredibly bad.
But give it time. There will be a standalone driver for Windows eventually, either from Valve or from the community.
> Many hardware platforms that have TPM, have it connected via a low-bandwidth LPC bus which would have nowhere near enough bandwidth for demand decryption/encryption of memory pages.
Ah, of course. I was more thinking along the lines of "CPU loads the key for decrypting RAM directly from the TMP into registers, and reloads it from there after waking from suspend or after a task switch has refilled those registers".
This might make sense once SteamBox is a large percentage of Linux Desktop installs.
Right now, it would be insanity. Just the situation with running SteamOS on hardware with NVIDIA cards would be a showstopper. And a whole lot of consumer PCs ship with NVIDIA chips...
Very funny idea. That basically means a carbureted gas engine, or a direct injection diesel with a mechanical governor and mechanically timed injection pumps - can't run a direct injection gas engine without a digital engine control unit, because the injection timings are much to precise to do mechanically.
So, basically '60s Formula 1. Might be fun to watch. We'd certainly see some crazy engine designs and a lot of re-fueling pit stops...
There's an efficiency sweet spot where hardware that people have anyway gets a higher percentage of load.
MacBooks have a lot of memory and a lot of FLOPs. They mostly sit unused all day. Yes, the excess energy use will be higher than a GPU in a datacenter doing the same work, but you have to generate an absurd amount of tokens before the dollar-efficiency catches up with the MacBook.
Because there's better alternatives same places. Norway has legendary well-suited topography for hydro power (>90% of electricity), and it's reliably windy (>8% of electricity). It's also so far north that the sun doesn't shine very much for half the year, and it's notoriously cloudy.
So yes, it will probably never make much sense to build a lot of solar panels in Norway. Same for Greenland, Iceland (substitute geothermal), and probably some parts of Canada, Alaska and Southern Argentina.
But also, yes, there's almost nobody living in those places. They're not terribly relevant in the grand scheme of things. Probably significantly less than 50M people in total.
Of course. My agentic coding containers can only access the internet through a proxy, and I use whitelists to limit from where they can send/receive data. It's annoying in the beginning as the whitelist grows, but in the end really useful information for the agent usually comes from a very limited amount of domains.
> The defining element of a LAN party, however, is the social factor. Playing a game with others in the same physical space, sometimes huddled side-by-side on the same large table, is an intimate affair. Cries of joy and frustration fill the air.
That's really the major thing that made LAN parties so special. Being in the same room is so, so different than online gaming together and hanging out on discord.
It also forces you to compromise when choosing games and maps, because you're stuck together for the night. You can't just sit out a game/map if you don't like it, you can't just hop on a different voice channel and play another game with other people. You end up playing games you're not as familiar with (and not as dominant in), so your friends will play your game with you later. This brings you into situations, where the person next to you frantically gives you the crash course in rush build orders while building their own base, making the payoff so much better when it actually works out.
The Prius (and all subsequent Synergy Drive cars) were widely known - from the very beginning - to be extremely fuel efficient ICE cars. As time went on, they universally became known to be both fuel efficient and also absolutely bomb proof.
Both of those things surprised basically no-one, since the direct successors (Camry, Corolla, 4Runner, Tacoma, Hilux) were also already known for being fuel efficient and reliable cars.
The only people who really care about why and how exactly they got so fuel efficient and reliable are engineering nerds - and many of those already knew, the planetary gear set + atkinson cycle engine are a pretty legendary design. They hit it out of the park on the first try, after all.
And as this video shows, explaining the why and how to non-engineering nerds takes a good part of an hour anyway. How do you do marketing with that?
This is the case for the majority of users. The rules are complex and not always obvious or clearly defined. The world is complex, unfortunately, and so is describing it accurately.
One of OSM killer features for me is finding drinking water along the route when I'm hiking/biking/exploring. Unfortunately, there isn't a single, consistent label used for all sources of drinking water. So I have to check amenity=drinking_water, man_made=water_tap, amenity=fountain, one after the other.
I think StreetComplete has missions to add the label drinking_water=yes to all of those, so the situation might improve in the future.