Change that to definitely. I added a brand-new road on OSM and a week later it was on google maps.
HN user
GreyStache
I never bought the benevolent technical angle for not supporting flash. I'm pretty sure Apple strategists knew the value of the gate-kept platform, the app-store revenue stream.
The pivotal point was that flash would break this stronghold by allowing rich applications that are reasonably self-publishable. (Excuse me while I go rinse that sentence out of my mouth)
Broadly speaking: IP Transit is the relaying of bandwidth towards the rest of the world. Dark fiber is a fiber optic connection where you shine light in and get it out on the other end, no other party on the physical fiber strand.
(Both are generatalizations)
Something akin to ssh agent-forwarding ("oauth-forwarding"?) is really needed. And it needs to be integrated similarly well like support for jumphosts.
Haven't seen anything like this, I'll try to bring this up with the openssh folks.
Apart from the business model and mobility benefits, those scooters are just plain dangerous. They are absolutely fun to drive, and easy to drive swiftly.
But your body mass is so high off the ground on a very small base, with VERY small wheels. Riding on a bird I hit a small pothole (it looked like a very slight puddle) and catapulted off onto the sidewalk. The physics are undeniable.
Personally I'd like to see the same model with bicycles, even if they are electric.
And for the love of public space: force all competing brands to share vehicles, drop-off zones and handlers.
One more nit-pick: the screen is polarised the wrong way. You can't see anything when wearing polarised sunglasses (those are always oriented so they filter out the polarisation of water puddles).
One of the things I really considered is that if nobody gives these "independent" Linux-focussed vendors a chance, then Linux-on-the-desktop will forever remain a non-factory option and a second-class citizen in support manners.
They use hardware from clevo-computers.com, but they select certain parts. The uefi is not the stock, so I'm assuming they do some tuning.
TuxedoOS was very limiting to me; a vanilla Debian works very well.
I'm typing this on my 1 year old Tuxedo InfinityBook (S 14 Gen6, not the Pro).
Now I'm definitely spoiled by the Lenovo X1 series, but I'm not happy.
The hardware is a rebrand from clevo-computer.com - some minor spare parts can be had from there.
The system is VERY prone to overheating, the fan is noisy. They claim the fan noise is "not annoying" which is only true in the short term. I have opened up the bottom shell and I believe the fan recirculates a bit of hot air back into the case. This really is a limiting factor for me, I'm considering an alternate cooling solution.
The case had a minor chip in it within the first ten minutes out of the box (I don't know how that happened, I think it just pinged off by itself!). The palm-rests are starting to show dark spots. My barrel jack power connector is loose, I have to hold it in with a rubber band. (I still have the usb-c port) All the rubber feet at the bottom fell off quite some time ago, superglued them back on. The (super compact) PSU started to whine, that was replaced under warranty - but is stated to be a consumable item!
Out of the box they have their own OS, which is a somewhat modified Ubuntu. My main driver is Debian and almost everything worked right out of the box - sometimes I got back (usb-boot) to their distro to validate things (see: support).
The firmware is more than okay for me; I managed to cross-compile their "control centre" to allow me to change performance/fan characteristics on the fly. The uefi updates work fine (boot from a stick), but they are undocumented.
The support is ... rigid. The first response is to boot their own distro and kernel. This is fair for a mass market product I guess, but I somehow hoped that specific questions would find their way proper Linux Gurus (tm).
There is a very cute penguin instead of a windows logo on the keyboard :-)
Regarding the termination: our local fiber provider handles the termination with some optical precision connector (forgot the name). Both to the sunken-in-sidewalk multiplexer and in the home to the optical termination point (both gpon). So for mass deployments fiber connections do not require fibre welds are not required.
I have to see it play out in practice and I'm not a fan of the idea that one telco controls controls (ie stifles competition) in a gpon scenario. The conduit has recently been placed in our street, so "soon"...
The gallery in the article links to this drone footage I hadn't seen before: https://www.youtube.com/watch?v=BrGsCD2nVrk