"This long-term investment that began on the mobile-first foundations of the Android Open Source Project has produced a full mixed reality operating system used by millions of people."
Hopefully they stick to a proper license model with AOSP as a cornerstone.
Still lots of dark areas [1] and lots of unnecessary allocated space to original adopters. I wonder if the Governments will ever exercise an Eminent Domain on IPv4 one day?
There is no government control on IP address space. The only actual binding is to the 5 RIRs*, and if you want to see how eminent domain would fare there... Take a look at the current AfriNIC situation :(
Projects like this warm my heart. There is a level of detail to appreciate on the capture of 2600, the POTS regional numbers ending in 2600, and BBS xfers.
Kudos to the owner, founder, and maintainers. You embody the spirit of 2600!
When this occurs does the company count that as revenue and record the discount or do you adjust the accounting to reconcile?
I've seen in the thread that bobfunk (netlify CEO) and raiyu (cofounder at digital ocean) say the bill forgiveness is the right strategy. It got me curious on the above question though.
Since the article discusses interception and rewriting prompts, I find this entertaining. If your statement is true, hopefully others will enjoy the irony as I did.
Lots of cars throughout the last two decades have suffered from latent issues as a result of new drive by wire implementations. It was very frustrating in some models from early 2000s where the electronic throttle modules where severely delayed. You'd push the pedal to the floor and get no immediate feedback. Terrifying when you're trying to get out of the way.
I've had issues with throttle-by-wire but not so much latency as much as the traction control nannies telling me how to drive. First time I had this happen in a '14 Tundra it scared the crap out of me, because it works by cutting throttle to the drive tires if it detects loss of traction. Then it seems like the vehicle is not responding to throttle inputs until the computer decides traction has been regained.
I get that it's "safer" for your typical driving conditions, but I'd imagine trying to get out of the way in a hurry it could be a problem... Knowing that's the case now, I kind of expect it, so it's changed my driving habits slightly and has made me plan ahead more than normal.
But I can't imagine how actual input latency would feel after that experience.
Keep in mind 10 character spaces should be represented by the selection pool size (A-Z = 26, a-z = 26, 0-9 = 10, so 26+26+10=62). You now can say 62^10 = total possible guesses available. Certainly you can start to make intelligent decisions on guessing properties and priorities to reduce your time.
Also I didn't discuss entropy here in order to represent it more basically for the parent comment.
Hopefully they stick to a proper license model with AOSP as a cornerstone.